View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002298 | FSSCP | Platform-Engine interaction | public | 2010-08-29 23:29 | 2012-02-08 06:57 |
| Reporter | Alex_LQW | Assigned To | Goober5000 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.6.12 RC4 | ||||
| Summary | 0002298: Return-to-center tension on Sidewinder Force Feedback 2 is de-activated. | ||||
| Description | When running 3.6.12 RC4 using a Microsoft Sidewinder Force Feedback 2 joystick (under Windows 7, 64-bit), the "return to center tension" is deactivated when the game starts and not re-applied at any point. The joystick inputs are still accepted and otherwise seems to work fine, but the lack of RTCT is pretty annoying. Other games (StarLancer and Tachyon: The Fringe for example) don't exhibit this bug. If I unplug and plug in the joystick from the USB port, the tension is restored but FS2 no longer seems to receieve any inputs from the device after this. | ||||
| Tags | No tags attached. | ||||
|
|
NOTE: The above behaviour only happens when "Enable Force Feedback" is selected (I'm using "FS2 Open Launcher 5.5f" to start FS2) |
|
|
This is highly irregular. I don't think anyone has changed the force feedback code in some time. First of all, make sure your joystick didn't come unplugged, and then make sure that your grip is activating the joystick grip sensor. |
|
|
EDIT: Its got something to do with the difference between the release and debug builds. I can't replicate the issue using 'fs2_open_3_6_12d_INF.exe' but it always happens with 'fs2_open_3_6_12r_INF.exe' as far as I can tell. The moment the game starts (i.e. as the intro-movie / cutscene plays) I loose all RTCT under the release build and I don't get any FFB in the missions either. Under the debug build it seems fine - both FFB and RTCT. -------------------------- This issue has existed in all versions as far as I remember - including the retail FS2 distribution (also with the 1.2 patch). Previously you could get around it by Alt-Tabbing out, going to the drivers of the device, and re-setting the RTCT value. I think this issue affects users of the other Microsoft Force Feedback devices too. The only reason I've logged it now is that there are no updated drivers coming out for this hardware from MS which allow you to configure things like the forcefulness of the Force Feedback and torque of the return to centre tension - meaning this workaround no longer works on Windows versions after XP SP3. It still comes up as a valid gaming device supported by the generic drivers and DirectInput etc., but the other features from the "proper" drivers are no longer available to us in Windows Vista / Windows 7. |
|
|
Does this still happen? |
|
|
Will check as soon as I can - this might take a few days. |
|
|
Any status update? |
|
|
This appears to be resolved - all be it in a really weird and "I really don't get it but as a workaround it's done the job" kind of way. 0) Problem existed as described above. 1) Bought a new Sidewinder X3 mouse, installed the software which came with it - which allows you to configure things like the extra buttons on the device. (IntelliPoint - driver version 8.20.409.0, 18/05/2011) 2) Problem with joystick no longer occurs. 3)I did a System Restore to roll back before the X3 Mouse install: the problem returned. 4) I installed the Intellipoint stuff again (without attaching the new mouse), and the problem resolved itself again. 5) I removed the start-up-on-boot entry for the program that the IntelliPoint installer adds - IPoint.exe. The problem still appears to be solved. In conclusion: Nothing appears to have changed as far as the joystick settings or driver versions etc. (According to device manager its still the out of the box 6.1.7601.17514, 21/06/2006 version of the "HID compliant game controller"). For some reason installing the latest Intellipoint release from Microsoft fixes the issue, even when you're not using any devices which use drivers laid down by it and are not running any of the executables the installer puts down too. Go figure. Feel free to close off this bug report. Whatever is going on, I doubt its down to FSOpen - more likely its a weird quirk related to DirectInput / DirectX / Hardware Drivers or one, some of all of the above. |
|
|
Well, that's a relief. :) And that explanation makes the most sense out of any I can think of. Closing. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-08-29 23:29 | Alex_LQW | New Issue | |
| 2010-08-29 23:41 | Alex_LQW | Note Added: 0012339 | |
| 2010-08-30 23:17 | Goober5000 | Note Added: 0012340 | |
| 2010-08-30 23:34 | Alex_LQW | Note Added: 0012341 | |
| 2010-08-30 23:49 | Alex_LQW | Note Edited: 0012341 | |
| 2010-08-30 23:53 | Alex_LQW | Note Edited: 0012341 | |
| 2010-08-30 23:56 | Alex_LQW | Note Edited: 0012341 | |
| 2010-08-30 23:57 | Alex_LQW | Note Edited: 0012341 | |
| 2010-08-30 23:58 | Alex_LQW | Note Edited: 0012341 | |
| 2010-08-31 00:01 | Alex_LQW | Note Edited: 0012341 | |
| 2011-10-30 08:01 | Goober5000 | Note Added: 0012912 | |
| 2011-10-31 11:28 | Alex_LQW | Note Added: 0012915 | |
| 2012-01-22 07:34 | Goober5000 | Note Added: 0013105 | |
| 2012-02-08 00:06 | Alex_LQW | Note Added: 0013246 | |
| 2012-02-08 06:57 | Goober5000 | Note Added: 0013247 | |
| 2012-02-08 06:57 | Goober5000 | Assigned To | => Goober5000 |
| 2012-02-08 06:57 | Goober5000 | Status | new => closed |
| 2012-02-08 06:57 | Goober5000 | Resolution | open => no change required |
