adelinadragonborn
New Member
Thanks for reply! Unfortunately non of them work, I assigned keycodes 0x10, 0x11, 0x12, 0x13 in io-cct and OBS doesn't work with those codes, apparently.
- Thread starter univrsal
- Start date
univrsal
Active Member
Can you download the sdl2.gamepadtest.zip from here and see if the button events show up in the console?
Gamepad issues · Issue #297 · univrsal/input-overlay
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 ...
github.com
adelinadragonborn
New Member
Tested, button events for paddles are not showing up in console.Can you download the sdl2.gamepadtest.zip from here and see if the button events show up in the console?
Gamepad issues · Issue #297 · univrsal/input-overlay
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 ...
univrsal
Active Member
Then it's most likely an issue with SDL not getting events for those buttons, not sure what would cause it, though.
wysoczanski
New Member
hey, is there any way to display an overlay just on top of a game without recording ?
FrizouWasThere
New Member
Hey there, I absolutely love this extension and I find it very useful for there to be a tool that assists the creation of layouts.
Unfortunately, I have ran into an issue that I cannot fix no matter what: I am using a canadian french keyboard both in hardware and software and for us, the # key is located where is -I believe- the ` key, on top of Tab and left to 1. While I can set up and use the layout I have created perfectly fine, the # key specifically is never recorded and will never be highlighted inside of OBS. In the web editor, it seems my input of # is recorded correctly though. If you know what I can do to fix this issue or if this might be something I'd have to report to the OBS github, let me know.
Unfortunately, I have ran into an issue that I cannot fix no matter what: I am using a canadian french keyboard both in hardware and software and for us, the # key is located where is -I believe- the ` key, on top of Tab and left to 1. While I can set up and use the layout I have created perfectly fine, the # key specifically is never recorded and will never be highlighted inside of OBS. In the web editor, it seems my input of # is recorded correctly though. If you know what I can do to fix this issue or if this might be something I'd have to report to the OBS github, let me know.
univrsal
Active Member
univrsal updated Input Overlay with a new update entry:
Some fixes and new presets
Read the rest of this update entry...
Some fixes and new presets
Read the rest of this update entry...
univrsal
Active Member
Try running demo_hook.exe and see what keycode shows up in the console when you press it. You can also download the file from github:
Add support for Mac Catalyst. Fixes #168 · kwhat/libuiohook@90c2248
A multi-platform C library to provide global keyboard and mouse hooks from userland. - Add support for Mac Catalyst. Fixes #168 · kwhat/libuiohook@90c2248
github.com
FrizouWasThere
New Member
It seems it was indeed the incorrect keycode, but replacing with the supposedly correct one (222, or 0xDE, according to the linked program) does not change anything inside of OBS. I have made sure that I saved the .json and restarted OBS on multiple occasions without any results. Checking with the web editor, the keycode was indeed changed to 0xDE so it should be the right one.
Hephaistos
New Member
Hello,
my Wireless Xbox Controller goes instantly off since I updated the Input Overlay to v5.0.5
my Wireless Xbox Controller goes instantly off since I updated the Input Overlay to v5.0.5
What is really curious is:I don't know if browsers detect the paddles, so I'm not sure if I can add support for them to the editor. You should however be able to set the keycodes manually. Just untick "record keycode" and enter the number:
View attachment 102989
Here's the list of codes:
Specifically the paddles:
Not sure which one is the correct one, so you'll have to test that.
SDL_CONTROLLER_BUTTON_PADDLE1 16 SDL_CONTROLLER_BUTTON_PADDLE2 17 SDL_CONTROLLER_BUTTON_PADDLE3 18 SDL_CONTROLLER_BUTTON_PADDLE4 19
It might just be that the anti cheat prevents the plugin from working. I don't think there's much that can be done in that case.
I was able to make toe plugin works when I open another "program" which do the same.
For example, if I download nohboard and open it, the OBS Input overlay instantly works in GTA 5, but if I close the nohboard program, the OBS Plugin stop to work.
The only think I can guess is: somehow the obs input overlay plugin need any DLL loaded or smth like that similarly to nohboard, but when another program loads that dll, the plugin start to work.
So at this moment, when I want the plugin to works properly in GTA 5 I open the nohboard, so plugin start to working and let the nohboard "opened" in bg to input overlay works.
Got an interesting issue. Currently, I'm competing with one problem vs. another, and this one seems like the problem most likely fixable.
I have an SN30 Pro that I'm trying to get working with this plugin, but I only seem to be able to get it to be seen by the plugin if I connect to my PC via XInput mode (causing it to be seen as an XBox pad). This works perfectly fine... except that because it's an XBox pad in this mode, the bottom L and R buttons are seen by everything as analog triggers. Where I'm trying to use it, it is unable to recognize both buttons being pressed at the same time (ZUp at max and ZDown at max cancel each other out and it is seen as no input at all).
This changes if I instead connect under DInput, where the bottom L and R buttons are seen as the digital buttons they are, but the plugin does not seem to recognize this as a controller anymore. As what I'm trying to play on isn't going to be changing any time soon, I'm hoping I can instead find a means to get this plugin to see the pad while in DInput. Any ideas on what I might be missing?
I have an SN30 Pro that I'm trying to get working with this plugin, but I only seem to be able to get it to be seen by the plugin if I connect to my PC via XInput mode (causing it to be seen as an XBox pad). This works perfectly fine... except that because it's an XBox pad in this mode, the bottom L and R buttons are seen by everything as analog triggers. Where I'm trying to use it, it is unable to recognize both buttons being pressed at the same time (ZUp at max and ZDown at max cancel each other out and it is seen as no input at all).
This changes if I instead connect under DInput, where the bottom L and R buttons are seen as the digital buttons they are, but the plugin does not seem to recognize this as a controller anymore. As what I'm trying to play on isn't going to be changing any time soon, I'm hoping I can instead find a means to get this plugin to see the pad while in DInput. Any ideas on what I might be missing?
To add, I should note that using the online tool to build an overlay only partially recognizes the pad in DInput mode - no option seems to recognize the d-pad portion.