Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to resolve reference and null keys on reload [unstable RimWorld 1.1.2586 rev1244] #134

Open
Hechicera64 opened this issue Mar 28, 2020 · 6 comments

Comments

@Hechicera64
Copy link

Describe the bug

Start a new game containing at least Harmony and Work Tab. Grab weapons, set a farm area, set a mine area. Go to Work Tab, change to numeric (mine is set to 1-6 in options) and change some things. Let pawns go to a few of the newly assigned jobs and do them. Usually 5 mins or so. Save to Menu, reload game. Check log. Game however seems to work, and if you then save (in my case to desktop) and reload the second reload log is fine, and you can carry on. So it may self-fix if force reload on error.

Expected behavior

No errors in log.

Steps to reproduce

  1. New game w/Harmony, Core, Royalty, WorkTab, on unstable
  2. Do usual game start tasks.
  3. Change priorities to numerical, and rearrange pawns to jobs.
  4. Let them exercise those tasks for a few minutes.
  5. Save to Menu, Reload that game, inspect log

Other mods

I don't think so. The only other error in the log I will provide is isolated to it. But Facial Stuff 1.1 is the only other error thrower.

Output log

Since the Current log will show the clean second reload, here is the saved log from first reload:
https://drive.google.com/open?id=1b6qr0FZaUqcycYsZ8mUaVYrUn9T5Ozsk

Save game

Zip of last two saves, quite small as new game.
https://drive.google.com/open?id=15e6h5fXc8rj_e01Jic7MgBi9ZxiWNjsd

Screenshots

Nothing to see. If I weren't looking at the log file on load because of unstable testing I wouldn't have noticed.

Environment

  • OS:
  • 32/64 bits
    Boring Windows 10 64 bit.

Game

  • 32/64 bits
  • Steam/DRM free
  • Version
    Steam unstable branch RimWorld 1.1.2586 rev1244
@Hechicera64 Hechicera64 added bug Something isn't working unverified bug has not yet been verified/replicated labels Mar 28, 2020
@Hechicera64
Copy link
Author

I think it has a mod conflict or load order component. Tried to recreate it with just WorkTab and just WorkTab and Facial Stuff (my only other error throwing mod) and couldn't recreate. Either that or I haven't properly identified the trigger.

@Hechicera64
Copy link
Author

Hechicera64 commented Mar 28, 2020

I have seen it again, but both times with a full mod list so unsure exact cause still. I have been running with verbose logging on and I do get this warning on RimWorld load:

Type TextureChooser probably needs a StaticConstructorOnStartup attribute, because it has a field LeftArrow of type Texture2D. All assets must be loaded in the main thread.
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

I can get that with only Harmony, Core, Royalty and Work Tab loaded on unstable RimWorld 1.1.2587 rev830.

@Yaksinikos
Copy link

Yaksinikos commented Mar 30, 2020

same here, as soon as i change the number-limit to 5 and start with num 5 it shows me error log on loading the savegame.
afterwards it resets all to default :/

Gist

@zhrocks11
Copy link

zhrocks11 commented Mar 30, 2020

Adding to this - https://gist.github.com/HugsLibRecordKeeper/9fae038fab55cceff86a115829f44a5b When autosave happens it has an issue with Saving the pawn therefor its also throwing errors on reload - went through my modlist 1 by 1 until i could confirm it was indeed worktab. - Its only happening when you use more then the default 4 priorities

@zhrocks11
Copy link

https://gist.github.com/HugsLibRecordKeeper/2e81cf8a0e09118726bbbe499fc34c00

After doing some addtl testing on the below comment - i have figured out its a new compatibility error between Work Tab and Edb's Prepare Carefully.

@Hechicera64
Copy link
Author

I don't use Prepare Carefully (can see in my log), so there is at least one additional trigger. In a recent run (log sent went to unstable testing chat) I triggered a pawn not deep saved, warning that you will get error on load with a very small mod set. I didn't put it here, as Work Tab wasn't in that set. But here is log with pasted in add'l info. You can see the warning of error on reload, then the relod with the error. No Work Tab, does have Pharmacy ... but I suspect issue deeper atm

https://gist.github.com/024bb979c01096cbcd68678a7bd9ad10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants