I had to reinstall Windows 10 and thus also reinstall MSFS on my pc. Today, I did reinstall LFTZ La Môle Saint Tropez Airport v.1.0.0. by Stairport, bought via MSFS Marketplace.
When I enter runway 6 the game freezes and then CTD.
This happens every time. Only when in “Safe Mode” (with default airport) there is no CTD.
At exactly this broad yellow stripe the game freezes and CTD:
I have also the taxi assist arrows activated, but they did not show. Only when in “Safe Mode” with the default airport, the taxi assist arrows did show.
Content Manager tells me, that this v.1.0.0. is “up to date”, but I do not think so after this repeated CTDs.
UPDATE: version 1.0.0.1. is available, so please update Marketplace!!
UPDATE 2: after contact with the developer, I deleted rolling cache on his suggestion. And after restarting my computer and MSFS, the problem was solved.
Asobo/Microsoft cannot bugfix 3rd party content even if they wanted to. It is entirely up to the producers and they will usually be aware of it so next time research before buying.
I bought it on MSFS Marketplace, so I think it is MSFSs problem. Some time ago I asked you guys to include the e-mail adresses from the third party developers, but nope. Should I now go and search the internet for the developer???
This is the discussion board for MS Flight Simulator. The Moderator Team cannot receive/ingest or process technical support. We’re not even MS-Asobo employees - we are volunteer staff - users just like you. We are here to facilitate safe, respectful and relevant conversations about the simulator.
Officially, Zendesk is the support function. If you feel strongly this is a Marketplace issue, please feel free to file a request there.
One year ago I asked them to include the e-mail adress for support , but they didn’t…
Also, even when third party developers did update, all to often, it did not reach Marketplace, as here it turned out to be: on Marketplace this airport is v.1.0.0. but it should be v.1.0.0.1
Well, thank you very much.
But, again it seems to be a case of not updating (in time) of third party content in MSFS Marketplace, for already version 1.0.0.1 is available elsewhere!
I would like to argue that there are two things here:
A) a third party airport … which is buggy … not an Asobo issue
B) a game engine which crashes … just because of a buggy airport … this is an Asobo issue
I think it actually is a bug of the game engine if “trivial game assets” can crash it … crash it hard.
In that sense I would disagree with @CasualClick that this is resolved by simple declaring it a SEP (someone else’s problem).
Just like an operating system should not be “crash-able” by buggy apps … or a browser should not crash just because of buggy JS in buggy web pages.
IMHO if someone can find reproducible third party driven CTD issues … Asobo should be thankful and investigate what bug those assets trigger in their game engine.
You’re welcome to have conversations about it to see if there is a peer resolution available, but if you feel this is Sim-related, the ONLY way to get it ingested into the Defect analysis process is to file a Zendesk.
Most likely though, the vendor will have a faster answer, whether it’s a defect on their end, Marketplace versions n mismatch or something else.
If with “this” you mean the isolation of external “code” in order to protect the main software and prevent it from doing a CTD then … as I already pointed out … I would use any web browser (Chrome, Firefox, Brave, …) as an example.
Why do we have JavaScript on webpages … because the browser can “sandbox” that (platform independent) code in order to protect against crashes. The same applies to the entire idea of WASM, which is mainly just a better and faster sandbox.
I admit that I have no clue how MSFS works internally. So far I was thinking that external assets get their code executed inside WASM sandboxes. If that is the case (and so far I considered this a pretty smart design strategy on the Asobo side), then there seems to be some bug in the games WASM isolation strategy / implementation.
If, however, external assets can bring along and bind against native DLLs then I would agree, that there is nothing Asobo can do … besides totally redesigning its code strategy for the inclusion of third party assets. But at least so far I can not see any reason why a WASM sandbox would not be fast enough for any 3rd party asset … where airports clearly are not the most demanding (code) category.
