If my math is right, the log is showing it wants roughly 50 max sized textures each of which is 1GB large. Effectively it wants 50GB of VRAM and the GPU has choked and died trying to deal with it.

Thanks for the report. This is now fixed for the next release.

Do you have some sample save file that shows the issue? Looking at the code I don't see anywhere that looks wrong which makes me wonder if it might be the setting of the schedule through the lua API breaking the logic.

I've changed the icon for the next release.

Since this report never went anywhere internally with discussions, I'm deciding that I will simply change how spoilage works for this case and make the inserter put it into the trash slot if the normal output is full.

Thanks for the report. This is now fixed for the next release.

Thanks for the report however that's intended. 301 / 50 (the stack size) is 7~ slots worth of space which is all the roboport has. It then no longer will have space for any construction robots and so they leave.

Thanks for the report. This is now fixed for the next release.

Thanks for the report. This is now fixed for the next release.

This sounds like something steam would have to implement since it would be the one to get the command line options and then pass them along to the process once started.

I've added LuaPrototypes::utility_constants read for the next release.

Note virtually all prototype reads return nil when called on the wrong thing. This is intentional because of the way everything is setup through inheritance it would otherwise be a nightmare to know if something is valid to call on a given instance.

Added for the next release.

Thanks for the report. Looking at the log - it appears to be crashing when saving is almost completed. It has finished saving everything and was attempting cleanup and at that point it crashed. I don't see how it could possibly ever crash in that scenario since everything in the cleanup stage is ...

Looking at the desync report, I'm not seeing anything stick out. The electric and fluid flow are different. Electric and fluid flow happen all the time on every single save so if there was some underlying desync with them it feels like they should be breaking a lot faster and more frequently.

Have ...

Thanks for the report. This is working correctly: if an item is available in the logistic network the auto-request logic will make the request on one of the available rocket silos.

If you then remove those items and manually put them in a different silo, or just remove them from the network - the ...

So the mods explicitly require the space-age mod or do they require the feature flags for space age features?

I've added LuaSurface get_default_cover_tile() and set_default_cover_tile() for the next release.

I think that may run into the same issue but from the other end. Where the rail ghosts get built in the air before the ramp is moved, getting the ramp robot stuck again. But I don't know for sure.

Personally, I think the game is trying to be too smart about everything in this scenario and it's not ...

Looking into this, I don't think there's a solution that will allow the robots to actually perform the requested operation. The elevated rails require supports and the logic wants to remove one of them to move it slightly... but it can never do that without also removing the elevated rails.