Home/ Questions/Q 1053831
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T17:18:48+00:00

I’m trying to simulate keyboard commands for a custom game controller application. Because I’ll

  • 0

I’m trying to simulate keyboard commands for a custom game controller application. Because I’ll need to simulate commands in a DirectInput environment most of the usual methods don’t work. I know that using a hook would work 100% but I’m trying to find an easier implementation.

I’ve done quite a bit of searching and found that by using the SendInput API with Scancodes instead of virtual keys should work, but it seems to behave like the key’s are “sticking”. I’ve sent both the KEYDOWN and KEYUP events but when I attempt to send the message in a DirectInput environment, the game acts as if the key is being held down.

For instance, if I simulate a “W” keypress and have that key mapped in a First Person Shooter to the “move forward” action, once I’m in game, the function below will cause the character to move forward. However, just by issuing the command once, it will move the character forward indefinitely.

Here is a code snippet (in C#) for the SendInput function I’m calling:

[DllImport("user32.dll")]
static extern UInt32 SendInput(UInt32 nInputs, [MarshalAs(UnmanagedType.LPArray, SizeConst = 1)] INPUT[] pInputs, Int32 cbSize);

public static void Test_KeyDown()
{
    INPUT[] InputData = new INPUT[2];
    Key ScanCode = Microsoft.DirectX.DirectInput.Key.W;

    InputData[0].type = 1; //INPUT_KEYBOARD
    InputData[0].wScan = (ushort)ScanCode;
    InputData[0].dwFlags = (uint)SendInputFlags.KEYEVENTF_SCANCODE;

    InputData[1].type = 1; //INPUT_KEYBOARD
    InputData[1].wScan = (ushort)ScanCode;
    InputData[1].dwFlags = (uint)(SendInputFlags.KEYEVENTF_KEYUP | SendInputFlags.KEYEVENTF_UNICODE);

    // send keydown
    if (SendInput(2, InputData, Marshal.SizeOf(InputData[1])) == 0)
    {
        System.Diagnostics.Debug.WriteLine("SendInput failed with code: " +
        Marshal.GetLastWin32Error().ToString());
    }
}

I’m not sure if this method is a lost cause, or if there is just something silly I’m missing. I hate to over complicate my code if I don’t have to by using hooks, but this is also new territory for me.

Any help anyone can give is much appreciated.

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’ve found the solution to my own problem. So, I thought I’d post here to help anyone who may have similar issues in the future.

    The keyup command was not working properly because when only sending the scan code, the keyup must be OR’ed with the scan code flag (effectively enabling both flags) to tell the SendInput() API that this is a both a KEYUP and a SCANCODE command.

    For instance, the following code will properly issue a scan code key-up:

    INPUT[] InputData = new INPUT[1];

InputData[0].Type = (UInt32)InputType.KEYBOARD;
//InputData[0].Vk = (ushort)DirectInputKeyScanCode;  //Virtual key is ignored when sending scan code
InputData[0].Scan = (ushort)DirectInputKeyScanCode;
InputData[0].Flags = (uint)KeyboardFlag.KEYUP | (uint)KeyboardFlag.SCANCODE;
InputData[0].Time = 0;
InputData[0].ExtraInfo = IntPtr.Zero;

// Send Keyup flag "OR"ed with Scancode flag for keyup to work properly
SendInput(1, InputData, Marshal.SizeOf(typeof(INPUT)))

    Thanks to Hans for the response. I did some investigating and sending two messages back to back like the original example does indeed simulate a “keypress” but it’s very fast. It would not work well for a movement command, but would be ideal when action keys are to be “tapped” and not held down.

    Also, the virtual key field is ignored when sending a scan code. MSDN had the following to say on the subject:

    “Set the KEYEVENTF_SCANCODE flag to define keyboard input in terms of the scan code. This is useful to simulate a physical keystroke regardless of which keyboard is currently being used. The virtual key value of a key may alter depending on the current keyboard layout or what other keys were pressed, but the scan code will always be the same.”

    http://msdn.microsoft.com/en-us/library/ms646271%28v=VS.85%29.aspx

    • 0