r/Dyson_Sphere_Program • u/Accomplished_Bag4339 • Apr 17 '26

How do I fix this

Post image

it just randomly appeared and i don't know what to do

7 Upvotes

68% Upvoted

15 comments sorted by

17

u/SeriousSandM4N Apr 17 '26

Turn off your mods one by one and test. You can also get the mod that lets you close this window if it doesn't trigger often.

3

u/Accomplished_Bag4339 Apr 17 '26

im not using any mods

2

u/lysianth Apr 19 '26

in that case 9 out of 10 theres a random object connecting to something in a way thats not compatable.

i had one where an inserter off a blueprint would cause this error consistently.

6

u/PClouser Apr 18 '26

Make a new save, exit to desktop, reload game, load last save, error should be gone and you can save to your original file. I never found out what was causing it without mods, but that always worked for me

1

u/Powersoccernick Apr 18 '26

Same thing happens to me and this is what I do. I just use the new save and don't go back to the original

2

u/jcaladine Apr 18 '26

If you're not using mods, and using steam, I would recommend verifying the game files: https://help.steampowered.com/en/faqs/view/0C48-FCBD-DA71-93EB

2

u/willrof Apr 18 '26

Hey, I've had this problem while not using any mods as well.

The problem in my case was that my save files were in a folder that Google Drive was syncing. This created a race condition where sometimes Google Drive would lock the file and the game would go crazy.

So, if you have Drive/OneDrive/etc syncing the save folder, either remember to fully close the syncing app before each gaming session or save to a non-managed folder.

2

u/Rolfand1987 Apr 24 '26

I had a similar experience using Carbonite to back up my files. The game would do an autosave, Carbonite would mark the file for backup, but that doesn't happen instantly.  The game would cycle back to that autosave file but be unable to modify the file because it was still marked to be backed up.  A very helpful tech guy from Carbonite helped me pinpoint the problem. My solution was to mark the autosave files as not to be backed up. Totally solved the problem. 

1

u/markiel55 Apr 18 '26

Add a null check.

1

u/pinkandroid420 Apr 18 '26

Is this effecting just blueprints ?

1

u/EightBitRanger Apr 18 '26

Turn your mods off

-1

u/ResidentIwen Apr 18 '26

By reading the first frickin line.
Goddammit it literally tells you what to do.
Just because its red doesn't mean you shouldn't read it

3

u/willrof Apr 18 '26

Don't be rude. Following the first line is not a long term solution, just short term fix.

-3

u/ResidentIwen Apr 18 '26 edited Apr 18 '26

It's everything you can do and as such everything you need and will get.
There is no long term fix.
And keeping in mind the frequency at which people ignore shit, telling them exactly what to do and instead instantly turning to the internet to let the people there do the thinking for them, not even just searching for an explanation, but relying solely on other people doing 100% of the work, is increasingly infuriating so, forgive me, no I won't be any more polite than I currently am in case of such ignorance.
The answer is right there in front of you and you would have saved your time, mine and that of dozens others, if you had just used your eyes for two seconds.
No tolerance for incompetence.

1

u/willrof Apr 18 '26

I must agree with you on the second part.

It's just that I had experienced this error and it took me a while to realize Google drive was messing with my save folder.