- Messages
- 30
- Country

I have developed five airports for Microsoft Flight Simulator 2020 all of which worked flawlessly up to Patch V1.16.2.0. Now, two of these airports works flawlessly, but the other three causes MSFS to crash to the desktop and I have no idea why.
It is not that I am doing anything funny. All my airport objects are designed with Blender and exported using the Blender2MSFS toolkit. The textures for all the airport buildings are 1024x1024. I use BenneyBoy444’s method of placing apron markings using 512x512 textures. Nothing strange so far.
I compiled the airports using SDK 12, SDK 13 and even SDK 10. Someone suggested that I try ModelLibChanger. It suggested that I changed the name of the Model Library. Someone also suggested that I checked the model version of the object XML file and make sure that it is set to version="1.1". None of these did anything to resolve the issue.
I could run MSFS, select the airport ICAO from the list and then it will load about two thirds before the music starts stuttering and BAM, crash to desktop!
I updated my graphics drivers, updated Windows 10 with all the patches available, even the ones that were deemed as not needed. BAM, crash to desktop!
I then figured that maybe the issue is with the models, so I exported them all over again and re-compiled the airports… BAM, crash to desktop!
Ok, maybe it has something to do with the materials as I use for the apron markings and the taxiway lines, so I removed those and re-compiled the airports… BAM, crash to desktop!
Right… Maybe if I delete the airport and start from scratch again. I mean, surely that MUST work… BAM, crash to desktop!
Right now, I am standing here beside myself, not knowing what more to do.
All this started after Patch V1.16.2.0… Before that everything worked simply fine, absolutely no issues! Even stranger is that two of my airports still work! The only difference between the two that work and the three that does not work, is the materials for the ground markings. That is why I thought of removing the materials, but that did nothing. Still… BAM, crash to desktop!
I am giving up on MSFS…
I develop airports for FSX, Prepar3D and even X-Plane. Over the years there have always been hot fixes to these flight simulators and the only time I have seen anything like this happen is when the developer did not follow the rules of the SDK. My airports have always worked; through all the versions of Prepar3D and X-Plane with only minimal changes from one version to the next, because I always follow the guidelines of the SDK.
Maybe the guys where right in that MSFS is not ready for release… That is why things that were working perfectly well with one patch now just does not work anymore. Maybe the three airports that does not work now, will start to work again with Patch V1.17… but I am not holding my breath!
Until then it is bye-bye MSFS and hello Prepar3D/X-Plane!
It is not that I am doing anything funny. All my airport objects are designed with Blender and exported using the Blender2MSFS toolkit. The textures for all the airport buildings are 1024x1024. I use BenneyBoy444’s method of placing apron markings using 512x512 textures. Nothing strange so far.
I compiled the airports using SDK 12, SDK 13 and even SDK 10. Someone suggested that I try ModelLibChanger. It suggested that I changed the name of the Model Library. Someone also suggested that I checked the model version of the object XML file and make sure that it is set to version="1.1". None of these did anything to resolve the issue.
I could run MSFS, select the airport ICAO from the list and then it will load about two thirds before the music starts stuttering and BAM, crash to desktop!
I updated my graphics drivers, updated Windows 10 with all the patches available, even the ones that were deemed as not needed. BAM, crash to desktop!
I then figured that maybe the issue is with the models, so I exported them all over again and re-compiled the airports… BAM, crash to desktop!
Ok, maybe it has something to do with the materials as I use for the apron markings and the taxiway lines, so I removed those and re-compiled the airports… BAM, crash to desktop!
Right… Maybe if I delete the airport and start from scratch again. I mean, surely that MUST work… BAM, crash to desktop!
Right now, I am standing here beside myself, not knowing what more to do.
All this started after Patch V1.16.2.0… Before that everything worked simply fine, absolutely no issues! Even stranger is that two of my airports still work! The only difference between the two that work and the three that does not work, is the materials for the ground markings. That is why I thought of removing the materials, but that did nothing. Still… BAM, crash to desktop!
I am giving up on MSFS…
I develop airports for FSX, Prepar3D and even X-Plane. Over the years there have always been hot fixes to these flight simulators and the only time I have seen anything like this happen is when the developer did not follow the rules of the SDK. My airports have always worked; through all the versions of Prepar3D and X-Plane with only minimal changes from one version to the next, because I always follow the guidelines of the SDK.
Maybe the guys where right in that MSFS is not ready for release… That is why things that were working perfectly well with one patch now just does not work anymore. Maybe the three airports that does not work now, will start to work again with Patch V1.17… but I am not holding my breath!
Until then it is bye-bye MSFS and hello Prepar3D/X-Plane!





