When working in Dev Mode, the simulator crashes unexpectedly, after some operations.
It happens with a .XML file that contains water polygons. The file in question is about 9 Mbytes large. With files of the same type but up to 5 Mbytes in size, no CTD.
Repro steps:
During the visual verification phase of the water polygons in the Scenario Editor, some, even if correctly excluded in QGis and then transferred to .SHP format do not apply the exclusion correction.
The verification is done to find a solution … but I can not complete the verification process, because the CTD arrives.
Note: The attached . XML file (make a backup) every time they are loaded in the Scenario Editor the “Force elevation” attribute is added which is not necessary as it causes a further unwanted flattening in the final scenario
To overcome this, I clean the .XML file of this attribute every time and compile with fspackagetool.exe from outside of DEV Mode.
I wanted to thank you for the time and effort you put into investigating the issue. Your work was really valuable and I really appreciate your analysis.
Unfortunately, from my tests the problem persists.
Tried on the same project that I shared with the team. When you select the polygon (Caspian Sea) and only that polygon the CTD arrives.
I tried another project that previously the big polygon I had divided into several parts so that it was not greater than 65536 no CTD.
Eccezione non gestita in 0x00007FF7579DE9E7 in FlightSimulator2024.exe: 0xC00000FD: Stack overflow (parametri: 0x0000000000000001, 0x000000A483403000).
Unhandled exception at 0x00007FF7579DE9E7 in FlightSimulator2024.exe: 0xC00000FD: Stack overflow (parameters: 0x0000000000000001, 0x000000A483403000).
In C:\Users\User\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState no other file is recorded except crashdata.txt
I can confirm that with the latest SU3 flighting, handling polygons with more than 65,000 vertices no longer causes crashes (CTD).
Also, the warning message about the polygon having too many vertices is useful for debugging.
If I’m not mistaken, there was talk of 65536 vertices maximum supported.
Anyway, I recompiled the entire project including the two polygons exceeding the maximum number of vertices allowed without receiving an error from the compiler.
I hope this is integrated into the SDK documentation.