Happens in every place I open in Studio.
Log: https://devforum.roblox.com/t/camera-constantly-spins-while-in-shiftlock-mode/4738084
Expected behavior
Camera should not spin on its own.
Happens in every place I open in Studio.
Log: https://devforum.roblox.com/t/camera-constantly-spins-while-in-shiftlock-mode/4738084
Expected behavior
Camera should not spin on its own.
Hello! I hope you’re doing well.
Thank you for taking the time to submit this issue and for reading our message.
Don’t worry — we’ve got you covered!
You can find step-by-step instructions on how to generate and send the log How to post a Bug Report - Bug Reports - Developer Forum | Roblox
Following these steps will help us better understand the issue and work on a solution more efficiently.
Thank you again for your cooperation!
Also happening for me, anything that sets UserInputService.MouseBehavior to Enum.MouseBehavior.LockCenter results in intense spinning and either looking directly up or directly down.
Happening to me too. It seems to be that when you are holding right click while you are in thirdperson, and about to transition to the lock-center camera mode, this bug happens.
Hi, thanks for the report, we’re investigating. Is this only happening in Studio or Client as well, and what platforms?
Happens in first person and shift lock, only in Studio, running Windows 11.
Opening and closing the escape menu fixes it, but unfocusing the window will cause the issue to happen again when focusing again. Attempting to move the cursor away from Studio while inside of first person or shift lock will cause it to freeze in place until left or right clicking, and occasionally attempting to click away to unfocus while still focused will teleport the cursor back to the center of the playtest screen, and other weird buggy behavior.
Sorry for the inconvenience. We’ve identified the issue and now rolling back the change that caused it. We’ll update this thread once the fix is out.
The change has been rolled back. Please, restart Roblox Studio and let us know if you still have this issue.