安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
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.