I am trying to use mobiflight for the inibuilds a350 with the winwing FCU and. I was told I had to list the hardware so Im also using the winwing EFIS L, MCDU, Thrustmaster TCA Throttle and stick, logitech G rudder pedals.
The profile im using has worked before but it randomly does this and the light either are stuck at full, or go completely dark. Simapp pro still sees the inputs and it works fine in the test.
#Waiting for WASM module issue
fiery notch
Okay I have a clue that might be causing this
subtle gulch
Repeat of my message.... You need to find the cause for your panels to be spamming the wasm module with constant actions without the user having moved the knobs. This typically is caused by misbehaving potentiometers. Check your Mobiflight log to try to identify what is the origin of your issue.
fiery notch
Repeat of my message.... You need to find the cause for your panels to be spammi...
I was flying the a350 last night and I tried to adjust the dimness of the screens, in this config I can use the brightness selector on the MCDU which controls all of the screens in the a350. but on this flight I saw that everytime i tried to dim it down, it would automatically go back to max bright. this is the input you are looking for
neat robin
Enable logs in mobiflight and keep an eye out for something repeatedly sending brightness events
hasty sinewBOT
To help diagnose your problem we need to see your MobiFlight logs. Follow these steps to share them: Providing logs from MobiFlight
neat robin
With other people who've reported similar symptoms, it's always a potentiometer somewhere spamming MobiFlight with value updates
fiery notch
I found that key in the mobiflight thing, and I disabled it. this has to fix it, but im still left wondering why it happened now, ive been using this profile for a while with no problem
nevermind, its a bunch of buttons
neat robin
it wouldn't be the MCDU key causing it, it would be whatever was forcing the value back to 100%. Enable logs, fly for a bit, see what happens
fiery notch
it wouldn't be the MCDU key causing it, it would be whatever was forcing the val...
what do you mean by fly for a bit?`can i just stay here at the gate?
neat robin
sure, that could work too
fiery notch
neat robin
just run for a bit in the sim and look at the logs and see if you notice anything constantly sending updates. when you're just parked at the gate not touching anything I wouldn't expect any key events
neat robin
Well that's not great 😅 But also not likely the cause of your WASM issues.
fiery notch
It seems like everythign is sending inputs, not just one
neat robin
upload the entire log, the doc link explains how
fiery notch
Im really sorry im a bit tired its late im just trying to get the flight done so what should i do here
LOG
neat robin
you restarted mobiflight between the screenshot above and sending the logs?
neat robin
Oh
neat robin
Are you using MSFS2024?
fiery notch
yes
after the screenshot where i had enabled logging, i closed out the thing after a few min, opened it, copied the log
is that the correct order
neat robin
I was hoping to see the logs that had the ncalc errors, but whatever.
Please check and make sure WASM is properly enabled in MSFS2024. Sometimes they disable it for no apparent reason. From your logs it looks kinda like it is disabled.
https://docs.mobiflight.com/guides/wasm-module/enable-in-msfs2024/
fiery notch
thank you
how am i supposed to find "event module" it wont pop up by searching and i got 270 items in here
neat robin
The steps in the guide are the way to do it. If you follow each step as written it will show up
neat robin
Post a screenshot
neat robin
And if you search for "event" it doesn't show up?
neat robin
odd. well, try closing MSFS2024 and reinstalling it. https://docs.mobiflight.com/guides/wasm-module/wasm-reinstall/
fiery notch
thanks I will try
neat robin
I have to go for dinner, hopefully that fixes it.
fiery notch
I have to go for dinner, hopefully that fixes it.
enjoy dinner, I just did that, will load in, will check the marketplace, thanks for the help
good so far
thank you again, it worked, thanks to you aswell @subtle gulch