Subdivide algorithm differs from the industry standard #76457

Closed
opened 2020-05-05 23:04:15 +02:00 by Sergey · 20 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92

Blender Version
Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-01 21:55, hash: 83304e4c22
Worked: (newest version of Blender that worked as expected)

Short description of error
subd.gif
Blender subdivide algorithm shrinks (smoothes) the model more than the same Catmull-Clark algorithm in other software. This creates problems when importing/exporting models. In version 2.79, the algorithm worked the same way as in other software.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 **Blender Version** Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-05-01 21:55, hash: `83304e4c22` Worked: (newest version of Blender that worked as expected) **Short description of error** ![subd.gif](https://archive.blender.org/developer/F8514580/subd.gif) Blender subdivide algorithm shrinks (smoothes) the model more than the same Catmull-Clark algorithm in other software. This creates problems when importing/exporting models. In version 2.79, the algorithm worked the same way as in other software. **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]
Author

Added subscriber: @borschberry

Added subscriber: @borschberry
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

#75632 (Subsurf modifier and multirres modifier give different results when subdivide)
#76302 (Multires Rebuild Subdivision shrinks shape)

#75632 (Subsurf modifier and multirres modifier give different results when subdivide) #76302 (Multires Rebuild Subdivision shrinks shape)

Added subscriber: @APEC

Added subscriber: @APEC

to clarify, it since 2.8 version

to clarify, it since 2.8 version

Added subscriber: @nudelZ

Added subscriber: @nudelZ

this is not a bug - see https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Modeling#Subdivision_Surfaces_and_Multires

to "fix" that there should be an option to disable the "limit surface" feature

this is not a bug - see https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Modeling#Subdivision_Surfaces_and_Multires to "fix" that there should be an option to disable the "limit surface" feature

In #76457#925320, @nudelZ wrote:
this is not a bug - see https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Modeling#Subdivision_Surfaces_and_Multires

to "fix" that there should be an option to disable the "limit surface" feature

so blender is especial program with its especial Catmull-Clark algorithm?
Why need to invent bicycles if there is a industry standard algorithm that used in all other 3d apps?

> In #76457#925320, @nudelZ wrote: > this is not a bug - see https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Modeling#Subdivision_Surfaces_and_Multires > > to "fix" that there should be an option to disable the "limit surface" feature so blender is especial program with its especial Catmull-Clark algorithm? Why need to invent bicycles if there is a industry standard algorithm that used in all other 3d apps?

Added subscriber: @moisessalvador

Added subscriber: @moisessalvador

Maybe I'm wrong but I think it's based on OpenSubdiv, which in itself is another standard, so pick your poison. But I agree, I think it should come back as an option, particularly if it gives old performance back

Maybe I'm wrong but I think it's based on OpenSubdiv, which in itself is another standard, so pick your poison. But I agree, I think it should come back as an option, particularly if it gives old performance back

OpenSubdiv it's improved Catmull-Clark in performance (if I understand correctly), so visually you don't see difference.
But we see difference in 2.8 blender.
Need clarification on this.

OpenSubdiv it's improved Catmull-Clark in performance (if I understand correctly), so visually you don't see difference. But we see difference in 2.8 blender. Need clarification on this.
Author

In #76457#925320, @nudelZ wrote:
this is not a bug - see https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Modeling#Subdivision_Surfaces_and_Multires

to "fix" that there should be an option to disable the "limit surface" feature

It would be nice to see such an option. I think this could be fix for this problem as well

> In #76457#925320, @nudelZ wrote: > this is not a bug - see https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Modeling#Subdivision_Surfaces_and_Multires > > to "fix" that there should be an option to disable the "limit surface" feature It would be nice to see such an option. I think this could be fix for [this ](https://developer.blender.org/T76302) problem as well

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Brecht Van Lommel self-assigned this 2020-05-07 00:01:51 +02:00

This is not a topic for the bug tracker in any case, a better place to discuss this is devtalk:
https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

This is not a topic for the bug tracker in any case, a better place to discuss this is devtalk: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
Author

@brecht I understand that the current algorithm works as planned by the developers. But is it possible that using an inappropriate algorithm that gives an unexpected result is a bug in itself?

@brecht I understand that the current algorithm works as planned by the developers. But is it possible that using an inappropriate algorithm that gives an unexpected result is a bug in itself?

It might be a bug according to your definition, but by the definition we employ to decide what is handled in the bug tracker this is not a bug.

It might be a bug according to your definition, but by the definition we employ to decide what is handled in the bug tracker this is not a bug.

Added subscriber: @jeacom

Added subscriber: @jeacom

It seems to be trying to approximate the final position of the vertices when infinitely subdivided. Isn't it slower than just subdividing?

It seems to be trying to approximate the final position of the vertices when infinitely subdivided. Isn't it slower than just subdividing?

Added subscriber: @ckohl_art

Added subscriber: @ckohl_art
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
8 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#76457
No description provided.