poor pawns prove perplexedly passive - perambulation paucity

[pawn_of_destiny]

All my pawns have entered a permanent state of "standing" perfectly still, and will not undertake any autonomous activities. Only drafting them convinces them to do anything at all. Strangely, the problem manifests in both current and saved files -- even saved files which used to work just fine, which is very puzzling -- but anyway, going back in time to older saves does not fix the problem. Looking through previous forum posts, I found mention that an XML tag "reservations" with a null entry might be at fault, but I found no such tags in my latest game file. Below is copied the meta tag from that same game file. Environment is Steam on Mac. I am unable to attach an example save file to this post because the file is 8 MB and the post limit is 600 KB. Anyone have any thoughts on how to release the pawns from their catatonic calamity?

   <meta>
      <gameVersion>0.14.1249 rev944</gameVersion>
      <modIds>
         <li>Core</li>
         <li>715565262</li>
         <li>705924057</li>
         <li>706426033</li>
         <li>722085442</li>
         <li>717632155</li>
         <li>691822594</li>
         <li>722087475</li>
         <li>725576127</li>
         <li>725623521</li>
         <li>725747149</li>
         <li>710511138</li>
      </modIds>
      <modNames>
         <li>Core</li>
         <li>Colony Manager</li>
         <li>Xeva's Rimhair</li>
         <li>Vegetable Garden </li>
         <li>ED-Embrasures</li>
         <li>PowerSwitch</li>
         <li>Animal Hide Working v2.10</li>
         <li>ED-Moat</li>
         <li>Glitter Tech</li>
         <li>[T] MoreFloors</li>
         <li>Tilled Soil</li>
         <li>Soylent green</li>
      </modNames>
   </meta>

[milon]

Awesome attempt at alliteration, pawn_of_destiny. 

And you can try 7-Zip to see if it can compress it small enough to attach you log - it's just plain text and you usually get really good ratios, especially with 7z @ max compression.  Failing that, upload it to google drive / dropbox / one drive / etc etc...

Pawn paucity ("NPC's all stand still!" etc) is a known bug, which I *thought* was solved.  Can you post your build number?

[pawn_of_destiny]

Thanks for your help! The zipfile is attached. I didn't locate a build number, per se, but the opening screen states "Version 0.14.1249 compiled Jul 29 2016". If the standing-pawn problem is new (or re-introduced) to this recent build, that might explain why the earlier saved-game files, which worked fine a few days ago, are also manifesting the issue.

[attachment deleted by admin - too old]

[milon]

That's the most recent one.  The 0.14 indicates Alpha 14.  The build number is next (1249).

Whoever has a chance first: please test the save with the same mod profile and report if you experience the same issue.

[pawn_of_destiny]

Any updates? Thanks for your help.

[milon]

I haven't had a chance to try it out with your mod profile, but I see that you're running Vegetable Garden. I think there was a bug in it that recently got corrected. Check that and see if there's any updates.  Then make sure all mods are A14. The other thing you can do is post your log file (info in sig).

[pawn_of_destiny]

"I see that you're running Vegetable Garden" => The installed version appears to be v4.0 ~0.14.124.

"make sure all mods are A14" => This appears to be the case.

"The other thing you can do is post your log file (info in sig)." => I was unable to discover the location of the RimWorld log file from the instructions in the sig. I am using Steam on Mac, and as far as I can tell, RimWorld log files are not in the same directory tree as the RimWorld save files or the Steam log files. Running the game in developer mode with verbose logging enabled, I see two types of error messages repeat in an infinite loop, and they are attached to this post as jpg files.

Any advice to fixing the bug(s) and making the game runnable again is much appreciated.



[attachment deleted by admin - too old]

[milon]

Thanks for the screenshots.  It's a little helpful, but the log file is best.

And sorry about having the wrong location for the log file - I was just guessing based on how Steam seemed to operate on Linux & Mac. 

What you're looking for is a file called Player.log and it should be in a RimWorld related folder, either buried in Steam's folder or else in a user files folder.  Sorry I can't be more helpful, but doing a file search should turn it up.  If not, you can force the log file to write to a specific location according to this:
https://ludeon.com/forums/index.php?topic=21565.msg235378#msg235378  (NOTE: Directions are for Non-Steam RimWorld, but it *should* work for steam too since it's the same RimWorld engine that creates the log files.)

If you do find the Player.log file, please tell me where it's located so I can correct the directions.

EDIT:
It seems that the log file location is set by Unity.  Try looking in
/Users/<UserName>/Library/Application Support/Ludeon/RimWorld/Player.log

[pawn_of_destiny]

The RimWorld log file titled "Player.log" for Steam on Mac is located in:

~/Library/Logs/Unity

For example, if the username is "frodo", then the location is:

/Users/frodo/Library/Logs/Unity

Attached is the output log for BugTesting1.rws, in which all the pawns almost immediately fall into perma-stand. All of my saved games now exhibit the same behavior, which means that the bug must have been introduced in a very recent update to core or mod.


[attachment deleted by admin - too old]

[milon]

Thank you!! I'll update the directions and future players will thank you too.

There's two things of note in your log file:
1. (Minor-ish) you've got a lot of overlapping power structures, like Solar Panel over Solar Panel. The game complains about that every time.

2. Your pawns are all being broken mentally as relates to food. This doesn't seem to be a Core issue, but there is a bug present, which is why I moved this to Mod Bugs.  Try this:
- back up your game save
- disable all mods that affect food
- use dev mode to delete any non-vanilla food
- save game (remember, you've still got an unmodified back up in case this goes south)
- exit and reload