January 24, 201610 yr I have discovered an issue I can't seem to resolve. I'm using CH yoke and pedals. Calibrated only through CH control panel with dead zones to prevent noise or accidental issues.I do own FSUIPC however I've never calibrated with it or checked any of the boxes.The issue is this, whether I'm starting from the gate with autobrakes off, or landing with whatever setting I decide on, I can disarm the autobrakes. However, pressing the manual brakes seems to lock the autobrakes on. Tonight I started my taxi and as soon as I applied manual brakes to slow for a turn the plane just slowed to a stop. I can push the throttle all the way to 40% N1 before I even move. Yet switching the autobrakes from off to RTO back to off allows it to move again. In other words, manual braking seems to engage autobrakes. I don't get it. Chocks are off, everything is set up fine. How is this happening? What are my options?? If autobrake is off and/or disarmed then I should be moving. - Chris Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD | 1000 Watt Gold PSU | Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ) Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired
January 24, 201610 yr probably not the autobrakes that are the issue. Most likely the brake axes of your pedals need to be reversed. I have to do this when setting up any aircraft, though I use FSUIPC to assign and calibrate. Is there a facility in the ch software to reverse the axes ? If not then do not process the axes in ch sowtware, and use FSX or FSUIPC. What is happening at present is when your pedals are not being pressed there is no signal being sent. As soon as you press them the axes are "alive" and although you release the brakes the axes are sending a full brake signal. You can test this by pressing the fully and holding them, you will find you will be able to taxi. Peter Schluter
January 24, 201610 yr Author It's so strange. I had kinda noticed the Duke Turbine was hard to taxi as well, and this shouldn't be the case. IOW, it'll get going but upon stopping won't just move forward with condition levers alone. I don't have time to run the PMDG and test it out, but I loaded the Duke for a quick test to see if I could elucidate the problem there. Figuring it's a hardware/assignment issue, I adjusted a host of things. Brakes are reversed in FSX, no problems there. Plane stops with manual brakes as desired, but getting moving takes a bit of throttle. Interestingly enough, once stopped in the Duke, I'm stopped, regardless of the amount of condition I have going. If I engage the parking brake then release it, it rolls again. Not sure I understand how this could affect it. Anyhow, after playing with FSUIPC, and trying to change a few things with the brakes, I wasn't able to fix it. What I did do is lower my null to 0 in FSX for the brakes. For some reason, lowering the null to zero, or removing it, seemed to eliminate the problem. I went back and was able to stop manually and then roll again without playing with the parking brake. Real strange. I checked all my keyboard assignments and everything. Pressing the period key didn't help either. I will try tomorrow and see if that fixes the NGX braking oddity too. - Chris Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD | 1000 Watt Gold PSU | Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ) Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired
January 24, 201610 yr It may be that your ch software is interfering with your fsx settings and they are fighting each other. I dont install any yoke/pedals/throttle quad software and actually disable them in the sim (disable yoystick). Then assign and calibrate everything in fsuipc. Added advantage is you can have a different setup for each aircraft type you fly. Peter Schluter
January 24, 201610 yr Commercial Member How is this happening? FSX is terrible at interpreting pedal info. What are my options?? Assign the axis in FSX (you may need to select "invert" - I did for my Saitek pedals). Open FSUIPC and calibrate (and ONLY calibrate - do NOT assign) the axis. You will want to depress the pedal and watch the number that changes. There will be a SET button next to that number. Place the cursor on that button but don't click yet. Release pressure on the pedal and then depress the pedal slightly (maybe a centimeter or two). Press SET. Do the same thing for the other pedal, but try and match the SET number from the other side (that way you don't get inherent bias when braking because of the null zone). Kyle Rodgers
January 25, 201610 yr Author Removing the null in FSX seems to have fixed it. Not sure why it was doing that but whatever. I miss FS9, it wasn't nearly as fussy.... - Chris Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD | 1000 Watt Gold PSU | Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ) Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired
Create an account or sign in to comment