Hints with sizes of brush shows up on world-axis for some camera-angles · Issue #2487 · TrenchBroom/TrenchBroom · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TrenchBroom 2.1 (and older version, 2.0.6) on Windows 10
Expected Behavior
Hints with sizes of brush shows up on the brush itself, if there enough place due to camera view.
Steps to Reproduce
Create new map
Move default brush away from center of world-axis
Zoom in camera, so brush would not completely fit camera-view and look at brush from different angles.
Looks like sometimes editor wants to place this hint on specific brush-edge (not on any suitable edge) and if it can't - it places it on world-axis.
At some camera angles and zoom (and brush coordinates), world-axis could be completely outside of camera view, so it looks like hints doesn't appear at all (probably it's not an issue if in most cases this hints would be placed on brush edges).
The text was updated successfully, but these errors were encountered:
Hmm, looks like the bounding box did not get updated.
kduske
added
Type:Bug
Errors and problems
Prio:2
Medium priority: Non crash bugs that impede the user, features that add new functionality.
labels
Dec 10, 2018
System Information
TrenchBroom 2.1 (and older version, 2.0.6) on Windows 10
Expected Behavior
Hints with sizes of brush shows up on the brush itself, if there enough place due to camera view.
Steps to Reproduce
Looks like sometimes editor wants to place this hint on specific brush-edge (not on any suitable edge) and if it can't - it places it on world-axis.
At some camera angles and zoom (and brush coordinates), world-axis could be completely outside of camera view, so it looks like hints doesn't appear at all (probably it's not an issue if in most cases this hints would be placed on brush edges).
The text was updated successfully, but these errors were encountered: