Multiresolution sculpt: changing viewport level inside sculpt mode hanging (recalculating modifier?) #87843

Closed
opened 2021-04-26 18:38:15 +02:00 by Vyacheslav Kobozev · 7 comments

System Information
Operating system: Windows-8.1-6.3.9600-SP0 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab

As title says. I expect, that viewport level change will not influence to sculpt mode at all and will not calculate level untill I'll go to object mode.

2021-04-26_19-33-59.mp4

**System Information** Operating system: Windows-8.1-6.3.9600-SP0 64 Bits Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40 **Blender Version** Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `02948a2cab` As title says. I expect, that viewport level change will not influence to sculpt mode at all and will not calculate level untill I'll go to object mode. [2021-04-26_19-33-59.mp4](https://archive.blender.org/developer/F10039545/2021-04-26_19-33-59.mp4)

Added subscriber: @Vyach

Added subscriber: @Vyach
Member

Added subscriber: @filedescriptor

Added subscriber: @filedescriptor
Member

Hm, unfortunately, I think there is no good way around that. First, it's hard to know when to update and when not to. There is no good api to check for open viewports in the right mode etc. But more importantly, when should the update occur? Because it has to be updated at some point later. AFAIK there is no concept of a "delayed update" in the dependency graph. I presume that is what you would have to do.
But even then, it's probably better to do the update right away. If Blender suddenly freezes for no apparent reason 10 min after changing the setting because you went back to another mode, seems like not very good design.
IMO a better solution is to display progress on expensive tasks as well as an option to cancel them. So, in this case, you would change the setting, the UI stays responsive and you see the progress in the bottom bar with an X to cancel the operation. But that would be a bigger project for another time.

Hm, unfortunately, I think there is no good way around that. First, it's hard to know when to update and when not to. There is no good api to check for open viewports in the right mode etc. But more importantly, when should the update occur? Because it has to be updated at some point later. AFAIK there is no concept of a "delayed update" in the dependency graph. I presume that is what you would have to do. But even then, it's probably better to do the update right away. If Blender suddenly freezes for no apparent reason 10 min after changing the setting because you went back to another mode, seems like not very good design. IMO a better solution is to display progress on expensive tasks as well as an option to cancel them. So, in this case, you would change the setting, the UI stays responsive and you see the progress in the bottom bar with an `X` to cancel the operation. But that would be a bigger project for another time.

to check for open viewports in the right mode

all viewports opened in the same mode atm. There is no local modes, AFAIK

when should the update occur?

When I go back to object mode, if option was changed (if viewport level != viwport level previous)
there is only one object can be in sculpt mode, so there can be only one flag.

Okay, it will be nice, if I go object mode and get update immediately. But no. When I switch, blender updates again, and I shoul wait again…
So it is already freezes. So we have even worse design.

to display progress on expensive tasks as well as an option to cancel them.

Agree. There is topic at RCS: Panic button

> to check for open viewports in the right mode all viewports opened in the same mode atm. There is no local modes, AFAIK > when should the update occur? When I go back to object mode, if option was changed (if viewport level != viwport level previous) there is only one object can be in sculpt mode, so there can be only one flag. Okay, it will be nice, if I go object mode and get update immediately. But no. When I switch, blender updates again, and I shoul wait again… So it is already freezes. So we have even worse design. > to display progress on expensive tasks as well as an option to cancel them. Agree. There is topic at RCS: [Panic button ](https://blender.community/c/rightclickselect/4nhbbc/)
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

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

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

This looks more of a potential optimization than a bug. And with regards to the work being done after going to object mode, it doesn't look similar to the work being done when changing the levels. So Blender is probably not duplicating work and I wouldn't consider this a bug. Both cases are shown below.

20220224-114905.png

20220224-115258.png

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

This looks more of a potential optimization than a bug. And with regards to the work being done after going to object mode, it doesn't look similar to the work being done when changing the levels. So Blender is probably not duplicating work and I wouldn't consider this a bug. Both cases are shown below. ![20220224-114905.png](https://archive.blender.org/developer/F12885330/20220224-114905.png) ![20220224-115258.png](https://archive.blender.org/developer/F12885329/20220224-115258.png) For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
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#87843
No description provided.