Problem importing materials from USD 21.11 [USDU-342]
See original GitHub issueIn USD 21.11, the type of the UsdPrimvarReader.varname
input was changed from token
to string
, with this commit. Because of this, importing into Unity assets created with USD 21.11 creates objects that are simply colored instead of fully textured.
This can be easily reproduced by exporting a cube with a textured Standard Surface material from Maya 2023 (that ships with USD 21.11).
Is this a known issue ?
Issue Analytics
- State:
- Created 6 months ago
- Reactions:1
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Blender import usd not importing materials
Basically I have taken unreal projects, used omniverse to bring them into Create. Then exported usd and fbx files to try and open...
Read more >Missing Plug-in Configuration for USD Import · Issue #3226
Describe the bug Missing Plug-in Configuration drop down option when you are importing USD files. I expected there to be at least an...
Read more >Official - USD for Unity Updates | Page 3
I have a problem with USD plugin. In realtime importing script, completely based on example ImportingMeshExample script I have next error
Read more >3ds Max maps and materials appear blank when exporting ...
Issue: When exporting 3ds Max scene files to .FBX or USD format for import into Unreal Engine, the materials may appear blank (pure...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks @vickycl. I just rebuilt from your branch and our assets now look as we expect them to: geometry is properly textured.
@lee-aandrew These particular USD files are not exported from third party applications but instead created programmatically in our pipeline.
Hey @nicolaspopravka the fix for this has landed in dev, and will be released soon in 3.0.0-exp.3. Please do reopen the case if you have any more issues 😃