Input Overlay v5.0.4

i Enjoy it a lot i just wish i could show more of the keys that i use when playing certain games.

I'm very new to obs and just figuring out plugins. When I ran the installer everything seemed good and the overlay was in the plugins folder, but when I went into obs the overlay wasn't there. Where would I go in obs to find it?

There are literally NO instructions whatsoever, and trying to find the image file it requests (even reading the comments) is infuriating so... after some searching I find it... except there is no mouse/wasd option. This is just not very well explained and honestly for someone looking for some plug and play option, this isn't it.

It works, but it's far more complicated than it needs to be and it does not work 'out of the box' you have to go through hoops just to get it to do what its supposed to do.

Its a good Plugin but, i dont understand the section of "2_key_row/col" i was unable to create my own keyboard
btw, still have a problem with the default presets
When i use the
Qwerty Full, this happens: http://prntscr.com/krzzzd
WASD Full, http://prntscr.com/ks00mo
And every preset is like that
Need help :C

Does more or less what it says on the tin, though setting it up and knowing where to put the image files and so on isn't mentioned in the "installation" instructions.

One major problem/oversight, though, and the reason I'm rating it the way it is, is that the "Input History" overlay has several keyboard buttons that it doesn't register. Specifically, no punctuation marks show up when you press them.

Since I was planning to use this to make some Photoshop and other tutorials more accessible with visible keystrokes, this oversight makes the plugin unusable for me, since ctrl++, ctrl+[, etc. are common keyboard shortcuts, and none of them register. (Ironically, they do show up on the keyboard overlay, but displaying the whole keyboard on-screen at once takes up way too much screen real estate.)

It looks like I'll have to find some external solution that runs outside of OBS.

Everything appears to work, but the I have to call the overall experience quite dysfunctional. Documentation is poor, leaves out large portions of information that the programmer seems to think is "too obvious" to tell us (or something, I'm guessing. Point is there's steps missing). Best to start with the presets and reverse engineer them to make your controller work (assuming of course that one of the presets doesn't suit your needs simply as-is).

Didn't play well with my retro controller. I used JoyToKey to remap it to different keyboard keys and set the overlay map as a keyboard overlay with the retro controller images. Speaking of which, the background image, the base controller, can't be included in either the OBS plugin or the (more importantly) the provided web tool to generate the .json file for your controller, for what reason I have yet to fathom. You just have to guess where the controller buttons should land and push them a few pixels at a time this way, a few more that way, until they sit properly on the base image. The image swap on the button presses is also a lot more cryptic than it needs to be. He's got this 3 pixel gap thing going on that seems to work fine in the videos but somehow it doesn't work that way when setting up your own controllers.

[sigh] ... all that said... if you can get through all those roadblocks, or, if one of the presets suits your needs, it appears to work just fine. I am satisfied with the final result, at least. It has not broken so far... knock on wood.

Hi How to use in Streamlabs OBS ?

Seems like it should work, but when I tried to make my own preset, none of the buttons would leave the far left edge of the source, making it useless. The only reason I'm not rating lower is because it looks like I ran into a pretty nasty edge case.

Worked for a while, but recently doesn't seem to detect any input whatsoever. May not be compatible with newer version of OBS anymore.

It's really not clear on where to put the file in

and the videos are in russian

Used this about a month ago, created the textures, exported the .jsons, loaded them up, everything worked fine.
Now the plugin asks for .ini files rather than .js? Something that isn't exported by YOUR tool. So until fixed cannot really recommend.

Doesn't actually seem to do anything. I've yet to find an instance in which this actually responds to keypresses or mouse buttons. It's just a picture you put in OBS.

The plugin is not compatible with Linux(Mint/Ubuntu) Libuiohook cannot be compiled as 'xt' is not available even after installing xen-tools

APPALLING!

The plugin itself doesnt work, it asks for an "overlay image file" and an "overlay config file". It doesnt come with any "default" options, in case you have no idea wtf it wants. It's just assumed whoever wants to use this is an uber-1337 coder who can figure it out.

Theres a video "tutorial" but its starts with just a finished product, and just a lot of talking, no showing from scratch how to set it up. A tutorial should start from the beginning and walk you through every single step. There is a "tool" to help apparently create presets, but no explanation of how to use THAT either. Again the tutorial starts off with a finished product so no good.

Raised as an feature/issue on github, and the dev replied to state that ANYONE WHO WANTS TO USE THIS PLUGIN IS EXPECTED TO KNOW HOW TO CODE HTML, JAVASCRIPT AND CSS!!!

Software seems great, but lack of support simply kills this. It is a download page with instructions which do not help at all. When you go to developer's tutorial, you find it to be outdated where he installs his plug ins to a master folder. I follow his instructions until I install his plug in into a obes program.

I load this plug in successfully and then he casually asks us to direct program to graphical files for this plug in which does not exist! This plug in looks like something which I might eventually figure out how to install. However, developer offers abysmal technical support to people here and the only feedback from him is not supportive, but rather combative and defensive rhetoric back.

I'm sorry, but this thing ruins experience for so many people and I want to this to be made painfully clear. Why I must to spend hours figuring out how to solve something which should be easily done via help of an installer?