FSUIPC crashed (7.5.5a - beta version)

[John Dowson]

11 minutes ago, kaha said:

I understand. But I'm not pressing any buttons before the flight is loaded. Maybe some USB devices send some button states anyway?

Maybe - could be due to the initial button state scan...

12 minutes ago, kaha said:

This never happened before 7.5.5d September 7th.

Then I think this is because of the change I made to allow repeated LuaValue calls with the same parameter - but I'm not sure how this change could cause this error!
I have disabled Button actions before everything is initialized in the attached version.

John

FSUIPC7.exe

[kaha]

Thank you John, I'll test.

[kaha]

Seems to work. Let's see if it returns.

[kaha]

It "crashed" yesterday when I listed LVars. I was checking some things and hadn't switched on Buttons and Keas log at that time.

I got the window you see in the screen shot and had to kill it, there was no crash dump.

Karl

FSUIPC.zip

[kaha]

This might be helpful?

FSUIPC_evtx.zip

[kaha]

Today it crashed. I was about to show input events in the FSUIPC GUI. Same aircraft as with the incident yesterday. Same .ini file. 

Karl

 

FSUIPC7_crash_20250912.zip

[John Dowson]

These crashes were related to the logging of the parameter type for input events. According to the documentation, this can be either Float64 or String, but, as far as I know, only Float64 types have currently been implemented/are available. I request the parameter types for all input events received, but it looks like I am only getting a response for some of these, leaving the other unitialised. It is these uninitialised ones thar are causing a memory error/exception due to a buffer overrun.

I have corrected this in the attached (by setting the default parameter type to 'Unknown'). As the parameter type is also not really useful for end users (it is always a number!), I have removed the logging for this, unless you have set logging for Extras or Input Events.

Please find the updated version attached.

Regards,

John

FSUIPC7.exe

[kaha]

Thank you, I'll test and get back to you.

[kaha]

John, this one gets deleted by Defender.

Karl

[John Dowson]

47 minutes ago, kaha said:

John, this one gets deleted by Defender.

This happens due to a Windows virus definition update causing a false positive, and its continually happening. It happened in an update a few days ago, but another definition update the same day fixed the issue. If they don't update to fix  this in a day or two, I report it and it tends to get fixed in a subsequent update a day or 2 later.

I have just checked and I also now get that here - and there have been 2 updates today. You can use the attached, which isn't compressed (its the compression of the exe that seems to trigger this): FSUIPC7.exe

If this isn't fixed by Microsoft in a day or two I will report (again).

John

 

[kaha]

Works. And doesn't crash anymore.

[kaha]

On 9/7/2025 at 8:16 PM, John Dowson said:

The only anomaly in that log is when trying to set/execute an input event that doesn't exist:

 

I was able to reproduce it. Sometimes (not very often) when assigning input events to a button the available events in the drop down list are doubled. So each entry is there twice (will make a screenshot as soon as it happens again).

If I then select one of the two it might be the one that results in the 'Cannot execute empty Input Event' message.

[John Dowson]

5 minutes ago, kaha said:

I was able to reproduce it. Sometimes (not very often) when assigning input events to a button the available events in the drop down list are doubled. So each entry is there twice (will make a screenshot as soon as it happens again).

Thats strange, but a screenshot is no use - I believe you. I would need to see your log file, generated with logging for Input Events enabled. If you close an open the Assignment window, is it then ok? If so, its something strange happening with the pop-up menu population and the log file is probably of no use.

7 minutes ago, kaha said:

If I then select one of the two it might be the one that results in the 'Cannot execute empty Input Event' message.

No, I don't think this can be the cause. When you get this error, try listing the available Input Events - is it there?

[kaha]

Attached is the log file with this error message. Logging for Input Events was enabled.

Here's what I did: I use some potentiometer axes as input for cabin air levers or heat levers by using 'Send to FSUIPC Offset' and then taking care of it in a lua script using event.offset. Some aircraft have variable levers and some have just 2 positions, on and off.

For those with 2 positions I use the 'virtual buttons' (offset 0x3340). I was about to assign a potentiometer low and high values to a off/on of a virtual button for controling carb heat (AUXILIARY_CARB_AIR). This didn't work, it generated the error message.

I assigned the input event to a normal switch, this worked. I then tried to reassign the input event to the virtual button and was presented the drop down list with each event shown twice. I selected the second one of the two AUXILIARY_CARB_AIR events and it worked. Another look at the drop down list showed a normal list with each entry only once listed.

The attached .zip file also includes the .lua file I use for those potentiometers.

FSUIPC7.zip

[kaha]

Something seems to be wrong. After restarting the sim and FSUIPC I'm again getting the error message for the carb air input event. I switched button &keys and InputEvents log on, here's the log file.

This time only the Carb Air input event shows twice in the drop down.

Karl

 

FSUIPC7.zip

[kaha]

For real hardware buttons the drop down shows the CarbAir only once, for the virtual button it's shown twice.

Reassigning the first of the two to the virtual button doesn't change anything, but reassigning the 2nd makes it work. After that the drop down list is ok again.

Karl

FSUIPC7.zip

