I'd be fine with the even shorter usdBlender2411. We just need to always remember to bump this version at the same time as the main library version (and hope that linux distro's do the same if…
Right this is due to floating point precision issues and is not unique to blender. In fact, here is what Python would give (they even use 64bit floating point precision) for a similar calculation: …
Let's close as a duplicate. I've added the fix to the backport list today as more bugs are coming in for it.
This particular issue is the same as #127434 which is fixed for 4.3 and scheduled to be back ported to 4.2 LTS sometime in the future (hopefully for 4.2.4 next month). I'll close this as a duplicate.
Thanks Jorn, that information is enough to confirm the issue - we need to properly guard the JSON code paths regardless of how that file ended up broken.
Just a heads up, but there's 2 .blend files attached to Issue 115871 that show bad behavior with this PR. Both will consume all memory available when trying to view or render the volumes.
It's possible, though my report above was done using the 2.2 version of ociocheck as that's all I have available. Either way, it's still something for Nuke support to confirm on their side.
You will need to contact Nuke support as we're not going to be able to diagnose their issue either. According to ociocheck our config file is valid in so far as what it checks (report attached).
I'm guessing you mean version 4.2.3 above. In any case, animated instancing support has not been implemented yet unfortunately. We typically don't track unimplemented features here but since we…