VR Haptics are Unusable

Bug Reports Engine Bugs
,
1

Around when the HapticEffect instance was introduced, HapticService vibrations stopped working in my game entirely. I tried swapping to HapticEffects, but if I understand this post correctly HapticEffects dont even support PCVR controllers as of right now (and it didn’t work when I tried). I understand the HapticService is now deprecated, but if i can’t use HapticEffects either then I’m stuck without any vibration.

Calling SetMotor directly, nothing happens.
HapticService:SetMotor(Enum.UserInputType.Gamepad1, Enum.VibrationMotor.LeftHand, 1)

I’ve also made sure that Haptics are enabled in the game settings while playtesting.

2

Thanks for reaching out! We understand how important haptics are for creating an immersive VR experience.

It looks like PC-VR haptics weren’t previously supported on HapticService, so this would be considered a new feature rather than a regression. Both HapticService and HapticEffect should still work as expected on standalone VR devices.

We really appreciate you flagging this—your feedback helps us prioritize improvements. We’ll make sure to pass this along to the team for consideration!

1 Like
3

Sorry, I worded that totally wrong. I‘m using a standalone Quest 3 connected to a PC.

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.