• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

CTD when creating an airport in the SDK.

Messages
71
Country
us-california
Hello, so I have been using the SDK to make my own simple airport in MSFS 2020. At first, everything was going fine; however, starting a few days ago, I began to experience a CTD after several minutes every time I go to work on my airport. Sometimes I will get an error that says a breakpoint has been reached with the code 0x80000003, and other times there will be no error at all. I did a Google search and saw some people say to change the virtual memory to automatic and to make sure there was sufficient disk space, which there wa,s and the VM was already set to automatic. Some other things I checked are as follows


Restarted the computer


Ran the sim with all mods disabled


Made sure everything was up to date, including my drivers and Windows itself, which they were


Ran both the memory tester and disk checker, which showed no errors.


Ran an integrity check of the game’s files through Steam


Also, not sure which version of the SDK I have, but I made sure to update to the latest version, but unfortunately, none of that worked


Also, I have done a little flying in between, and I don’t seem to have the problem then only when working in the editor.


So, any suggestions on how I can fix this?


Thanks
 

Attachments

  • unknown_2025.10.25-19.15.png
    unknown_2025.10.25-19.15.png
    170.5 KB · Views: 64
  • unknown_2025.10.25-19.15_1.png
    unknown_2025.10.25-19.15_1.png
    188.5 KB · Views: 63
I'm guessing you have Windows 11 and 32GB of memory. Otherwise you may be needing an update as lack of memory could be a cause. We don't know your hardware setup.
I sometimes need to check my Windows integrity. Attached is a zip file of a batchfile I use to cleanup Windows. Assuming you have the above specs met, and have cleaned Windows, you still could have a hardware issue.

I had a memory issue that hid from a simple memory test, and only swapping out modules found the problem... it may have been a heat issue with the memory. Heat in general can cause crashes. Desktop computers collect dust and cause lots of issues.

If only the one addon causes the problem, it could be something there. You could try to recreate the addon from scratch and see if it resolves the issue, but that's a long shot, as the 2020 Compiler is pretty good. Is your Community folder empty? It could be something in there.

Good luck finding the issue.
 

Attachments

I'm guessing you have Windows 11 and 32GB of memory. Otherwise you may be needing an update as lack of memory could be a cause. We don't know your hardware setup.
I sometimes need to check my Windows integrity. Attached is a zip file of a batchfile I use to cleanup Windows. Assuming you have the above specs met, and have cleaned Windows, you still could have a hardware issue.

I had a memory issue that hid from a simple memory test, and only swapping out modules found the problem... it may have been a heat issue with the memory. Heat in general can cause crashes. Desktop computers collect dust and cause lots of issues.

If only the one addon causes the problem, it could be something there. You could try to recreate the addon from scratch and see if it resolves the issue, but that's a long shot, as the 2020 Compiler is pretty good. Is your Community folder empty? It could be something in there.

Good luck finding the issue.
Thanks for the help. I will post the full specs below; however, I actually only have 16GB of memory. While I agree that upgrading my memory can't hurt, I am not sure if that is the issue. As I mentioned, it was working fine at first, and the airport is very basic, consisting of only a small building and some runways and aprons. Also, I do not have any issues when doing flights in the sim, just when working on the airport in the SDK. I guess it may use more memory when working in the SDK, but I'm not sure.

As for Windows integrity, I actually updated to Win 11 since the issue began, and am still having the issue, so I doubt that it's an issue with the integrity of Windows, but I could be wrong.

Lastly, I haven't compiled anything yet, as I am still working on building the airport in the editor, but I did do a test with everything removed from the community folder, and still had the issue.

Here are my PC specs:

CPU: Ryzen 5 5000

GPU: Radeon RX 6600

RAM:16GB

HD: 2 TB SSD with 130GB free space.

I will make sure to give the computer a good clean in case it is from the RAM overheating, but other than that, do you have any other suggestions?
 
I suspect this is a hardware issue. MSFS2020 taxes the system quite hard. What airport are you working on? Maybe you found a bug in the default scenery. And to clarify, this happens only while using Devmode in the sim?
 
Here's a comparison of settings: My normal graphics settings...
Memory_01.png


With turning graphics down:
Memory_02.png


With a lower graphics setting, I stay within 16GB system memory while developing, and I could go lower if I needed. And you could turn them back up while not developing. I don't know if this would solve your problem, but if it does, a memory update to 32GB might be a permanent solution. I have 48 GB after I found my memory was failing, and I don't have CTD issues. But again, no guarantees as every system is different. I'd hate for you to update your memory and have no relief. It would be a waste of money.
 
As Asobo indicated the MSFS rendering engine was being changed to cull what 'they' considered less-critical-to-display content when user-requested content burdens the internal run time qued task list, one might wonder if testing very low complexity settings might be a next step ?

Also, even if the OP does not have a critical physical memory address error, if he defrags and enlarges a user-enforced fixed virtual memory paging file on at least a single physical storage drive, that should substitute for running out of physical memory address space.

But, if he is running out of free space on his storage drive(s), Windows may not commit to use of much- if any- virtual paging file address space.

Interesting troubleshooting scenario. :scratchch

I would recommend MS uber-geek Mark Russinovich' SysInternals Suite of tools to analyze / remedy this:

https://apps.microsoft.com/detail/9p7knl5rwt25?hl=en-US&gl=US

GaryGB
 
Last edited:
Back
Top