Thanks fro the tip. I gave it a go. SOme actions are recognised by enent monitor but not all. In fact most are not. Weird
I like how they have the Canadian flag on PMDGās livery but theres not a single Canadian livery in there installer. Cāmon PMDGā¦really. I tried some 2020 version paints in 2024 but none work.
They honestly might have had trouble finding or getting permission for authentic ones. I think Buffalo used -4s, not 6s, and there arenāt really any other known Canadian bush operators that would attract buyers. Itās entirely possible that permission for the Canadian Pacific and Pacific Western, as well as other secondary carrier liveries would be more trouble than theyāre worth getting, sadlyā¦ especially when PMDG can pretty reliably count on modding support for that.
Buffalo have the only swing tail cargo -6 in the world! Itās currently in storage and not part of their active fleet.
Anyone know how to get rid of orange radios in the DC-6ā¦
Work around.
Since build 2.04.062 no more WASM crashes for me
It would be interesting to know what fixed it.
They could share that info with other devās.
Iāve updated a few of my textures to the 2024 version, the rest will follow in a few weeks.
And it looks like the GNS responds as it should without having to swap around in the tablet.
This might be a dumb question but where can I download these great repaints?
You can find them on Flightsim.to
Do you know if theyāre uploaded already or are they pending?
If you still find issues, please send us a ticket. We are still looking at a few things, but are generally pretty happy with the stability now. The weird thing is that we still have no idea what so ever why some users had issues and others had not.
Robert spend some time explaining our efforts, let me copy:
*WASM Crashes: The Known Unknowns
We have been chasing WASM crashes in MSFS24 since the our first 777 released onto the platform in 2025. Over the past six months, we have invested an enormous amount of development capital into an effort to identify causes and implement fixes. It is hard to overstate the enormity of this effort, and it involves nearly every developer at PMDG in some fashion or other, as we review every line of code in every product looking for problems that might potentially have something to do with aggravating the sim and causing a wasm crash.
The frustrating part here, is that nobody in the dev community (our peer devs, for example) has a clear idea of what, specifically causes a WASM crash. I cannot, with certitude, tell you that WASM crashes are caused by a problem in our product or its source code. I also cannot tell you with certitude that wasm crashes are not caused by a problem with our product or code.
As a result, we have undertaken a rigorous exercise in code investigation, operational analysis, benchmarking, static analysis and data collection in an effort to clean out any possible problem within the product that might potentially upset the platform. This effort has involved many thousands of man hours, numerous tools, an assiduous effort to follow vague advice provided by the platform developer, and a significant amount of code refactoring in order to ensure that we eliminate any possible faults from within the PMDG product.
This effort has been focused primarily on an internal 737 test build, with a side-lobe effort taking place on the DC-6 as we speak. We do not feel certain that WASM crashes can be cured entirely by us as a developer- but we are spending a significant amount of developer time in an effort that we hope will allow us to say with certainty that we have eliminated any potential weak points in our code that could aggravate the platform. It is hour hope, that once this problem is completed, our products will become magically WASM crash free- but the hard reality is that this is not likely the sole cure that is required.
WASM crashes could be entirely out of PMDGās control. They are likely resulting from some weak spot in the platform, or some conflict in the way multiple developer products conflict within the platform for memory or resources. We just do not know- and none of the questions we ask on the topic get answered, which tells me that the platform developer doesnāt know either.
At PMDG we are sharing any information we learn with our peer developers- in hopes that someone will have that āah HA!ā moment that brings WASM crash misery to an end. While we absolutely love the MSFS 2024 platform, as developers we are deeply concerned about the impact wasm crashes is having on simmer morale- and the willingness of simmers to support the platform and products made by PMDG and our peer developers if instability simply has to be viewed as a cost of enjoying the hobby.
Internally at PMDG, we are referring to this effort as our āWASM Crash Moonshot.ā We hope the financial and effort investment will be worth it in the end- and we appreciate your patience while we try to find the answers.*
So do report these issues to our support, if they come with solid details, they help our efforts.
Mathijs Kok
PMDG
Thanks to PMDG for these efforts. I tend to agree itās sim base code causing problems. MS/Asobo need to join forces with devs in an open collaborative way to resolve WASM crashes.
We are totally ready to share our information, and by now we understand far better what increases the likelihood of WASM issues. But that has not yet led to any clear path to solving it.
They are already available there.
They donāt seem to be updated. The TAL one says it was uploaded 5 years ago and my download from 2021 is up to dateā¦
Itās up to the livery creator to update them.
I understand that. But when Jankees postet the screenshots I asked where I could download them and another member of the community told me on flightsim.to.
All Iām asking is where to get these beautiful liveries.