Skip to content
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

Exported files can't be opened in Reality Converter because of wrong type for Color (FTV-662) #176

Open
hybridherbst opened this issue Apr 28, 2020 · 3 comments

Comments

@hybridherbst
Copy link
Contributor

Apple's Reality Converter is very picky about data types.
usd-for-unity uses types a bit incorrect, e.g. diffuseColor is a float3 and not a Color3f (according to spec, it must be Color3f).
This prevents RealityConverter from importing the files.

@jcowles
Copy link
Contributor

jcowles commented May 7, 2020

IIRC, this was a change to the preview surface spec when Color3f was added, but yeah, strictly speaking we are not adhering to the spec:
https://graphics.pixar.com/usd/docs/UsdPreviewSurface-Proposal.html

We should fix it

@jcowles jcowles added the bug label May 7, 2020
@cguer cguer changed the title Exported files can't be opened in Reality Converter because of wrong type for Color Exported files can't be opened in Reality Converter because of wrong type for Color (FTV-662) May 8, 2020
@riemaeker
Copy link

riemaeker commented Nov 19, 2020

We are also running into this issue, and additionally had to update normals data to use a specific type as well (float3 to normal3f). So these are the manual changes we had to make to our USDA (exported with 1.0.3-preview.2) to get it imported without errors in Reality Converter (version 1.0 (20)):

float3 inputs:diffuseColorcolor3f inputs:diffuseColor
float3 inputs:specularColorcolor3f inputs:specularColor
float3 inputs:emissiveColorcolor3f inputs:emissiveColor
float3 inputs:normalnormal3f inputs:normal

@judubu
Copy link
Contributor

judubu commented Nov 24, 2020

Thanks for the update. A fix for this won't be available in the next release but we'll schedule it for the following one.

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

No branches or pull requests

5 participants