Page MenuHome

Transform gizmo: Scale handles and rotation handles overlap on ortographic views
Closed, DuplicatePublic

Description

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59

Blender Version
Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: rBa2d59b2dac9e

Short description of error
Rotation handles cover related scale handles, all ortographic views are affected. Same issue as for T57203: Transform gizmo: Scale handles and rotation handles overlap

Exact steps for others to reproduce the error

  1. Add any mesh to the scene
  2. Switch to ortographic view alligned with any axis
  3. Use transform tool. Try scaling object via handles.

Event Timeline

Pratik Borhade (PratikPB2123) changed the task status from Needs Triage to Needs Information from User.Jul 14 2022, 7:47 AM

Thanks for the report. Am I understanding it correctly that you're not able to use scale handle (instead it detects rotation gizmo)?

Rotation handles cover related scale handles

Even though they are overlapping, I'm able to use both scale and rotation handles.

I tested the thing a little. It is actually possible to scale it in orto view, but only if approaching the handle with mouse from the side towards square at the end of the handle. Most part of scaling handle is overlapped by rotation handle (for 3.0 version, I guess, scale was displayed in front of rotation thus both were easily reachable).

Pratik Borhade (PratikPB2123) changed the task status from Needs Information from User to Needs Triage.Jul 19 2022, 3:37 AM
Omar Emara (OmarSquircleArt) changed the task status from Needs Triage to Needs Information from User.Jul 19 2022, 11:37 AM

It seems to be working fine here as well even when approaching the line before the square. Did you change any preferences related to the gizmo? Like its size?
Does it work with factory settings? File > Defaults > Load factory Settings.

It should also be noted that I get identical behavior in 3.0, did you confirm the change in behavior between 3.2 and 3.0 or just a guess?

Seems like false alarm - resetting to factory settings fixes the issue.
Although while having all my addons up, the case is persistent. I managed to observe that behavior only on Layout workspace tab.
Which setting I should look for in addon scripts to find that bug?

If there are only a handful of extra add-ons enabled, just disable them one by one until you find the culprit. If they are large in numbers, you can disable them in groups.

I finally got some time to go through the thing - I disabled addons one by one to find the culprit. The thing is that even while having all add-ons disabled manually, scaling part of gizmo still hides, so perhaps it is not the addon itself the reason but some changes it introduces to blender settings?

In Preferences > Viewport, there are some options related to Gizmos, like Gizmo size, did you check those settings?

Yes, 85 px gizmo size. Changing/resetting settings there were no help

Can you attach the userpref.blend file? It should be available in blender/3.2/config/userpref.blend.

Sure thing!

Omar Emara (OmarSquircleArt) changed the task status from Needs Information from User to Needs Triage.Aug 4 2022, 8:38 AM

I can't replicate even with your userpref unfortunately.

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Aug 4 2022, 3:25 PM

Can you check if it is related to the GPU Depth Picking option in PreferencesViewportSelection?

Checked, same behaviour with and without the option. Please refer to the attachment. Worth mentioning that this happens only in Layout Workspace. Others like Modelling or Sculpting seem to not be affected.

I cannot reproduce this either.
And I don't see much how we can help.
Without being able to replicate or knowing the settings that affect it, unfortunately this can't be triaged as a complete bug report.

Many bugs are fixed between the official releases. Please try the latest development snapshot of blender: https://builder.blender.org/download

I can now replicate the issue. It seems the small scale of the object is the significant part in being able to reproduce the issue. This is the same as T100321. So I will merge.