EisernUnion

yes, mine has the 1st Nov .... will reinstall and hope 🙂

I have the same issue since updating to 7.4.18 .. already followed any vcruntime troubleshooting guide, also the remarks in the readme... ; windows updates are paused, so there is nothing other updated in between... FSUIPC has crashed 2 times today, 5 times yesterday.... the reinstall of the vcruntime was done yesterday ... i have no idea what raises up this issue..... And @John Dowson : Its not the error about a missing VCRUNTIME140_1.dll ... its a memory access error Name des fehlerhaften Moduls: VCRUNTIME140.dll, Version: 14.40.33816.0, Zeitstempel: 0x7d65c186 Ausnahmecode: 0xc0000005 Fehleroffset: 0x00000000000111fb ID des fehlerhaften Prozesses: 0x0x733C Startzeit der fehlerhaften Anwendung: 0x0x1DB315041059C78 Pfad der fehlerhaften Anwendung: C:\FSUIPC7\FSUIPC7.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Berichtskennung: 396e3f8e-a1ba-4be6-b4fb-f29d5766bc6a Vollständiger Name des fehlerhaften Pakets:

Today is one of those days wasm module wont keep alive .... third msfs restart and silently dies ... like the last time we discussed this issue... it was running fine the last days since 7/27 .... nothing changed, nothing installed etc.... 20240813_FSUIPC7_prev.log20240813_FSUIPC_WASM.logFSUIPC7.log20240813_FSUIPC7.log

Hi, dont know what is going one since a couple of versions .... The WASM Module is quite unstable and "dies" to easy .... 5 Min within MSFS and it quits its service.

Start thinking im just to dumb to get it work with the fenix ... but its doing really strange things... and at the end what makes me thinking im to dumb to get it work.... why is a "big player" tool like FCR not working and SkyDolly does its work pretty well ....

The current working is 7.4.13a, will replace it with b

Just a quick note: Since i started to log with the file you provided .... no crash happend.... i stopped creating trace logs now... crazy ....

ok... first flight done so far no error ... but.. will see....

Will make this changes and continue logging.... yes, it stops anytime later ... i have no idea when, today it was on the second leg after the first leg EDDH-LOWS at some point on the second flight from LOWS-EGNT. After arriving in EGNT i restarted MSFS and now im flying Touch and go's at EGNT, this msfs session is running for 1:16 min now and still everything is still working. Im thinking about how to monitor the status of the wasm module to notice the silent die of it and try to figure out if something else had i did at this time and might had an impact on it

Same as yesterday evening.... as i wanted to turn on landing lights at FL100 stopped working .... wasm debugger flagged it again as "dirty" and is not working anymore. FSUIPC7.log

First thx for your support .... Second: Stopped working again... .... recognized it when i was about to switch off landing lights, TO lights and didnt respond after touchdown ... touchdown was at 20:06:48z ... last entry in wasm log 19:54:41z ... (nothing happend, nothing noticed while on final... just after landing as the buttons not responded anymore) FSUIPC7.log FSUIPC_WASM.log might be nothing, but dirty sounds not so good at all ?!

So far, finished another flight, engine shutdown and still everything works (still).... maybe i re-enable both of the functions in the lua script and will check if the error occurs again.... but, all 3 scripts were running without issues for "years" until some days before... 😕 Computer ^^ (says no)^^ 🙂

i noticed it because on my streamdeck the gsx options went black .... no more access to gsx... other buttons also stopped working which are reliaing on lua scripts i commented 2 functions out in on of the lua scripts, afterwards it works .... but... whats the reason this error occurs when shuting down engines and not before.... strange i added some logs ... FSUIPC7_prev.log FSUIPC7.log FSUIPC_WASM.log FSUIPC_WASM_prev.log

Here are the files with your testing exe..... included Autostart -> no Lua working & Back to main menu restarted flight -> no lua working will add the last use case "exit fsuipc" and restart manually -> no success .... the wasm at addons is still at "enable" set and not running logs_usecase 1,2.zip usecase 3.zip

Lua silently died just when arrived at the gate and shutdown engines ... instantly no lua is working anymore .... it was still the release version. ... not the one you provided .... its really strange .... instantly on shutdown, at the same time i would say.... the lua logs stopped 20:06, fuuipc.log a moment before 19:59.... shutdown was exactly at 5/28/2024 8:04:52 PM * Engine control 1:cutoff the lua.logs are to big to attach... only the tiny lua file is possible to attach The "addon" -> WASM -> "disable" -> "enable" dont work ... after disabling not possible to enable it (the last few lines in the log ) FNX320_LIGHTS.log FSUIPC_WASM.log FSUIPC7.log