Optmization for viewport refresh (Cycles)
Developers must check the GUI around how working for Optmization for viewport refresh (Cycles). There is many issues that refreshing viewport in cases is not needed, eg. disable selection in outliner. If hardware is strong, then maybe not visible the re-rendering after click the checkbox, but in my carer I see often this type. I'm suggesting to put some by users info in comments what user meet as viewport refresh if not needed to resolve problems and optimize rendering process.
I can add, that many time on laptop fun wind is not need coz GPU is not charged, but in case GUI requesting rerendering, then fun must start working and turingin on whole energy management, etc. It's broking comfort of work and going to equipment wear.
2 Comments
I agree, but it shows even on a strong machine, if the scne and/or shaders are complex enough.
Specific cases, where a Cycles update in the viewport is certainly not needed:
That's what I found so far.
This makes sense and reflects my own experiences. Especially adding a new unconnected node in the shader editor....this will have a short slowdown even in very efficient scenes.