System Information
Operating system: Microsoft Windows 11 Pro - 64-bit - Version=10.0.22000
┌────────────────────────────────────────────────────────────────┐ │ * Hardware Information: │ │ - GPU: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 │ │ - GPU Driver Version: NVIDIA Corporation 4.5.0 NVIDIA 511.79 │ │ - CPU MaxClockSpeed=3187 │ │ - CPU Name=12th Gen Intel(R) Core(TM) i9-12900K │ │ - CPU NumberOfCores=16 │ │ - Total System RAM: 34.088476672 GB │ └────────────────────────────────────────────────────────────────┘
Blender Version
Broken: 3.1.0 ec5bbebf3ee1
Worked: 3.0.0 f1cca3055776
Blender Executable Location: C:\Users\olliv\Desktop\Olliver\programs\Blender\blender-3.1.0-beta+v31.ec5bbebf3ee1-windows.amd64-release\blender.exe
Short description of error
So today I encountered a bug where a blend file first created in 3.0.0 f1cca3055776 which was upgraded 3.1.0 saw severe performance issues related to a specific set of geometry node modifiers.
The symptoms would only appear if I was either selecting objects in the viewport, was in solid view or wireframe view.
The symptoms would disappear by disabling and again enabling viewport visibility for a set of geometry node modifiers and no symptoms seem to re-appear after restarting the blend file afterwards if you save your file after enabling/disabling the modifiers.
To demonstrate (Sorry in advance for the lengthy video) :
To give some history on the file, it was first created in Blender 3.0.0 f1cca3055776 (build hash) where I created the geometry node trees and modifiers that glitched out. I believe the bug appeared at first when I opened the file in 3.1.0.
So if I were to make a guess based on that, hence my issue title as I believe the issue could be caused by some form of geometry nodes related cashing that gets reset once you disable/enable viewport visibility. If this is the case, an appropriate fix would probably be to on file open, check if the file was last saved with the same blender version and if it wasnt reset the cache).
Unfortunately I dont have any 3.0.0 copy of the file on my disk anymore, so I can not experiment to see if the issue always re-appears when opening a 3.0.0 file in 3.1.0
Exact steps for others to reproduce the error
- Download the blend file attached
- On Blender 3.1.0 Beta, open the attached file
- Switch to solid view.
- Check the performance by selecting some objects
And to "fix" the issue, select the wireframe cube object in the center or your viewport and disable the modifiers, then re-enable them.
The issue may seem insignificant for some as its easily fixed by disabling/enabling your modifiers, but as an unknowing end user it was difficult for me to figure out that this particular modifier was the cause.
