View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001659 | FSSCP | gameplay | public | 2008-04-11 06:08 | 2008-09-14 19:31 |
| Reporter | Cobra | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | not fixable | ||
| Product Version | 3.6.9 | ||||
| Summary | 0001659: Joystick Detection Randomly Becomes Off-Center | ||||
| Description | It only seems to be happening to Saitek x52 HOTAS sticks. What happens is that when a player is in-game, the FSO builds after 3.6.9 like to screw up on the joystick center detection, causing the game to think the player is turning his or her ship to the left or right, depending on how screwed up it gets. alisbin from HLP originally posted the thread, and he had a good description of the actual problem: "ok, the problem: seemingly at random my joystick (a saitek x52) gets its center messed up (so x0 y0 becomes x12 y1 for example, there doesnt seem to be a pattern in the mistake). thus i drift at center which can be a major problem in the middle of a dogfight. i've figured out an easy fix, but it requires pausing the game so i can't do it in multiplayer." The actual fix is unplugging the cable that leads to the x52 joystick itself, then plugging it back in, but it's disruptive for singleplayer mission and a death trap in multiplayer. | ||||
| Additional Information | I'd also like to note that my x52 LED lights flash when the detection gets screwy, but it might be a result of the reset in center detection, as it never happens in any other game. | ||||
| Tags | No tags attached. | ||||
|
|
This is a hardware issue, it happens to me too. I quit out of FS2 when it happened and the joystick calibration window in windows shows the stick has uncalibrated itself. I haven't noticed it happening in other games though (falcon 4, X2, X3, IW2), so I don't know what is going on. Of course it sucks even more by unplugging and plugging the stick back in since my freespace2 profile gets lost and i'm back to the default binds. |
|
|
I don't think it's a hardware issue if it only happens in FS2. It could be software-related, as in a conflict between the game and driver or something. |
|
|
I don't know, it happened to me again tonight and it fixed itself after I reseated the cord that ran from the throttle to the stick. |
|
|
I think it is probably a hardware or driver issue. There is nothing in FS2 that resets the joystick calibration settings inside windows itself. Since reseating the serial cord that goes from the throttle->stick (not the throttle->pc) seems to make it go away, it may bee some electronics issue inside the stick. But i've never seen it occur on IW2 or Falcon 4, so I'm at a loss. I can try it on either of those games this weekend. |
|
|
I can actually vouch for it not happening in IW2 or Falcon 4.0. |
|
|
Was browsing through Mantis when I came across this report, so I wanted to add my two cents on this. I very recently picked up a Saitek X52 myself and have seen the exact same symptoms in Freespace 2, with exactly the same fix of briefly disconnecting the throttle / joystick unit and reconnecting them. Similarly, hopping back out to the Windows-based joystick control center also shows the stick out of calibration when this happens. This also tends to happen to me mostly when the joystick is under "heavy" use, with a lot of juking and direction-changing going on (I actually never saw the problem at all until I started playing TBP, because the fighters in that take a lot more effort to hit accurately). The reason why I'm posting however is that I have found another game this occasionally happens in - Mechwarrior 4 - and again, only when the joystick is under heavy use. Because of this, I don't believe whatever trigger this issue is Freespace 2-specific - it's gotta have something to do with the stick itself and the way it's interacting with these games, and I don't believe there's anything that could be done on a coding end with just Freespace 2 that would fix it. Those curious might want to give Mechwarrior 4 a good workout, as I've been able to repro consistently in that game with this stick (much to my annoyance in multiplayer). |
|
|
Now that you mention it, it does seem to happen when I really start moving it every which way. |
|
|
My two cents: I have a Saitek x52 Pro. But I do not install the profile software. Ever. In WinXP (SP2 and 3) I only install the drivers. In Vista 32bit, I leave the default windows drivers in place. The only issue I have noticed is in vista regarding one side button not being detected properly (it flashes the center LED for the POV and does not register as a bindable function. This affects every game, not just FSO) and that I can not change the LED intensity with the MFD scrollers like I can in XP. But the center detection has never been lost. I am pretty sure the issue is between the interaction of the Profile Software->Driver->Hardware and is not a FSO issue. That being said, I seem to recall it mentioned that the input interface in FSO still needs some help. |
|
|
Can I close this if there is nothing we can do? |
|
|
Since this is a hardware issue, we can't fix this. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-04-11 06:08 | Cobra | New Issue | |
| 2008-07-25 17:51 | phreak | Note Added: 0009505 | |
| 2008-07-25 17:54 | phreak | Note Edited: 0009505 | |
| 2008-07-25 18:36 | Cobra | Note Added: 0009507 | |
| 2008-07-30 03:43 | phreak | Note Added: 0009519 | |
| 2008-07-31 03:52 | phreak | Note Added: 0009523 | |
| 2008-07-31 04:42 | Cobra | Note Added: 0009524 | |
| 2008-09-01 07:50 | Parias | Note Added: 0009633 | |
| 2008-09-01 07:52 | Parias | Note Edited: 0009633 | |
| 2008-09-01 18:08 | Cobra | Note Added: 0009635 | |
| 2008-09-01 22:14 | Zacam | Note Added: 0009636 | |
| 2008-09-03 20:12 | phreak | Note Added: 0009643 | |
| 2008-09-14 19:31 | phreak | Status | new => closed |
| 2008-09-14 19:31 | phreak | Note Added: 0009677 | |
| 2008-09-14 19:31 | phreak | Resolution | open => not fixable |
