Frequently Asked Questions
The game does not see Joystick Gremlin inputs, only the original joystick ones.
This will happen quite often as Joystick Gremlin cannot hide the physical devices inputs. The most reliable way to solve this is to use HidHide to hide physical devices from the game.
How to verify that Joystick Gremlin produces the desired output?
The simplest way is to use Gremlin’s builtin Tools -> Input Viewer and verify you see what you expect.
Another option is to use Windows’ game controller program, which can be launched by running joy.cpl. One drawback of this tool is that it requires focus to show anything which can be a bit cumbersome at times.
Macros don’t work in-game
The most likely cause for this is that the game was launched with administrator privileges while Joystick Gremlin was launched with normal user privileges. As the macro system injects key presses into the Windows event system, Joystick Gremlin has to have the same or higher privilege level as the receiving application. As such if the game is run as administrator then Joystick Gremlin needs to be run as administrator as well.
Another reason why macros might not work is that they send key presses too fast. By default Gremlin adds a small delay, however, should this delay be too small the game might not register these presses. The Settings tab allows changing this default pause duration and increasing it might help in some cases.
Macro doesn’t produce a stream of characters
A common misconception is that when a key is held down that this will result in a sequence of key presses. This stems from the fact that holding a physical key down a bunch of characters will appear in a text editor etc. What happens in reality is that Windows will, behind the scene, emit these characters at a set frequency, despite there being only one physical key press event.
This means that you should not expect to see a macro that holds down a key to result in a bunch of characters appearing in a text field, but only one. This is the correct behavior and games expect and handle this properly. To check if a macro sends the correct key strokes you should use a keyboard testing program such as https://keyboardtester.io/tester/, or any other one that a search turns up, to verify keys are pressed and released as expected.
My Xbox controller doesn’t work
Starting with Release 16 Gremlin detects XInput devices, such as Xbox controllers, and reads them through XInput rather than DirectInput, so no workaround is needed. This does not apply when the Use legacy dill option is enabled.
Releases before 16, and the legacy input library, see these controllers through their DirectInput driver, which is not working nicely. A common symptom is that inputs appear as if they only do something when Gremlin is focused. One possible workaround in that case is to use a tool called Xidi which effectively provides a better DirectInput behavior for Xbox controllers. You need to download the release and unpack it, then place the dinput8.dll file in the same folder as the Joystick Gremlin executable.
Version Xidi 4.2.0 is known to work so you should stick with that.