Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: rpm on January 26, 2011, 09:43:41 AM
-
I have a Saitek X-52 Pro. 2 nights ago I was flying a P-51 when suddenly my hat switches, buttons and throttle all quit working. I recalibrated the joystick in both Windows and the game. I checked all the control mapping in setup. Everything is now working except my throttle. It barely gives any input at 100% even tho it shows to be giving 100% in setup. The only time it works is when using WEP. Once out of WEP mode the throttle goes back to minimal input.
I've always had a bug with the pony & 38 where I had to look right on takeoff to get the throttle to work. Now it's like that's the case but looking no longer fixes the problem.
BTW, this is with ALL aircraft not just the P-51.
:bhead
-
do you have a rotary knob or dial or slider programmed to adjust your RPM's...... rpm?
example... on my CH Fighter Stick, I have programmed the rotary throttle on the base to control my rpm's if I turn the rpm's down it is as if my throttle isn't giving me 100% even if my Pro Throttle is slide to the WOT position.... as soon as I hit the WEP button, this over rides the rpm wheel/control and gives me WOT with WEP
just a suggestion that you might have over looked....
hope this helps
-
It's on the slider and it shows to be working in calibration.
-
I've emailed my dxdiag.
-
It's on the slider and it shows to be working in calibration.
your RPM's is on the slider? although it shows to be working in calibration. have you tried messing with it in game ... while trying to take off?
test it, without the wep.... launch to the runway and go wide open throttle.....if the plane still acts as if no throttle is working, adjust your RPM slider to see if it has any effect......
it may be possible that it is "inverted"... ie... working in reverse , I know I had to go in and click the invert axis box on my RPM's once........
outside of that, I don't know what else to suggest, unless you use Sateik controller programming software and it somehow has become corrupted on this one command regarding the RPM's....
but what you have explained on how it works with the WEP but not without, seems identical to what I ran into on my CH HOTAS and RPM wheel/axis
Good Luck
-
Yes, I've tried it in game. Yes, it works in game. The problem is limited to throttle response from the game. The game is getting the input according to setup, it is just not responding.
-
What command do you have mapped to the throttle on the stick? It should be "Throttle 1".
-
Throttle 1
-
Just to clarify, when you said you recalibrated the joystick you also recalibrated the throttle? Did you do the full calibration in AH or the individual calibration?
-
Sounds like you've tried all this but I know sometimes my rpm takes a little bump to get it to recognize it, even if it shows full. Also, i have forgotten to calibrate my rpm before and it shows similar symptoms.
-
I did a complete reinstall of the game and my controllers. Everything works now, I just wonder for how long. :joystick:
-
keep a copy of your settings folder. next time it happens, delete the folder and install your copy. for some reason the data gets corrupted every once in a while. it happened to me several times, and that's how i got it fixed.
semp
-
It was definitely something with the way you mapped it.
In Aces High you cannot toggle WEP unless you're at "full throttle" -- it won't do anything. So if you're at full throttle something else will be slowing you down. It's possible you tried to map the RPM and the Throttle to the same axis (I know I used to play around with that as well, but I thought you could no longer do it?) so that as you were increasing throttle you were decreasing RPM.
Toggling WEP automatically boosts RPM regardless of current settings, if I recall.
It fits what you described.
Have you done any funky mapping with saitek drivers or anything? Have you gone into the windows game controllers testing screen to make sure the inputs are sliding properly (i.e. not sticking, jumping in surges)?
-
I did nothing. It happened mid-flight while dogfighting. At first I thought I had disconnected the throttle cable, but it was plugged in tight. I recalibrated in game, in Windows and everything looked to be working correctly. But when I tried to fly it was the same result.
I also did a thorough virus and malware scan and came up clean.
-
We have discovered if the USB bus voltage drops too low, but not low enough to drop the device, it will cause Windows to think a new device has been installed and it will drop the calibration from the previous install.
-
Which explains why an externally powered USB hub helps in many cases.
I suspect turning off the led's and display screens would probably also help.