Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Trung giản thể)
繁體中文 (Trung phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bulgaria)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraina)
Báo cáo lỗi dịch thuật






































Maybe i'm doing something wrong, but couln't find it :(
There is a conflict with a scenario introduced in AOBA's mods. I believe the scenario is introduced in Dead Man's Switch, but it depends on prefabs from the Fortified Features Framework.
When playing the 'Last Command' scenario, initiating the GravJumper quest causes a hard crash, a partially spawned 21x21 map layer, cascading errors and instability. Under the hood, when the GravJumper quest spawns a temp map, the AOBA scenario tries to spawn the prefab on it and runs out of space.
Fortified.ScenPart_GeneratePrefab:PostMapGenerate (Verse.Map)
My workaround was to add the 'Scenario Amender' mod and then remove the prefab from the scenario before spawning the GravJumper quest.
I don't think it a bug in this mod (although if you want the details to write better handling for other mod events, lmk and I'll submit the logs and analysis I've done over the last three days). I'm reporting it to AOBA. Just sharing here for vis.