I don’t think me providing a video on clicking a button would help.
Just seems like some sort of bug on my end and I can’t really do anything to fix it, I’ve reinstalled studio and have tried opening it on other places but no luck. Seems to work fine when I switch to my laptop though.
This is happening to me regularly and is really quite frustrating as this button is vital for any sort of UI development.
Unfortunately I can’t find any easy way to reproduce it. The button works at first but as time passes it breaks until I reopen studio. Studio has team create enabled.
After trawling through Studio logs and trying a few things I’ve managed to figure out that this is likely the error arising from the button not functioning whenever clicked.
I’ve taken out a few numbers in case they’re sensitive. Message me for the full error.
2022-03-01T13:18:07.342Z,2012.342285,77e4,12 [DFLog::HttpTraceError] HttpResponse(#3140 0000020ED53A5260) time:155.1ms (net:155.0ms callback:0.0ms timeInRetryQueue:0.0ms)status:400 Target and EventType parameters are required bodySize:11 url:"https://ecsv2.roblox.com/studio/e.png?studioSid=####&clientID=####×tamp=1646140687562&userID=1696941&placeID=5575768736&category=Action&evt=&label=RibbonMainWindow&value=0&platform=64bit&dev_segment=top%5Fdev&SD.Platform.MD.DebugVersion=FFlagStudioFlushDeferredEventsBlock%2C%20FFlagFixMissingStudioStartupSummaryEvent%2C%20FFlagFixWinStudioMissingStartEvent&SD.StudioSession.MD.Type=None&SD.StudioSession.ID=####&SD.StudioSession.CT=####&SD.UserSession.MD.Type=LoggedIn&SD.Platform.ID=####.Platform.CT=####&SD.UserSession.ID=####&SD.UserSession.CT=####&SD.MainViewSession.ID=####
EDIT:
It seems to be caused occasionally when an auto-recovery file is created and you’re either messing with GUI properties or using the emultor. This can be tested easily by changing the auto save rate in settings.
It only happens when a auto-recovery file is created.
I’ve been noticing similar behavior myself - it seems to occur for me on every TeamCreate session I join - but doesn’t occur on those I initiate. It still functions via manual triggering in the Testing tab within studio, but having the button is far more convenient when testing.
Hi, I had this problem too and the way I would solve this is either clicking play on the normal emulator and stopping it afterwards. If this doesn’t work then another thing I would do is reopen the place. Hope this solves the problem!