Throttle and Brake Problem
-
Hi Guys,
When im taxiing and use the brakes it seems to set my throttle to idle.
Only way to get going again is to go full AB and drop back again.
On the runway i’m not able to throttle up while holding the brakes.
Any ideas what the problem might be?
using Dunks keyfile setupThanks
-
What are you using for the Brakes? Do you have pedals? Do they have differential Braking?
From what you’ve said I would be checking the Throttle and Brake assignments in the BMS Setup screen and then check these axis in Windows device manager for operation.
-
Sounds like you need to reverse your brake axes
-
brake is on the paddle switch on the joystick
-
Hi!
I’m having the same thing happening with dunc’s file too. Think it’s reproduceable by pressing alt+k on keyboard. Believe it’s got something to do with the paddle switch also set up as ap-override. Not sure if it’s a bug, but at least a nice feature on ground saving fuel:p(You’ll notice the fuelflow drops from 900 to 0) -
Yup, this is true, I’ve seen it too.
Dunc’s profile uses paddle switch, as DX button for AP-Disc and a K - key for brakes., at the same time, … but that collision shouldn’t happen, between DX button and keyboard key,
so there is clearly some callback or engine issue, or a bug which affects throttle(actually I’ve noticed this behavior only on F18C/D/E/F , when lining up on cat, not sure about F-16, so …, so to narrow things a bit down)
Cheers
p.s. I’ll test assigning another key for brakes and/or another button , so I’ll report then., and will test both planes… gimme half a falcon hour
-
Key collisions…I expect they happen differently from controller setup to setup. Brakes seem to be the worst offender for this for some reason. No idea why.
-
Please, You can send this to “Tech support” , as a bug report, probably. When I’ve #rem-ed paddle switch in key-config , which leaves only k(wheelbrakes macro) , I couldn’t reproduce problem then.
So it is “SimAPOverride” callback , definitely connected with the problem, narrowed down, but what exactly , didn’t go that far.Stevie
Mmmm, yes and no, … You see, like I’ve said in previous post, technically is collision and not,
It is the same device (Cougar) , but it is not the same interface
… yes keys are pressed at the same time , they are down event, K_DOWN , DX4_DOWN,
BUT…
First is DirectInput interface , other is emulated usb keyboard, separate, … only connection is same device (cougar), but different interface. And Cougar is perfectly able to coexist between numerous of interfaces, DirectInput, Usb-keyboard, usb-mouse, etc… any? - in the same time , parallel output… it is in the book , and the help of foxy, (don’t know for target, never used)
So, while more correct , it is not key collision, but is it a bug in the BMS , Eg. No such behavior in 4.32 also.Cheers
Cheers
-
This is a known issue.
See also here.