Open univrsal opened 1 year ago
DS4 controllers doesn't seem to have full recognition by the overlay. Only ones that work are the d-pad, the joysticks, and the triggers. The rest don't show, even when clicked.
Just came from #302 , finally got around to trying this.
Not sure if you are still accepting gamepad related issue threads so I'll drop something here and let me know if I should continue it in a thread.
Checked that this detects my controller inputs, and it does.
Then I saw there was an update to input-overlay so I updated. Installed and hit my controller button and OBS crashed. It crashed every time a controller input was detected. It also seems like it wouldn't detect my controller until I unplugged it, then plugged it back in. Once I did, then hit any button, crash.
Did some looking around, and my config file had the old codes for controller inputs. So I updated it with the new codes from the config site, and it worked. Then I plugged my controller in and out, hit my button, and it crashed.
That's where I am now. It crashes if input something with the controller after the controller is disconnected then reconnected. This might be ok for some people but I'm emulating a controller thru ReWASD thru keyboard keys. I'm having it disconnect when I alt tab from the game, and reconnect when I tab back in. All so my keyboard buttons are free when I'm not in game. I did confirm all this behaviour with a normal controller, so I'm sure it's not ReWASD.
OBS 29.0.2. input-overlay 5.0.3
provide the crash log and the full obs studio log
Can you download the plugin build at the bottom of this page, install it and see if it fixes the crash?
That would be under "Artifacts" --- input-overlay-windows-x64-85da14516 Correct?
If so, that does fix the crashes but now it doesn't detect the controller inputs most of the time. And I'm struggling to see the pattern. At first I thought it only worked when the controller was plugged in when OBS launched. But then I tried that again and it's not detecting it. The only thing I think (?) I can confirm is that when it works or doesn't work, it will do so for the rest of the OBS session. If it works, then I can disconnect and reconnect the controller and everything is fine. You want logs?
I had an older version of this that worked great (possibly pre-5.0) but I wiped the OBS and had to redownload - now it's super busted.
I tried the latest release, as well as the most recent Actions build, but I only see my sticks and triggers working (no buttons will light up)
i just got V5.0.5 and i don't see any inputs from my Gulikit KK3 the program linked in #297 can see my controller's inputs correctly but i don't see any inputs on the pro controller overlay of that version's preset .zip file if i swap it from Bluetooth mode to USB mode(wireless dongle that emulates a 360 controller) it doesn't work either
i just got V5.0.5 and i don't see any inputs from my Gulikit KK3 the program linked in #297 can see my controller's inputs correctly but i don't see any inputs on the pro controller overlay of that version's preset .zip file if i swap it from Bluetooth mode to USB mode(wireless dongle that emulates a 360 controller) it doesn't work either
I can also confirm my pro controller does not work with the default preset (switch or default gamepad).
When I first added the input overlay source, my joysticks seemed to be in non default positions. Restarting OBS put them back in the center, but still no input is being shown on the overlay.
The controller test program (sdl2.gamepadtest.zip) seems to read the inputs fine
18/6/24 - Update Bluetooth seems to work fine (was charging controller yesterday), but not over usb.
I've just finished some tests with SDL2, and it seems like I could replace the gamepad library with it. Before I do that, it would be good to have some people test SDL2 with their game pads to see if the mappings are working. SDL2 is used in a lot of games so I assume there shouldn't be any issues. I've attached the SDL2 gamepad test.
sdl2.gamepadtest.zip Holding shift will show the back of the controller with additional buttons.
I'll also close all gamepad related issues and we'll just use this issue to collect information regarding gamepads.
SDL2 tests so far
Previous gamepad issues:
294
286, #253
Should be fixed when using SDL2
260
Should work with SDL2, if not I won't spend any additional time on this for now
208
Apparently a crash with the gamepad library, should be fixed when using SDL2.
195, #191
Mapping/ D-Pad issue should be fixed with SDL2
183
SDL2 should support xbox one gamepads just fine
175
More mapping issues once again SDL2 should handle them correctly
241
Another dpad issue
116
General issue with gamepad being detected
213
Razer Rajiu not being detected, apparently that is a controller, so sdl will most likely handle it just fine.
196 DirectInput implementation seemed to have caused stalls (probably waiting for a mutex)
Semi related issues:
285 The incorrect position of the analog sticks is an issue with the library using different value ranges for linux and windows
199 The binding tab will be removed as sdl2 should take care of correct bindings