USD preview material bug - Quixel Asset
1715 5 2- papsphilip
- Member
- 385 posts
- Joined: July 2018
- Offline
I was importing a Quixel usd asset as a reference and noticed the textures were showing up weird.
The available material is a usd preview surface
If i edit the material first i lose the textures
if i remove the uv primvar reader textures appear again but they are still weird
if i add a new usd preview surface and plug my texture its shows up correctly on the viewport.
Is this Quixel or Solaris bug? or am i doing something wrong?
Here are some screenshots of the steps
The available material is a usd preview surface
If i edit the material first i lose the textures
if i remove the uv primvar reader textures appear again but they are still weird
if i add a new usd preview surface and plug my texture its shows up correctly on the viewport.
Is this Quixel or Solaris bug? or am i doing something wrong?
Here are some screenshots of the steps
- papsphilip
- Member
- 385 posts
- Joined: July 2018
- Offline
just noticed when i edit the material and dive inside i need to override the uv string name on the subnet. The input string parameter.
That fixes the brown material issue but the weird seams are still there. The whole problem comes down to the usd preview surface node. The settings are exactly the same between the Quixel one and the one i created. Could it be corrupted?
That fixes the brown material issue but the weird seams are still there. The whole problem comes down to the usd preview surface node. The settings are exactly the same between the Quixel one and the one i created. Could it be corrupted?
- goldleaf
- Staff
- 4175 posts
- Joined: Sept. 2007
- Offline
I'm not sure which one you're referring to, that could be corrupted. If you select the mesh prims in the Scene Graph Tree, and look at the Scene Graph Details, you can see what the name of your surface parameterization is (i.e.
I wouldn't think any seam issues are in the shader; but you might need to log a bug through support, where you can securely/confidentially share the files with us if necessary to resolve the bug.
st
or uv
- some USDZ files have decided to use st0
by default...). As long as that name is in the USD Primvar Reader, it should work; you may also want to double-check that the type matches your primvar (i.e. is it a vector2 or vector3).I wouldn't think any seam issues are in the shader; but you might need to log a bug through support, where you can securely/confidentially share the files with us if necessary to resolve the bug.
I'm o.d.d.
- papsphilip
- Member
- 385 posts
- Joined: July 2018
- Offline
- goldleaf
- Staff
- 4175 posts
- Joined: Sept. 2007
- Offline
- papsphilip
- Member
- 385 posts
- Joined: July 2018
- Offline
-
- Quick Links