Throttle inputs on taxiing not always being read?
-
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.
-
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’m using a “virtual rudder” axis on my T500RS wheel / pedals combo and am having the same issue with the paddle switch reducing fluel flow to zero, so while it’s not exactly a proper HW rudder device, it happens with the virtual rudder function too.
Cheers, Uwe
-
Can’t seem to fix it without losing the ability for either wheel brakes or AP….
Anyone having an alternative? -
weird…had the issue with 4.32 but it went away.
had no issue on 4.33 but now, on U1, i seem to have the issue again… -
seemed to have fixed the issue.
since i had no problems on 4.33, i tried copying the BMS-Full keyfile that i used from the 4.33 to the U1 config folder, loaded the keyfile and voila! no more Fuel Flow to 0 issues anymore.
so, strangely enough, the issue seems to be in the keyfile.
if anyone else still has the issue and wants to use the cougar with dunc’s tmj with the BMS Full keyfile, here’s the link to the key file:
https://www.dropbox.com/s/o92md0yxtdlplz8/BMS%20-%20Full%20%282%29.key?dl=0
cheers,
-
Next weekend i’ll copy the Cougar DX part to my keyfile
-
this is not an issue.
Can you imagine you enter 3D wih your throttle Half or Full and it is beeing recognized as soon as entering ?
That would result in a big boom as soon as you enter 3D.
Therefore it is safe practice do desactivate throttle input when entering and wait the user to move it to actualize it
-
It is…
Going to runway X … brake with the paddle on the cougar untill the viper stops… fuellflow going down to 0 with running engine ???
-
First, it is not the key file. In no way there is something in there, which can trigger that except you fubared your HOTAS setup…
Btw., the Dunc_DX key file is by 99.9% identical (!) to the full key file. Only two key assignments are different.Mav: I have posted a bugtracker issue about the “when you press the paddle switch, Fuel Flow goes to zero” thing.
This is clearly a bug. See internal forum. Maybe you missed it. -
I tend to agree with you Kolbe.
However, when loading the old key file, the issue is gone. I load the U1 BMS-Full.key, the issue is there. Don’t ask me why.
If it were only so simple for everyone, we wouldn’t be having this issue since 4.32.
Anyone else used my attached file? Still have the bug? -
Hi sambucca,
of course it is working for you because you replaced the callback SimAPOverride (which has a bug on key release event -> FF drops to 0)
by the callback SimWheelBrakes.Go into pit and try Alt-A (default assignment for SimAPOverride invocation). FF drops.
The key file is sane. No data problem at all. The callback SimAPOverride is buggy, so code related. -
Right Kolbe, i came to the same conclusion.
If i remember well, Sambucca changed something in DUNC’s tmj too -
Really? Don’t remember changing anything in the key file but I guess that must’ve been it. Never really use the paddle for AP override (although, come to think of it, that would come in handy from time to time. ��)
And yes manta, I added the shifted key to activate VAC.
-
found it Sambucca it’s in a pôst here , nothing to do with the paddle
BTN T4 /I KP*
/O {DX22}Maybe you changed the AP override at the same occasion.
-
Right. I can’t remember ever changing anything else, will test whether ap override works when I’m back from Ecuador