Intended implementation of Force Feedback and other controller features in 5.6

Development Programming & Scripting
, ,
1

Hello!

It seems like there has been a push in creating a new standard/“intended way” of utilizing the controller features in Unreal Engine since 5.2, and I’ve wanted to check what the current recommendations would be.

We’ve been previously only using Force Feedback assets for “classic” approach to vibration (Xbox controllers), while utilizing the submix in audio (with endpoint of vibration output) for the audio based haptics (for DualSense), as it seemed like the way to go in 4.27 and earlier versions of UE. But, perhaps, this is now considered outdated or potentially can be deprecated in the future?

In essence, what I would like to know is:

  1. Should all Force Feedback (including audio-based haptics, Sony’s Adaptive Triggers and Microsoft’s Impulse Triggers) now be handled via Force Feedback assets as explained in https://dev.epicgames.com/documentation/en\-us/unreal\-engine/force\-feedback\-in\-unreal\-engine?application\_version\=5\.6 ? If it isn’t and the described above method of using submix is used, what are the downsides and what is the current “vision for the future” from Epic as far as these features are concerned?
  2. If Force Feedback assets are indeed required now, does this also include using said assets inside sequencers for cutscenes, or would that have a different solution?
  3. The Light Bar functionality of DualSense should also be handled via Force Feedback assets or is there a better way?
  4. For controllers with speakers (like DualSense), is there a “correct” way of implementing the sounds, with the fallback like “if the controller speakers sounds are set to 0 volume, play sound through main audio output device”?

Hope this isn’t a very complicated issue.

Thank you!

2

Steps to Reproduce

3

Force feedback assets are not required to handle trigger haptics, and the setup you describe will work perfectly fine.

5.2 added the input device subsystem and "Device properties). You can use the input device subsystem to set active “Device Properties” to do things like set trigger resistance, controller light color, and more. You can also now do this right from within force feedback assets, which makes it a lot easier to set things up for more complex trigger affects all in one place. It is not required that you use it though.

Lyra actually has a test map in its ShooterTests plugin which you can see examples of using these new systems, as well as how to set up the audio submix assets for playing things through the speakers versus the main audio.

I hope that helps!

Ben