kronovan

Thanks for getting back to me Pete. I resolved the problem and it turns out it was being caused by the Razer Tartarus 2 - not a total surprise because I've found its driver and software on occasions to be problematic. Once I disconnected the Tarturus keypad, ended its Synapse applet and ran FSX, the CH PRO PEDALS USB were correctly enumerated and written into the FSUIPC.INI file. However, when I reconnected the Tartarus and ran FSX again, the Saitek Pro Flight Throttle Quadrant and Saitek Pro Flight Yoke were incorrectly written into the INI as Razer Tartarus devices!? The solution was to reboot my computer and run FSX again, whereupon all of my input devices were written into the INI correctly - including the Tartarus. I had disconnected and reconnected all of my HOTAS devices recently, so maybe that explains what triggered this. As well, the Tartarus' Synapse software got updated this week, so maybe that was the cause. All my USB devices with the exception of the Tartarus are connected to a single, powered USB 3.0 hub. Situations where I encounter a problem with a USB device not being recognized have been far more rare than common.

I started up FSX:SE last night and discovered that my CH PRO PEDALS USB are no longer mapped. When I accessed Addons > FSUIPC and clicked [Axis Assignments] , nothing was listed when I moved my pedals - same for the toe brake axis. Even when I did a rescan nothing is detected for rudder movement. So I checked the FSUIPC.INI in my ..\FSX\Modules\ folder and noticed that my CH PRO PEDALS USB aren't even listed in that file's JoyNames section. This is what's listed: I created a backup copy of that INI file a weeks back, as I was considering editing some of my profiles, but never did make any changes. This is what the JoyNames section looked like then Note the error though, in that the CH PRO PREDALS USB and Saitek Pro Flight Throttle Quadrant are listed with the same GUID. I did disconnect my Thrustmaster T.16000m around that time, as I'd just gotten my Saitek Pro Flight Yoke and was short a USB cable, which is why it isn't in that list. Not sure why my Razer Tartarus V2 is no longer listed, but I never configure it internally within any flight sim anyways. I also found a file in the \Modules folder called FSUIPC4.JoyScan.csv and opened it. I noticed that my CH PRO PEDALS USB are listed in each of the 3 sections and have confirmed via the Windows Registry that the VID and PID values for the CH PRO PEDALS USB are correct. I'm not sure of the other long hex value (I'm guessing that's the GUID), as there doesn't seem to be an equivalent of it in the registry. I should probably mention, that all of my USB devices (including rudder pedals) are working correctly when tested from the Windows 10 - "Devices" > "Devices and Printers" > "Game Controller Settings" > "Properties". As well my CH PRO PEDALS USB are being recognized and working correctly with X-Plane 11, IL-2 Cliffs of Dover and the IL-2 Battles of Stalingrad flight simulations. So I'm wondering what I need to do to get FSUIPC to recognize my rudder pedals again? Could it be a simple as renaming that FSUIPC4.JoyScan.csv file and then stating up FSX? Any help in getting this resolved would be much appreciated. [Edit] Just realized, I should have also mentioned that with FSX started, I can access Settings > Control > [Axis] and successfully map my CH PRO PEDALS USB to the rudder axis - which I then immediately delete. I checked axis mapping from that same FSX form for all of my USB devices and none of them have any axis mapped.

Many thanks for the reply Pete. I didn't really grasp all of the explanation in the manual about the different throttle tabs, such as 4 throttles, so I'll go back and reread that section. Indeed the To for the Throttle Incr (full forward thrust) would be the max for the particular lever. I'd dearly love to assign more than 1 lever for engine control, because some of my aircraft such as Aerosoft's DHC-6 Twin Otter are next to impossible to fly without 2 quadrants. Alas I only have a single throttle quadrant with 3 levers; throttle, prop & mixture. I also use a joystick instead of a yoke, as I also fly a number combat flight sims and keeping my GA configuration similar helps me be more effective in those. That of course means I don't have many levers on my stick to use and the 1 throttle axis I have gets assigned to elevator trim. I could afford to buy an additional quadrant or replace with a 6 lever quadrant, but they're all out of stock in my city and web-stores that have reasonable shipping to my region in Canadian appear to be all out of stock too. I'm guessing that this is a result of the pandemic disrupting supply chains and forcing some manufactures to temporarily shut down.

Hello all, 1st time posting here. My apologies if this has already been covered somewhere else in this forum, but my search-foo didn't come up with anything. I have a single Saitek ProThrottle (model with red, blue and black handled levers, w/6 rocker switches & 3 detents) which has increments of 0, 25, 50, 75 and 100% marked on its levers. I've gotten Throttle Decr working via a button assignment to the detent button below the throttle lever, but what I'd instead like to have is Throttle Decr be controllable in a range beginning at the 25 increment mark and ending at 0. I've tried this by creating 2 ranges for the throttle axis; 1 for Throttle Incr with a From at the 25 increment and a To at 100, and 2 with a Throttle Decr with a From at the 0 mark and a To a the 25 mark. It doesn't seem to work however, with the Throttle lever still effectively having Throttle Incr from 0 to 100? I did notice that the From and To values flipped for the 2nd Throttle Decr range I set. I didn't find much in the manual about the "Up" and "Down" check boxes and I'm not really sure what they should be set to for these 2 ranges; wondering if that's where I'm going wrong? Or is this just not possible to do for such an input device as ProThrottle? If anyone could give me any feedback or suggestions for doing what I hope to achieve, I'd appreciate reading about them. On another note, I have FSUIPC version 4.794 installed with FSX:SE, but I'm not running the beta branch. Do I need to upgrade to 4.795a? I'm nervous about any upgrading procedure that's done by installing over the top of an existing version - too many problems with other such approaches to updating in the past. So if my version is current enough please let me know.