[Temporary Fix] Select, Move, Scale, and Rotate permanently grayed out after opening scripts

Bug:

Upon opening a script via explorer and going back to the workspace, the building tools remain grayed out until you fully close any script.

This happens on both the new gen studio UI and the old. (No screenshot provided for new UI)
This also happens in all tabs with the building tools.
image

Steps to replicate:

Simply open studio, open any script via the explorer, and then click on the tab to open the workspace.
image
image


Temporary Fix:

Close any script after clicking back into the workspace

Expected behavior

Tools should be available again once returning to the workspace without the need to close the script.

8 Likes

Yup, experiencing the same issue. This latest Studio version seems to have broken a lot of things lol

4 Likes

Are you hitting the behavior every time you open up a new script, or only sometimes?

Every single time

charcharcharchar

Hopefully this helps visualize the issue

2 Likes

I’m running into the same issue—it just started today and has been slowing down my progress significantly.

1 Like

I am also experiencing this issue every time a script tab is present. Not being able to move bricks is quite disruptful ): Here is a short video.

1 Like

Hi thanks for the vids! Still having issues reproing this on our end:

  • we saw some traffic on this being team create places only, does that make sense or is anyone seeing it on local files too?
  • Is this 100% of the time once you get it? Like instantly opening a script will make it happen despite restarts etc? (Only closing the script re-enable the buttons, as OP has put in “temporary fix”)
  • If its not 100%, any guesses on usage patterns before it appears?
  • Will take a log if you’re getting bit by this, need more info to track this down. Just repro and send the latest log, can DM to me and link to this bug.

I have sent a repro log to @MeshOfPaul a while back.
Added a part.. added 1 script to the part - BOOM.. icons unselectable.

Thanks, will get that from him. That’s from just a brand new base plate on a fresh start of Studio, so no team create involved right? Just trying to clear out culprits. Would you mind DMing a dxdiag.exe dump just in case its some weird timing thing (unlikely). Also, if anyone can confirm a Mac repro, that would also help.

(And for others in the thread too, we’ll take more logs on this!)

Absolutely.. no team create.. just the standard plate + 1 part + a killpart script.

Will send via DM

1 Like

Hi - we reverted one change from our end that could possibly be related. Can people hitting this please confirm whether they are still seeing the issue after a Studio restart? Thanks.

Still happening to me after restarting studio, currently inside of a Team Create place.

Still happening to me as well.

Still happening to me too, this also happening in local files for me, not just team create.

Same here - closed project & Studio - restarted and opened project - still the same.
Did the same with a blank plate - added a part - added a script (zero extras) still happening.
The script only had the default print("Hello world!") :sweat_smile:

EDIT : I have NO IDEA if this is related or not (highly unlikely) - but previously - whenever I opened my project.. ROJO would pop up and ask if I must connect.
It only happens with this one project - but it doesn’t ask anymore (which is ok since I haven’t sync’d thru Rojo in a while). Just found it odd.. at the same time. (FYI)

ALSO : It doesn’t matter what type of script (Script, LocalScript, Module) - all the same reaction.

Still occurring and I’m in a team create session.

This issue also seems to be affecting more than just the modeling tools, as the device emulator is also grayed out and stuck on my screen.

1 Like

This should be resolved now, we have rolled out a patch.

2 Likes