Cursor stuck in select

Hello reader,

I’ve been having this occurrence for about a maximum of two weeks now, and it has to do with loading into Studio or deselecting GUI.

When you load into Studio it happens about 50% of the time. In either an already existing file or a brand new baseplate file. I happen to have found this bug reappear when I was making a custom stamina bar system, and it is the exact same result as when you load into Studio with this bug. The only way to get out of this stuck cursor state is to playtest the game. So far I know, not a single keybind or button press undoes this bug. I screen-recorded me triggering this bug with a 100% success rate. I have looked through the Bug-Report forums and I have not seen a single person mention this, it makes me wonder if it is such a present and easy bug to trigger, why no one else has come across it?

Video

In the video, as soon as I click the workspace after I was in the frame, my cursor starts pointing and I am unable to click anything. This will be the same state as the 50% chance when I load into Studio. I then run the game, as that is the only way that I know of how to exit this bug. I trigger it again to show that it is a steady 100% consecutive rate.

If you require anything else from me, please let me know. I would be more than happy to help.

Thank you.

6 Likes

We’ve filed a ticket into our internal database, and we will let you know when we have updates!

Thanks for flagging!

2 Likes

I have found another way to replicate this issue. I also added my plugin page to show it is not because of any third-party installments. The only way to free yourself from this locked cursor state is to either run the game or manually go back to any cursor state (CTRL+1/4).

It doesn’t only happen when I click to select what part is the attachment, it happens as soon as my cursor changes. When I did it the second time, I pressed the ‘X’ to cancel, and my cursor was still locked.

1 Like

I had a similar issue myself, try exiting full-screen.

2 Likes

Thank you for the bug report. I have a fix for this that you will hopefully see early next year.

I’m very glad to see that this has been handled quickly. I will mark the topic as solved once the bug fix has been implemented.

1 Like

Apologies for delay. The fix for this should be rolling out now.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.