search

EatTheFuture / compify

Blender addon for easier/better compositing in 3D space.
Other
260 stars 12 forks source link

non-footage objects disappeared and when re-enabled stopped going away during "bake footage lighting" #3

Open marklio opened 3 months ago

marklio commented 3 months ago

Everything was working fine, and I think I interrupted the "Render Animation with Compify Integration", and suddenly nothing was rendering. I noticed that everything was "disabled in render", so I re-enabled them, and now they no longer go away when the baking occurs.

Is there something I can do to "reset" whatever state is stuck?

marklio commented 3 months ago

It's possible that unsetting the "disabled in render" across the board fixed me, but I could have sworn that during the texture bake that everything that isn't footage geo/lights would disappear (all shades of white in the viewport. It seems like maybe things are working though.

cessen commented 1 month ago

Sorry for the extremely delayed response.

This is unfortunately an issue with Blender, and there isn't really a good way for me to address it in Compify as far as I'm aware. Basically, Blender's Python API doesn't provide a reliable, race-condition-free way to run operators in sequence (e.g. bake, then render, then bake, ...) without completely blocking the UI. Compify relies on some tricks/hacks to make that work, which unfortunately does mean that the cleanup code (e.g. un-hiding the auto-hidden scene elements) doesn't always run if baking is interrupted by the user.

IIRC, this is actually true of just running Compify's bake on its own as well, because that itself is also using the same mechanisms for pre/post baking operations. Although it's rarer in that case.

I'm leaving the bug report open since it is, indeed, happening. But this is unfortunately just a limitation of Blender's current Python API, which isn't really designed to be used the way we're trying to use it.