vanislepilot

Just the one VPC panel. What do you recommend in terms of “ignoring” it? Disabling that entry somehow or just continuing as is? Thanks! Troy

Looks like I'm back in business, John! I connected the parking brake again and noticed that JoyID was registering it as controller 13 upon connection. Assuming this was the status quo leading to the problemc, I decided to skip the 13 slot and I swapped it into 14. Ran FSUIPC with your debug code and this is what I get... As far as I can tell, everything is looking good now! Thank you again for all the effort you've put into helping me - it's greatly appreciated! Regards, Troy FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

https://www.desktopaviator.com/Products/Model_2400/index.htm It’s a plug and play device, so I didn’t install any drivers manually. I’m assuming Windows drivers. I will give your steps a try later today after I return home. Many thanks Troy

If you are having issues getting the Fenix A320 V2 nosewheel steering to work, ensure you delete all 'SteeringTiller' lines in FSUIPC7.ini file under the [JoystickCalibration.FENIX A320] (or whatever you have named it) section. This solved it for me.

No luck with this either. Still results in the attached... Regardless, thanks for the help. FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

No joy with the above procedure. Please see attached. Thanks, Troy FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

Connected the parking brake and this is what we get... looks like the errors are back. Didn't touch the ini file. FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

Understood. Just before starting your procedure, I disconnected the parking brake and replaced the ini with the last working, and it seems that all is fine, but without the parking brake. And yes, I am still using the ThrottleTek. I believe it was accidentally disconnected which is why it didn't appear in the last ini - apologies. These are the files with the last working ini and parking brake disconnected. Not sure about registries but all seems to be fine in terms of programming each controller with FSUIPC. Should I proceed with your removeDevices procedure or attempt to turn on the parking brake again and see what we get? Thanks, Troy FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

Hi John... the "preferred set-up" was just a list I kept of the assignments that we sorted out last time with the last working ini (prior to adding the new parking brake controller). By maintaining those letter designations for each controller, it ensures that my aircraft-specific calibrations will correspond the correct control. After noticing several controllers were assigned duplicate letters, I was starting without an ini file, allowing FSUIPC to generate a new one to see what a fresh start would achieve. Please see the new files you requested as per above attached. FYI, these are the assignments from the last working ini file prior to running it in FSUIPC: Thanks for your continued help, Troy FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

John, Unfortunately I have to request your assistance on this one again, as I'm encountering the same problem. I believe your solution works; however, I added a parking brake controller to my setup recently, as the brake handle on the ThrottleTek broke internally. I seem to recall the addition of new hardware to have consistently caused this issue in the past. Fortunately aside from this case of replacing broken hardware, my set-up is "feature complete". With this new addition, my Agronn yoke is now missing from the list of controller IDs. My preferred setup is as follows: JoyName Device A AGRONN B737 Yoke V2.2 B Joystick - HOTAS Warthog C Cat3Design A320 Capt Tiller V2 D T-Pendular-Rudder - Capt E VPC Panel #1 F Fulcrum One Yoke G T-Pendular-Rudder - FO H LEFT VPC Stick MT-50CM2 I J Landing Gear Lever K Cat3Design A320 FO Tiller V2 L Throttle - HOTAS Warthog M throttleTek 3 and the new parking brake could be whatever. As before, I did notice a duplicate ID in one of the T-Pendular rudders this time, so I followed the removesDevices steps, but it seems like there is still a duplication problem. I will be away for a bit, so I will not have time to test whatever you send my way for some days. Thanks in advance for your assistance. Regards, Troy FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

All looks good John - many thanks. I hope that wasn't too painful and you sure saved me a lot of work! Attached are the files you requested. I was not using VPC or Gear Lever with FSUIPC. I just remapped a few L throttle commands to M (throttleTek) as a that was the correct one for my setup. Many thanks again! Troy FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

Not sure if it helps for your analysis, but for my rig set-up, I have dual controls (i.e. two physical controllers) for both of: - Thrustmaster Pendular Pedals -CAT3 Tiller (for some reason it is showing up as an FO tiller twice) ... for left seat and right seat etc Edit: Attached is a "clean build" ini file after the regedit... FSUIPC7.ini

Current update: Unfortunately, I saw your update too late, but it looks like fixing the registry for the ThrottleTek solved the "roving" detection failure issue. I am now registering axis movement on all controllers. I replaced the ini file I sent you with the backup I had of all my programmed controls, and then re-ran FSUIPC, so all of the assignments appear to be mismatched and I'll need to fix those, but hopefully it'll give you what you need for the ini update you mentioned? Many thanks Troy Original draft of response (prior to removeDevices): Correct. When moving axes and selecting buttons, simply nothing appears, although as you said, FSUIPC has detected the controller (just not registering axis and button use) To verify my ini file wasn't corrupted in any way, I deleted my original and let FSUIPC build a new one (which is why there are no assignments). All I did was start FSUIPC and then close it in the files I sent you, so not sure what is causing all the device scanning. FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv

Hi, I have a fairly extensive home cockpit setup with several USB controllers, and for a while, I had noticed that FSUIPC was no longer detecting axis movement and button presses on my Thrustmaster Warthog Throttles. I made do, and after a recent update (I updated Windows and FSUIPC to the latest release version), the Warthog Throttles movements were detected by FSUIPC again. However, at that point, I noticed that one of my CAT3 Design tillers was no-longer detected when attempting to move the axis and pressing buttons. I removed both tiller devices from the Windows devices app and then reconnected them, and now I find that they both are detected by FSUIPC but my Thrustmaster Warthog Joystick is now no longer detected. Hence this "roving" detection failure. The problem appears unique to FSUIPC, as Windows detects all controller axis moves and buttons presses, as does MSFS and spad. I have already tried using JoyID as recommended in your FAQ, to no avail. Thanks in advance for any help you can provide! Regards, Troy FSUIPC7.ini FSUIPC7.log FSUIPC7.JoyScan.csv HIDscanner_log.txt

EDIT: Looks like this was an issue with LVars not loading currently. Working fine now. Is it just me or are the 64D6 ELEC_BusPowered[16] offsets no longer returning the appropriate value? I had some Lua scripts based off of those and I notice they are no longer working.