Multires spikes #37997

Closed
opened 2013-12-30 19:40:42 +01:00 by Kevin Hays · 24 comments

System Information
OS: Windows 7 Professional SP1
Graphics card: nvidia geforce 560ti

Blender Version
Broken: 2.69.1 r61064

Short description of error
Multires occasionally messes up the geometry which leads to un-fixable spikes. When you try to smooth out the problem area on one multires level, it makes it even worse on other multires levels.

Exact steps for others to reproduce the error

I'm not sure how to get a sculpt into a state where this happens. In bugReport.blend, you'll see the spikes at multires level 3 near the knees. If you try to smooth them out, you'll get different spikes on multires level 4. Trying to smooth out the problem area on level 2 makes the level 3 spikes worse.

I attempted to reproduce the bug on a simpler model in bugReport2.blend and it took a long time to get it into this state where this bug happens. I used the crease, grab, smooth, and clay strips brush a lot, scaled down the object and applied the scale (not sure if that matters), and did some more sculpting. When you smooth out the problem area on multires level 1, you get issues on higher levels.

Here's a .zip of the files mentioned above: https://dl.dropboxusercontent.com/u/17578055/multires.zip

**System Information** OS: Windows 7 Professional SP1 Graphics card: nvidia geforce 560ti **Blender Version** Broken: 2.69.1 r61064 **Short description of error** Multires occasionally messes up the geometry which leads to un-fixable spikes. When you try to smooth out the problem area on one multires level, it makes it even worse on other multires levels. **Exact steps for others to reproduce the error** I'm not sure how to get a sculpt into a state where this happens. In bugReport.blend, you'll see the spikes at multires level 3 near the knees. If you try to smooth them out, you'll get different spikes on multires level 4. Trying to smooth out the problem area on level 2 makes the level 3 spikes worse. I attempted to reproduce the bug on a simpler model in bugReport2.blend and it took a long time to get it into this state where this bug happens. I used the crease, grab, smooth, and clay strips brush a lot, scaled down the object and applied the scale (not sure if that matters), and did some more sculpting. When you smooth out the problem area on multires level 1, you get issues on higher levels. Here's a .zip of the files mentioned above: https://dl.dropboxusercontent.com/u/17578055/multires.zip
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @KevinHays

Added subscriber: @KevinHays

#48864 was marked as duplicate of this issue

#48864 was marked as duplicate of this issue

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2013-12-31 01:28:15 +01:00

This is an issue on the todo list:
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Multires_Modifier

It's due to the multires representation used, some mesh shapes give this problem, but fixing it requires a pretty big change in how we store and calculate multiresolution levels that is not so much a bugfix but likely more of a partial rewrite of the system.

This is an issue on the todo list: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Multires_Modifier It's due to the multires representation used, some mesh shapes give this problem, but fixing it requires a pretty big change in how we store and calculate multiresolution levels that is not so much a bugfix but likely more of a partial rewrite of the system.

Added subscriber: @NGMAT

Added subscriber: @NGMAT

Do any of the current core devs have the expertise to make the fix/rewrite eventually (even if a year from now), or is it something that will require another dev altogether? thanks. I'm concerned about how opensubdiv will effect everything.

Do any of the current core devs have the expertise to make the fix/rewrite eventually (even if a year from now), or is it something that will require another dev altogether? thanks. I'm concerned about how opensubdiv will effect everything.

It's mostly a matter of having time, not expertise, everyone who could do this is pretty busy with other things.

It's mostly a matter of having time, not expertise, everyone who could do this is pretty busy with other things.

Added subscriber: @brecht

Added subscriber: @brecht

@brecht I gather from your response, the issue has been identified, but just no one is available to fix it? if so, thats at least some good news. I had thought it was just unsolvable by the team, thus my "expertise" comment, thanks for your time.

@brecht I gather from your response, the issue has been identified, but just no one is available to fix it? if so, thats at least some good news. I had thought it was just unsolvable by the team, thus my "expertise" comment, thanks for your time.

Added subscriber: @JonathanWilliamson

Added subscriber: @JonathanWilliamson

Added subscriber: @Psy-Fi

Added subscriber: @Psy-Fi

Added subscriber: @MatthewHeimlich

Added subscriber: @MatthewHeimlich

Added subscriber: @ismix

Added subscriber: @ismix

Added subscriber: @KenJinks

Added subscriber: @KenJinks

Would a quick fix be to add Edit mode to the levels? So that I could just edit out the spike manually?

Would a quick fix be to add Edit mode to the levels? So that I could just edit out the spike manually?

Added subscribers: @AlbertoVelazquez, @ErickNyanduKabongo

Added subscribers: @AlbertoVelazquez, @ErickNyanduKabongo

Added subscriber: @TonatiuhdeSanJulian

Added subscriber: @TonatiuhdeSanJulian

We are at the gates of 2.80... so sad that this is not fix yet... I hope to be able to use multirres in the near future for sculpting, not just for copy details...

We are at the gates of 2.80... so sad that this is not fix yet... I hope to be able to use multirres in the near future for sculpting, not just for copy details...

Added subscriber: @0o00o0oo

Added subscriber: @0o00o0oo

Added subscriber: @fatboyzzfatboyzz

Added subscriber: @fatboyzzfatboyzz

Added subscriber: @kfoong

Added subscriber: @kfoong

Added subscriber: @Rgladt

Added subscriber: @Rgladt

Just checking in. Now at 3.1 and this still is an issue. Is any fix for this on the horizon?

Just checking in. Now at 3.1 and this still is an issue. Is any fix for this on the horizon?
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
15 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#37997
No description provided.