安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









OK. Assuming device health is set on mission load then I'd set-up a test save right before leaving the Avenger and then use the binary search method. Helped me work out what was causing the Hunter (and only the Hunter) not to spawn, weirdly that was Nice Mission Debriefing. And that was fixed.
Binary search is talked about here: https://old.reddit.com/r/xcom2mods/wiki/mod_troubleshooting
You're not launching with the -regenerateinis argument are you?
Re-read the Description and follow the problem solving link
That was one of the few things that bugged me in WotC:
"protect the device" only to have a Sectopod and Gatekeeper spawn right beside it to pummel it from the start of the mission.