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

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

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

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

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.

Well no, I was too early. When I copied it to my sim PC it was not immediately deleted. But it got deleted when FSUIPC was about to start. I will try later.

Sorry, ok, Just tried it again and it works now. So if this happens again I just wait until it works, right? Karl

This version again gets deleted by Defender. Karl

Thank you John, that's great! Karl

Ok, thank you. Karl

As an example here are 2 controls: SET BALLOON VENT SET BURNER PITCH AXIS Those can be bound in sim, but I cannot access it in FSUIPC. I don't use any bindings in sim for USB devices except for keyboard and mouse. Every other device (Joystick, Throttle, Pedals ...) is bound in FSUIPC. Karl

Thank you! Karl

Oh, sorry to hear this, take your time! Karl

wnd.font with face WND_COURIER does not result in fixed space font. I use this code: disp_AP = wnd.open("Display on", 3000, 100, 550, 535) wnd.font(disp_AP, WND_COURIER, 10) wnd.text(disp_AP, 5, " Hello") Karl

Works. And doesn't crash anymore.

John, this one gets deleted by Defender. Karl

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

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

This might be helpful? FSUIPC_evtx.zip

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

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

Thank you John, I'll test.

I understand. But I'm not pressing any buttons before the flight is loaded. Maybe some USB devices send some button states anyway? This never happened before 7.5.5d September 7th. Karl

Something else: Starting with 7.5.5d September 7th I sometimes see the following problem. FSUIPC starts up normally while the sim is still in Menu. After loading a flight it seems FSUIPC cannot connect. FSUIPC is alive, I can show the window. Also the sim is responsive. I then exit FSUIPC, restart it and it works normally. Please see the .log file attached. This happens with different aircraft. FSUIPC7.zip

Ok, I see. I didn't pay attention if the sim itself got unresponsive like, maybe, pressing Esc. All my inputs, also all camera view changes are bound in FSUIPC.