-
-
Notifications
You must be signed in to change notification settings - Fork 35.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USDZLoader doesn't support all .usdz(usda) files. The only showcase example file works. #28693
Comments
I can reproduce with all files. They render a bit differently with the current
The loader needs a different implementation regarding how to resolve paths and ids like the values assigned to |
I would like to contribute to this issue, but it's beyond my capabilities. However, it touches on a fundamental question about USD and three.js, which I have been asking myself. A few years ago, Autodesk demo'ed USD in the browser. There is also a USD web visualization project ran by the Academy Software Foundation. What is the current status of these projects? Can these efforts help three.js avoid having to create a custom parser which has to be kept in sync with a living standard? |
I've mentioned this topic in #28639 (comment). It would be a help if However, after working at the latest issues, I have realized this is not the actual major issue. It's the fact that USD is an incredible complex format that will be hard to implement and support. Reminds me a bit at Collada and FBX^^. It seems the goal is to provide a format so teams with different authoring software can work on common scenes. Such a focus means respective 3D assets tend to be expensive to deliver and parse on the client side, though. I'm not sure what to kind of goal we should have with USD in |
Description
Can't open normally other usda files by usdzloader. I've used the same showcase example configuration but had broken preview. Normally works only original file from threejs models/usdz/saeukkang.usdz
Reproduction steps
Code
// code goes here
Live example
Screenshots
Version
165
Device
No response
Browser
Chrome
OS
MacOS
The text was updated successfully, but these errors were encountered: