Multires does not maintain corners when applying Crease after Linear and Simple Subdivision methods #81958

Closed
opened 2020-10-22 13:17:55 +02:00 by Alex · 9 comments

System Information
Intel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB
Windows 7 x64

Blender Version
Broken: 2.91 Beta, 2.92 Alpha
Worked: 2.79

Short description of error
Multires seems to have a very peculiar problem if you apply Crease to edges after subdivision has been done. This doesn't seem to happen if you apply creases before the subdivision. This seems to be happening while using Linear ans Simple subdivision methods.

Exact steps for others to reproduce the error

  1. Create a simple Plane
  2. Apply Multires and make a few subdivisions (Linear or Simple)
  3. Enter Edit Mode and apply Crease 1.0 on all four edges
  4. Exit Edit Mode and Plane's corners will stretch. It looks like the more subdivisions you apply the farther they will stretch.

If you apply Crease on edges before applying Multires it doesn't happen.
MultiresWrongCorners.jpg

**System Information** Intel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB Windows 7 x64 **Blender Version** Broken: 2.91 Beta, 2.92 Alpha Worked: 2.79 **Short description of error** Multires seems to have a very peculiar problem if you apply Crease to edges after subdivision has been done. This doesn't seem to happen if you apply creases before the subdivision. This seems to be happening while using Linear ans Simple subdivision methods. **Exact steps for others to reproduce the error** 1. Create a simple Plane 2. Apply Multires and make a few subdivisions (Linear or Simple) 3. Enter Edit Mode and apply Crease 1.0 on all four edges 4. Exit Edit Mode and Plane's corners will stretch. It looks like the more subdivisions you apply the farther they will stretch. If you apply Crease on edges *before* applying Multires it doesn't happen. ![MultiresWrongCorners.jpg](https://archive.blender.org/developer/F9034830/MultiresWrongCorners.jpg)
Author

Added subscriber: @SpectreFirst

Added subscriber: @SpectreFirst

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

I cannot reproduce this with either the latest stable or current development versions of Blender:

Please try the latest daily build: https://builder.blender.org/download/

Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

If the problem persists, please give us more clear instructions on how to reproduce it from scratch.

I cannot reproduce this with either the latest stable or current development versions of Blender: Please try the latest daily build: https://builder.blender.org/download/ Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue. If the problem persists, please give us more clear instructions on how to reproduce it from scratch.
Author

Sorry, I forgot to test all modes so I haven't noticed that this thing happens with Simple and Linear subdivision methods. It's 100% reproducible on 2.9.01 as well as current 2.91 Beta and 2.92 Alpha. I'm always using separate localized versions of Blender for testing so there is no need to reset them. Reproducible with default Cube as well, same exact method as described - add Multires to a Cube, subdivide, enter Edit Mode, select all, apply Crease 1.0, exit Edit Mode.
MultiresWrongCorners2901.jpg
MultiresWrongCorners291.jpg
MultiresWrongCorners292.jpg

Sorry, I forgot to test all modes so I haven't noticed that this thing happens with Simple and Linear subdivision methods. It's 100% reproducible on 2.9.01 as well as current 2.91 Beta and 2.92 Alpha. I'm always using separate localized versions of Blender for testing so there is no need to reset them. Reproducible with default Cube as well, same exact method as described - add Multires to a Cube, subdivide, enter Edit Mode, select all, apply Crease 1.0, exit Edit Mode. ![MultiresWrongCorners2901.jpg](https://archive.blender.org/developer/F9046485/MultiresWrongCorners2901.jpg) ![MultiresWrongCorners291.jpg](https://archive.blender.org/developer/F9046510/MultiresWrongCorners291.jpg) ![MultiresWrongCorners292.jpg](https://archive.blender.org/developer/F9046515/MultiresWrongCorners292.jpg)
Alex changed title from Multires does not maintain corners when applying Crease after Subdivision to Multires does not maintain corners when applying Crease after Linear and Simple Subdivision methods 2020-10-23 11:08:47 +02:00

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'
Member

Added subscriber: @PabloDobarro

Added subscriber: @PabloDobarro
Member

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Member

This is the expected behavior, and it is a consequence of how Multires works.
When you create a simple subdivision in the model without creases, Multires is going to create displacement data on top of top of the current limit surface of the cube. If you change the crease values of the base mesh, you are modifying the limit surface. As the limit surface changed but the displacement info is still the same, the results won't match.

This is the expected behavior, and it is a consequence of how Multires works. When you create a simple subdivision in the model without creases, Multires is going to create displacement data on top of top of the current limit surface of the cube. If you change the crease values of the base mesh, you are modifying the limit surface. As the limit surface changed but the displacement info is still the same, the results won't match.
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
3 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#81958
No description provided.