As is well known, when using shiftlock/mouselock, the cursor is locked in the center of the screen.
However, due to some bug, the cursor simply detaches after a few seconds. This issue has been observed in many experiences; the demonstration was filmed using a standard (unmodified) “baseplate” template. This issue does not exist in the studio.
This issue is very serious, as it is essential in a significant number of experiments, and with this issue, it becomes simply unusable.
Demonstration in studio:
Demonstration in client:
Expected behavior
The cursor should remain attached to the center of the screen while shiftlock/mouselock is on and the standard roblox menu(CoreGUI) is not open.
Thanks for the report. We couldn’t immediately reproduce the problem - could it be an issue with conflicting software? What are your computer specs, and which version of the client does the issue occur on?
Furthermore, it seems that the place you provided in the private message is private - could you make it public + uncopylocked, or provide us the placefile? Thanks!
There is no third-party software running (except VPN/zapret. VPNs simply redirect traffic to a foreign server, while zapret changes outgoing traffic by splitting packets into pieces. These are used so I can use Roblox in my country and do not affect the client or studio, only the packets).
Info about the client:
PC:
OS: Windows 10 Pro, 22H2(19045.4894)
CPU: AMD A8-4500M APU with Radeon™ HD Graphics 1.90 GHz
GPU: AMD Radeon HD 7640G and AMD Radeon HD 7670M
RAM: 4GB
(My computer isn’t very powerful, but Roblox and Studio work fine on minimum graphics.)
Place now public and can be copied(but as i said, it happens everywhere)
(just recently noticed) A similar problem occurs in first person mode:
And recently circumstances forced me to reinstall the OS, now I am using Windows 10 LTSC, 21H2(19044.1288), Well, as you can see, the problems haven’t gone away.
The application was installed from the official website.
Perhaps the problem occurs on low-end devices?
I haven’t noticed any errors in the developer console.
Unfortunately, our team of internal testers tried to reproduce this bug without success.
We are marking this issue as ‘cannot reproduce’ for now, but if anyone is still experiencing the bug, please respond with any additional details that could help our investigation and we’ll be happy to re-open to look into it further.
