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

Read boolean material parameters and primvars #15

Open
kenmcgaugh opened this issue Sep 2, 2020 · 2 comments
Open

Read boolean material parameters and primvars #15

kenmcgaugh opened this issue Sep 2, 2020 · 2 comments

Comments

@kenmcgaugh
Copy link

kenmcgaugh commented Sep 2, 2020

Hello,

It looks like boolean primvars and material parameters are skipped over completely by UsdIn (and pxrUsdIn). Would it be possible to have them cast to an integer upon import? Where this is causing an issue for me is that the Autodesk Standard Surface shader has the "thin_walled" parameter declared as a bool. But this parameter cannot be inspected from within katana as it is completely skipped over on import. The only option is to declare the parameter as an int within the USD file, breaking the spec for that shader.

Thanks.
--Ken

@kenmcgaugh
Copy link
Author

Sorry, I need to clarify the above a bit. While digging deeper into this I realised that UsdIn actually is
casting boolean material parameters into integer values, but it is not for primvars. This makes it difficult to use a primvar to override a boolean shader parameter.

Attached is a repro showing both bool and int material parameters and bool and int primvars. The material parameters get expressed as attributes when imported into katana. However for the primvars only the integer one comes in with its value intact.

katana_bool_issue.zip

@JamesPedFoundry
Copy link
Collaborator

Hi Ken,

Thanks for raising the issue, and further thanks for providing a repro file! I've logged this ticket internally for us to investigate #446834.

I will keep this thread updated as to when this starts and the progress on it.

Cheers,
James

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

No branches or pull requests

2 participants