SU1 issue - Editing projects

Version: 1.3.23.0

Frequency: Consistently

Severity: Blocker

Context:
SU1 related issue when opening projects created before SU1 release.

Bug description:
Since SU1 released, the editor has become unusable at around 2-5fps when opening certain projects and then eventually crashing to desktop. This is present at multiple scenery projects including OMDB, EGLL, YBBN, KLAX.

Repro steps:
It might be difficult to repro. Try opening a large airport project and see if the sim crashes. We are on the latest SDK version (1.2.4)

Attachments:


@iniGeorge

Unfortunately we don’t see that kind of issue with our (big) projects.
Would it be possible for you to send us a project that demonstrates the issue through Private Content?

Best regards,

Eric / Asobo

I can confirm that I’ve been having this same problem in my airport since the first SU1 update. I haven’t found anything that could be causing this. I’ve already reinstalled the simulator, video drivers, chipset, and Visual Basic. Something tells me that this problem is caused by the engine itself, because in the video you can clearly see that before opening the project, the FPS drops instantly. After opening the project, the SDK tries to pull the 3D models and closes by itself. My workflow has been delayed for months because I can’t open the project. Before the first update was released, it was normal, reaching 45 to 60 fps in the SDK.
I don’t have any mods installed in the community folder, and if I compile the project using fspackagetool, the scenario compiles correctly without errors in the console. I put it in the community and it runs smoothly at 60 fps without crashes or FPS drops.

My settings: Ryzen 5700 x3D
RX 7800 XT 16 GB
32 GB DDR4 3600
Kingston Fury Renegade SSD, 1TB Read: 7300 MB/s, Write: 6000 MB/s.

video link below:

1 Like

Hi @EPellissier

Thanks for the response. We’ve discovered a random workaround to get the editor working how it was pre-SU1.

The temporary solution is to spawn at a smaller airport (EGHR for example), and then open the project (EGLL). After this, load the scene BGL and double click on any element which will take you to the correct location. I’m now back up to 70fps in-editor now with no crashing. An extremely random solution but hopefully it might help locate the issue.

If you need anything else from me to help identify the cause, I’d be happy to assist.

All the best,
George

1 Like

It worked here too, thanks for the temporary solution

Thank YOU Sir. You saved my day/week/month with that solution. I started to work with the SDK some days ago to adapt my scenery from ADE to the SDK without having to start from scratch. I could finally obtain a rather good result and suddenly ctd ctd ctd ctds as soon as I entered in Devmode. The culprits were repeatedly the kernelbase.dll and ntdll.dll in the System32 folder. I tried anything including testing the onboard memory, unistalling MSFS with no joy, amongst other things, and finally saw this thread and your solution. Now I can carry-on working on my project. The good news - for me - is that I can select as departure the VOLC3 helipad which is inside LFPG airport but not a part of it and so I don’t have to translate.
Than you again.
Xavier

It really is the strangest issue I’ve ever encountered with flight sim. I do hope it can be fixed eventually as it’s affecting a new project we’ve just started also which is an empty project. There is no reason for constant CTDs opening an empty project at an airport.

I don’t think they can fix it if they don’t see the issue and none of you share an offending project with them?

I’m happy to share the current project via private content to see if the issue can be reproduced on their end. We’ve had 3 people try to open the current project on different PC setups and each one encountered a CTD. The temporary solution works fine though, it is a sim bug.

1 Like

Please proceed if you can share the model - as stated in my previous post, we never saw such a behavior internally.

Best regards,

Eric / Asobo