[John Dowson]

16 hours ago, kaha said:

Attached is the log file with this error message. Logging for Input Events was enabled.

17 hours ago, kaha said:

For those with 2 positions I use the 'virtual buttons' (offset 0x3340). I was about to assign a potentiometer low and high values to a off/on of a virtual button for controling carb heat (AUXILIARY_CARB_AIR). This didn't work, it generated the error message.

You are getting these '' Cannot execute empty Input Event' messages as you are trying to use them before they have been found/received by FSUIPC7. I can't tell from your log when the input events are initially found/received as these messages are not in your log for some reason, e.g. from my log:

Quote

...
    21265 InputEvent found: 'UNKNOWN_MOUNT_CUP_EFB_VISIBILITY_HIDE' with hash=15237142074348370721 [type=0]
    21265 InputEvent found: 'AIRCRAFT_DOOR_WINDOW' with hash=1824284457481133066 [type=0]
    21265 Subscribed to InputEvents (233 found)
    21265 **** Adding Input Event 'HANDLING_Yoke_Hider_1' to offset 0xA020
    21281 -------------------- Starting everything now ----------------------
...

Not sure why you haven't got his logged - did you set Input Event logging later, after starting FSUIPC7? You will get this message if you try to use an input event before it is known/has been received by FSUIPC7.

I just think you need to give it more time before you try and use Input Events - and you can only ever use these (in the assignments window) when an aircraft is loaded and ready )i.e. not when in the menu system).

16 hours ago, kaha said:

Reassigning the first of the two to the virtual button doesn't change anything, but reassigning the 2nd makes it work. After that the drop down list is ok again.

Not sure why there are two entries. I will look into this at some point, but this is low priority I currently have more pressing things to do. I will look into this when time permits.

I would like to understand why you aren't getting the other log messages about input events though. If you are getting a 'received' message, this indicates that the input event was found, but this isn't being logged for some reason.

John

[kaha]

Right, I enabled logs later on.

Attached please find a new log where logs were enabled at the beginning. I waited for a long time but the error didn't go away. I then reassigned using the 2nd of the two and it worked.

Not sure how long I should wait.

(I don't know where the trigger of the ambient light input event comes from that fills up the log).

Karl

FSUIPC7.zip

[John Dowson]

Thats a better log and does show an issue.. When you profile is initially loaded, the input event is not known. The inputs events are received after the profile is loaded, but the loaded profile isn't updated - it is only updated here:

Quote

   562906 [Buttons] now profile-specific:
   562906    0=P72,12,CILIGHTING_LANDING_LIGHTS,1.000000
   562906    0=P72,12,CILIGHTING_LANDING_LIGHTS,1.000000
   562906    2=P72,0,CIELECTRICAL_BATTERY,1.000000
   562906    2=P72,0,CIELECTRICAL_BATTERY,1.000000
   562906    4=P72,2,CIELECTRICAL_AVIONICS_MASTER,1.000000
   562906    4=P72,2,CIELECTRICAL_AVIONICS_MASTER,1.000000
   562906    6=P72,9,CILIGHTING_NAVIGATION_LIGHTS,1.000000
   562906    6=P72,9,CILIGHTING_NAVIGATION_LIGHTS,1.000000
   562906    8=PD,0,CL16:V,30
   562906    9=PD,1,CL16:V,-30
   562906    10=PG,8,CL16:V,130
   562906    11=PG,6,CL16:V,-130

and so after this, the assignment to the input event works. I am not sure what caused the profile to be reloaded here, but they are reloaded when you open/close the assignment panels, so that may be it.

This also explains the double entries in the menu. When you see this, the input events are loaded (hence visible), but the input event is not linked to the button assignment, so another entry is added.

Previously I was reloading assignments when input events are received from MSFS, but this was disabled as it could occasionally write an empty assignments section (basically removing all assignments), so ?i removed this. I have reenabled this in the attached version, and tried to correct the writing of an empty section. So please try this version, but also please take a back-up of your ini file(s), just in case (although you should have a back-up in your backup-ini folder, as inis are now backed-up on re-installation).

 

1 hour ago, kaha said:

(I don't know where the trigger of the ambient light input event comes from that fills up the log).

Like standard events, some aircraft continually emit some inout events. You can ignore these by adding the following to your [Profile.C172_Carenado] section in your FSUIPC7.ini:

DontLogTheseIE=VARIABLE_AMBIENT_LIGHT_UPDATE

Let me know how it goes with this version,

John

FSUIPC7.exe

[kaha]

Thank you, I'll test it as soon as Defender allows.

Karl

[John Dowson]

8 minutes ago, kaha said:

I'll test it as soon as Defender allows.

Allow it - its a false positive, as always....

[John Dowson]

The uncompressed exe is also now getting flagged/blocked. I have reported to Microsoft.

John

[kaha]

It doesn't let me, it deletes it anyway although I tell Defender to allow it on my system.

[John Dowson]

Just now, kaha said:

It doesn't let me, it deletes it anyway although I tell Defender to allow it on my system.

You have to go into protection history and restore from there.

[kaha]

Sorry, I don't know how to do it.