Throttle inputs on taxiing not always being read?
-
To anyone having experience in programming on the HOTAS cougar:
The problem is somehow situated as follows:
it is by RELEASING the paddle switch after braking on the ground, that the fuel flow unexpectedly drops to 0000 instead of 0900!
I don’t know any button/key combination that would temporarily drop the fuel flow to 0…
Therefore I’m assuming this is somehow a bug in 4.33 or something wrong in the Dunc_DX profile?Until further notice: using the keyboard “k” to brake solves the problem for taxiing!
-
To anyone having experience in programming on the HOTAS cougar:
The problem is somehow situated as follows:
it is by RELEASING the paddle switch after braking on the ground, that the fuel flow unexpectedly drops to 0000 instead of 0900!
I don’t know any button/key combination that would temporarily drop the fuel flow to 0…
Therefore I’m assuming this is somehow a bug in 4.33 or something wrong in the Dunc_DX profile?Until further notice: using the keyboard “k” to brake solves the problem for taxiing!
It is a bug in 4.33 not Dunc_DX profile. I don’t use it, I have my own personal Cougar profile
-
It is a bug in 4.33 not Dunc_DX profile. I don’t use it, I have my own personal Cougar profile
How do I reproduce this bug without using Dunc’s profile?
-
How do I reproduce this bug without using Dunc’s profile?
Hi mate, use the line above for the paddle switch (BTN S4), making sure DX4 is assigned to the paddle switch in the keyboard/joystick buttons page. Sorry for lack of clarity, on iPad at work currently.
-
Im not using Foxy at all. How can I reproduce this BMS bug?
If I am interpreting it correctly, the inputs BMS sees are the DX4 keydown event and the k keydown event? And they are held down until the paddle switch is released?
-
Im not using Foxy at all. How can I reproduce this BMS bug?
If I am interpreting it correctly, the inputs BMS sees are the DX4 keydown event and the k keydown event? And they are held down until the paddle switch is released?
I’m not an expert but I think your correct. I indeed thought it emulates DX4 and “k” keydown event at the same time.
If you want you can open up the .tmm and/or .tmj files of Dunc_DX.
Above the specific line there are some comments made by the creator that might be helpful to you. I’m not sure if your able to read the .tmm and/or .tmj
files with notepad for example without Foxy. Can’t help you now since I’m not home. -
I have foxy, I just dont use it. DX mapping of the cougar is simpler and fits all my needs.
Ill take a look at recreating this bug when I get my stick plugged back in.
-
Im not using Foxy at all. How can I reproduce this BMS bug?
If I am interpreting it correctly, the inputs BMS sees are the DX4 keydown event and the k keydown event? And they are held down until the paddle switch is released?
Yep, that’s it in a nutshell. 4.33 sees DX4 being held down, and sees k held down also. It seems the keyup event of the 2 simultaneously (I use RATE 0 to throw the events as fast as the computer will allow) is what is chucking it out. Didn’t happen in 4.32
PS - real Cougar users use Notepad…
-
I have foxy, I just dont use it. DX mapping of the cougar is simpler and fits all my needs.
Ill take a look at recreating this bug when I get my stick plugged back in.
Any luck in reproducing the bug?
Thanks for looking in to it! -
I can chime in among the Cougar / dunc_dx users seeing this bug (fuel flow dropping to “0” when pressing the paddle to brake on the ground). Hitting the “k” key works fine.
Let me know if there’s anything I can do to help solve this issue.
Uwe
-
In our squadron we have a few people using duc’s tmj and tmm.
Last weekend some of us installed VAC and added new code in tmj to arm VACBTN T4 /I KP*
/O {DX22}After this code was added fuelflow was working correct again.
i’ll check it out this evening -
In our squadron we have a few people using duc’s tmj and tmm.
Last weekend some of us installed VAC and added new code in tmj to arm VACBTN T4 /I KP*
/O {DX22}After this code was added fuelflow was working correct again.
i’ll check it out this eveningWhat does that peace of code mean? I see the DX22 button being used, no idea which one that is.
A temporary solution is very welcome! Thanks for adding another piece to the puzzle -
What this code does
DX 22 = iff in
Dx 22 + shift (S3button pushed) = ARM VAC (keystroke Numpad*)/i and /o are the positions of S3
In 2 hours i’ll know if it works for me too
-
Notworking here,
After breaking …. and release paddle fuellstate still falling down to 0000 .when i pick up throttle slowly … the jet dont move… seems like the signal from throttle is to weak or not arriving ???
When push a little faster then ist ok, -
same problems here on X-55
The wheelbrakes on press “shift+ paddle” apparantly gives problems, throttle is moving in 3d on input but there is no reaction in engine rpm.these calls are used in keyfile for reference:
SimHotasPinkyShift 260 8 -2 0 0x0 0 “PINKYSHIFT”
SimWheelBrakes 261 -1 -2 0 0x0 0 “wheelbrake” -
To add one more thing if you are in the air ,pull throttle all the way back and press paddle switch fuel flow will drop to 000 and bounce back up to 900 . Because of air movement???
-
I am having the same problem with the throttle on the ground. I also have a Cougar HOTAS using the DuncDX profile.
I have to move the throttle to afterburner before I get any thrust. If I run up the engine with the wheel brakes on, then release the brakes, I get NO thrust even though the engine is run up. I have to move the throttle around to get rolling again.
-
Had this problem numerous times already. I can see the throttle move in-sim but I’m not getting any RPM.
-
Could it have to do with the fact of having rudder pedals or not?
Because I Know somebody who has pedals and he doesn’t have the problem, while
I don’t have any pedals and I do have the problem. -
I’ve encountered this problem too. Cougar using Kolbe’s replacement profile from the bms4.33 install dir, using paddle for braking, no rudder pedals. Have to throttle up to max and then quickly back down to get the engine to move beyond 0 fuel flow.