All mines at the beginning

Issue description

After loading a savegame of an edited map. The mine status is not loaded. All the mines look as if nothing had been mined.

Reproduction steps

1.Loading save file "Kalti Industry>Test 1.1" map Salvara Isla.
2.After loading, see the map.
3.All mine mining areas look unused.This refers to the two mines for coal and iron.

Game version and build number

v0.6.3a b333

Operating system

Windows

Attachments

20240428190456_1.jpg, 24-04-28_03-10-autosave.save, 24-04-28_03-25-autosave.save, 24-04-28_03-40-autosave.save, 24-04-28_03-55-autosave.save, 24-04-28_04-10-autosave.save, 24-04-28_04-25-autosave.save, Test 1.1.save, SlavaraIslav2_v2.map

Files not imported: 24-04-28_03-10-autosave.save, 24-04-28_03-25-autosave.save, 24-04-28_03-40-autosave.save, 24-04-28_03-55-autosave.save, 24-04-28_04-10-autosave.save, 24-04-28_04-25-autosave.save, Test 1.1.save

Another save game map Armageddon has the same problem. I played on ultra high. After I set the setting to balanced everything was back to how it should be. I also noticed that it's an anti-aliasing problem. With high msaa x2 there is no problem, only from msaa x4.Ultra high with msaa x2 is the problem also there. Ultra high with smaa the problem is no longer there. So it will be an anti aliasing problem.

I've tried all the settings on the map and they all have the error.
maybe it's because of the costem mad map.

I just tried this on my side and the terrain seems to be mined as it should. Does this always happen 100% time? Could you please also attach your logs so we can take a look if there are some issues.

Logs.zip

Here are the logs from today. At the last one everything was in place. The error was found in the first one.For the others, the program closed without an error message

my Cpu is Intel(R) Core(TM) i9-14900KF 3.20 GHz
My GPU is Nividia Geforce RTX 4090
Ram 64GB
And system Win 11

Thank you for the detailed report and attached files/logs. We have been able to reproduce this issue and fix will be available in the next patch.

This was fixed in v0.6.3b.