Using GN generated attribute in shader editor drastically reduces Workbench viewport performance after switching from Eevee #95766
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#95766
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system:
Graphics card:
Blender Version
Broken: (example: 2.80,
edbf15d3c0
, master, 2018-11-28, as found on the splash screen)Worked: (newest version of Blender that worked as expected)
Short description of error
When using attribute which is being generated by Geometry Nodes in Shader Editor, the Workbench viewport performance drops (especially navigation) drops drastically when switching to it from Eevee.
NOTE: I am attaching stripped down version of a production scene because I have not succeeded in recreating the issue from scratch. Here is a proof that I tried to recreate the issue from scratch:
GNSlowNavigationBug.blend
This attached file should contain all the same conditions which could possibly lead to the same bug, yet it does not happen in it.
Exact steps for others to reproduce the error
Open the attached .blend file: Tree_SlowNavigationBug.blend
Switch viewport mode from Workbench to Eevee
Switch viewport mode from Eevee back to workbench
Result: The viewport performance is poor
Expected: The viewport performance remains unaffected
In the shader editor, in M_Bark material, disconnect the Attribute node
Save the file
Re-open the file
Switch viewport mode from Workbench to Eevee and then back to Workbench
Result: Disconnecting the attribute node solved the Workbench viewport performance issue
Expected: Using the GN generated attribute in shader editor does not have such extreme impact on Workbench viewport navigation performance.
NOTE: While the source of the issue may be the same as https://developer.blender.org/T94609 I am still reporting it as a new bug, since the effect and repro steps are different.
Added subscriber: @Rawalanche
Added subscriber: @lictex_1
possibly same as #93440?
Added subscriber: @PratikPB2123
Seems same issue so I will mark this report as duplicate
@Rawalanche hi, feel free to comment or reopen if there is any misunderstanding from my side.
Closed as duplicate of #93440