Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The way to get the .WAV to work is to convert a different file with Audacity. If you don't have it you can get it here --> https://www.audacityteam.org/
Once you've uploaded your audio, export it as the following:
WAV (Microsoft) signed 16-bit PCM
Files exported like that (at least from my testing) will work in Storm Chasers.
As for the audio themselves, this part is a bit extra. The siren in Wakota County should be named exactly as it is in the guide (TornadoSiren.wav). However the EAS alarms work a little differently.
Each EAS has two versions. One Long and one Short (These can be toggled in the settings menu). for your custom EAS to work you have to name it after one of the versions.
As an example, let's say I want to make a custom Long EAS alert for Byrun County. I would name it like this:
Long EAS Warning - Byrun County.wav
Hope this clears things up for anyone running into issues.