Thanks for the report. Issue is now fixed for 1.1.70. It was related to a bad logic inside of a Loader where it was allowed to deactivate itself even when the entity it interacts with has no wakeup lists. Now a loader will stay active if the entity it interacts with has no wakeup list. To additional...

Thanks for the report. Issue is now fixed for 1.1.70.

No.

This idea is incompatible with one of the 1.2 changes where it would be a clear violation of the train stop limits.

Thanks for the report. Lets see how many mods are broken by my changes. Instead of forcing stack size to 1, it will not force any values anymore, but if it happens to be different than 1 it will throw instead. LuaItemPrototype::stackable should also be fixed for 1.1.70.

Thanks for the report. Issue is now fixed for 1.1.70.

Ok, i did tiny tweaks to make the HighlightBoxEntity behave slightly better: it will perform copy of target's selectionBox immediately during construction without waiting for next update call. That has some important behavior changes because copy of this selection box is then used as a bounding box ...

Thanks for the report. Save file has enough clues that i was able to reproduce the issue without any mods. It is related to upgrading underground belt ghosts. Issue is now fixed for 1.1.70. For now you can fix this this save file using a "prototype changed mode" which you can trigger manua...

When i was implementing train stop limits i was aware it will not work nicely with enable/disable exactly because of that case but i kept it because it gives different behavior for controlling trains (allows trains to skip some schedule records instead of waiting). I guess i have enough of those iss...

Merging of level data chunks from different save files is not allowed, it will not give anything usable.

Unfortunately there is not much that can be done with this zip file. It is corrupted. I was able to recover level.dat33 up to level.dat73 but there are parts from dat0 to dat32 missing and any gap will make this save file not recoverable.

Thanks for the report. Issue is now fixed for 1.1.70.

There are at least 2 reasons why this is unlikely to happen: - Gate has different collision mask than a wall has. This is one of many requirements for the current upgrade planner logic to consider 2 entities as upgradable which a gate-wall pair fails. - Walls have no direction when Gates have a dire...

Thanks for the report. This is a minor issue. Most likely it will not get fixed in 1.1, however i see it is already fixed for 1.2.

Thanks for the report. Issue is now fixed for 1.1.69. It was related to boiler's burner energy source not updating its buffer size.

Curiosity question: for MP, does the game do any checking of all game files, or just the game version? I'm wondering if maybe somehow one of the base files for the prototypes has been altered for this one person? If using the Steam version, I'd recommend maybe trying to verify the install? If that ...

Thanks for the report. I was able to find a relatively simple fix for this so it is now fixed for 1.1.69. Fix was to change solar panel's energy source buffer size every tick to match the solar power multiplier if it goes above 1.

mirpa wrote: ↑

Fri Sep 09, 2022 3:39 am

Bug is not reproducible.

Given this and the log file that does not contain anything useful (PipelineStateManager::~PipelineStateManager then d3d11 stack), i am moving this to 1/0 magic.

It was a value that cxxopts library silently ignored (not a flag, not consumed positional so it was put to keep). I do not think we want to dig into that library to change the behavior that will catch your issue.

Thanks for the report. This is quite minor issue. It works fine in 1.2 so i am considering this to be fixed for 1.2