SDL2InputDevice provides a new UE4 input device that utilizes the Simple DirectMedia Layer (SDL2) library. This device can then be used to access or provide more advanced functionality than what is available in the engine by default. It was designed from the start to be as transparent to UE4 as possible. SDL2InputDevice is as its namesake suggests a new input device. This solution means that input is passed into the various game systems of UE4 through the existing input pipeline. With SDL2InputDevice, there is no need for hacky blueprint glue code or special processing
Sorry about that. It’s a left over bug from when I pulled the code out of the project it was originally used it. The system button doesn’t have a UE4 GamepdKey equivalent because typically the OS doesn’t pass that through. If you are familar with C++ you can apply a quick fix by making the following change to FSDL2InputDevice::GameControllerButton() in SDL2InputDevice.cpp:
We have released version 1.1. This has some critical bug fixes that you’ll want if you are trying to use the plugin for non-game controller support. I’ve also released a new example project to our github page that is more flight-stick focused.
How do I uh… use a t16000m with this? I downloaded and installed the plugin, then tried using your flight stick demo and I was told by Unreal that the 4.25.3 is incompatible with the uproject file.
Is just want to rotate a cube using the flight stick at this point.
Failed to copy D:\hoevo_vehicle\Hoevo_Vehicle\Plugins\SDL2InputDevice\GameControllerDatabase\SDLControllerMappings.dat to D:\hoevo_vehicle\Hoevo_Vehicle\Saved\StagedBuilds\WindowsNoEditor\Hoevo_Vehicle\Plugins\SDL2InputDevice\GameControllerDatabase\SDLControllerMappings.dat
I just tested the plugin with 4.25.4 which is the last 4.25 version and it worked fine. You can try changing the “EngineVersion” value in the uplugin to just 4.25 and see if it clears up the notice. As for how to use it with a t16000m it should just work with RawInput. Check the examples.
Hello, I have the same problem on version 4.26.2.
I have to manually create the GameControllerDatabase folder under SDL2InputDevice and put SDLControllerMappings.dat into it to package successfully.
This is a bug. I’ll release a 1.2 patch shortly but in the meanwhile, in the file SDL2InputDevice.Build.cs at the very end of the file, you can see where I added the dependency. I remove that file in 1.1 but forgot to remove the dependency. Just remove this section:
// Add a dependancy for the Controller Database. NOTE: SDL2 has a default GameController compiled in, but this was we can
// add things without having to recompilee.
string ControllerDatabasePath = Path.Combine(PluginDirectory, "GameControllerDatabase", "SDLControllerMappings.dat");
RuntimeDependencies.Add(ControllerDatabasePath);
Hi, Recently I tried to package the XSX platform,I got an error in the log,It seems that the test is ok before replying to you on August 4th,Now there is an error, can you help fix it？
I tried to use the plug-in in XSX back in August and didn’t make any mistakes.
feel free to reach out to me via email (i’ve DM my address). The only supported platforms are Windows 32/64bit but I’m happy to help you try and get it working on a different platform.
Maybe I missed something, but I am not able to create SDL Preview Key or other SDL events in the blueprint. all of them appearing as messages, In 4.24, 4.25, 4.26, Copying from the Example project creating custom event.
so I’m trying to get my DS4 controller to work. I created a custom GameViewportClient class and like you said in the documentation, I receive duplicate input events one from XInput and another from SDL as expected.
I log the controller ID that I get from that input event, first one is 0 and another is 10 or 11 or 12 (depending).
In the doc it says to use the SetControllerID function on LocalPlayer, but when I do SetControllerID(10) or 11 or 12 etc anything other than 0, I lose all input and nothing works including keyboard!
What am I doing wrong? do I need to do something else?
You are not doing anything wrong. You’re setting the default player controller’s ControllerID to 10 which causes keyboard input (which is always ControllerId 0) to be ignored at that player controller. This is a side-effect of trying to exist peacefully with the default input system. How you deal with this depends on your game. If you’re game is controller focused, then just utilize the first player controller as sort of a menu player controller that manages input for the UI. If it’s a mixed game (like say a flight-sim) then you probably want to flip it and have a new Joystick PlayerController that funnels input back to the main game player controller.
Or you can adjust the plugin to hijack existing controller ids instead of co-existing with them. It would be pretty easy to do. If you go this route and have trouble, go a head an PM me and I’ll try and help you get it worked out.
Hmm, interesting idea. Can you even pair or connect a controller to the Quest? I have a Q2 here so maybe I’ll give it a go over the holiday and see what’s what.
@Vector
Did you register the actor you are using here as a Previewer? There is a function SDL Register Previewer:
You’ll also need to make sure the actor that is receiving these events implements the SDL2Key Notification Interface. Once you do that, the SDL Preview Input Key event should become available to you.
Do you have a Mac build? I read in the Questions section to reach out to you for a Mac build in order to test it. I’m not the one who asked the original question, but I’d really like to see if this works since I’m developing on a Mac.
](filedata/fetch?id=1834559&d=1605924518)
