Every time, in the middle of flights, MobiFlight seems to stop transmitting data. The MF Play button remains in play mode. In MSFS 2024, nothing connected to MF works anymore. After some time (for example, approx. 10 seconds), it recovers and everything works normally again. I have been experiencing this for months and just cannot find the cause.
Everything in the bottom bar is green; however, I do not know if that is the case when everything drops out, because in VR it is difficult to trace that immediately while simultaneously trying to save your flight.......
#MobiFlight seems to regularly stop transmitting data.
1 messages ยท Page 1 of 1 (latest)
yeah the log will help. Also did this start happening at some point? What changed in your setup then or just before it? Anything you added / changed etc? Just trying to figure out if there are any clues
I have noticed that the Wasm connection drops out. I have already reinstalled the Wasm module multiple times (after first removing it).
On the first start, I see the Wasm check mark light up green briefly and then immediately turn yellow again.
After a restart, it remains green, but during a flight, it sometimes drops out multiple times and then turns back on after some time (+/- 10 sec.).
Here is a log of the startup just now.
A log of the flight will follow later.
Troubleshooting a constantly disconnecting WASM module caused by noisy inputs.
I looked at your log, something is spamming the "HOLD" command
Looks like it is a potentiometer?
Hmm, strange, the log was created without any controllers connected to the PC. All USB connections were disconnected.
But now that I have connected my controllers, the MF UI log is completely quiet.
And yet, it still won't connect.
You have a vjoy joystick connected
Also since you are in MSFS 2024, it is worth checking to make sure the wasm module didn't get disabled, just to be sure. It can happen even if you uninstall and reinstall it.
https://docs.mobiflight.com/guides/wasm-module/enable-in-msfs2024/
Steps to enable the WASM module in Microsoft Flight Simulator 2024.
Wait! Now I do indeed see Execute Hold in the log.
In my opinion, vJoy didn't trigger anything.
But since nothing else is currently connected, vJou could indeed be the only source of a malfunction....
That's my guess
You have it mapped in one of your input configs
If you disable whatever input config that is, it should start working
Even if not a single controller is physically connected?
In that case, you won't receive any triggers, and no event will be executed in MF, right?
I have now loaded a completely empty profile, and yet Execute Hold keeps appearing in the log.....
Check this before looking at anything else
Yes, vjoy is considered a physical controller
I disabled vJoy. After that, the connection to the Wasm module was re-established.
Now I have enabled vJoy again and it has been working fine for 15 minutes.
I am curious to see if the problem stays away now.
I will let you know.
Thanks for the help so far.
Unfortunately, the problem recurs after a complete restart of the PC, MSFS, and MF...... No Wasm connection again.
If I disable vJoy and re-enable it, it works properly again.
To be honest, I don't really want to reinstall vJoy because it is a nightmare in Windows 11.
What are you using it for?
Maybe the order of start can make a difference? Let MF be the last app loading.
MF is already starting last
Only a few switches for camera views for which there are no simvars run on vJoy.
Edit the vjoy config to remove the axis from the virtual joystick and just leave switches
Been a while since I used vjoy but I believe you can do that, so your virtual joystick consists solely of buttons
@pine wasp hm, do you have the .mfproj file to share?
I am wondering what does "executing HOLD" mean? Is there a config named "HOLD"?
because this is weird, my log shows this:
yours has just
so there is no controller name, just those arrows
execute HOLD happens if you define On Hold and OnLongRelease events I think
but it is weird that it has no name for the device
do you have something that has HOLD defined?
There are some odd xml exceptions in the logs on startup that may be the root cause of the blank controller names
I have now disabled the vJoy driver and the issue seems to be resolved.
The Hold message is now gone and the WASM module is connecting again.
So it really does look like vJoy was the cause of the triggers.
I used the vJoy path mainly for various camera views for which no simvars can be found.
In my opinion, the only remaining replacement for camera function bindings is the Keyboard Input function. I have since taken over a number of vJoy bindings using this. However, some views use Shift with the arrow keys, and that doesn't seem to work......
Is there a solution for this?
Unfortunately, connection drops during flights.
I have since completely removed vJoy and all vJoy bindings in MF. I no longer have any "Execute Hold" entries, yet the connection still drops regularly for a few seconds.
However, I still see a line for vJoy in the log (see screenshot). I cannot find any trace of it in my controller bindings, though. I have checked everything one by one, but it is difficult to trace...
That VJoy message in the log also appears when no controller is connected.
Any idea how I can trace it and get the error removed from the log?
@grave idol Do you have any ideas here? I've never seen those XML config errors before
Does the disconnect happen if you open an empty project and try to fly with that?
It is difficult to determine that 100%, because sometimes it happens after 5 minutes, but sometimes also after 20 minutes....
I have flown with an empty project for approx. 15 minutes now and haven't had any dropouts yet.
However, I am getting the same errors in the log with that empty project. Even that VJoy message is there again (10th line).
This log was created with an empty project and my controller disconnected (USB unplugged).
Those errors as well.
i am not at my computer right now
i have no immediate idea why xml errors are displayed in MobiFlight 11
Okay, thanks.
I will wait patiently.
For this log, you haven't had any disconnects from WASM though, correct?
For this log, did the WASM disconnect?
When sharing logs please be clear about what state it was captured for, so we can look for differences between good and bad cases
Sorry, you're right. With that log, an empty project, and not even any controllers connected, Wasm is not disconnect.
ok that's good progress. Can you upload the project file that does cause the disconnects?
Also load up a project that's causing the disconnects, enable logging, fly until mobiflight stops sending data, then share the log and a screenshot of the main mobiflight window with the connection status dropdown in the status bar open
I don't think the XML errors have anything to do with this
In the meantime, I have performed a completely clean/new MF installation and loaded my project, and now all XML errors in the log are gone. The VJoy error has also disappeared..... It looks much cleaner now.
I am going to test this first.
I really like the emojis in your config names ๐
Thanks.
If you have many connections, it is more quickly recognizable as a result. However, it is a challenge to find suitable emojis.