I am currently in flight in 2024. Seems likely that it’s something to do with SU4. That and I spent a considerable amount of time with this aircraft in the past couple months.
No beta just su3. I’ve never had an aircraft go blank screens before. I thought it was the boris sound pack so I uninstalled it which made it only slightly better. But nope it’s unflyable. I reached out to aerosoft but they haven’t replied yet. Out of 20+ attempts the only one that worked was Gatwick to Manchester but nav didn’t work only heading mode. Tried all the variants they all die the same way. ![]()
I’m on su3 and it’s the only plane I own that gets blank screens or ctd. I want to fly it but it’s just impossible ![]()
Have you tried reinstalling it, or downloading this plane?
Have you tried deleting the wasm folder for this aircraft to have it recompile the wasm module?
Curious if you spent time with the CRJ in MSFS 2020 or 2024 these past months? I was under the impression that v2 was a new release for MSFS 2024?
Was the time you spent with the CRJ in MSFS 2020 or MSFS 2024?
Mostly in 2024, but both. I’ve not had any issues with the rudder or gear during any flights or steering on ground.
Yea mate I’ve tried everything it does it in 2020 too. Nothing I do does anything it’s just broken now ![]()
Did you try it in a vanilla sim, with no other addons?
No it would take me forever to disable everything. If it don’t work with my add-ons then there’s really no point.
It might be interesting to find out if, and which one, might be causing the problem.
This is quite common for a mod conflict to cause.
Sounds like you might benefit from the AddonLinker tool. That is just one click to disable all your mods. Really useful tool!
Simply rename the Community folder to Community_Back, for instance, and create another Community folder totally empty. It will take seconds to recover your addons after the test.
IT’s extremely poor of you to say do not purchase when SU4 is in BETA.
Lots of aircraft don’t work in SU4 beta because Asobo has messed up the WAsm link. (jetways as well right?).
Very disengenious of you.
I figured out what the problem was. As long as I don’t turn on the weather radar everything is fine.
So you would have third party devs fix their aircraft in SU4 beta, not knowing anything about the beta development process, and most likely break the aircraft for everyone in the commercially released and documented SU3?
I don’t think that would be a very sensible outcome do you?
my recommendation is always to leave the beta if an aircraft you really want to fly is affected by “features” in a new build. I have done that several times - but you really cannot ask the aircraft developers to do anything until there is a full commercial release…
BTW I’m flying the CRJ in the latest SU4 beta with no issues at all so I suspect the latest beta build has fixed many aircraft issues…
Left the beta and the A/C works now. I would say Microsoft/Asobo needs to put a big disclaimer on their marketplace for anyone buying product that are flying in Beta so folks know they assume the risk when this is the case.
Not sure about disingenuous given I was honest about the scenario, however, as I mentioned to the other individual who replied specifically to me, I left Beta and the CRJ works as intended. Microsoft/Asobo should warn everyone running beta that if you buy A/C while in beta they may not work and that each person assumes that risk.
The statement you agreed to when joining the beta: “This means that users may experience issues, including but not limited to, occasional crashes and data loss”.
Nothing is guaranteed to work properly in a beta.
I’m having all kinds of trouble with it in MSFS 2024 SU 3. Tablet does not work. Left engine will not start. Don’t know what else is wrong because I can’t get past that.
