Multiresolution sculpting broken after change in base geometry #95557

Open
opened 2022-02-06 18:41:31 +01:00 by Diogo Valadares Reis dos Santos · 16 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.1.2 30.0.14023.3004

Blender Version
Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-05 23:52, hash: 59a8bdd48c

The file was created at 3.1.0, but the model in 3.0.1 also has the same problem.

Short description of error
after deleting edges from a loop and recreating them in a different arrangement, some parts of the model cannot be sculpted with multiresolution on.

Exact steps for others to reproduce the error

In a model with multiresolution, I deleted and recreated some edges of the topology and this broke the sculpt mode of the multiresolution:

  • In the sculpt mode, whenever I was getting close from the model, it simply dissappeared, reapearing after zooming out.
  • When hovering the mouse over some areas of the model, doesn't change the brush gizmo, and I can't sculpt on those areas neither.
  • If there is a area that you can interact/sculpting, by doing it the areas that you were unable to sculpt will become sculptable again.
  • In the areas that you can sculpt, the brush gizmo rotation doesn't match the surface sometimes.
  • baking normals from this multiresolution causes blender to crash

I splited the model in some parts trying to remove the defective part, but this only changed the areas the bug was occuring, and I also tried to re-sort the vertices of the model, which had the same effect

In this video, the upper part of the leg is sculptable, but the rest of the leg is not
2022-02-06 14-33-33.mp4

This model is from a commission so I had to fair the upper part of it
broken multires.blend

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.1.2 30.0.14023.3004 **Blender Version** Broken: version: 3.1.0 Beta, branch: master, commit date: 2022-02-05 23:52, hash: `59a8bdd48c` The file was created at 3.1.0, but the model in 3.0.1 also has the same problem. **Short description of error** after deleting edges from a loop and recreating them in a different arrangement, some parts of the model cannot be sculpted with multiresolution on. **Exact steps for others to reproduce the error** In a model with multiresolution, I deleted and recreated some edges of the topology and this broke the sculpt mode of the multiresolution: - In the sculpt mode, whenever I was getting close from the model, it simply dissappeared, reapearing after zooming out. - When hovering the mouse over some areas of the model, doesn't change the brush gizmo, and I can't sculpt on those areas neither. - If there is a area that you can interact/sculpting, by doing it the areas that you were unable to sculpt will become sculptable again. - In the areas that you can sculpt, the brush gizmo rotation doesn't match the surface sometimes. - baking normals from this multiresolution causes blender to crash I splited the model in some parts trying to remove the defective part, but this only changed the areas the bug was occuring, and I also tried to re-sort the vertices of the model, which had the same effect In this video, the upper part of the leg is sculptable, but the rest of the leg is not [2022-02-06 14-33-33.mp4](https://archive.blender.org/developer/F12850515/2022-02-06_14-33-33.mp4) This model is from a commission so I had to fair the upper part of it [broken multires.blend](https://archive.blender.org/developer/F12850508/broken_multires.blend)

Added subscriber: @Diogo_Valadares

Added subscriber: @Diogo_Valadares

#100972 was marked as duplicate of this issue

#100972 was marked as duplicate of this issue

Added subscriber: @DarkKnight

Added subscriber: @DarkKnight
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

I can replicate the issue. While I think generally Multiresolution will not work well if the base mesh was edited destructively or additively, in my tests, sculpting still worked on those cases. So there might be an issue somewhere.

I can replicate the issue. While I think generally Multiresolution will not work well if the base mesh was edited destructively or additively, in my tests, sculpting still worked on those cases. So there might be an issue somewhere.

I really think there is something off with multires in 3.1, I remade the whole multiresolution and took care to not change the topology of the model, and I still got a problem.
I just tried to bake the multiresolution in 3.1 and it crashed the same way the broken one did. I then tried to do the same in 3.0 and It baked, but the result was this:

image.png
this one was done with 0 subdivisions in viewport

image.png
and this one was with one subdivision in viewport

in all the time I used multiresolution I never have seen stuff like this, even in the ones I edited the base mesh adding and deleting polygons.

