You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Awesome software. best overall I have found so far. If only it would see different keyboards as their own device as well, that would make this perfect.
In my case I'm using a numpad to map as a DirectInput controller for race sims. It works well but it sees a keystroke to map so it does also impact the normal keyboard I have on the side. If I could map to the device instead of the keystroke like with game controllers, I could even add multiple numpad button boxes in the future.
The text was updated successfully, but these errors were encountered:
While technically possible, that would be a complete change of the input handling system as it would require the usage of rawinput rather than the Windows event queue. This is not something I personally see myself ever implementing as it's a significant amount of work touching core aspects of Gremlin and is something that a very small fraction of people will ever have any use for.
Thank you for the thoughtful response. It doesn't change the fact Joystick Gremlin is the best mapping software I found for a low cost and simple set up.
Although it would be nice to have full control over inputs, in the real world it's probably more practiacal to keep it at 1 keyboard based button box anyway and just build directinput hardware for upgrades as that has gotten pretty affdordable as well.
Awesome software. best overall I have found so far. If only it would see different keyboards as their own device as well, that would make this perfect.
In my case I'm using a numpad to map as a DirectInput controller for race sims. It works well but it sees a keystroke to map so it does also impact the normal keyboard I have on the side. If I could map to the device instead of the keystroke like with game controllers, I could even add multiple numpad button boxes in the future.
The text was updated successfully, but these errors were encountered: