Wireframe mode bugs #57636
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#57636
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Win 7 64 Pro, GTX 1070, Blender 2.8
Blender Version
2.8 alpha 2 Hash:
c4c62e6df5
Worked: (optional)
Short description of error
Playing with 'Z' key, switching between viewport modes after a while hitting the 'wireframe' pie forgets to do anything.
Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
Added subscriber: @AlmaTalp
Added subscriber: @brecht
I don't have this problem, can you give more specific steps to redo the problem? Or attach a .blend where it is stuck in a particular mode?
I try to record it and upload as a GIF, I just played with the default cube, nothing has been changed, not scene-specific issue IMHO.
OK, I tested, it is partially a bug, also UX.
The problem was caused by the fact that after I switched to Xray mode and then I switched back to Wireframe mode it did not reset the X-ray mode (which is logical in some way, but in some other way it is not), also I think that the display of which modes area active is not so 'smooth'.
What I see it as a solution:
+1: I also would consider to forget using Pie menu for this. Personally I find using Pie menus as a 'trend', while it is not necessary at all and slows down visual operations.
Depending on the amount of choices I used to find Special menu-like ('W') solutions far more effective; something similar is what one of the 3rd party developers uses
This is an animated GIF!
Added subscriber: @lichtwerk
Also cannot get it to a state where pie is showing XRay OFF (even though it is ON).
(so for me 1. doesnt even have to be corrected, it is correct)
Is this still an issue with latest buildbot builds?
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Hello Bastien, do you need info/data from the devs on this? Thx.
In the screenshot X-Ray is not on, the edges on the backside of the cubes are obscured which means it is indeed off. There's just no bug here as far as I can tell, only suggestion for a different UI, which we don't track in bug reports.
Thanks, Brecht.
Now I understand, nut I think it is a very inefficient solution. While working when I hit 'Wireframe', I want to see a see-through wireframe, not hitting another button for 'X-Ray'. As it is a vital function, I suggest to make an additional pie where it happens together (also with hotkey) from UX aspect. I cannot find simple wireframe without xray useful at all for daily workflow; even in cases when it could be handy it is more rare than the case we need see-through wireframes (based on more than 20 years in archviz/game asset and as someone who works hard on putting Blender into focus with leaving AD products.
Thanks.
X-Ray is on in wireframe mode by default, and off in solid mode. The settings are decoupled, so if you never toggle X-Ray in wireframe mode it should do what you want?
I will check if I use the latest 2.8, but I answer it differently.
I would like a single hotkey/pie to work in the same way as in 2.79 when switching to wireframe mode as the 'basic' behaviour what results full see-through wireframe for the entire scene.
Now the X-Ray settings affect hidden line visibility AFAIK in wireframe mode, with making an 'illusion' the x-ray is off.
I could make a screenshot if you need (but from a new 2.8 if it was a bug).
Ok, so it works as it should, but it heavily affects the classic wireframe function (still can't see if will it cause a conflict or not).
Left image: Wire on, X-Ray on with value= 1 (which makes no sense to use X-Ray)
Right image: the same with X-Ray = 0
So both logic works, but See-Through Wireframe mode (as it called under other apps, shortened to 'Wireframe' should be the default with an X-Ray = 0 in my opinion.