Skip to content

Instantly share code, notes, and snippets.

@meshula

meshula/usd-industry.md

Last active August 18, 2022 18:15
Show Gist options
  • Save meshula/3aba2b342c550f2ba84cdfee53c7bbaf to your computer and use it in GitHub Desktop.
Save meshula/3aba2b342c550f2ba84cdfee53c7bbaf to your computer and use it in GitHub Desktop.
Download ZIP
Raw
usd-industry.md

notes from Siggraph 2022, USD Industry Council, Aaron Luk moderating

  • ifc requested by many https://en.wikipedia.org/wiki/Industry_Foundation_Classes although it sounds like many consider it to be on a ramp to obsolence

  • discussion of an "interning" schema for IoT data streams bridged via fabric or directly into usd available in usd via dynamic payload

  • coordinate systems frequently mentioned example comment: "up axis needs units" insert Nick rant about formalisms around coordinate systems my opinion is that we are 90% of the way to the finish line here: https://graphics.pixar.com/usd/release/wp_coordsys.html but formalisms around metrics are missing

  • parametric prims important for architects (e.g. stair cases where the stairs are computed, Rhinoceros/Grasshopper logo appears in everyone's slides it looks like this: https://medium.com/generative-design/computational-design-in-grasshopper-1a0b62963690 and has results like this: https://www.grasshopper3d.com/page/architecture-projects

  • Fosters and Partners materialX chosen as standard to describe their materials wish for lod support need parametric relationships/dependencies (see Grasshopper) Internet of Things - digital twins they wish for an mdn-like doc site, tracking USD features, compatibility eg: https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Page_structures/Compatibility_tables and: https://github.com/mdn/browser-compat-data

  • Berge "because USD is an open format people can stay in their software, that don't (sic) scare away clients" prefer usd to vdb, they see no need for two formats (performance, portability) need for custom metadata in USD, specifically attach a json dictionary with their custom doodads CATIA <-> 3ds Max NURBS interchange desired. Discussion revealed that the USD support in 3ds max "degrades" usd assets significantly structure, subd information, nurbs, all "degrade"

  • Escape Technologies Seeing a transition from single user/machine to cluster/farm/collaboration higher order nurbs desired in USD desire for cross version USD support akin to vfxplatform ~ a stable way of moving forward through USD versions round tripping of subdivision surfaces a concern

    • e.g. loading subdiv data into an application that doesn't support them has the possibility of degrading the source data if the data is edited (pointing to degradation via 3ds max again) random thought by Nick: could payloads with degraded data be marked as such via a property or other mechanism?

  • round table

    utf8 - skipped my questions are around security and common attacks and bidi, didn't get to discuss

    georeferencing desire for compatibility with any of the many existing schemes geoPose is picked for glTF, it looks good. http://geopose.org

    fabric the main point is decouple sim frame rate from rendering frame rate, aka decouple usd writes from rendering rate. Nick wonders: should this be a capability of hydra? Seems "yes" to me at first blush, I gather from discussions comments by Side Effects and game devs around hydra integration, that this tends to come up a lot.

    markup desire for annotations such as "accuracy" need to be associated with individual points, edges, and faces. In a lidar survey, they want to encode "this point is accurate within 10cm". In a file describing a building component, they want to encode "this beam needs a 1cm tolerance"

    coordinate systems and metrics came up again, most of the discussion was about ad hoc fixes via metadata and that sort of thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment