Page MenuHome

Axis constraint guides are too big - graphical glitch
Closed, DuplicatePublic

Description

System Information
Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-20 05:59, hash: rBf470a02afaea
Worked: about 17th September?

Short description of error
When constraining axes the r,g or b guide is much larger than usual.
Edit - this is only in perspective view - guides are fine in orthographic views.

Exact steps for others to reproduce the error
Constrain an axis while translating

Event Timeline

same on OSX Mojave and AMD Radeon R9 M395X

dupoxy changed the task status from Needs Triage to Needs Information from User.Sep 23 2020, 5:49 PM
dupoxy added subscribers: Russell (russ1642), dupoxy.

This has to do with the Preferences - Interface - Line Width settings. If it's set to Thick the bug appears.

If this appears "too big" only when the preference is set.
Maybe a duplicate of [T80974 :Axes overlay when moving an object has become very large (Thick Line Width preference)]

@Wayne Johnson (slowboy) does changing Preferences - Interface - Line Width settings to Thin solve the issue?

This bug only appears for me when the Thick setting is used. Thin and Auto do not show the bug. Also note that when the bug appears the axis thickness is scaled by zooming. You can zoom in and have the axis line cover your entire view for example. This makes doing simple operations like moving an object next to impossible.

I have mine set to Auto, but yes, when it's set to thin, it's back to normal.

I'm only getting the bug with Thick.

Auto and Thick for me :]

dupoxy changed the task status from Needs Information from User to Needs Triage.EditedSep 23 2020, 6:24 PM

Ok thanks for the info.
Look like a duplicate of T80974 except that it's also showing with "Auto" Line Width Preference for @Wayne Johnson (slowboy).

Russell (russ1642) added a comment.EditedSep 23 2020, 6:36 PM

With a little trial and error I've found that the bug will appear with a setting of Auto and a Resolution Scale >= 1.19

I'm using a 3840x2160 monitor and Windows is set to scale its UI 150%. Hope that helps.