For now the workaround I found is applying the multiresolution, then adding a multiresolution and unsubdividing it. the base mesh will probably be slightly different, but close enough.

I really think there is something off with multires in 3.1, I remade the whole multiresolution and took care to not change the topology of the model, and I still got a problem. I just tried to bake the multiresolution in 3.1 and it crashed the same way the broken one did. I then tried to do the same in 3.0 and It baked, but the result was this: ![image.png](https://archive.blender.org/developer/F12859738/image.png) this one was done with 0 subdivisions in viewport ![image.png](https://archive.blender.org/developer/F12859744/image.png) and this one was with one subdivision in viewport in all the time I used multiresolution I never have seen stuff like this, even in the ones I edited the base mesh adding and deleting polygons. For now the workaround I found is applying the multiresolution, then adding a multiresolution and unsubdividing it. the base mesh will probably be slightly different, but close enough.
Member

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
Member

I just tried to bake the multiresolution in 3.1 and it crashed the same way the broken one did.

By crashed, you mean Blender suddenly closed? If that's the case, can you attach the crash log as described in https://docs.blender.org/manual/en/latest/troubleshooting/crash.htm?
And does the 3.2 daily build work? https://builder.blender.org/download/daily/

> I just tried to bake the multiresolution in 3.1 and it crashed the same way the broken one did. By crashed, you mean Blender suddenly closed? If that's the case, can you attach the crash log as described in https://docs.blender.org/manual/en/latest/troubleshooting/crash.htm? And does the 3.2 daily build work? https://builder.blender.org/download/daily/

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

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

I think there may be more than one bug interacting here and it may not be related to the original bug in the thread.

in 3.0 the baked texture is grey as described, BUT, after switching between object mode->edit->object->sculpt->object it started baking as usual, also in 3.0 some of the 3.1 models are not being shaded until the previous process is done or until the area is sculpted. I'd guess it's because of the normal changes that were done in 3.1

in 3.1 when I bake it closes blender but It doesn't give me a .crash file. Debug log gives me:

Windows fatal exception: access violation

Thread 0x000046bc (most recent call first):
  <no Python frame>

in 3.2 it magically bakes with no problem whatsoever

I'm not sure if I should open another bug report for this since this one may not be directly related to the multiresolution problem.

I think there may be more than one bug interacting here and it may not be related to the original bug in the thread. in 3.0 the baked texture is grey as described, BUT, after switching between object mode->edit->object->sculpt->object it started baking as usual, also in 3.0 some of the 3.1 models are not being shaded until the previous process is done or until the area is sculpted. I'd guess it's because of the normal changes that were done in 3.1 in 3.1 when I bake it closes blender but It doesn't give me a .crash file. Debug log gives me: ``` Windows fatal exception: access violation Thread 0x000046bc (most recent call first): <no Python frame> ``` in 3.2 it magically bakes with no problem whatsoever I'm not sure if I should open another bug report for this since this one may not be directly related to the multiresolution problem.
Member

@Diogo_Valadares If it is a different issue under different circumstances, then yes, you should create a new report for this issue.
It is good that it works in 3.2, if we can reproduce the issue reliably we can find the commit that fixes the issue and put it in version 3.1 before release.

@Diogo_Valadares If it is a different issue under different circumstances, then yes, you should create a new report for this issue. It is good that it works in 3.2, if we can reproduce the issue reliably we can find the commit that fixes the issue and put it in version 3.1 before release.
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

report for the crash is #95672 (Crash: baking normals from multires in 3.1 (fixed in 3.2))

report for the crash is #95672 (Crash: baking normals from multires in 3.1 (fixed in 3.2))
Member

Added subscribers: @spacepets4, @TheRedWaxPolice

Added subscribers: @spacepets4, @TheRedWaxPolice
Philipp Oeser removed the
Interest
Sculpt, Paint & Texture
label 2023-02-10 09:11:33 +01:00
Philipp Oeser added the
Interest
Modeling
label 2023-02-10 11:18:20 +01:00
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#95557
No description provided.