Blender 2.8 Modifier Subsurf not able to Optimize Display #60922

Closed
opened 2019-01-27 15:41:06 +01:00 by João Rosado · 11 comments

System Information
Operating system: Windows 10 Home
Graphics card: GTX 1060 6GB

Blender Version
Broken: 2.8 Beta
Worked: 2.79b and older

Short description of error
On 2.8 Beta when subsurfing an object If Optimal Display is checked nothing changes blender keeps drawing all edges.

Exact steps for others to reproduce the error
Just subsurf the default cube set the number of sub to 2 in the viewport and check Optimal Display then change to wireframe mode and u will see that nothing changes and Blender keeps drawing all the edges. Try the same with Blender 2.79b and u will see a diference between them.

**System Information** Operating system: Windows 10 Home Graphics card: GTX 1060 6GB **Blender Version** Broken: 2.8 Beta Worked: 2.79b and older **Short description of error** On 2.8 Beta when subsurfing an object If Optimal Display is checked nothing changes blender keeps drawing all edges. **Exact steps for others to reproduce the error** Just subsurf the default cube set the number of sub to 2 in the viewport and check Optimal Display then change to wireframe mode and u will see that nothing changes and Blender keeps drawing all the edges. Try the same with Blender 2.79b and u will see a diference between them.
Author

Added subscriber: @jprosado

Added subscriber: @jprosado

Added subscriber: @deadpin

Added subscriber: @deadpin

Right now, after you turn on optimal display, you need to change the following setting to some lower value than 1 (try 0.86): Overlays -> Wireframe

Anything higher than .86 you will start to see the secondary edges that sub-d adds start to appear. Anything below 0.86 the wireframe of the primary edges starts to break up.

I personally don't like this design either, since it's not obvious these 2 options are tied together and most uses of optimal display don't require seeing the secondary edges.

Right now, after you turn on optimal display, you need to change the following setting to some lower value than 1 (try 0.86): Overlays -> Wireframe Anything higher than .86 you will start to see the secondary edges that sub-d adds start to appear. Anything below 0.86 the wireframe of the primary edges starts to break up. I personally don't like this design either, since it's not obvious these 2 options are tied together and most uses of optimal display don't require seeing the secondary edges.
Member

Added subscribers: @Sergey, @JacquesLucke

Added subscribers: @Sergey, @JacquesLucke
Member

@Sergey, should we just get rid of the Optimal Display setting? It does not feel like it belongs there anyway imo..

@Sergey, should we just get rid of the Optimal Display setting? It does not feel like it belongs there anyway imo..

Added subscriber: @fclem

Added subscriber: @fclem

I think it's rather important and useful feature to have, otherwise viewport will become a mess real quick.

This is something for @fclem to look into. The overlay should respect edges which are set for display, and not force-display other edges.

I think it's rather important and useful feature to have, otherwise viewport will become a mess real quick. This is something for @fclem to look into. The overlay should respect edges which are set for display, and not force-display other edges.
Clément Foucault was assigned by Sebastian Parborg 2019-01-28 18:44:13 +01:00

Well, the intent was to have the possibility to partially draw the sub-D edges (with varying alpha). It only shown all sub-D edges with full intensity if wireframe value is 1.0. Anything lower is already lowering the sub-D edges alpha. Maybe we should just force the shaded sub-D edges at wireframe == 1.0?

Well, the intent was to have the possibility to partially draw the sub-D edges (with varying alpha). It only shown all sub-D edges with full intensity if wireframe value is 1.0. Anything lower is already lowering the sub-D edges alpha. Maybe we should just force the shaded sub-D edges at wireframe == 1.0?
Author

Well, I would rather have it as it was on 2.79 and later cause this setting is important and useful not only improves performance as improves visibility in the viewport. The point is we should keep it simple and fast to use, I personally would rather have only one option instead of 2 options in different places.

Well, I would rather have it as it was on 2.79 and later cause this setting is important and useful not only improves performance as improves visibility in the viewport. The point is we should keep it simple and fast to use, I personally would rather have only one option instead of 2 options in different places.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

This was fix some time ago.

This was fix some time ago.
Sign in to join this conversation.
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
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#60922
No description provided.