Loosing controller input in flight

[Chad P]

Hi,

I've this problem, I don't know if it's FSUIPC realated or Sim, but it occurs twice after the last FSUIP Update. All my axes are calibrated and assigned into FSUIPC and not in the sim anymore, this worked for 4 years. But after the last Update the rudder Axis won't work sometimes (suddenly)

Yesterday It ruined my flight becuase I've had a crosswind landing at hat no rudder input.

Also there was a strange FSUIPC error after I quit my last flight. FSUIPC was still in the process manager without the sim and taking all CPU resources, I've had to kill the process manually.

Log File attached

FSUIPC7.logFetching info...

[Kimchi]

Same here. Got all buttons mapped within 7.5.0. I start the flight and during secure cabin checklist the flaps lever work. And after engine start, suddenly I loose all buttons on the throttle device. Its random with devices. Now its the throttle device, tomorrow it can be another device. This happens since 7.5.0

[John Dowson]

  On 12/16/2024 at 6:40 AM, Chad P said:

All my axes are calibrated and assigned into FSUIPC and not in the sim anymore, this worked for 4 years. But after the last Update the rudder Axis won't work sometimes (suddenly)

Expand  

Can you please also show me / attach your FSUIPC7.ini file.
Your log shows some issues with a lua script:

  Quote

 20082078 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082188 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082297 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082407 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082516 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082625 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082735 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082844 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20082938 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20083063 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20083172 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20083266 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20083391 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20083500 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value
 20083610 *** LUA Error: D:\Sim Tools\FSUIPC7\PMCO_FNX32X.lua:341: attempt to perform arithmetic on a nil value

Expand  

Could you also attach that script please.

If you exit FSUIPC and restart, does it then work or not? if not, can you exit MSFS and also attach your FSUIPC_WASM.log file.

  On 12/16/2024 at 6:40 AM, Chad P said:

Also there was a strange FSUIPC error after I quit my last flight. FSUIPC was still in the process manager without the sim and taking all CPU resources, I've had to kill the process manually.

Expand  

Then I need to see the log file from that session - the one you attached shows that FSUIPC exited normally, so I presume that was from a different session, no?

  On 12/16/2024 at 11:07 AM, Kimchi said:

And after engine start, suddenly I loose all buttons on the throttle device. Its random with devices. Now its the throttle device, tomorrow it can be another device. This happens since 7.5.0

Expand  

So if one device stops working, does the other still work? Is it just assignments to presets/lvars that stop working, or all assignments? If you exit and restart FSUIPC, does it then work or do you have the same issue? Please supply further info, add/attach your log and ini files and check to see if the WASM has crashed or not (exit MSFS and check to see if the WASM exited cleanly or not in the WASM log file).

John

[Chad P]

FSUIPC7_prev.logFetching info...

Here are additional files.

I've no FSUIPC_WASM.log File. Where can I find it? Or do I have to enable it?

FSUIPC7.iniFetching info... PMCO_FNX32X.luaFetching info... Fetching info...

[Chad P]

  On 12/16/2024 at 12:20 PM, John Dowson said:

If you exit FSUIPC and restart, does it then work or not? if not, can you exit MSFS and also attach your FSUIPC_WASM.log file.

Expand  

Yes it works after a restart.

[John Dowson]

The last log file you attached when FSUIPC was still running - please exit FSUIPC before attaching any files.

  On 12/16/2024 at 1:56 PM, Chad P said:

Yes it works after a restart.

Expand  

Ok. The next time this happens, can you open FSUIPC and go to the axis assignment panel and see if your axis is recognized.
Can you also check the USB hub settings (in windows device manager) and make sure 'Allow the computer to turn off this device to save power' is unchecked/disabled for all your USB hubs and devices. Also check if its a USB-2 device it is connected to a USB-2 port, and if its a  USB-3 device its connected to a USB-3 port.

[John Dowson]

You also have an unrecognised device:

  Quote

A=<< MISSING JOYSTICK >>

Expand  

You have re-assigned to this as device  C. You should remove all assignments to device A and remove that line, i.e. these:

  Quote

0=AX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=AY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=AZ,256,F,65765,0,0,0    -{ TO SIM: AXIS_THROTTLE_SET }-
3=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-

Expand  

John