It seems, Blender recalculates all modifiers in the scene, when I change property for new primitive in operation adjustment popup #75983

New Issue

Vyacheslav Kobozev · 2020-04-21T23:28:47+02:00

2020-04-21 23:28:47 +02:00

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59

Blender Version
Broken: version: 2.83 (sub 13), branch: master, commit date: 2020-04-16 15:38, hash: 8cb10c124e
Same issue in 2.79b and 2.82a
Was that reported before? Looks like «bug of decades»

Short description of error
Condition: many objects with modifiers in the scene. Even instanced.
When I add cylinder and trying to change vertices quantity fast, I have extremely slow reaction.
In the new scene it fast.
If scene have hight polycount (Millions) speed will be slow too. So Blender recreate all scene. Do you think this bug should have high priority?
2020-04-22_00-01-48.mp4

Exact steps for others to reproduce the error

Add new cylinder into this scene.
option changes slow.blend
Drag option (vertices) fast back and forth.
Then link modifiers from one icosphere to all duplicates.
Do (1) again and compare speed/fps

You can put all duplicates with modifiers in collection, instance it and unlink.
Speed will be slow too.

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59 **Blender Version** Broken: version: 2.83 (sub 13), branch: master, commit date: 2020-04-16 15:38, hash: `8cb10c124e` Same issue in 2.79b and 2.82a Was that reported before? Looks like «bug of decades» **Short description of error** Condition: many objects with modifiers in the scene. Even instanced. When I add cylinder and trying to change vertices quantity fast, I have extremely slow reaction. In the new scene it fast. If scene have hight polycount (Millions) speed will be slow too. So Blender recreate all scene. Do you think this bug should have high priority? [2020-04-22_00-01-48.mp4](https://archive.blender.org/developer/F8488071/2020-04-22_00-01-48.mp4) **Exact steps for others to reproduce the error** 1. Add new cylinder into this scene. [option changes slow.blend](https://archive.blender.org/developer/F8488097/option_changes_slow.blend) 2. Drag option (vertices) fast back and forth. 3. Then link modifiers from one icosphere to all duplicates. 4. Do (1) again and compare speed/fps You can put all duplicates with modifiers in collection, instance it and unlink. Speed will be slow too.

Vyacheslav Kobozev commented

2020-04-21 23:28:47 +02:00

Added subscriber: @Vyach

Vyacheslav Kobozev commented

2020-04-21 23:31:44 +02:00

May be the same roots with this problem: https://developer.blender.org/T73199

Brecht Van Lommel commented

2020-04-22 10:46:52 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2020-04-22 10:46:52 +02:00

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

Brecht Van Lommel closed this issue

2020-04-22 10:46:52 +02:00

Brecht Van Lommel self-assigned this 2020-04-22 10:46:52 +02:00

Brecht Van Lommel commented

2020-04-22 10:46:52 +02:00

This is one of the issues remaining to be addressed in #60695 (Optimized per-datablock global undo).

Specifically:

Fix slow undo of adding/duplicating/deleting datalocks. The undo diffing does not appear to be smart to match up the right datablocks in such cases, causing many unrelated datablocks to be marked as changed, which also means excessive memory usage. The session_uuid could be used to find matching datablocks.

This is one of the issues remaining to be addressed in #60695 (Optimized per-datablock global undo). Specifically: > Fix slow undo of adding/duplicating/deleting datalocks. The undo diffing does not appear to be smart to match up the right datablocks in such cases, causing many unrelated datablocks to be marked as changed, which also means excessive memory usage. The session_uuid could be used to find matching datablocks.

Vyacheslav Kobozev commented

2020-04-22 11:49:36 +02:00

@brecht okay, good to know, that you know and working on it!
I did not assume, it is about undo.

Just adding and duplicating/deleting primitives is fast for me. Only property editing after adding is slow.

@brecht okay, good to know, that you know and working on it! I did not assume, it is about undo. Just adding and duplicating/deleting primitives is fast for me. Only property editing after adding is slow.

Vyacheslav Kobozev commented

2021-04-25 16:34:02 +02:00

New test, it is strange that new cylinder editing is slow only right after colpying modifiers to all. And then it works well again.
@brecht can you check it? may be it requires only tiny effort to make it work properly in any case?
2021-04-25_17-29-46.mp4

New test, it is strange that new cylinder editing is slow only right after colpying modifiers to all. And then it works well again. @brecht can you check it? may be it requires only tiny effort to make it work properly in any case? [2021-04-25_17-29-46.mp4](https://archive.blender.org/developer/F10037492/2021-04-25_17-29-46.mp4)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

It seems, Blender recalculates all modifiers in the scene, when I change property for new primitive in operation adjustment popup #75983