Yes, I have been recommended those as solutions but oddly enough it doesn’t seem to work for me. I have tried switching to different desktops. Tried opening up mission control and even switching mouses but it didn’t work. I was always forced to completely leave out of game and rejoin.
But even if there was a temporarily solution, it’d be even better if it was fixed completely haha!
YES, me as well. Unfortunately, the only solution I’ve found is rejoining the game. I’ve noticed that this issue also occurs when you interact with the border of the window, such as resizing.
Really? Resizing the border/window works completely fine for me. It only happens when I get calls from other programs or another application asking me to update. Anything that jumps over the ROBLOX window will break the pointer for me.
I have this all the freaking time too. It feels like Roblox neglects Mac’s studio hugely. I posted this well over a month ago and bumped it, all Macs have this issue, and nothing has happened about it.
There are a limited number of resources we have at our disposal. As far as we know this only affects a single model but we aren’t able to reproduce this issue consistently enough to fix it.
I am easily able to reproduce my issue every time so maybe I could be of some help?
I’m just a bit bummed that this issue has been going on for months now and it hasn’t been fixed. It was an update that did this because this wasn’t always occurring. Hopefully soon this can get fixed.
I’ve had this problem for so long! I remember stumbling on this forum post and sighing but I recently found a cure! If you press F4 for the “Spotlight Search” whilst in-game it fixes the stuck cursor, atleast that worked for me.
In regards to fixing this problem, I have found that opening Launchpad, then closing it while moving the mouse could also fix the cursor.
When I open and close Launchpad without moving the mouse, the issue persists.
If the mouse is moving when Launchpad finishes closing, the issue went away for me.
I am unable to reproduce this issue on the same MacBook/OS. Is the issue still happening and, if so, are any extra steps necessary to make this happen?