Butiksside
RimWorld
Alt Diskussioner Skærmbilleder Illustrationer Broadcasts Videoer Værksted Nyheder Guider Anmeldelser

RimWorld

Butiksside
RimWorld >  Værksted > BlackMarket420s værksted > The Army Of Fetid Corpses > Diskussioner
The Army Of Fetid Corpses
Beskrivelse Diskussioner17 Kommentarer620 Ændringsbemærkninger
Malhavoc 9. okt. 2023 kl. 18:13
Edge of Map Bug?
Got a monster of a bug when running this and I cannot figure out why. As soon as one of my Pawns got within 50 tiles of the edge of the map, they began vibrating violently in place and were unable to move. Reloading or resetting the game didn't help. This bug was repeatable. Every pawn I sent to the edge would freeze and begin vibin'. Since this was the only new mod I had installed recently, I pulled it out and the error stopped happening.

I have no idea if this is some sort of horrific mod conflicts or what. The errors that kept popping every tick was:

Soyuz caught this error. Please don't report this to the RocketMan team unless you're certain RocketMan caused this error. with error System.IndexOutOfRangeException: Index was outside the bounds of the array.
at (wrapper dynamic-method) Verse.AI.Pawn_PathFollower.Verse.AI.Pawn_PathFollower.PatherTick_Patch3(Verse.AI.Pawn_PathFollower)
at (wrapper dynamic-method) Verse.Pawn.Verse.Pawn.Tick_Patch3(Verse.Pawn)
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

Exception ticking Andrea (at (145, 0, 226)): System.IndexOutOfRangeException: Index was outside the bounds of the array.
at (wrapper dynamic-method) Verse.Pawn.Verse.Pawn.Tick_Patch3(Verse.Pawn)
at Verse.TickList.Tick () [0x0015c] in <95de19971c5d40878d8742747904cdcd>:0
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)
< >
Viser 1-3 af 3 kommentarer
BlackMarket420  [udvikler] 10. okt. 2023 kl. 12:03 
Hm, I guess it is a mod conflict since mine's running completely fine, how about disabling mods that messes AI path finding, if it doesn't work, please send the full log error here, I'll try my best to fix it
#1
Malhavoc 10. okt. 2023 kl. 13:22 
Oprindeligt skrevet af BlackMarket420:
Hm, I guess it is a mod conflict since mine's running completely fine, how about disabling mods that messes AI path finding, if it doesn't work, please send the full log error here, I'll try my best to fix it
I am now no longer sure if it has anything to do with pathfinding or not. I reinstalled the mod and reloaded an earlier save where the bug happened and I am not getting it now. I have cleared the log and have begun playing around on that save file to see if anything crops up. If that is clear for a few hours, then I'll see if anything happens when adding the mod midgame to another save.
#2
Malhavoc 10. okt. 2023 kl. 20:39 
Okay, I think I have things figured out, and I believe this is a case of a false positive. I am 90% certain that it is another mod that was causing a failure in the pathing code due to the xenotype I was running.

The issue was repeatable, because each pawn was the same xenotype and all trying to path to the same area and immediately hitting the error when the pathing reached that point. I had been using the xenotype for over a three weeks now, with no issues, so it wasn't initially a suspect.

When I decided to yank my latest installed mod (this one) from the save to begin diagnosing things, it reset things and the bug immediately vanished. Which is why I initially thought this mod was the cause.

Anyway, tl;dr, this mod isn't causing pathing shenanigans. It is in fact a very good mod for the season of spooks and I will be playing the absolute crap out of it in the coming days.
#3
< >
Viser 1-3 af 3 kommentarer
Per side: 1530 50