OpenUSD v24.08 release candidate available on GitHub

General Announcements
1

Hi all,

The release candidate for the upcoming 24.08 release is now available on GitHub under the 24.08-rc1 tag. The CHANGELOG for this release is available here:

Version 24.08 is scheduled for release next Monday, July 22nd. Please post any questions or feedback you may have in this thread, and file issues in our GitHub repository for bug reports.

Thank you!

  • Sunya
4 Likes
2

Very exciting! I’m particularly happy to see the StageSceneIndex stuff advancing so much. Are there any major remaining “todos” before it reaches feature parity with UsdImagingDelegate?

In particular I was excited for this item to show up, because its absence was a blocker for Houdini to switch over to the StageSceneIndex approach: Fixed UsdImagingGLEngine::DecodeIntersection when using StageSceneIndex.

But I have a concern here… It seems like the implementation of that method uses a function HdxPrimOriginInfo::FromPickHit, which uses _ComputeInstancerAndInstanceIndicesAndLocations, which looks to me a lot like the code that led to the need for the vectorized HdSceneDelegate::GetScenePrimPaths and UsdImagingPrimAdapter::GetScenePrimPaths methods implemented by the instancer and point instancer prim adapters.

Are my performance concerns here unfounded because this method is actually really fast? Or is a vectorized FromPickHits already in the works? Or should I get onto the task of creating a PR to add this method?

Thanks,
Mark

3

Hey Mark!

StageSceneIndex is coming along really well! We’ve deployed it to a bunch of workflows internally, so at least in those use cases it’s quite stable :). We’re still missing UsdSkel support and material collection bindings, but those are next on our list, and then StageSceneIndex will be at/past feature parity.

The note about FromPickHit is a good one. I expect it to be a bit cheaper than GetScenePrimPaths because we prepare the path reconstruction data ahead of time and that function is just doing the path stitching. For that reason, I think doing a vectorized decode might not get you anything over just throwing everything in a parallel for. But if you find differently, we definitely want to make this code work well for you.

Cheers,
Tom

4

Hi all,

We’re delaying the 24.08 release originally scheduled for today, pending a new release candidate with some late additions and fixes. We now plan to release 24.08 this Thursday, July 25th.

RC2 will be published early Tuesday, July 23rd. The new changes in this release candidate are:

  • Fixes for various issues for the new GfColor and GfColorSpace classes

  • Added “--onetbb” option for build_usd.py to enable oneTBB when using the build script, based on feedback from (among other places) this thread.

We think these changes are important to get in for 24.08, but they are relatively small so a shorter period between release candidate and release seems appropriate. I will post a follow-up to this thread when the new release candidate is available.

Thanks for your patience!

  • Sunya
1 Like
5

Hi all,

OpenUSD 24.08 release candidate 2 has been published on the GitHub repo under the v24.08-rc2 tag.

  • Sunya
1 Like
6

Thanks Tom, we’ll try out FromPickHit, hopefully in the not too distant future, and let you know how it compares to GetScenePrimPaths. Or more specifically, we’ll let you know if there is a problem :slight_smile:

And thank you for the info about remaining todos for feature parity. It’s really helpful for our planning.

Mark