Well at least I know what the problem is now. Thanks!

I am facing the exact same problem on Windows 11. Pimax Headset (setup as standard device in XP12) and a USB headset. XP12 sound plays on Pimax Headset but TG plays in headset!? Did you get any solution for this issue?

@KAPA-Flyer said in Continued WASM issues in SU4: The Orange Screens are a Sim issue, most likely introduced with SU4 The orange screen was intentionally added in SU 4 partway through the beta to make it easier to identify a WASM crash and the error messages whenever one occurs, so they’re supposed to be there. Whether a WASM crash occurs more often after SU 4…. Well that’s a different matter.

thanks Martyn for letting us know, I appreciate the teams care on this planes. Have further great days to get save into 2026. Dierk Kaller

@AngleofDangle Have you tried checked that you have enough fuel in the tanks? It does that when the tanks are dry.

If I'm understanding your question correctly, and you are using "L:var_AnnunciatorTestButton", for example, which returns immediately, try using "L:var_AnnunciatorTestButton_IsDown". That should work for most momentary L:Var switches/buttons in my aircraft.

It is very much possible that your TRP was blank, that is when you get no A/T. Happened to me earlier. I only experienced this with the RJ85, but not the 100.

After about 5 flights, the most annoying bug so far was the TRP not powering up, thus no A/T, resulting in a flight wasted. My first four flights were in the RJ100, this last one with the TRP issue in the RJ85. I will continue testing the 85, maybe the issue is limited to this variant. It would appear to me that either the variant or tone of the selectable states in the EFB, if clicked, may have to do with the "dead" TRP. During my first four flights I haven't clicked any of the selectable cockpit states in the EFB, just used the aircraft as it loaded into the sim. But on this last flight, I did select the cold and dark state. Before I gave up, I even tried selecting the "Ready for takeoff" state to see if it brings the TRP to life but nope, it does not. A major bug, flight cancelled. I hope this will be quickly fixed.

Nope. Clearly there is a bug here. And as far as I can see people have been reporting it for over a year and all they receive is irrelevant information. It is time to find out that bug causes the TRP not to turn on because it ruins the experience. I would say, there is something with the EFB turnaround states.

After testing, I believe it this is a bug and has to do with the flight states after clicking on them in the EFB. When I just used the state the a/c loaded with I did not have this issue.

TRP did not power up at all. I did exactly as I did during the previous 4 flights - following the "Flying the RJ" section of the manual. No TRP (blank) and no A/T either.

That would be cool. Most modern aircraft addons provide such updates on demand.

I just purchased and installed my Warrior and am having the same issue of not being able to hide the iPad, having tried to click on the suction cup. Any suggestions?

@mikced1976 hi! I find the model pretty good and challenging. What’s there not to like in it?

I bought the ARJ yesterday and I experienced this very issue myself on my last flight, approaching Calgary. The aircraft started to capture the LOC, after I prepared by flying a nice 40-degree intercept angle but it overhsot and continue turning in the opposite direction. I disengaged the A/P and landed manually. Both NAV radios were tuned to the ILS and both were active, with the correct course set.

Solved! The complete correct syntax is: (A:AUTOPILOT VERTICAL HOLD VAR,Feet/minute) Merry xmas!

Maybe tomorrow

I've had this type of behavior on many coupled approaches with a large number of aircraft in FS2020 (still getting 2024 set up). In all cases the "aggressive pitch-down" occurred when I released the AP. For instance, if I maintain coupling all the way to the MAP, the aircraft (could be any of them) will immediately go out-of-trim with a pitch-down (even though it should maintain the trim that was there). I've resolved this for the most part by simply uncoupling at least 100' above the MAP - this usually results in a stable glide path and the trim being spot-on. I've always attributed this to a fault in the MSFS AP though maybe it's an issue with my stick (Thrustmaster T.16000M). I've never had this happen with the Starship, though that may be due to my early AP release procedure.