[A17.1527] Pawn/animal pathing breaks

Started by aaraggornn, May 03, 2017, 07:34:19 PM

Previous topic - Next topic

aaraggornn

Started a new colony for A17. The game runs normally for a few minutes then the pathing breaks and most colonists/visitors/animals stop moving. Saving then reloading fixes it for a few minutes till it breaks again (same with saving/quitting/loading).

I let the game run for a while and two colonists died of starvation but the 3rd one, the dog and a trader were stuck and their food stat did not decrease.

A raid appeared while this was happening and the raider moved around normally for a while then froze after a time, same with some animals.

I could perform all actions such as placing blueprints etc. and incidents occurred but the game eventually was running slow at around 13 FPS (normally 60). Right-clicking something for a colonist to do just shows "(no path)" for some actions but the correct action for others (such as "Consume packaged survival meal")

Attached are saves/logs

[attachment deleted by admin due to age]

ison


ison

It seems that the path grid and region grid are out of sync.

Can you still reproduce the issue? After how many in-game days does it usually happen after loading the attached savefiles? I let it run for 3 days and there were no errors.

NeoVeet

i got the same thing. debug log keep typing: http://imgur.com/VdjidNd and FPS go down to 3.

ReZpawner

Same thing here. Happens almost every time I try to build a wall. Completely unplayable at this point.

ison

@NeoVeet Thanks, but I think that your bug is different and it's already fixed. Your bug was caused by RegionAndRoomUpdater.

dolphinigle

I think they're the same issue. I'm able to repro the colonist stop moving bug (attached). In particular, when the game is in development mode, the FPS suffer. Otherwise the FPS is OK.

Save game:
https://mega.nz/#!BnYxgI7A!ovutn7qSm_Cb7_9iIA8SxAMM8JLwPTUjJ1HPdyyEJOw
(the 7z file size is too big for attachment)

1) Load the save game
2) Run in max speed. Wait until 17H.

Hope this helps.

[attachment deleted by admin due to age]

yoyo

I am getting the same issue and have reproduced it twice. I don't know about the others but both times I paused when I start the game to get a lay of the land, then queue up buildings. After about 2 hours in game the pawns freeze wont move on their own or when drafted. "no path"

axeladalidez

I "fixed" it by making only one of my colonists as a builder, looks like it has a problem when they build roof or walls when they are too near.

GabMSouza

Same thing happening in my save. When the first release of a17 was installed, there was no such thing. After that last update it begun (the problem). It always work to reload the save, but sometimes it takes little time to bug on me again.
Appart from that, I love the new version!

asolare

#10
I'm having the same problem with pawns today. Did not have this issue yesterday but now my pawns are getting stuck/not moving.

I've reproduced it a couple times and it seems to happen when constructing walls/doors and maybe roofs. All I did was start a new game, start hauling stuff to stockpiles, and then began constructing a room. While the room is being constructed the pawns become stuck even if they are not near the room. Also tried a different order of tasks and the pawns consistently become stuck once the room is finished (but before a roof is placed).

I turned on the environmental display and I'm finding a strange area of no values around the pawn that initially becomes stuck.

edit: appears to be fixed with a17.1528

aaraggornn

@ison I can't replicate it in the current version (a17.1528) after running for a few in-game days. In 1527 it would happen after only a couple in-game hours.
In 1527 I had replicated it with a new game in a different hex (same map gen settings/seed) as well but don't have saves/logs from that. Is there a way for me to downgrade to 1527 to check again if you need me to?

ison

There was a bug with very similar effects in 0.17.1527, which is already fixed in 0.17.1528. It was caused by RegionAndRoomUpdater. However the logfile attached to the first post indicates that RegionAndRoomUpdater didn't cause any errors, which is why I think it's a different bug.

Okay, I'm going to lock this thread. I think it's better to just see if it happens again in 0.17.1528. If it does then please report it. Thanks.