If you really, really can’t stray from the 3.3 LTS release (and I get it- I spent a lot of time in film/animation/vfx), what is preventing you from running both and using the OV Blender build to export into Nucleus / Omniverse apps? Is it the plugins you mentioned, or some other incompatibility?ĭefinitely the plugins not being compatible (and even if they are compatible often not working in reverse), along with not wanting issues like I said before where files accidentally end up with mixed versions. In the end I just don’t want to risk throwing a wrench in a working system, or having issues like someone accidentally saving a file in a newer version which while that usually works can cause issues.

And where my goal here is to more easily use game environments to render higher fidelity animations and such, that would be a problem. I’ve also heard from some people newer versions can have issues with crashing during rendering. In the end it’s more reliable to stick to an LTS.īut yeah a lot of this is due to Python and API changes. There’s also other tools used for creating animations that can also break (retime, anim-aide, etc). Additionally, those updates can cause changes to the rig, it’s just too risky.Īs such I try to stick with one version for as long as possible. I could see some Python Add-ons needing updating but overall your experience shouldn’t be that different, and if it is we’d love to know what the pain points are.Ĭertain rigging assets I use mostly, there’s an asset we use called Auto Rig Pro that frequently breaks with new blender versions, and also their FBX export behavior changes which can cause problems in a big game project.

I’d be curious to hear what specific assets and plugins don’t work with the OV Blender build.

Blender current version