Afterburner Bug ?

OmniusALX · Post by **OmniusALX** » Thu Apr 03, 2008 10:32 pm

Just wondering if this is normal...

I use an X52 Pro flight stick. I use the D button for my afterburner, but I've noticed when I change direction while holding the afterburner button, the afterburner cuts out even though I have the button pressed.

If I release the joystick, but keep the afterburner pressed, it works continously, but as soon as I try to move the joystick it starts to flick on and off in quick succession.

Any ideas???

Post by **Vice** » Thu Apr 03, 2008 10:35 pm

Nope, not normal. Could be a flaw with the stick itself. The joystick on my X52 sometimes cuts out on me entirely when playing any game and I have to unplug its cable and plug it back in to re-enable it. Seems quirks like this are fairly rare, but common enough to be reported fairly often on their forum. The D button is on the throttle, so I'll change my control bindings and test it now, just to be sure.

Post by **Vice** » Thu Apr 03, 2008 10:46 pm

Just tested and my X52 keeps the afterburner active with the D button pressed regardless of how much I turn with the joystick. Check the settings in the Game Controllers menu, verify that the D button still lights up red in that menu when you move the stick around.

[Edited on 4-3-2008 by Vice]

OmniusALX · Post by **OmniusALX** » Sat Apr 05, 2008 1:14 pm

I've tested my stick in windows using the control panel, and I'm pleased to say that holding down the D button while applying full throttle and moving the stick doesn't cut out the D button press (solid red light on panel) like it does in game with the afterbutner.

I've tried it with my EV:R profile enable and without (Windows control panel), it works fine, could it be something to do with setting the sensitivity to low within the in game settings?

Regards

[Edited on 4-5-2008 by OmniusALX]

Post by **Vice** » Sat Apr 05, 2008 2:50 pm

I've tried it with my EV:R profile enable and without (Windows control panel), it works fine, could it be something to do with setting the sensitivity to low within the in game settings?

It shouldn't, the D button is simply an on/off input. So my guess is that some setting may be over-riding the afterburner input (perhaps due to two or more controls being mapped to the same function). I'm not even sure how that could be done and I'm not familiar with Saitek's programming software as I map everything in-game. I do recall having a control quirk before and it turned out to be a driver issue. After I updated the drivers to the latest on Saitek's website, the problem went away. That might be another step you want to try.

http://www.saitekusa.com/usa/down/drivers.htm

OmniusALX · Post by **OmniusALX** » Sat Apr 05, 2008 4:22 pm

Thanks for the replies Vice,

I've had another look at my profile and made sure nothing was mapped to the buttons in game. It seems to be working ok now for some reason

One thing though, I guess its normal for the speed indicator to change even when the afterburner is at 4K and you throw the ship into a hard turn?

Apart from that, the afterburner doesn't splutter on and off now.

As for the drivers, I'm using the beta 2 drivers (No issues on any games really, and I prefer to have a custom LED layout rather than all green)

Regards

[Edited on 4-5-2008 by OmniusALX]

Post by **Vice** » Sat Apr 05, 2008 5:07 pm

One thing though, I guess its normal for the speed indicator to change even when the afterburner is at 4K and you throw the ship into a hard turn?

Yes, because the physics/flight model is realistic and not 'arcade'. If you make a turn, you are changing direction, but your momentum has been built up for the direction you were originally heading, so your forward velocity gauge will decrease as you turn while your lateral speed gauge will increase. For more details on flying a spacecraft in zero gravity, click on the 'Flight and Navigation' section of the strategy guide: http://www.starwraith.com/evochronreneg ... rguide.htm

MMaggio · Post by **MMaggio** » Sat Apr 05, 2008 8:17 pm

Originally posted by Vice

So my guess is that some setting may be over-riding the afterburner input (perhaps due to two or more controls being mapped to the same function). I'm not even sure how that could be done and I'm not familiar with Saitek's programming software as I map everything in-game.

http://www.saitekusa.com/usa/down/drivers.htm

Yes, Vice et al. It is possible to map two keys to the same function. It's actually possible to change the key # assignment to any other key.
But, in this case, that wasn't the problem.
Have fun...

OmniusALX · Post by **OmniusALX** » Sun Apr 06, 2008 9:30 pm

I've managed to sort the issue as it has raised its head once again.

I've only 2 buttons mapped through the game now, the trigger and now the afterburner on the D button (button 6 in game)

All my other buttons are mapped using the SST (along with all the pinkie and mode alternative buttons)

The afterburner now works a treat so it must be something to do with this one key when mapped solely in the SST???

Anyway, its working 100% this way so I'm happy

Oh just one thing while I'm on - Why are some of the Navy and Guild ships on the target list in yellow or green? And why do they target with the nearest hostile button aswell as the nearest target button? I thought only red targets would target with the nearest hostile button?

Regards.

Post by **Vice** » Sun Apr 06, 2008 10:41 pm

Some Navy and Guild allied ships are more friendly than others, just not hostile unless you have a negative reputation with one or the other, or both.

When there are no hostile targets in the area, the targeting system will default to just targeting the nearest ship.

[Edited on 4-6-2008 by Vice]

49rTbird · Post by **49rTbird** » Mon Apr 07, 2008 7:40 pm

This is only a test.