Wednesday, July 14, 2021 (2:00PM PT/5:00PM ET)
- Conversion from USDZ into blender and out to GLTF is a great short term solution, but...
- Worth doing test for conversion of animated models over time.
- Makes a compelling case for a native Sdf plug-in for GLTF import/export.
- Past initial mesh import, would USDSkel and GLTF bi-directional conversion be lossless?
- Draco plugin may need to support native Draco files better, or does it matter in a separate Sdf plugin?
- KTX as native Hio plugin would likely be mandatory, does Hio support unpacking direct to GPU texture via Hgi? (Brian from AMD hints at a yes)
- Is MaterialX and its advances (especially in tackling WebASM) going to be the way forward for all shading interchange in USD.
- OCIO and color accuracy again came up as important, but too large a topic compared to getting a better bare-bones implementation anyone can use.
Video Conference Link
Wednesday, June 2, 2021 (3:00PM PT/6:00PM ET)
- Autodesk showed USD import into Forge. Translates to Forge-native geometry.
- Autodesk also working on a WebGPU Hydra delegate that does PBR shading.
- A lot of overlap between the delegate above and Filament (i.e. SPIR-V tools running in browser)
- TBB remains an issue that everyone is keen to solve.
- Philippe Sawicki working on an MVP list for JS-bindings.
- Dhruv Govil is interested in what can be leveraged from ASWF initiative to auto-gen Rust bindings.
Wednesday, May 5, 2021 (3:00PM PT/6:00PM ET)
JavaScript bindings, need a real strategy on how to tackle them.
Static Initialization macros don't work well in WebASM, but being explicit about what is used for dead stripping to occur might be better for download times.
See what changes have landed in /dev that may help reduce reliance on WebAsm-TBB and its CORS issues.
Github issue for PRs
Wednesday, April 7, 2021
Working example of WebASM build of USD with a Hydra delegate for Filament
Ideally GitHub Pages version at https://marsupial.github.io/USD/extras/imaging/examples/hdFilament would be a live demo, but
Wednesday, March 10, 2021
- Roman Zulak
- Philippe Sawicki
- Alexander Schwank
- Dhruv Govil
- Alex Gerveshi
- Nick Porcino
- JT Nelson
Goal is to have USD WebAsm branch and a WebAsm build of Filament Hydra Delegate by next meeting (April 7).
- Gain a better understanding of performance and limitations loading arbitrary assets and materials.
- Let a larger audience see the size of changes needed to support the platform.
- If the changes are too large for Pixar to mainline, what options are there?
- Provide a use case for Filament that could help push HdFilament code into Google's repo.
- Initially may be a private repo/branch not totally accessible to the world.
JavaScript bindings to USD.
- Roman has started porting a ui-handle implementation to WebGL that would be simplified with re-use of Gf/math library.
- What is the cost (in terms of source code) for additional bindings.
Python support via browser (à la Pyodide)?
- Is there any gain in having existing Python scripts run in a browser?
- May be too expensive of a runtime environment.
Plugins and external dependencies for a WebASM build:
- http(s) ArResolver would be very useful once everything starts working.
- OpenSubdiv is probably a good candidate for a next-step.
- Is OpenVDB support in WebASM via NanoVDB a possibility (or useful)?
- Qt WebASM is interesting, but a little too unstable right now.