happened to me while flying on sayintentions…
If you fly with live weather and use ATC (default or 3rd party), 8 out of 10 times you will be given a different landing/approach to what was planned, especially on long haul flights.
WASM crashes made me stop using FS2024 for flights longer than 2-3hrs and I won’t buy another wide body plane until these crashes are reduced to 0. Thankfully there are alternatives to FS2024.
Has anybody noticed improvements with SU5? Amazingly, I was somehow able to perform what I believe to be my first successful flight in the Inibuilds A330. I’m not sure if I was just lucky or if something changed with SU5. Being a 6900XT user I was able to launch the new beta version today for the first time (after always facing CTDs on startup with previous versions).
I did my usual test flight from EDDK (Aerosoft version) to EDDF using ATC, kept changing the approach in the MCDU during climb, cruise, descent and even approach phase, set multiple DIRECT-TOs - so a real stress test - and never had a WASM crash. Before, all of this was guaranteed to cause a WASM crash.
Some things worth noting:
- I believe I deleted the WASM folder before switching to SU5 (not sure because I spent some time away from the computer), however so far this never made any difference
- I’m using Simbrief Dispatch without Navigraph subscription and import flightplans via the EFB, but today the AIRAC cycle was matching; so that might be a key factor
I’m going to keep testing to find out if this was just a coincidence or if there’s been some improvements.
Specs:
- AMD 6900XT
- Intel i5 14600K
- 32GB 5600MHz RAM
I would hope whenever they released a beta or an update that everyone deletes their “old” WASM folder and let the sim rebuild. I’m on SU4 but haven’t had 1 WASM crash. I fly the default a320 which is the only default airliner I fly.
and I would hope, that if wiping the WASM folder is required for an update, that this would be part of the installation routine or at least clearly stated in the release notes.
It should never be expected that the user will do what he is not requested to do. That’s what installers and release notes are for. We are not talking about freeware here but about professional payware for paying customers.
To each his/her own but completely unnecessary. Don’t need to wipe the rolling cache, shader caches, or all of Windows either.
And mods or devs focusing on this?
The “bug-logged” tag indicates that yes, they are - or at the very least it is officially in their queue.
But maybe we will never see this bug got fixed…
There are certain elements of software development that will never be 100% fixed. I presume, based on the complexity, that WASM crashes will always be a risk as long as code is being compiled using WASM. The best we can hope for is improving the situation by reducing their frequency, or by incorporating autosave functions like that of the iniBuilds A350 which allow users to pick back up where they left off prior to the WASM crash.
So, are u think WASM crash is sim-related or addon-related? Some WASM plane is very stable, but some are often crash like ini airbus and FSS E-Jets.
Both - some addons like Fenix compile their WASM outside of the sim and seem very stable. That and some other things some devs have alluded to suggest that some or much of the issue has to do with how MSFS is compiling WASM. But obviously if you use aircraft which don’t use WASM, this is a non-issue.
I’m also thinking a bit of both. I fly the PMDG 737 and 777 as well as the inibuilds A350. I can force the PMDG aircraft to WASM crash, but it requires me to enable all of my ground visual enhancement mods at large 3rd party airports and then try to load a simbrief flight plan. Whereas the A350 will do it anywhere simply by changing the arrival route with no other addons enabled. Given this, and bearing in mind that performance in PMDG aircraft is much smoother than inibuilds and scenery LOD is far better in PMDG aircraft due to them using less system resources, I’d say that WASM crashes are most likely to occur in demanding situations
So I think this is more iniBuilds’ problem than Asobo.
It does lean slightly more towards inibuilds aircraft not being as well optimised as they maybe could be
But why inibuilds doesnt use external apps… C’mon… stability is everything.
Because you can’t on Xbox
It couldn’t be sold in the Marketplace and, as another user pointed out, it couldn’t be used on consoles.
This is obviously not a choice for first-party devs which must create products which work on all platforms. This is also a choice for third-party devs who want their product to be accessible to the widest range of users possible.
Also “PC is much better than Xbox” is a pretty broad and often false statement - find me a PC for $300 that can run the sim as well as an Xbox Series S and I’ll be stunned.
But Xbox is much simpler and a fraction of the cost. I don’t spend my life worried that the next graphics card drivers are going to have me troubleshooting crashes for the next few weeks. I switch on my Xbox and I know it will work every time