Slowdown of Adjust Last Operation panel after changing remesh modifier settings #89428

Closed
opened 2021-06-25 11:43:39 +02:00 by Garek · 11 comments

System Information
Operating system: Windows-7
Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab
Worked: (newest version of Blender that worked as expected)

Short description of error
Changing Octree Depth or voxel size of remesh modifier results in drop of performance of any action in Adjust Last Operation panel, most noticable at Octree Depth 5 or more.

Exact steps for others to reproduce the error

  1. Open .blend file
  2. Change Octree Depth or voxel size. You may lower it, increase or even decrease and increase to where it was.
  3. Do action that will show you Adjust Last Operation panel such as: move cube with G, rotate with R or add another object such as UV sphere.
  4. Tweak operation via Adjust Last Operation panel to measure performance.
  5. Do another action and tweak it - performance is much better.
    I can't confirm it on 2.93 or higher since they dropped Windows 7 support.
    remesher octree depth.avi
    Octree Depth test file.blend
**System Information** Operating system: Windows-7 **Blender Version** Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `02948a2cab` Worked: (newest version of Blender that worked as expected) **Short description of error** Changing Octree Depth or voxel size of remesh modifier results in drop of performance of any action in Adjust Last Operation panel, most noticable at Octree Depth 5 or more. **Exact steps for others to reproduce the error** 1. Open .blend file 2. Change Octree Depth or voxel size. You may lower it, increase or even decrease and increase to where it was. 3. Do action that will show you Adjust Last Operation panel such as: move cube with G, rotate with R or add another object such as UV sphere. 4. Tweak operation via Adjust Last Operation panel to measure performance. 5. Do another action and tweak it - performance is much better. I can't confirm it on 2.93 or higher since they dropped Windows 7 support. [remesher octree depth.avi](https://archive.blender.org/developer/F10201850/remesher_octree_depth.avi) [Octree Depth test file.blend](https://archive.blender.org/developer/F10201965/Octree_Depth_test_file.blend)
Author

Added subscriber: @Garek

Added subscriber: @Garek
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

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

I think this is essentially the same issue as #78171 (Adjust Last Operation: Other changes outside that panel are reverted back automatically)

Having the Adjust Last Operation panel open, then tweaking some other settings (e.g. in the Properties Editor) will revert the stuff done in between (causing the slowdown).
Can you confirm this is only an issue when you tweak remesh settings with Adjust Last Operation panel still open?

I think this is essentially the same issue as #78171 (Adjust Last Operation: Other changes outside that panel are reverted back automatically) Having the Adjust Last Operation panel open, then tweaking some other settings (e.g. in the Properties Editor) will revert the stuff done in between (causing the slowdown). Can you confirm this is only an issue when you tweak remesh settings with `Adjust Last Operation` panel still open?
Author

In #89428#1182575, @lichtwerk wrote:
Having the Adjust Last Operation panel open, then tweaking some other settings (e.g. in the Properties Editor) will revert the stuff done in between (causing the slowdown).

I don't see how it would cause slowdown when you change setting to lower level or to lower level and back to original. Besides in this case there are cases with no revert (see below)

In #89428#1182575, @lichtwerk wrote:
Can you confirm this is only an issue when you tweak remesh settings with Adjust Last Operation panel still open?

If you saying about "if panel open prior to changing settings or not" then answer is: even prior to triggering panel if you don't click prior to operation.
See video below. In first case I should click on cube prior to moving cube, no change in performance. But if I use hotkey to add sphere (or if I selected cube prior to moving it) there is performance drop. In both cases there are no Adjust Last Operation panel active.
Click or not to click that is the question.avi
At first I thought you ask about whether it's only with remesh modifier so I checked that first. I tested with subdivided default cude with array modifier and it's same behavior.
But changing object properties (location, scale) and then adjusting via panel does not trigger any noticable slowdown. Perhaps this operation is too light but I don't know then which is excluding modifiers.

Also to clarify: it's not just that this panel open, you can change operation. So if you move cube (trigger appearance of panel), change modifier settings and try to adjust via panel, your settings will revert (bug you mentioned) and you'll get slowdown. But you can move cube, change modifier, then add sphere (or move again, I guess it counts as new operation) and then adjust, you'll get only slowdown without any revert.

I would assume this is very similar bug that sits in the same broken system but still should be listed separate. I think it's better some more knowledgeable dev can make correct judgement. But prior to that confirm whether latest version have that since I unfortunately can't do that.

> In #89428#1182575, @lichtwerk wrote: > Having the Adjust Last Operation panel open, then tweaking some other settings (e.g. in the Properties Editor) will revert the stuff done in between (causing the slowdown). I don't see how it would cause slowdown when you change setting to lower level or to lower level and back to original. Besides in this case there are cases with no revert (see below) > In #89428#1182575, @lichtwerk wrote: > Can you confirm this is only an issue when you tweak remesh settings with `Adjust Last Operation` panel still open? If you saying about "if panel open prior to changing settings or not" then answer is: even prior to triggering panel if you don't click prior to operation. See video below. In first case I should click on cube prior to moving cube, no change in performance. But if I use hotkey to add sphere (or if I selected cube prior to moving it) there is performance drop. In both cases there are no `Adjust Last Operation` panel active. [Click or not to click that is the question.avi](https://archive.blender.org/developer/F10202035/Click_or_not_to_click_that_is_the_question.avi) At first I thought you ask about whether it's only with remesh modifier so I checked that first. I tested with subdivided default cude with array modifier and it's same behavior. But changing object properties (location, scale) and then adjusting via panel does not trigger any noticable slowdown. Perhaps this operation is too light but I don't know then which is excluding modifiers. Also to clarify: it's not just that this panel open, you can change operation. So if you move cube (trigger appearance of panel), change modifier settings and try to adjust via panel, your settings will revert (bug you mentioned) and you'll get slowdown. But you can move cube, change modifier, then add sphere (or move again, I guess it counts as new operation) and then adjust, you'll get only slowdown *without any revert*. I would assume this is very similar bug that sits in the same broken system but still should be listed separate. I think it's better some more knowledgeable dev can make correct judgement. But prior to that confirm whether latest version have that since I unfortunately can't do that.
Member

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

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

