Lemontree Softworks - Enhanced Raw Input - Support for all Windows game controllers

Distribution Product Discussion
1
Features

  • Supports all HID gamepad/joystick devices (steering wheels, flight controllers, joysticks, including gamepads like Xbox Controller, etc.)

  • Hotplug support

  • Support for multiple simultaneously connected devices, e.g. for multiplayer

  • Automatic detection of the axis range and mapping to gamepad range (-1 to +1), axis range (0 to 1) or raw values of the driver (configurable)

  • 100% compatible to "Enhanced Input"

  • Automatic mapping of axes/buttons/POVs to engine keys

  • Manual mapping, via configuration, also possible

  • Up to 8 Axis, 128 Buttons, 4 POVs/Hat Switches/D-Pads

  • C++ and Blueprint function library for extended information such as: manufacturer, product name, serial number and information about axes and POVs

  • Built-in function to use Hat Switches/POVs directly as D-Pad buttons

About

"Enhanced Raw Input" is ideal for supporting all gaming input devices on Windows. All devices recognized by Windows as HID game controllers are supported. It is a direct replacement for the included ā€œRaw Inputā€ plugin with extended capabilities and does not have the limitations of it, such as: no hotplug support, no multiplayer support, or simple use of the D-pad.

Documentation

Support

2

Does this work correctly with 5.6?
The old native RAWN INPUT plugin has the problem that it does not register Axis input anymore.

3

Ok, tested it out myself. Works perfectly fine.

1 Like
4

Plug in a generic joystick device (arcade stick, etc.) and press a button quickly. On a print, the print doesnā€™t print every time the button is pressed. More presses increase this delay (buffer?). Testing via a gamepad testing website does not reflect this, nor does Steam input, so this seems directly related to the plugin.

This makes this plugin fairly unusable in this stage.

5

Does this also happen when you start the game in standalone mode or as a packed game?
The Editor Viewport (especially in debug mode) can sometimes delay inputs.

6

just tried it out and it does not seem to offer good support to dualsense controllers. the dpad(POV Axis 1) is constantly firing ā€œupā€ every tick. I also noticed that it usually fires button presses twice in a single tick when pressing a button. also, the debug menu is not showing up in console commands

7

Thanks for the feedback.
I can confirm the problem with the D-pad on the Dualshock controller.
A fix is in the works and will be available soon.

showdebug enhancedrawinput as a console command should work. Please note that the debug HUD is only displayed in the viewport or new window (PIE) and when the game is also started.

8

@dragon_souls_1 Version 1.1 is now on Fab, Dualshock D-Pad should work now.

9

Is there a method to ask which [key]s are set to a specific controller?

I was hoping to get that with something like ā€œGet Axis Infos for Deviceā€ but the [key] value is missing there.

10

Do you mean when ā€˜Auto Assign Controllersā€™ is enabled?

Yes, you can use ā€˜Get Axis Info for Deviceā€™, for example, to find out which axes the controller supports. Axis X (Axis Usage enum) is then assigned to the corresponding key: X to ā€˜Enhanced Raw Input Axis Xā€™, Y to ā€˜Enhanced Raw Input Axis Xā€™, RX to ā€˜Enhanced Raw Input Axis Rxā€™, etc.

For buttons and POVs, the corresponding index in the array: Button with index 0 is ā€˜Enhanced Raw Input Button 1ā€™, etc.

11

Thank you that helps a lot.

Yes itā€™s with auto assign.

Does that mean if a second controller/joystick is installed it will get the same keys attached?

12

Yes.
With ā€˜Use shared deviceā€™, the controllers share a device, so to speak, meaning that Unreal only sees one controller, but both controllers function in parallel.

Otherwise, (without ā€˜Use shared Deviceā€™) the second controller is assigned to the second player (player controller). With enhanced input, the inputs are then treated independently of each other. No need for other keys.

13

Hmm, ok.

Thatā€™ll make setups impossible where two input devices are used for different things.

With the old RawInput I wrote additional code to change the keys applied in engine (in the game menu), guess Iā€™ll have to do that here as well.

Edit.

Thanks for your fast replies

14

Would you like to have the input from two (or more) joysticks/controllers in one player?

Send me an email (lemontree-softworks (a) outlook.com) I may have something for you, but I need to clarify a few things first.

15

This plugin works perflectly !
There a resolve my issus with RawInput in 5.6

1 Like
16

Thanks for the offer. Iā€™ll write you later next week.

We got a demo to be out on Monday and I fight with the enhanced input system not wanting to rebind the axis keys on the fly for some stupid reason. So I donā€™t really have the time for anything else.

Is it possible that the 1.1 version for 5.6 isnā€™t available?

Got it for 5.4 but 5.6 stays the same. Or is that another FAB bug I have to deal with?

17

I just checked: The version for 5.6 that I uploaded to FAB is definitely the right one.
But youā€™re right: The latest update isnā€™t showing up for 5.6, so Epic must have messed something up when checking and deploying it. Iā€™ll sort it out with the support.

18

Seems to be some kind of problem with the Unreal Game Launcher.

Try uninstalling the plugin, clearing the cache (https://www.epicgames.com/help/en-US/epic-games-store-c-202300000001639/launcher-support-c-202300000001735/how-do-i-clear-the-launcher-cache-on-pc-a202300000013316) and reinstalling the plugin. That worked for me.

19

Thank you.

Edit.
I had to do the things from the link and disable automatic updates.
Then I was able to get the newest version thru ā€œInstalled Pluginsā€.

I really wish Epic would spend some time fixing all the old ā€œnewā€ stuff before adding even more features that only partly wƶrk like they should.

20

Hi @LemontreeSoftworks
I have a issus with your plugin.

In the SendControllerEvents function, the message:
MessageHandler->OnControllerButtonReleased(ā€¦) sometimes does not trigger. However, with the ShowDebug function, we obtain the correct value (false), but SendControllerEvents continues to send Pressed with repate.

Edit:
It is possible that the problem stems from the fact that the SendControllerEvents() and ProcessMessage() functions are not on the same rate and that ProcessMessage disables HasChanged before SendControllerEvents() is called.