John Dowson

Did you get anywhere with this? Logging shows that the governor is using: ROTOR_GOV_SWITCH_OFF ROTOR_GOV_SWITCH_ON and the two ignition switches (magento and plasma) are using: MAGNETO1_SET PLASMA_SET Did you try those? If not working, there are also these Input Events you can try: ENGINE_Governor_Switch_1 ENGINE_Governor_Switch_2 ENGINE_Magneto_1 ENGINE_Plasma_1

Your logs show the elevator trim decreasing in your prev log file, down to -4208, and when you restart it gradually increase slightly to -2788. I would guess its the AP controlling this, and there is not much difference between the values after the restart so I don't think this can be causing the issue. The spoiler offsets remain at 0, so this looks ok, although maybe PMDG aircraft don't use these offsets - I will check the PMDG SDK/offsets to see if there is anything there to log which could be useful. For now, drop those (0BD4 and 0BD8) and add 0BB4. Looks like you didn't set logging for Events and Axis Controls. Can you set logging for these please Were those logs attached when the problem persists or went away? Seems it was restarted quite soon - after 10 seconds or so....

Yes. Yes - remove all entries for scripts not installed. Yes. Or maybe just: I don't know...try listing the lvars to see what is available.

For which aircraft? Try looking for an appropriate preset - check Select for Preset and use the Find Preset... button. Alternatively, use the HubHop search (https://hubhop.mobiflight.com/presets/) to find the relevant preset and then select that from the preset drop down menu. Also, try searching this forum as this question has been asked several times before...

Yes, it looked like a software driver was missing! Thanks for the update. Cheers, John

@Coast_Flyer I have now received feedback from Spad,neXt and they have confirmed that this issue is on their side - when FSUIPC7 is running, it is sending the keystrokes to FSUIPC7 instead of MSFS2020. They will (maybe) correct this in a future update. I will update again once this has been done. John

No idea! Try the usual things: use logging for Events, open the logging console and see if anything is logged when you activate those in the VC. If anything is logged, try using those events. Otherwise, list the lvars to see if anything looks applicable and try them. Also try listing any Input Events and see if any of those look applicable. Otherwise, as a final resort, use the devmode debugging window to see how these work in the behaviors window, as shown in this post: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/. I see this is a freeware helicopter. I can install it and take a quick look, although I am not that familiar with helicopter controls. It may take a day or two before I have time to install this and take a look though. John

First, can you check the power management settings on your USB devices and hubs. Make sue Allow the computer to turn off the device to save power is disabled/unchecked. That is usually the reason for such issues. You also have your axes assigned to multiple devices and multiple axes: i,e you have your ailerons assigned to 2 axes on one Logitech Attack 3 (0), on one axis on another Logitech Attack 3 (2), and another on a device called New (4), which you also have two of. This seems very strange and can cause issues, as each axis can send values on the slightest movement. Better to only assign axes to one controller. Pease check and correct these issues and try again. If you get the same issues, please activate logging for Axes controls and fly with the logging console window open. When the joystick freezes, take a note of the timestamp of the latest log entry before unfreezing. Once you have recovered and finished the flight, zip up the log file and attach it here, with a description of what you saw in the logging console when this occurred, together with the timestamp. John

It does not get added automatically - you must have added this, and it is also in your ini file for P3Dv4. This won't cause any issues, just log a message. Probably due to a windows or driver update. Nothing to worry about. Well, any errors are logged with the line number in your FSUIPC5.log file. You can also set logging for lua plugins, which will log each line executed, and you can send these logging statements to a separate log file if you wish. See the options in FSUIPC's logging tab. It must either be a different script, or you would have had the same issues on your old PC. You said they were in 3 places (always a bad idea!) - maybe you copied the wrong one? No, this would make no difference to this issue, as the issue is missing lua functions. Maybe you copied the wrong ini file as well? That depends....generally not, but, if, for example, you were using GoFlight or PFC devices, then you would also need to install the drivers for these. Your ini also references the following lua files: So they should be present. However, if you are not using any of these (note that ipcReady.lua will always be started automatically) then you can remove the entries. However, do NOT change the index number of the scripts you are using (My320functions.lua) otherwise the assignments to this script will no longer work. Are you also using LINDA? If so, make sure that is installed and up-to-date.

Just show me/attach your FSUIPC ini and log files initially, preferably from a session where you experience this issue. We can add more logging later if necessary. Also check any assignments in the FS, if controllers are not disabled. John

You can't do that...it seems that your device is not recognised, and no manual editing can fix this. Ok. Please update if/when you find a solution. Maybe try a different cable though. There have been previous support issues with serial-to-hid devices due to poor quality cables.

Can you try the attached please: FSUIPC7.exe Hopefully this fixes some issues when starting FSUIPC7 (in various sim states), when restarting a flight (note that luas will be left running, not killed), and when exiting a flight and going back to the main menu (luas killed when plane in parking state, regardless of camera state). John

Dont worry about it - I am working on this at the moment. There are various issues as the data/events being received from MSFS are not consistent. I will post an updated version for you to test, hopefully later today. John

One last thing you could try is running the HidScanner program (available from the Download Links -> Useful additional programs section of this forum) and send me the output. If that recognises your device, then you could use a lua script (HidDemo.lua, available in the Example Lua scripts package) to convert your buttons/axes to virtual ones. But I still think you would be better off getting a solution for your issue from the vendor. Please update if you solve your issue. John

This was because you had a VRInsight section in your ini - I have removed this in the ini file attached below. Looks like the name of your T.16000M Joystick has changed - it was just 'T.16000M' but is now 'T.16000M Joystick'. This is why your assignments to this device were not recognised. I have corrected for this in the ini attached below. if you are having problems with your lua, try debugging them. I they have errors on your new PC then they would have had errors on your old PC, or they are different scripts... In the log file you have the following: The lua errors should be obvious - you are using functions AB_MPL_LightSwitch, AB_OVH_Pushbutton and AB_MPL_LightSwitch which are not defined anywhere. This must also have occurred on your old PC, or it is a different script. And you only have assignments to keys F1, F2, F3, F4, F6 and F7. No assignments to F6 (116) or ctrl (17). FSUIPC6.ini

For future reference, please only attach files (.log files especially) once you have exited FSUIPC7. FSUIPC7 see's no sign of your device. I'm afraid that there is nothing I can do - you will need help from the vendor with this issue. John

Note also thar you can also run FSUIPC7 on client PCs, and have further devices connected there.

Thanks

i think this issue is related to your other issue (luas not being stopped), so I would like to know if it happens with the latest beta I posted in the other thread, and will investigate if it occurs in that, In fact, use the following version, as this has some additional checks/logging around the same code area: FSUIPC7.exe John

The next time this happens, can you please save the event (as a .evtx file) and attach it, together with your FSUIPC7.log file. I may need a crash dump file as well, but I will try to locate this without this initially.... Thanks, John

Add logging for offsets 0BB4 (ELEVATOR DEFLECTION PCT) and 0BC0 (ELEVATOR TRIM PCT) as S16 using the Log->Offsets facility, and maybe also 0BC2 (ELEVATOR TRIM INDICATOR) also as S16. Also activate logging for Axes Controls. When you get the issue and restart FSUIPC7 and everything is working as expected, zip up your FSUIPC7_prev.log and FSUIPC7.log files and show them to me. John Later: maybe also the spoiler positions, offsets 0BD4 and 0BD8 as U32. You can only log 4 offsets at a time, so maybe drop 0BB4.

Can you please try the attached version which has additional logging. Please activate logging for Extras, and send me the log file when this happens again. I suspect this issue is related to a timing issue where the plane parking state is received before the new camera state, but the additional logging will confirm this. Note that if you continue to have such issues, you can set the following in the [General] section of your FSUIPC7.ini file: KillLuasOnSimStop=Yes But don't set this for the time being.... John FSUIPC7.exe

Looks like I missed adding an additional check in the key assignments code that I added in the button assignments code for this issue - sorry about that, Please try the attached version, 7.4.3a: FSUIPC7.exe Note also that when assigning key presses, always Confirm before pressing Ok, otherwise the parameter will not be saved. John

FSUIPC handles up to 16 devices only (vie the windows API, + 3 additional PFC devices). Each device can have up to 12 axes and 128 buttons. FSUIPC does not do anything special with Leo Bodnar devices - they are just seen as another HID joystick type device. Many people use these cards with FSUIPC. Please try the trial license, available from a post at the top of this forum. John

Lua files, by default, should be placed in your FSUIPC6 installation folder. Line 191 is: event.flag(12,"AB_OVH_Ext_LANDING_retract") There is no such function called AB_OVH_Ext_LANDING_retract in the lua file, hence the error. Can you see the assignment to that button in the button assignments window? Can you set logging for Buttons & Keys as well as Events, and show me an FSUIPC6.log file showing your issue. Also, please attach your FSUIPC6.ini file every time you attach a log file - I need to see these both together to determine what is happening. Note that you also have another error in your log file: John