error

[Соединенные Штат]

Hello, I keep getting this error every few seconds.

Simulation error: Array index is out of range.
at TerrainManager.GetSurfaceCell (Int32 x, Int32 z) [0x00000] in <filename unknown>:0
at TerrainManager.SampleDetailSurface (Single x, Single z) [0x00000] in <filename unknown>:0
at TerrainManager.SampleDetailSurface (Vector3 worldPos) [0x00000] in <filename unknown>:0
at WildlifeAI.IsFreePosition (Vector3 position) [0x00000] in <filename unknown>:0
at WildlifeAI.SimulationStep (UInt16 instanceID, .CitizenInstance& citizenData, .Frame& frameData, Boolean lodPhysics) [0x00000] in <filename unknown>:0
at CitizenAI.SimulationStep (UInt16 instanceID, .CitizenInstance& data, Vector3 physicsLodRefPos) [0x00000] in <filename unknown>:0
at WildlifeAI.SimulationStep (UInt16 instanceID, .CitizenInstance& data, Vector3 physicsLodRefPos) [0x00000] in <filename unknown>:0
at CitizenManager.SimulationStepImpl (Int32 subStep) [0x00000] in <filename unknown>:0
at SimulationManagerBase`2[Manager,Properties].SimulationStep (Int32 subStep) [0x00000] in <filename unknown>:0
at CitizenManager.ISimulationManager.SimulationStep (Int32 subStep) [0x00000] in <filename unknown>:0
at SimulationManager.SimulationStep () [0x00000] in <filename unknown>:0
at SimulationManager.SimulationThread () [0x00000] in <filename unknown>:0 [Core]

Thank you!

[CyberVibes]

Seems to be really common issue this week after the Xmas patch, it's normally caused by trying to 2nd load a game after playing another one first but it's more commonly popping up in game at the moment, it has to be related to a mod that's been.. or is needing an update.

Go to content manager / mods and click the last modified tab and look to see what's been recently updated, then one by one disable mods and test, it can be a bit pain staking having to quit to desktop after trying these one by one or in small batches but maybe quicker in the long run than waiting for replies from people who are having a similar experience.

[Соединенные Штат]

Originally posted by CyberVibes:

Seems to be really common issue this week after the Xmas patch, it's normally caused by trying to 2nd load a game after playing another one first but it's more commonly popping up in game at the moment, it has to be related to a mod that's been.. or is needing an update.

Go to content manager / mods and click the last modified tab and look to see what's been recently updated, then one by one disable mods and test, it can be a bit pain staking having to quit to desktop after trying these one by one or in small batches but maybe quicker in the long run than waiting for replies from people who are having a similar experience.

I disabled Automatic Bulldoze and it worked, thank you!

[CyberVibes]

Glad you found the culprit :)