In #89428#1182627, @Garek wrote:
I don't see how it would cause slowdown when you change setting to lower level or to lower level and back to original.

If the undo/revert takes places, this is re-evaluating the modifier (twice even I think), thus the slowdown.

But if I use hotkey to add sphere there is performance drop.

Can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this

(or if I selected cube prior to moving it) there is performance drop.

I am having trouble reproducing that, maybe you can even get better repro steps?

you can move cube, change modifier, then add sphere and then adjust, you'll get only slowdown without any revert.

Same as above, can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this

you can move cube, change modifier, then move again (I guess it counts as new operation) and then adjust, you'll get only slowdown without any revert.

Yes, can repro that as well now

I think it's better some more knowledgeable dev can make correct judgement. But prior to that confirm whether latest version have that since I unfortunately can't do that.

Sound offensive, why? I am just trying to prepare the report as good as possible for a dev to look at, Anyhow, can only speak for the stuff I can actually reproduce, but yes, this happens in 2.93 and master as well...

> In #89428#1182627, @Garek wrote: > I don't see how it would cause slowdown when you change setting to lower level or to lower level and back to original. If the undo/revert takes places, this is re-evaluating the modifier (twice even I think), thus the slowdown. > But if I use hotkey to add sphere there is performance drop. Can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this > (or if I selected cube prior to moving it) there is performance drop. I am having trouble reproducing that, maybe you can even get better repro steps? > you can move cube, change modifier, then add sphere and then adjust, you'll get only slowdown without any revert. Same as above, can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this > you can move cube, change modifier, then move again (I guess it counts as new operation) and then adjust, you'll get only slowdown without any revert. Yes, can repro that as well now >I think it's better some more knowledgeable dev can make correct judgement. But prior to that confirm whether latest version have that since I unfortunately can't do that. Sound offensive, why? I am just trying to prepare the report as good as possible for a dev to look at, Anyhow, can only speak for the stuff I can actually reproduce, but yes, this happens in 2.93 and master as well...
Author

In #89428#1182666, @lichtwerk wrote:
Can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this
Same as above, can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this

I don't think it's quite the same. I mean, you're probably right to say it's about re-evaluating the modifier (I am by no means programmer so I can't say things for sure), it's just I think it might need different bugfix since in one case slowdown is persisted and in the other not. Just like pipe can break in two places - fundamentaly problem is same in that water is leaking and flooding neighbors below but in one case pipe was corruded by rust and in the other joints weren't set up right.

I am having trouble reproducing that, maybe you can even get better repro steps?

  1. Select cube with remesh modifier on it (preferably with Octree Depth on 5-6)
  2. Don't move it with G (or else you'll trigger Adjust Last Operation panel appearing)
  3. Change Octree Depth
  4. Move cube with G
  5. Use Adjust Last Operation panel to see performance drop

Sound offensive, why? I am just trying to prepare the report as good as possible for a dev to look at

Sorry if it appeared that way, didn't mean to in any way. Undo stuff is tricky AFAIK from Bastien commit messages (when he did Scene Editing in Object Mode project) and I think conditions for this potential bug to appear is unique enough to not merge it with other report before some dev can take a closer look at it.

> In #89428#1182666, @lichtwerk wrote: > Can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this > Same as above, can repro that, confirmed #85756 (Adjust Last Operation panel is slow (some Undo/Redo happening?)) for this I don't think it's quite the same. I mean, you're probably right to say it's about re-evaluating the modifier (I am by no means programmer so I can't say things for sure), it's just I think it might need different bugfix since in one case slowdown is persisted and in the other not. Just like pipe can break in two places - fundamentaly problem is same in that water is leaking and flooding neighbors below but in one case pipe was corruded by rust and in the other joints weren't set up right. > I am having trouble reproducing that, maybe you can even get better repro steps? 1. Select cube with remesh modifier on it (preferably with Octree Depth on 5-6) 2. **Don't** move it with G (or else you'll trigger `Adjust Last Operation` panel appearing) 3. Change Octree Depth 4. Move cube with G 5. Use `Adjust Last Operation` panel to see performance drop > Sound offensive, why? I am just trying to prepare the report as good as possible for a dev to look at Sorry if it appeared that way, didn't mean to in any way. Undo stuff is tricky AFAIK from Bastien commit messages (when he did `Scene Editing in Object Mode` project) and I think conditions for this potential bug to appear is unique enough to not merge it with other report before some dev can take a closer look at it.

Added subscriber: @mont29

Added subscriber: @mont29

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

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

Thanks for the report, but this is more like a general known limitation/improvement potential for undo system and depsgraph (re)evaluation. Definitely not a bug.

Thanks for the report, but this is more like a general known limitation/improvement potential for undo system and depsgraph (re)evaluation. Definitely 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#89428
No description provided.