#Connection to the WASM module

1 messages · Page 1 of 1 (latest)

astral zenith
#

I start Mobiflight together with other MSFS accessory programs via the appropriate Addon-Linker function and occasionally MF remains waiting for connection to the WASM module which I have already tried to reinstall obviously by restarting the SIM.

If I start MSFS and MF directly without using Addon-Linker the WASM is detected correctly.

My question is: has any program been identified that can make the connection between Mobiflight and the WASM module difficult ?

And finally: is there anything I can do to understand what causes this ?
Maybe by activating some tools in Developer Mode.

Thank you

trim violet
#

if you run everything via addon linker when this happens, then close and re-run MSFS2020 (but leave MF running) does that fix it?

arctic oriole
#

If someone installs a cooy of mobiflight wasm it might conflict. Search your addons for .wasm files and deactivate suspicious addons. Maybe you can find a trouble maker.

astral zenith
#

In fact, there are quite a few WASMs in Community folder

trim violet
#

that's fine, wasm is just a file format

#

the only one that mobiflight cares about is mobiflightwasmmodule.wasm

#

since this only happens intermittently when using multiple app launch from add-on linker it's more likely to be some sort of weird timing issue

#

next time it happens restart MSFS2020 and see if that works

astral zenith
# trim violet next time it happens restart MSFS2020 and see if that works

Restarting the sim leaving MF open did not activate communication with the WASM but I deactivated AutoRun and restarted Mobiflight and the WASM was activated.

I'll try again but I already had the impression that AutoRun affected this behavior in my case.

Once the simulator was started, I restarted Mobiflight with and without AutoRun active and if deactivated it always connected correctly.

I'll leave AutoRun off and test.

trim violet
#

it's more likely that restarting mobiflight did it, not the autorun state

#

but interesting that it doesn't always work if autorun is enabled. I wonder if there's a race condition somewhere

astral zenith
#

I have the impression that introducing a small delay to go into AutoStart could improve things.
In any case I will continue to try without AutoStart.

trim violet
#

keep us posted, and if you can isolate it to being related to autostart open an issue in github

#

I checked the code and autorun is triggered when an aircraft change is detected

astral zenith
trim violet
#

it will still cause the event to fire because the plane "changes" when you load the sim, from nothing to the plane you are flying

astral zenith
#

I noticed this in yesterday's sim update 15 changelog:
SIMCONNECT
...

AircraftLoaded system event is triggered later once the aircraft is loaded
...