Bump node in Eevee. Huge performance drop. #79638

New Issue

Sergei · 2020-08-08T09:59:42+02:00

Sergei commented

2020-08-08 09:59:42 +02:00

System Information
Operating system: Win10 x64,
Graphics card: Nvidia GTX 1660

Blender Version
Broken: 2.83.4
Worked: 2.8

Start Blender 2.8 with Eevee as a default renderer.
Set viewport shading to Rendered
Plug some color or texture to the Color input of the Principled BSDF
Plug some noise or a map to the Bump node and connect to the Normal input of the shader.
Notice the amazing viewport render speed
Save scene and switch to Blender 2.83.4
Open this scene and set the viewport shading to Rendered
Notice that significant lag with this Bump node.

Far as I have checked, this lag started manifesting from version 2.81 and persists even in 2.91 Alpha. Please correct it, because it is the only thing that averts people from
compiling high-quality PBR shaders in Blender and pushes them to different software for texturing, while it could have been done so much better in Blender.

**System Information** Operating system: Win10 x64, Graphics card: Nvidia GTX 1660 **Blender Version** Broken: 2.83.4 Worked: 2.8 1. Start Blender 2.8 with Eevee as a default renderer. 2. Set viewport shading to Rendered 3. Plug some color or texture to the Color input of the Principled BSDF 4. Plug some noise or a map to the Bump node and connect to the Normal input of the shader. 5. Notice the amazing viewport render speed 6. Save scene and switch to Blender 2.83.4 7. Open this scene and set the viewport shading to Rendered 8. Notice that significant lag with this Bump node. Far as I have checked, this lag started manifesting from version 2.81 and persists even in 2.91 Alpha. Please correct it, because it is the only thing that averts people from compiling high-quality PBR shaders in Blender and pushes them to different software for texturing, while it could have been done so much better in Blender.

Sergei commented

2020-08-08 09:59:42 +02:00

Added subscriber: @kritzien

Evan Wilson commented

2020-08-08 11:48:53 +02:00

Added subscriber: @EAW

Evan Wilson commented

2020-08-08 11:48:53 +02:00

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

Evan Wilson closed this issue

2020-08-08 11:48:53 +02:00

Evan Wilson self-assigned this 2020-08-08 11:48:53 +02:00

Evan Wilson commented

2020-08-08 11:48:53 +02:00

Thanks for the report. This was an intentional change in 2.81 in order to improve the quality of the bump node.

On EEVEE's bump node implementation.
ffd5e1e6ac

We basically duplicate the height map branch plugged into the bump node,
and tag each node in each branch as dx/dy/ref using branch_tag.

Then we add a one pixel offset on the texture coordinates if the node is
tagged as dx or dy.

The dx/dy branches are plugged into (new) hidden sockets on the bump node.

This match cycles bump better but have a performance impact. Also, complex
nodetrees can now become instruction limited and not compile anymore.

While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports.

To improve performance, consider using less complex geometry, simpler shaders and smaller textures.

Thanks for the report. This was an intentional change in 2.81 in order to improve the quality of the bump node. On EEVEE's bump node implementation. ffd5e1e6ac >We basically duplicate the height map branch plugged into the bump node, >and tag each node in each branch as dx/dy/ref using branch_tag. > >Then we add a one pixel offset on the texture coordinates if the node is >tagged as dx or dy. > >The dx/dy branches are plugged into (new) hidden sockets on the bump node. > >This match cycles bump better but have a performance impact. Also, complex >nodetrees can now become instruction limited and not compile anymore. While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports. To improve performance, consider using less complex geometry, simpler shaders and smaller textures.

Sergei commented

2020-08-08 11:54:09 +02:00

Whatever you say. But right now, Bump node in Eevee is unusable even with the simplest setup. That's an unfortunate downgrade from version 2.8. Will have to revert to 2.8. Thanks anyway

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

Bump node in Eevee. Huge performance drop. #79638