Since installing 4.35 my throttle won't work *WORKAROUND FOUND*
-
Since installing 4.35 I’ve experienced a problem with my throttle - can anyone please help me as it’s stopping me flying in BMS.
Issue:
In Setup/configuration and all seems OK - my joystick, throttle and pedals are correctly assigned and seem to be working as expected; in the Joystick Buttons section, when I move my throttle, the throttle slider moves as expected showing full movement and that my Idle and Afterburner are set.
However, when I get into the cockpit and try to fly the throttle won’t respond (apart from a very small amount of movement). All other controllers are working properly.
Observations:
Up until I installed 4.35, I had been using 4.34 and all was working perfectly.
After installing 4.35, I found that 4.34 behaved the same way and I was experiencing the same issues with my throttle.
I have since removed both 4.34 and 4.35, re-installed 4.35 and still have the same problem.
I also fly DCS and my throttle works as expected. It seems I’m only having this issue in BMS.
Setup:
Joystick: Virpil Warbird
Throttle: Thrustmaster Cougar TQS with TUSBA 2 (I have the Vipergear throttle upgrade pots)I’m running it on Windows 10 Pro which is fully up to date with patches and updates
My throttle is calibrated using the TUSBA calibration tool (RS_HID_DEV_TOOL). I have removed my throttle and re-calibrated it twice. I have also replaced my upgraded throttle pots with the originals and the same issue occurs.
Can anyone offer any advice? This is really really frustrating
Thanks in advance
-
Have you actually tried a ramp start? I had the same issue and reported it as a bug, but apparently it’s a feature
The throttle starts moving for me once the engine spins up. Very weird and unexpected, but check the other thread in the tech support forum for an explanation.
Cheers, Uwe
-
Try sliding throttle from zero to full and back before engine start up just after you got controls. That worked with my CH throttle but I had same problem from 4.33->
-
I have made a habit of entering 3D with the throttle in the zero position. If entering a live jet (no ramp), move the throttle full forward and all the way back in a steady but not slow fashion, maybe 3 seconds in total. That makes it come alive, but that has been an “issue” for me since 4.34. I have also noticed that I do not get much response for the first 0-20% of the full motion, as measured from the fuel flow gauge. So I see also some reduced axis usage, but not as bad as you describe. Also, I do not have an idle cutoff, only AB
-
Thanks for the responses. Sorry, I should have mentioned this. After installing 4.35, I had tried to run ‘Ground Ops’ from the taxiway and was surprised when the first thing that happened to me was that I careered away at almost full throttle! I’ve since been testing in Instant Action - so am in flight.
I did try moving the throttle as suggested by M79, by that didn’t help
Further information:
Thinking that it might be a DX issue I’ve run DXView which reports all OK I’ve run sfc /scannow and that didn’t report any problems either. I checked DIView and that seems to report all was OK. Again, I’m having no problems whatsoever with DCS.
I’ve gone switched the pot back to the Vipergear one, since that didn’t seem to make any difference.
If it helps anyone, here is the contents of my DeviceSorting.txt file:
{100412E0-0000-0000-0000-504944564944} “TUSBA TQS R2”
{B679044F-0000-0000-0000-504944564944} “T-Rudder”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{40C83344-0000-0000-0000-504944564944} “RIGHT VPC Stick WarBRD”For the moment I’ve run out of ideas…
-
Set it up in Alternative Launcher 1.60 and see if that works…
-
… was surprised when the first thing that happened to me was that I careered away at almost full throttle! …
How did you manage to do that? Do you use idle detent with button or throttle range? Your first post sounds like throttle range. So how are you able to start the jet if the throttle is not reacting? It’s not like your throttle axis has to be reversed?
Cheers
-
Did you select your throttle here? Just trying to rule out the simple stuff…
-
Hi, thanks for your comments.
I’ve started the game in both instant flight or the ground ops mission - both times with engine already started. The throttle is always set to mil power and however much I move my throttle there is only the smallest amount of movement of throttle in the jet. I use the 3D cockpit.
I had configured the throttle in the normal controller setup - and this is what I find strange, I can select the controller axis without a problem and when I move my throttle I get full and free movement of range shown in the setup page. It seems to not work only when I’m in the jet. (Works perfectly in DCS)
I haven’t tried the alternative launcher, but will tomorrow morning. As I said earlier, I have no issues whatsoever configuring it, the problem only seems to affect me when I’m in the jet.
-
Couldn’t wait until morning
Tested using the alternative launcher. Didn’t solve the problem but some interesting observations:
1. It kept defaulting to my joystick Z axis for the throttle and it took me 3 or 4 attempts to remove this. Not quite sure what the Z axis is, think it’s my joystick paddle
2. I did manage to configure the TUSBA as the throttle. When I flew, I did get some movement, but only 80 to 100 % - which I guess is better, but still not fixed
3. Checked setup and again it showed that when I moved my throttle I was getting full movement
3. Tested in DCS again and as before worked perfectly -
Can you please provide the number range (raw values) that are given in game controller setup of windows? IIRC virpil uses hall sensors with very limited number range. Also of course it would be nice to know what the game controller shows as range of motion.
In regards to your ground ops TE, you start with TAXI? Otherwise I wouldn’t know how to have engine already running when entering with RAMP.
And when you say “… 3D pit…” I assume you can watch the throttle move in the 3D pit. And it shows being in afterburner range and doesn’t move when you move your RL throttle, correct? -
Using the alternative launcher to set up controls I’ve been able to get this to work. Whoo hoo.
I still can’t get this to work using the normal config but to be honest, I can now fly and I’ve spent enough time trying to fix this so I’m not going to waste more time.
In response to wolfman - the range of raw values (actuals) is 0-4095, but if this was calibrated, then shouldn’t this still be 0-100%? I start in the Taxiway, so the engine has been already started and is running. when in the cockpit (3D) whatever movements I made with my throttle (physical), the throttle representation in the 3D pit hardly moved at all - the engine was at mil power and didn’t change.
I’m a happy man - and appreciate all those who have posted messages to assist…
-
Happy to hear.
0-4095 means you have a 12bit ADC, so very fine resolution. It still should end up being 0% at 0 and 100% at 4095.Happy flying!
-
Using the alternative launcher to set up controls I’ve been able to get this to work. Whoo hoo.
I still can’t get this to work using the normal config but to be honest, I can now fly and I’ve spent enough time trying to fix this so I’m not going to waste more time.
In response to wolfman - the range of raw values (actuals) is 0-4095, but if this was calibrated, then shouldn’t this still be 0-100%? I start in the Taxiway, so the engine has been already started and is running. when in the cockpit (3D) whatever movements I made with my throttle (physical), the throttle representation in the 3D pit hardly moved at all - the engine was at mil power and didn’t change.
I’m a happy man - and appreciate all those who have posted messages to assist…
Could you try hardest possible entrance to field and start engine by your self? Not that hard with very good youtube videos. It can help deleloppers on this.
-
Some of the training missions used to work (TR-BMS-02, 03, 04) if you jumped into the jet when it was already airborne. After a while, repeating the stuff I’ve got down before I can get back to the area where I’m weak is demotivating. Is this no longer possible in 4.35? Did I miss the warning to that effect somewhere?