There seems to be a bug on the scale tool, specifically when using L Shift while dragging the part. It scales the entire part like it is supposed to. However, when you let go of L Shift while still moving the orb, it resets the brick to the size it was before using L Shift to scale it.
This was a deliberate behavior change (when you release shift it acts as though you did the drag without having shift held at all), though we hear the feedback on this. The old behavior will be restored in the September 23rd Studio release.
Happy to hear, I definitely prefer the old behavior. I ran into this as well; apparently I often hold shift to scale up a part in all dimensions really fast, and then fine tune afterwards on the dimension I initially grabbed. It really saves me time by just releasing shift and fine tuning with the same grab, instead of having to re-select the scale handle on the part.
With the update for the CTRL issue, whatâs its current state? For me it still has the strange teleport issue.
Also hereâs a cool build I made with with the new draggers. Moving the parts into place was a breeze, I do have to say the most time consuming part was probably resizing everything correctly
It will be changed back to the old behavior in the September 23rd studio release, I already fixed it but it takes a while for fixes to make it down our release pipeline. For the time being, also releasing and re-dragging the handle when you press / release Ctrl will give you the same behavior as before.
will there ever be an option to revert to the old draggers, since many people are requesting that
Iâm fine with the dragger itself, but why change the rotation tool? It worked perfectly before, and, frankly, looked much better than the new one. The old rotation tool was larger (easier to see), divided into slices more clearly, and just generally looked more professional. The new tool isnât difficult to use but is subjectively a downgrade from the old tool.
Why not just make the tools themselves optional? The dragger itself is good, but what if the users prefer the old visualization? They work exactly the same, one is just clearer and easier to use than the other, with everyone having their preference.
It only âworked perfectlyâ insofar as people were very used to it dealing with its downsides after 10 years of it working that way. No other popular 3d editing tool has its rotate tool work in that way (requiring you to grab at particular points to rotate), and for good reason.
The only existing issue that itâs unfortunate the rotate tool had to ship with is the visible segmentation of the rings. Weâre still going to fix that as soon as possible, the graphics feature we needed to avoid that just temporarily fell through and the visual difference is minor enough that we decided to proceed with the rollout without it.
Fair argument on the particular points, you get used to it but I can see how fixing this would be an improvement.
But in other than that, the visualization itself seems to lack anti-aliasing. The parts behind the tool are all smooth, while the tool itself is very pixelated. Studioâs quality level is set to max so Iâm not sure what could be causing this.
For reference, the old tool did not seem to have this issue.
The old tool didnât have anti-aliasing on most machines either, they use the exact same primitive rendering underneath the hood. The difference is that now that the handles are flat shaded, the fact that they arenât anti-aliased is more noticable. The old handles having some lighting applied to them partially hid the fact that they werenât anti-aliased.
On quality level 21:
Seems this problem still havenât been fixed?
Although this new update include a billboardGUI with text âLâ which help me to indicate where the position of part and the handle but I later find that I am not able to find the handle if the part is big in size.
Probably changing of mouse icon when you touch the handle would be better.
For example:
The handle did not show up and I would like to resize the height of the red part. However I did not know if I am able to select the handle like the left side of the picture, it would be a big chance of selecting the grey part instead. A change of mouse cursor (like the example) would be good to know if I am able to touch the handle.
Another problem I found: Seems the Collisions option do not work on the new dragger.
My bad, I intended to carry your exclusion from the rollout forwards, if that hasnât been carried forwards Iâll fix it. Iâm actually working on the fix for the handle culling right now, unfortunately it requires some very non-trivial changes to the renderer (and it required us to add a new API to HandleAdornments, which took a while to pass review, so we couldnât start on it sooner), so I wonât be able to get it in for next weekâs release.
But, yes, a fix for this is still coming, donât worry.
Details? It should work.
please, atleast make this OPTIONAL. many of my friends are complaining, half of us are, and this update wasnât widely wanted. it ruins things for a lot of builders and i hate to see this being forced on us!
Could you give us any specifics as to issues theyâre causing with your workflow and what you feel they âruin?â Thanks.
Please disable these new draggers for me, the rotate function is really confusing to me!
As others state here, it would be nice to have this optional but this ruins my building experience on Roblox.
I am very disappointed, I canât even develop anymore because the LUA dragger is extremely bugged
As you can see in this video I cant move the model properly, It is very bad and makes me close Roblox studio and do something else!
Canât even select parts, models properly
Restarting doesnât seem to fix the issue and I believe that there are more people with this issue
Do you have an XBox Controller connected to your machine? Try disconnecting it.
No, I donât have an Xbox controller connected
Itâs true that more people asked me to do the same but the problem still here also before it worked just fine with the Xbox controller and without.
I believe the âLuaâ dragger is interfering with the Xbox controller script right? Because connecting it made things worse!
PSA: If anyone else is having problems similar to @Sir_Numb (Where dragging a part âflickersâ back and forth between two different locations), and does NOT have an XBox controller connected to their machine, I would be very interested in talking to you about the details of your setup, please PM me.