Can I be sure, that when on MSFS startup the external simconnect interface becomes available, the standalone WASM modules already have been initialized?
Thanks a lot!
Can I be sure, that when on MSFS startup the external simconnect interface becomes available, the standalone WASM modules already have been initialized?
Thanks a lot!
Anyone some information?
Hi,
SimConnect server initialization and its dependencies happens “lately” in the boot process. That means that messages, sent by an external process or an standalone module, are queued and will be processed later (once the server is opened).
This means that depending on when you start your external process, the number of package in your community, the number of standalone module you have, if you need to recompile a standalone module or not… a simConnect connection can be started before another.
Best Regards
Maxime / Asobo
Hi Maxime,
thanks a lot. I can follow that behavior now also in the simconnect logging. During startup at some point in time the simconnect endpoint becomes available for clients. But no messages are executed (apparently they are queued as you wrote). At some later point in time 10 to 20 seconds later on my system simconnect message processing starts and also the simconnect_onrecvopen callbacks are sent. The processing starts with the queue.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.