These are the Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Notifications

Clear all

FSUIPC7 log around an uncommanded dual engine shutdown (Fenix A320, MSFS 2024) - help reading it?

micromoon · 2026-10-06T11:11:56Z

Hi John,I'm chasing uncommanded dual engine shutdowns in MSFS 2024 that I've seen in the Fenix A320 and the Aerosoft A346 Pro. Because I had event, axis and button/key logging switched on, FSUIPC7 recorded the moment it happened. I have no buttons, keys or axes assigned in FSUIPC. The only script is the Lua callout script PMCO_FNX32X, started via [Auto]; I checked it and it contains no ipc.control, writeLvar or other write calls, it only reads values. I would appreciate your view on the log, as you can read it far better than I can.Setup: FSUIPC7 7.5.8, MSFS 2024 1.8.16.0 (MS Store), Fenix A320, WinWing URSA MINOR 32 Throttle Metal R and Joystick L with SimAppPro2 0.1.10 (Fenix support active), ChasePlane, VR with Meta Quest 3 via Virtual Desktop.What happened (4 Oct 2026, local time CEST):- 17:08:24 a number field in ChasePlane's camera window got the cursor; MSFS blocked the sim inputs. I typed a value (your log shows Backspace, 0, ., 1 and arrow keys).- 17:08:50 the field lost focus and MSFS released the input block. In the same second the Fenix log shows "Engine control 1: Master switch off", and at 17:08:52 both engines cut off. Parallel 42 checked their logs and confirmed that ChasePlane sends no aircraft command at that point.What I see in the FSUIPC log (excerpt attached, unmodified lines, time base explained at the top):1. No button or key event at all around 17:08:50.2. 17:08:50.5 to 17:08:51.0: LIGHT_POTENTIOMETER_SET 32/33/34 to 0 and LIGHT_POTENTIOMETER_13_SET going 7, 2, 0, all logged as AXIS.3. 17:08:52.2: TOGGLE_FUEL_VALVE_ENG1 and _ENG2, which I take to be Fenix shutting the engines down after the master switch change.4. The same light potentiometer pattern (rising this time) appears at 15:07:08, exactly when the Fenix log also shows "Master switch off" (on the ground, engines off).5. Throughout the session SPOILERS_ARM_SET, FUEL_SELECTOR_LEFT and FUEL_SELECTOR_2_RIGHT arrive about every 100 ms, and after the shutdown FUEL_SELECTOR_RIGHT takes over.For comparison: on 6 October I repeated text-field focus/release tests (Microsoft EFB, Fenix EFB, ChasePlane) in 2D, on the ground with engines running, without typing. No shutdown occurred, and the light potentiometer pattern did not appear. The original incident was in VR, in flight, and involved typing beforehand.My questions:1. Can you tell from these logs whether FSUIPC or the running Lua script issued any engine, fuel or mixture control? Which possible input paths would not be visible in this logging?2. Does "AXIS" for the LIGHT_POTENTIOMETER events mean they came from an input device, or can it also be a SimConnect client or WASM module sending them?3. Is there a way to see which client sends the controls repeated every 100 ms?4. Is there a logging option that would capture L:var writes (for example a WASM module writing the Fenix engine master variable), so I can see where the switch change comes from next time?Related reports with videos: MSFS DevSupport: Aerosoft forum (A346 and Fenix):I'm not a programmer; I analysed this with AI assistance, but all observations are from my own flights.Thanks a lot!

Page 2 / 2 Prev

Posts: 383

FSUIPC Support

Moderator

October 8, 2026 2:49 pm

(@fsuipc-support)

Joined: 12 months ago

If you have an entry in the FSUIPC7.log file that shows the shutdown commands, to determine which application this comes from (if indeed it comes via SimConnect) you need to activate and look at the SimConnect.log file. However, this will only help if the event is being triggered via SimConnect though. If its coming directly from a gauge or js code then this won't be reported in the SimConnect log file. Some aircraft do use The SimConnect interface internally, and also via WASM, so it may help.

If you want to try this, first activate the generation of the SimConnect log file. To do this, see:

https://fsuipc.com/community/fsuipc-faq-other/logging-simconnect-when-request-by-fsuipc-support/.

Once you have a simconnect log file, you need to find the entry in the log file. This can be difficult... Maybe try this application that helps interrogate the simconnect log file:

https://github.com/bm98/SConnectLogReader

Note I have been meaning to try this app but have not yet done this...

I also found your posts in the MSFS dev support forums and Aerosoft forums and have put the links to these back into your original post. Reading these, it seems that this is either an issue for Asobo or the aircraft developers and is not related to FSUIPC at all, although you can still use FSUIPC's logging facilities to see this happening.

Sorry I can't be of more help. Please update this thread if you find the solution or any further information regarding this issue.

Regards,

John

Posts: 4

micromoon

Registered

Topic starter

October 8, 2026 7:00 pm

(@micromoon)

Joined: 5 days ago

Next chance at the weekend, I think. 😅 I´ll be back. Thank you! 👍

Page 2 / 2 Prev