Still experiencing this all the time 
(Hard to take a screenshot because it disables the cursor)
Edit: I’ve noticed it seems to happen when entering then exiting play solo. Team create is enabled
3 Likes
I just tried this (sort of) and it worked. I say sort of because I actually just clicked on the “Parent” property of a “UIPadding” object since I was already editing UI anyways. Clicking changed my cursor to something else, and then I right clicked the property container to cancel changing it. My mouse cursor went back to normal right after. Nice find!
3 Likes
heres a lifehack; if youre on windows you can change the mouse loading icon. i personally made mine to be the inverted mouse cursor (so black and white instead of white and black)
this genuinely happens so often that i needed to make this change.
It’s been 7 months, any chance this will ever be fixed? It’s infuriating and happens multiple times daily.
1 Like
If this is still annoying you, you can fix it by play testing your game, hitting pause and then the resume button.
Crazy Roblox has not fixed this yet.
Quick “fix”:
Create a part, create an ObjectValue, assign the Part as the Value, unassign it by clicking the red X, Fixed.
Annoying, but better than restarting studio, plus you can always leave the part+objVal in storage for a quick fix.
24 Likes
This has happening ever since i was testing or making my own stuff.
Whether or not. Thanks bitsfps for the quick fix!
Hi all, would appreciate some help narrowing this one down. Can anyone point to a semi-reliable method of getting this to happen on baseplate or something we can access reliably on our end? Also, if anyone can get this to occur and snap a log that would help as well.
1 Like
I’m unable to provide a log myself at the moment, but the issue within this thread seems to be the bug of “when I press play at just the right time as it starts autosaving, the cursor gets stuck with the ‘loading’ image”
1 Like
Thanks Alphonce - just curious, what mode are you using? Team create, cloud save, group game, local file, etc? May or may not make a difference, but those do have different patterns for saving.
1 Like
I get the issue in a non team create game.
Both when working from the cloud (using ‘publish to roblox’), and working from local files. And as stated above it seems to happen sometimes when starting a playtest.
Thanks, if you’ve noticed does it coincide with autosave & hitting play as Alphonce has noted above? Also, any play mode? Or just Play Solo?
2 Likes
I’m not sure, but I do think that’s a possible cause. As it doesn’t happen always when playtesting. Maybe one in 10 playtests or so.
Also if it’s of any value: the fix described here does work:
1 Like
I can only speak for team create, which is where I’m occasionally experiencing this issue. Every single time it has happened for me, it has coincided with auto-saving and hitting play. I haven’t ever been able to replicate it on purpose but I have a feeling that the larger the place is, and therefore the longer auto-saving may take - the more likely you are to end up play testing at the same time as auto-saving and will also be more likely to experience this issue. I’ve tried to purposely time auto-saving with play testing to replicate this a few times but I’ve never been able to get it to happen on purpose, unfortunately.
To avoid confusion, this is the play button that I’m hitting.
1 Like
Majority of my projects utilise team-create solely for the purpose of autosaving; I’m unsure of if it’s possible to recreate this issue if you were to instead save manually, but it would be good to try (edit: to my knowledge the cursor icon doesn’t change when saving manually, so is therefore not an issue)
This is still happening to me when it autosaves or when im uploading an image to roblox. You guys really need to fix this, it is very irritating.
This was happening to me when my game was a large map, 9k parts with a lot of textures. But after I separated the game to multiple places, and less textures the issue with the forever spinning cursor stopped.
1 Like
Maybe that’s because your Autosaves are so quick they aren’t that likely to coincide with a Play? My game is heavy, but everything is stored away, the map is literally just a Baseplate, a 50x50 piece of terrain and 12 Parts used as a Greenscreen, still, Heavy game > longer time to autosave > frequent autosaves > this bug all the time, always related to Autosaving while pressing Play.
2 Likes
Not sure about that, because my current game has the same auto save function and the issue is not happening since I reduce the parts/textures amounts.
Hey, I’ve attached my log file, this has been a pretty consistent issue for me, it disrupts my workflow and I’d really like to see it fixed.
Thanks so much for your time.
0.578.0.5780566_20230606T181323Z_Studio_67411_last.log (4.0 MB)
4 Likes