Virtual Rudder / key-controlled rudder possible at the same time?
-
BMS Manual p247 might offer you a better solution:
g_bUseDeprRetAsBrake
Enables use of a unipolar avionics axis mapping to the analog braking function. Specifically, if you have a set of driving sim pedals that you want to use with Falcon BMS this can give you a way to use them to simulate the F-16 rudder bar and brakes.
g_bUseDeprRetAsBrake only works with g_bUseVirtualRudder (lets you use the left and right toe brake axis mappings to simulate rudder input) set to 1 (true). What you can then do is map your driving clutch and accelerator pedals in the setup UI to the right and left (respectively; try it before you say “that’s backwards…”) and the driving brake pedal to the DEPR RET axis, with the net result of analog rudder input by using both pedals and single channel analog brakes in the jet by pressing on the driving brake control.
-
Thanks Darkman, that was some excellent advice. Now I can use all three pedals on my t500 rs with BMS, fantastic!
Uwe
EDIT: Another bonus using the brake pedal is that the idle thrust isn’t reduced to “0” any more as opposed to using the paddle switch on the Cougar… not exactly a bug fix, but a nice workaround nonetheless.
-
Yes, it’s like a poor man’s differential braking for those of us with driving pedals.
Works like a charm and much more convenient than swapping between pedals and rudders, as we only need 'em on the ground (for the most part) in the F-16.
-
I’ve tried everything I can think of, but I cannot get this to work reliably. Whenever I restart BMS, the reticle depression axis is reset to “keyboard”. Once I assign the brake pedal to the reticle depression axis, one of the rudder pedals ceases to work (I have my t500rs set up for split axis operation of throttle and brake).
Any idea what could be causing this?
All the best,
Uwe
-
Some screenshots might help I guess:
here’s the situation before assigning the brake pedal to reticle depression:
Then I assign the reticle depression axis to the steering wheel’s “y” axis:
When I check the “flight controls” screen, the rudder setup now looks like this:
The “Schieberegler” for the Brake function has now become the brake pedal on the T500 instead of the clutch pedal (although the naming remains the same).
I have my pedals mounted on the floor so I’ve had to reverse the axis positions in the TM control panel (the pedals can also be mounted on the wall which naturally reverses throttle and clutch).
All the best, Uwe
-
I have my t500rs set up for split axis operation of throttle and brake
How? Using set g_bUseVirtualRudder 1 in your falcon bms.cfg file (correct), or with the Thrustmaster software (incorrect).
For reference these are my FLIGHT and AVIONICS CONTROL tabs:
-
Sorry to revive this old thread. I just replaced my cougar with my “spare” warthog HOTAS (DX mode only, 2 devices) and I’m still having a problem using reticle depression as brake together with the virtual rudder functions.
I have set virtual rudder and use reticle depr. as brake in bms config. I think the t500 pedals operate in split axis mode by default, you need to set them to combined axis using the software.
The problem still persists:
when assigning my reticle depr. axis, the virtual rudder ceases to work and the throttle is no longer recognized.
However I have mapped my pedals in “reverse” (throttle is clutch and vice versa), but again the axes work fine for virtual rudder as long as I don’t assign the reticle depr. axis to the TM pedal’s brake axis.
All the best, Uwe
EDIT: I just tried setting the T500 to “normal” mode (clutch left, throttle right) but I have the same problem only that the clutch axis is then no longer recognized instead of the throttle axis for use with the virtual rudder.
-
Darkman, I just checked your screenshot and they show you have set your g25 to “combined pedals” operation (take a look at the "rudder"axis).
I do not have such an axis when operating the t500rs pedals in split axis mode so I have assigned my rudder axis to the default “keyboard”.
Still virtual rudder works fine in BMS as long as I do not assign the reticle depression axis to the brake pedal.
Cheers, Uwe
-
I just tried setting my TS500 pedals to “combined axis” mode (meaning that brake and throttle represent a single axis instead of two separate ones, using the T500RS setup controller feature), but I’m still not seeing the “combined axis” for rudder controls like in your screenshots, Darkman.
All the best, Uwe
-
Confirm you have set g_bUseVirtualRudder 1 as well as set g_bUseDeprRetAsBrake 1 in your falcon bms.cfg file?
My pedals are not combined in the Logitech Profiler app, only in BMS using the config options above.
-
Hello Darkman,
yep, my falcon bms.cfg has both values set to “1”.
Are there any other T500RS users out there using all three pedals successfully with BMS?
If your pedals are not combined natively within the g25 software then I’m wondering where this “combined axis” comes from that your rudder is set to, that’s quite weird. I’m only seeing the “original” axes of my wheel and pedals there (plus some other stuff that has nothing to do with the wheel itself)
All the best & thank you for your support!
Uwe