Workspace option to disable 3d scene related calculations to free up system resources when doing non 3d stuff such as VSE or compositing.
Modifiers recalculate every frame during playback causing a MASSIVE drop in performance even when the 3d viewport isn't visible and the user has no need for it to be calculated.
Please vote to add a per workspace option called 'Disable 3d scene calculations', so that all system resources are available when the user needs to use the non 3d related aspects of Blender such as VSE or Compositing.
3 Comments
Would be good to have a bug report containing a blend file that shows this issue. This needs to have some research why it happens. Perhaps there is a valid reason, or a specific case we just didn’t think of,
Hi. One of the scenarios it happens under is when there's an addon that updates the compositor in the only way available, by disabling all render layer nodes and calling render.render().
Ideally if the 3d viewport has been excluded from rendering by disabling the render layer node, then the 3d scene shouldn't be evaluated. This is particularly problematic when updating the compositor from the frame change handler, because it means all modifiers get calculated every frame, making playback extremely slow.
The only solution is for addons to disable all modifiers and hide all objects at the beginning of playback and then re-enable them afterwards, but this is extremely risky as it could result in the scene being saved in that state during the auto-save. This could in turn result in a user having to manually re-enable modifiers and visibility settings if they need to continue working from the auto save following a crash.
calling render.render does 3d related stuff. how would in this case this feature request help. Although this solution might make it easier for add-on developers I do find it a strange option for end-users. There might be better options like having more control on the render pipeline. IIRC there has been a request to make the pipeline node-based so you can have more control.
That said a nodal based pipeline is not a small task. But having a not future proof option is IMO not desired from developement and maintenance point of view.