Saitek Cyborg throttle and SETA issues

Scarecrow · Post by **Scarecrow** » Mon, 13. Sep 10, 20:48

My old Sidewinder Precision 2 finally died on me and I just picked up this Saitek. It seems to have a bad case of the jitters which continually shuts off SETA.

Anyone got a fix for this? I have played with the deadzone settings a bit and that doesn't seem to help any.

I have installed all the latest drivers and software from the Saitek site.

TIA

Grimgard · Post by **Grimgard** » Mon, 13. Sep 10, 21:21

I have the Saitek Cyborg Evo and it works just fine with my game. Did you check the windows properties for the joystick to make sure its not moving all over the place?

It could be a bad joystick maybe?

Bill67 · Post by **Bill67** » Mon, 13. Sep 10, 21:23

I just got that stick a few weeks ago and was thinkinbg of returning it for that same issue. Problem is, wasnt much of a choice and if I do return it, the only other option was a less button joystick which I didnt want to do.

Cant believe not many choices for joysticks anymore, even thought of ordering one but didnt seem many choices there either.

Scarecrow · Post by **Scarecrow** » Mon, 13. Sep 10, 21:38

There have been some posts in the past about similar issues and the fault seemed to lie some how with the USB signals, I think.

Don't remember anything about those posts since I didn't have the problem with the old Sidewinder.

Post by **X-Warrior B AS** » Mon, 13. Sep 10, 21:56

It's an issue I've been having for long. I think it's just too accurate (Cyborg Evo here), so even the slightest movement triggers a change in speed, cancelling SETA.

My workaround was to set the throttle to max, and then decelerating using the keyboard buttons. This way you'll be able to keep SETA going at less than max speed

Scarecrow · Post by **Scarecrow** » Mon, 13. Sep 10, 21:59

That's exactly the problem, at either extreme it seems to be stable.

Will give the work around a try.

Mortis494 · Post by **Mortis494** » Mon, 13. Sep 10, 22:00

I'm using the Saitek X52, I adjusted the settings and I works pretty well now, the problems only occur on vessels with a high max speed (250+) as per other poster, try using max speed then adjusting with the keyboard to prevent seta problems.

Scarecrow · Post by **Scarecrow** » Mon, 13. Sep 10, 22:12

Kinda begs the issues of having a throttle if you have to use the keyboard doesn't it.

Gonna try to program the scroll wheel to the x & z keyboard commands and see if that will work.

Twest09 · Post by **Twest09** » Mon, 13. Sep 10, 22:48

Kinda funny cause I bought a Saitek flight controller when I bought this game and some other airplane fighter games and with this game I just prefer the keyboard + mouse... it just seems more accurate and responsive for me.

terrigat · Post by **terrigat** » Mon, 13. Sep 10, 23:36

Mortis494 wrote:I'm using the Saitek X52, I adjusted the settings and I works pretty well now, the problems only occur on vessels with a high max speed (250+) as per other poster, try using max speed then adjusting with the keyboard to prevent seta problems.

How exactly did you adjust this? I'd love to use SETA (& match speed) without moving my throttle all the way to the top.

Bill67 · Post by **Bill67** » Tue, 14. Sep 10, 02:45

I have the Cyborg X and I tried using keyboard speed but somehow it overides that after a bit and puts it back to throttle setting. Even matching speed to target most times has to be manual as it reverts back to throttle settings.

I would have kept my wireless joystick but that 1 kept maxxing speed if went into a sleep mode....

Scarecrow · Post by **Scarecrow** » Tue, 14. Sep 10, 03:13

Mapping the x & z keys to the stick scroll wheel didn't work.

Using the work around by pushing the throttle to max and then using the keyboard worked just fine for me when I was following that stupid pirate all the way to Gaien Star.

Parias · Post by **Parias** » Tue, 14. Sep 10, 18:43

terrigat wrote:
Mortis494 wrote:I'm using the Saitek X52, I adjusted the settings and I works pretty well now, the problems only occur on vessels with a high max speed (250+) as per other poster, try using max speed then adjusting with the keyboard to prevent seta problems.
How exactly did you adjust this? I'd love to use SETA (& match speed) without moving my throttle all the way to the top.

The Saitek software lets you tweak the throttle deadzone to help offset this issue, via the Control Panel applet it provides.

terrigat · Post by **terrigat** » Tue, 14. Sep 10, 23:00

Deadzone is different though. It only removes an area of the axis from responding, not reducing the precision of position changes to the system / game.

Post by **Nanook** » Tue, 14. Sep 10, 23:08

This is a common issue among all joystick throttles that use potentiometers. There is no real workaround for using SETA, except for using the Shift-f (match speed to target ship). That gives the throttle a software setting rather than the normally used hardware setting, and allows you to use SETA for any throttle setting (providing you can find a ship that's going the speed you desire).

For instance, my USB CH Products Flightstick Pro has exactly the same issue. I can get SETA to stay on when the throttle is set to minimum, zero and maximum, and when I use Shift-f on another ship. Otherwise, the potentiometer windings are too coarse for the game's sensitivity, especially on the faster ships.

IceFire909 · Post by **IceFire909** » Wed, 15. Sep 10, 07:15

I remember when I was having this issue.
I can't say I solved it, but simply put, it's too accurate. And yes, deadzone won't fix it unless you're having "rest-state" issues where you don't touch the stick and the ship is effected.

I use a Saitek Cyborg EVO, I keep it unplugged most of the time (FPS games (like Borderlands) detect it and do crazy things like constantly turn right due to the throttle) but when I plug it in, I jump into X3 and even the stick becomes hyper-sensitive.

The solution for that is a quick re-calibration by moving the joystick in full extreme circles (all the way top-left > bottom-left > bottom-right > top-right several times), then move the throttle to both extremes a couple times. Those will help reduce its sensitivity.

But if you fly any fast ship, such as an M5, M4, M3, (potentially some M6, M8, TM, TS, TP, but I haven't flown them except for Mistrals and Mercury's) then the throttle will still be too sensitive and you'll have to have the throttle at full or empty and use the keyboard to adjust speed for SETA.

On a related note, I don't understand why you'd want to fly at 'less-than-full' speed while in SETA outside of escort missions. I personally only am adjusting speed while in combat and that tends not to be a very good time to be using SETA.

Scarecrow · Post by **Scarecrow** » Wed, 15. Sep 10, 08:11

Spoiler

Show

There's a portion of the Goner plot that takes forever at 78 .... and it just drives me nuts.

I tried to be vague but gonna spoiler it any way

IceFire909 · Post by **IceFire909** » Thu, 16. Sep 10, 07:17

I can't say I recall that event.

Could you (or anyone) PM me what it is?

Post by **Nanook** » Thu, 16. Sep 10, 19:49

Scarecrow wrote:
Spoiler
Show
There's a portion of the Goner plot that takes forever at 78 .... and it just drives me nuts.
I tried to be vague but gonna spoiler it any way

If you match speeds using Shift-f as I mentioned above, you can use SETA, no problem. It's how I did it for that situation. You do need to set the throttle to max, though, before matching speeds.

DaveyP · Post by **DaveyP** » Thu, 16. Sep 10, 22:39

I have an X52 which constantly either turns hard right or pulls me up into a major climb.

The only way I've found to counter this is to unplug it then plug it back in.

egosoft.com

egosoft.com

Saitek Cyborg throttle and SETA issues

Saitek Cyborg throttle and SETA issues