Displace modifier with Image Texture causes scene slowdown #83271

New Issue

Juri Unt · 2020-12-01T08:54:42+01:00

Juri Unt commented

2020-12-01 08:54:42 +01:00

System Information
Operating system: Linux-5.4.0-54-generic-x86_64-with-debian-buster-sid 64 Bits

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-11-25 08:34, hash: 0f45cab862
Worked: 2.83

Caused by 23919d2275

Short description of error
Mesh object with a Displacement modifier using IMAGE TEXTURE can grind scene to a halt by forcing modifier stack to reevaluate on smallest changes to scene (such as adding objects, removing etc).

Interestingly with built in textures (Cloud, Voronoi) it's very fast and functions as should.

Exact steps for others to reproduce the error

Add subD modifier. Relatively high level (with respect to detail)
Any image texture (e.g rocks, wood, cloth)
As bonus can add Decimate modifier to confirm slowdown and force reevaluation of scene.
Try add new objects, erase etc, everything will freeze until that particular objects modifier stack is reevaluated.

displace_image_slowdown.blend

Thank You!

**System Information** Operating system: Linux-5.4.0-54-generic-x86_64-with-debian-buster-sid 64 Bits **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-11-25 08:34, hash: `0f45cab862` Worked: 2.83 Caused by 23919d2275 **Short description of error** Mesh object with a Displacement modifier using IMAGE TEXTURE can grind scene to a halt by forcing modifier stack to reevaluate on smallest changes to scene (such as adding objects, removing etc). Interestingly with built in textures (Cloud, Voronoi) it's very fast and functions as should. **Exact steps for others to reproduce the error** - Add subD modifier. Relatively high level (with respect to detail) - Any image texture (e.g rocks, wood, cloth) - As bonus can add Decimate modifier to confirm slowdown and force reevaluation of scene. - Try add new objects, erase etc, everything will freeze until that particular objects modifier stack is reevaluated. ![displace_slowdown.gif](https://archive.blender.org/developer/F9418563/displace_slowdown.gif) [displace_image_slowdown.blend](https://archive.blender.org/developer/F9433188/displace_image_slowdown.blend) Thank You!

Juri Unt commented

2020-12-01 08:54:42 +01:00

Added subscriber: @JuriUnt

blender-admin commented

2020-12-01 08:54:42 +01:00

#92386 was marked as duplicate of this issue

blender-admin commented

2020-12-01 08:54:42 +01:00

#85343 was marked as duplicate of this issue

Germano Cavalcante commented

2020-12-03 14:17:52 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-12-03 14:17:52 +01:00

In fact it is possible that there is a bad dependency there.
Could you submit a simple .blend file demonstrating the problem?

In fact it is possible that there is a bad dependency there. Could you submit a simple .blend file demonstrating the problem?

Juri Unt commented

2020-12-03 14:39:13 +01:00

Thanks for looking into it. Blender file attached.

It's very simple scene with 1 plane (3 modifiers), 1 texture. Unlikely user dependency error. Works very well in 2.83 LTS, no such bug there.
With bigger scenes where you have many such objects, it becomes very challenging.

Thanks again

Thanks for looking into it. Blender file attached. It's very simple scene with 1 plane (3 modifiers), 1 texture. Unlikely user dependency error. Works very well in 2.83 LTS, no such bug there. With bigger scenes where you have many such objects, it becomes very challenging. Thanks again

Germano Cavalcante commented

2020-12-03 15:33:52 +01:00

Added subscriber: @Sergey

Germano Cavalcante commented

2020-12-03 15:33:52 +01:00

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

Germano Cavalcante commented

2020-12-03 15:33:52 +01:00

I can confirm.
In fact, the displace modifier, when with texture, causes the entire stack of modifiers to be recalculated after adding or removing an object in the scene.
It seems to be a regression that was introduced sometime between 55a2682348 and 826f6dd9ee.

(I have a strong suspicion that this problem was introduced in 23919d2275)

I can confirm. In fact, the displace modifier, when with texture, causes the entire stack of modifiers to be recalculated after adding or removing an object in the scene. It seems to be a regression that was introduced sometime between `55a2682348` and `826f6dd9ee`. (I have a strong suspicion that this problem was introduced in 23919d2275)

Sergey Sharybin commented

2020-12-03 15:58:22 +01:00

@mano-wii, it does indeed appears to be caused by the commit you've linked. P1831 is what effectively reverts the commit and it makes adding new object fast.

However, I don't currently understand who makes images to change and flush the changes.

P.S. I am not the only one working on depsgraph. There is also Sybren. Not we should always poke all persons in the area, or how to organize this. Better discuss it in the blender-chat though.

@mano-wii, it does indeed appears to be caused by the commit you've linked. [P1831](https://archive.blender.org/developer/P1831.txt) is what effectively reverts the commit and it makes adding new object fast. However, I don't currently understand who makes images to change and flush the changes. P.S. I am not the only one working on depsgraph. There is also Sybren. Not we should always poke all persons in the area, or how to organize this. Better discuss it in the blender-chat though.

Juri Unt commented

2021-03-07 14:32:29 +01:00

Hello. It has been 3 months now and I was hopeful that with new releases of Blender there would be a fix finally. Maybe I am the only one with the problem, but just had to work with a heightmap>displace modifier that was transferred to a 3D print team. The file was almost unworkable performance wise. Posting as a nudge and also to express gratitude to both for having a look prior as the patch provided by Sergei resolved issue in custom build. Thanks!

Philipp Oeser commented

2021-03-07 15:24:47 +01:00

Added subscribers: @Vyach, @lichtwerk

slwk1d commented

2021-03-07 20:08:10 +01:00

Added subscriber: @Slowwkidd

slwk1d commented

2021-03-07 20:08:10 +01:00

I can confirm, I'm working right now on a project where I'm using an image texture displacement and it's almost impossible to do any action without waiting several seconds. The issue occurs also with working with the Attribute Sample Texture in Geometry Nodes.

Philipp Oeser commented

2022-02-23 13:48:43 +01:00

Added subscriber: @Don-Macaron

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

Displace modifier with Image Texture causes scene slowdown #83271