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

Game stutters because of hauling / stacking: X started 10 jobs in one tick #20

Open
RadGH opened this issue Mar 3, 2019 · 1 comment

Comments

@RadGH
Copy link

RadGH commented Mar 3, 2019

I've got a late game base with lots of storage. I began running into some lag and turned devmode on to a wall of red errors all referring to moving pieces of apparel and "giving 10 jobs per tick". The hauling order seems to be related to Extended Storage.

I posted to the steam forums here: https://steamcommunity.com/workshop/filedetails/discussion/731732064/1798529872634941905/?tscn=1551633984

I have a detailed error log here: https://gist.github.com/HugsLibRecordKeeper/6db47236f97a30223328dcee09cf02a7

Note the error log was actually for debugging a pawn trying to have a social fight which was causing 0 FPS (the errors related to Yiol). That was fixed separately. Some other errors about Pick Up and Haul were fixed by just removing Pick Up and Haul entirely. Extended Storage is the one I can't just remove.

My solution was to just remove all of the apparel storage which seemed to solve the problem, although that's not ideal.

I have had the issue with medicine before too. That was fixed by restricting medicine storage to one type
of item each, and positioning them to be horizontal. Not sure if making it horizontal did anything but it seemed like that did the trick at the time. I think it was mostly that I moved the storage so they re-organized it all.

@RadGH RadGH changed the title Game stutters Game stutters because of hauling / stacking: X started 10 jobs in one tick Mar 3, 2019
@DoctorVanGogh
Copy link
Owner

I'm reluctant to blame ES here. Looking at the error log there are a bunch of pawn state related exceptions. Those might have set the worker logic into an unexpected state where the multiple jobs issue got triggered.

Would you happen to have a log (preferably even a savegame?) which exhibits the issue without prior 3rd party exceptions?

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

No branches or pull requests

2 participants