Our experience (private, in development) triggers HapticService bumps upon hitting objects in the game with your ball.
Fairly recently, haptics started having issues for one of our places- and only for that PlaceID and only on mobile. Desktop w/ controller (in the same session) with the same codepath works just fine. We have verified we are calling :SetMotor() properly, with no errors, on both platforms in the same way. We have also ran the following code with these results on both platforms:
for _, enum in pairs(Enum.VibrationMotor:GetEnumItems()) do
print(enum, HapticService:IsMotorSupported(Enum.UserInputType.Gamepad1))
end
--[[ Results:
Enum.VibrationMotor.Large true
Enum.VibrationMotor.Small true
Enum.VibrationMotor.LeftTrigger false
Enum.VibrationMotor.RightTrigger false
Enum.VibrationMotor.LeftHand false
Enum.VibrationMotor.RightHand false
]]
If we publish the same file (same code, same models) to a different PlaceID, it will work just fine on mobile. It’s only this place ID and on an iPhone 12 Pro / iPhone 14 Pro / iPhone 15 Pro Max that this problem will happen. We have not tested with Android yet, but we will soon as this may be a very important clue if it works just fine on Android.
Symptoms: Haptics work for ~3 seconds and then completely cease to work afterward. Joining the same experience at the same time on desktop w/ controller will work just fine
Devices: iPhone 15 Pro Max / iPhone 14 Pro / iPhone 12 Pro
Link: [Included in staff-only notes]
API:
HapticService:SetMotor(Enum.UserInputType.Gamepad1, Enum.VibrationMotor.Large, 1)
-- As well as
HapticService:SetMotor(Enum.UserInputType.Gamepad1, Enum.VibrationMotor.Small, 1)
This PlaceID happens to be our production environment, so we’d like to keep it without having to move over.
I’m not aware of any place-specific settings related to haptics. And it doesn’t make a lot of sense to me that it works for 3 seconds and then completely turns off. I’ve spent an hour verifying it wasn’t the code. Same exact code works in another place.
Expected behavior
HapticService should work on mobile for more than 3 seconds for this place ID
A private message is associated with this bug report
