[Optimisation] Disabling objects for render if its scale values are (0,0,0)
There IS the ability to animate keyframes for viewport/render visibility. But in the process of keyframing these two parameters, when the timeline slider goes after the "disable in viewport" keyframe, the object hides in timeline and becomes deselected, so when the slider goes back to "enabled" keyframe, you can't control the object immediately and you need to select the object again. Also you actually have to animate two parameters (disable for render, disable in viewport) in that case. It's not comfortable.
I found the solution that makes the animating process a lot easier: just scaling the object to 0 and using constant interpolation. The result looks like it's hidden.
The problem: Actually, there are still some geometry and materials, that still has influence in render. The objects are not disabled for render. They're just scaled to zero.
The solution: On postprocessing level, in code, make the optimisation, that will be interpret "(0,0,0) scaling" as "disable for render"
6 Comments
This could break some rigs IMO I dont think it should be implemented, it can be easily made with GN in 3.4. I really don't know but it feels to me it might break some stuff
self obj > obj info scale > less than 0.1 > delete obj
If this feature where to be implemented it would incentivize bad habits, to scale down things just so they don't render is so much worse than simply using the display button in the outliner and/ or view layers.
That's a weird and complex way around the actual issue: hidden objects should remain selectable.
Probably you're right and it will be kind of solution. But anyway, there's still the problem of animating two parameters to get the only one goal: disable the object. To be honest, just for me, scaling to zero is much comfortable. I think some people will agree with me.
developer.blender.org/T98124
It's hacky, but I do this sometimes as well. Saving a bit of render time would be awesome 👍