Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem






































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.