[mrduckman]

For some odd reason, and having installed Logitech's drivers, both the Launcher 5.5d and wxLauncher 0.8.0 detect/get reported a "Microsoft PC-joystick driver". What's weird is that besides the issue with the sensitivity under a process with more than one core is that the twist function with this joystick doesn't appear to work.

I checked the forum and mantis before posting on either and couldn't find anything. I've attached the log file from the INF debug build.

System is:

AMD Phenom II X4 945 4 GHz
NVIDIA Geforce GTX465
4Gb of RAM
Joystick Logitech Force 3d Pro J-UL19
Windows 7 X64 Ultimate

I would appreciate any help, but I would be against using Logitech Profiler. 

I'll raise the bug if this is confirmed by others.

Thanks!

Cheers,
Mr. Duckman

[attachment deleted by ninja]

[mrduckman]

Greetings.

I would appreciate an answer, please. It's not as the joystick is not detected. Rather detected incorrectly. And the twist function doesn't work on the game, but testing it from the Windows Control Panel works normally.

Could this post be moved to the SCP forum, please, if no one had this issue?

Thanks!

Cheers,
Mr. Duckman

[Trivial Psychic]

I'm thinking that this is a Launcher issue.  Whatever means that XP uses to relay joystick info, that the launcher uses to detect, it appears that Win7 uses something completely different.

[Zacam]

I _believe_ it's related to the DirectInput inteface in FSO. It only reads how Windows containers the input device, regardless of what the devices software or drivers have to say, because those ALL go through the windows implementation layer. They have to.

Ex: My Saitek X52-Pro reads the same way. And aside from the slider on the throttle, everything reads properly, including twist. Though, by default, the "Twist" function is not associated to anything, I have to assign it directly. Same with the Throttle.

FSO (and by extension, the Launcher) at the current moment will always read based on the OS reported layer handler. This may change in the future, but I can assure you that so long as it listing that device, then it has detected that there is a Joystick attached and that the rudimentary and basic functions of it will work correctly, even though it's not "properly" reporting the "correct" device.

[Fury]

Though, by default, the "Twist" function is not associated to anything, I have to assign it directly. Same with the Throttle.

Most of the time "twist" does get mapped by default to joystick axis correctly, but there are few times when it doesn't. I fix this by simply resetting default control configs from in-game control configs. After that twist axis works as it is supposed to. This behavior doesn't seem to be joystick specific at all, as I've had it with three different sticks.

I believe FSO not mapping twist axis happens when you create a new player when you don't have a stick plugged in and enabled in the launcher. But I'm not too sure about this.

[mrduckman]

I'll check this out during the weekend and get back to you. I really appreciate your answers, guys.

Cheers,
Mr. Duckman

[mrduckman]

Well, took me more than that weekend in January. But it worked. Fury, you were right. For some reason, you need to reset to default control settings in the in-game settings.

Thanks!