Baitball Posted October 4, 2019 Share Posted October 4, 2019 Surely I must be missing something obvious, but I can't seem to be able to get the rudder axis to recognize my TFRP Rudders. What am I doing wrong?:helpsmilie: Link to comment Share on other sites More sharing options...
RaisedByWolves Posted October 4, 2019 Share Posted October 4, 2019 I have the TM Pendular ones and just clicked on the axis category and found rudder and went to assign and depressed the pedals until it recognized and it works. Link to comment Share on other sites More sharing options...
Greyman Posted October 4, 2019 Share Posted October 4, 2019 make sure that you click on the cell in the column that has your pedals and in the row that has the rudder command. a dialogue should show up and be populated by your pedals axis when you press one of them. the two toe brakes will need to be set in the same way too. Link to comment Share on other sites More sharing options...
Baitball Posted October 4, 2019 Author Share Posted October 4, 2019 Yes, this is what I have been doing. Making sure I am clicking on the correct column that correlates to my pedals. And yet, it still will not recognize the pedal inputs. Link to comment Share on other sites More sharing options...
Greyman Posted October 5, 2019 Share Posted October 5, 2019 Ah sorry, it's a double-click that's required. Do you see the mapping dialogue open up before you move your pedals or is just the mapping "grid" visible? Edit press the rudder pedals in both directions alternately, until it registers. Link to comment Share on other sites More sharing options...
Raven (Elysian Angel) Posted October 5, 2019 Share Posted October 5, 2019 I also have the TPR pedals, and for me the binding worked as it should. I have the yaw axis set to a curvature of 30. Spoiler Ryzen 9 5900X | 64GB G.Skill TridentZ 3600 | Gigabyte RX6900XT | ASUS ROG Strix X570-E GAMING | Samsung 990Pro 2TB + 960Pro 1TB NMVe | HP Reverb G2 Pro Flight Trainer Puma | VIRPIL MT-50CM2+3 base / CM2 x2 grip with 200 mm S-curve extension + CM3 throttle + CP2/3 + FSSB R3L + VPC Rotor TCS Plus base with SharKa-50 grip mounted on Monstertech MFC-1 | TPR rudder pedals OpenXR | PD 1.0 | 100% render resolution | DCS "HIGH" preset Link to comment Share on other sites More sharing options...
Baitball Posted October 5, 2019 Author Share Posted October 5, 2019 The mapping dialogue does open, but moving the pedals fully in either direction does not register. My left/right toe brakes registered just fine. Link to comment Share on other sites More sharing options...
Raven (Elysian Angel) Posted October 5, 2019 Share Posted October 5, 2019 Have you tried pulling the USB cables out and re-connecting them? If so, I don't know what could be wrong other than a hardware failure (provided you have the same problem with other modules). Spoiler Ryzen 9 5900X | 64GB G.Skill TridentZ 3600 | Gigabyte RX6900XT | ASUS ROG Strix X570-E GAMING | Samsung 990Pro 2TB + 960Pro 1TB NMVe | HP Reverb G2 Pro Flight Trainer Puma | VIRPIL MT-50CM2+3 base / CM2 x2 grip with 200 mm S-curve extension + CM3 throttle + CP2/3 + FSSB R3L + VPC Rotor TCS Plus base with SharKa-50 grip mounted on Monstertech MFC-1 | TPR rudder pedals OpenXR | PD 1.0 | 100% render resolution | DCS "HIGH" preset Link to comment Share on other sites More sharing options...
Greyman Posted October 5, 2019 Share Posted October 5, 2019 and does movement of the pedals register when you open the usb game controller dialogue in windows and show the properties for your rudder pedals? Also, tm controllers tend to require calibration with tm software, so if you have calibrated the rudder pedals with windows, then reset to default, perhaps ironically using the usb game controller, and then recalibrate using the TM software. Link to comment Share on other sites More sharing options...
Baitball Posted October 6, 2019 Author Share Posted October 6, 2019 Have you tried pulling the USB cables out and re-connecting them? If so, I don't know what could be wrong other than a hardware failure (provided you have the same problem with other modules). I updated the driver and replugged into a different port, it works! Thanks for everyone's help! Link to comment Share on other sites More sharing options...
Recommended Posts