Hey all,  I have a Stream Deck Plus using PilotsDeck. I have gotten basically everything going exactly how I want for my profile with MSFS 2024 with one exception. I can't seem to find the variable address to give me the active frequency on my deck. I went through all the V2 Lvars that were posted on another thread.  I have checked the data logs in Spad.NeXt and can't seem to see any updated Lvars there either. Anyone have an obvious fix I am missing here? Thanks in advance!

Yes. It did not do anything

Did you first calibrate the Bravo via the Xindows joystick utility ?

Good to gather Good info to gather.  I flew another flight from KCOD to KDEN, but had all the simbrief info created from the in game menu (FS2020).  I changed all the W&B from the EFB, imported the weather and whatnot to the FMS, and loaded the flightplan from the FMS.  I flew the entire flight with BeyondATC going, in VR, and had zero issues.  The one thing I did not do was touch the charts tab on the EFB.  Everything worked just fine.  I saw on the navigraph forums that some folks have reported the issue there too, and they claimed that "the dev knows and has id'd the issue."  It looks like it may be the same issue, but reported with the xbox version.  (Problem on CJR V2 - Avionics Plugins - Navigraph)  This is definitely WASM crash symptoms though as you pointed out, but for the life of me, I haven't found a consistent cause yet.  Still have to fly my hops between KDEN and KCYS to test it out, but here's to hoping that it really is known and solution getting ready to implement.  

Hi,   I just got a Honeycomb Bravo yesterday, and am loving it, but noticed a problem with it.   When moving any axis, all the axes start to jitter for about 5 seconds, then stop. (See video) This causes issues in the simulator as the throttle keeps moving even when I take my hand off it.   Is this normal? If it is, is there anything I can do on the software side to help?     Recording 2025-05-10 164441.mp4

Of couse I had forgotten to report back, as promised: The issue I had reported, does not occur with trusty old D-ACNU (Lufthansa CityLine) on MSFS2020. Seems that N324PQ is the culprit in my particular case.

überhaupt kein Problem. Die Gesundheit geht immer vor. Ist doch klar. Freut mich, dass nun alles klappt. Happy Landings

Hallo RON 72 Bitte entschuldige, dass ich erst jetzt antworte. Musste meine Teststunden infolge eines Augenproblems stark beschränken. Nach langem Pröbleln habe ich mich entschlossen den A330 900 neu aufzusetzen und siehe da, es erscheint ein schöner Passgierraum. Im Moment ist alles bestens.   Vielen Dank für Deine Hilfe und freundliche Grüsse   Paul

I got these several times as well. The one that replicated at the same point multiple times was me inserting flightplan manually in FMS after inserting the departure runway and SID if i press exec wasm crash would follow. If i proceed to flightplan page and fill out legs so far it’s been fine.    On last flight wasm crash was en route whilst I was litterally not doing anything input wise so these can happen for different reasons it seems. I basically get it on more or less every flight so currently plane not usable in fs 2024 for me… 

Same error here, has happened 4 times in fs2024