Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Trivial Psychic on January 14, 2018, 10:08:17 pm
-
I have a Saitek Cyborg EVO (bought at Value Village for $7.99 a few years back, bargain, but that's another story) and it has been working find until now. The problem isn't the stick as Windows still detects it and the calibration software still indicates prefect operation. The launcher too detects it, but FSO completely ignores it. I was just trying out one of the new builds and found that I had no control. I went into the binding screen and attempted to rebind the controls and it wouldn't detect my stick input. I also tried reverting to an older build (Oct. 31th, my go-to build for proper lighting) and it wouldn't work either. Something is causing FS to completely ignore my stick. I tried cloning my pilot in case there was some kind of corruption and it wouldn't work either. I deleted that pilot and made another new one, no dice either. I tried unplugging and re-plugging my stick... nothing.
Here's my debug file using the Oct. 31st build:
I hope someone knows what the hell is going on.
[attachment stolen by Russian hackers]
-
Could you post your fs2_open.ini file? It should be located in %appdata%\HardLightProductions\FreeSpaceOpen\.
-
Done
[Default]
VideocardFs2open=OGL -(1440x900)x32 bit
TextureFilter=1
OGL_AnisotropicFilter=0
OGL_AntiAliasSamples=0
SoundDeviceOAL=Generic Software on Speakers (Logitech USB Headset)
SpeechVoice=0
SpeechVolume=100
SpeechTechroom=1
SpeechBriefings=1
SpeechIngame=1
SpeechMulti=0
CurrentJoystick=0
CurrentJoystickGUID=a3066404000000000000504944564944
EnableJoystickFF=0
EnableHitEffect=0
NetworkConnection=None
ConnectionSpeed=None
LastPlayer=FS1-Dude
ScreenshotNum=13
[Sound]
PlaybackDevice=Generic Software on Speakers (Logitech USB Headset)
CaptureDevice=Microphone (Logitech USB Headse
EnableEFX=1
-
The Joystick GUID in the log and in the settings do not match. I suspect that this is because the SDL version the engine uses is different from the launcher version. What happens if you use the newest nightly? Also, what launcher do you use?
-
I was testing out the latest build when that occurred first.
-
You could try running wxLauncher with SDL 2.0.7 and seeing if anything changes...
-
I'm using 0.12.0-RC2. Is that different from what you're referring to? If different, which build do I need?
-
He's talking about the SDL2.dll not wxLauncher itself. Try copying the SDL2.dll from the FSO build you're currently running into wxLauncher's directory (the one where the EXE is).
-
Ah. Got it. Done. I'll get back to you with the results. Thanks.
-
Ran into this same problem, and got a little confused by the advice in the thread. Trying to replace the .dll in wxLauncher's directory just breaks wxLauncher. Replacing the .dll in the FS2 root directory with one from a December 2017 nightly fixed the problem for me.
-
I noticed that with the launcher breaking, but didn't haven't had the time yet for a complete set of tests. I will attempt your fix though. Probably next week. Thanks.
-
@Rhymes: Judging from what I read on Discord, you tried to copy a 64bit DLL into wxLauncher's directory which is why the launcher broke (the launcher itself is 32bit).
Can you try again with the SDL2.dll from a 32bit nightly?