Skip to content

Fix a bug where newer RenderMan shading nodes would be skipped when exporting Usd from Maya #3999

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

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

katpet
Copy link
Contributor

@katpet katpet commented Nov 14, 2024

Fix a bug where newer RenderMan shading nodes would be skipped when exporting Usd from Maya. There is a hardcoded map in maya-usd/lib/mayaUsd/fileio/shading/rfmShaderMap.h, and newer nodes that don't appear in that map were being skipped. I don't think the map is necessary for nodes that don't actually require a name mapping; it would be difficult to keep the list up to date. This change adds some code that falls back to assuming the rendermanForMaya writer is appropriate for nodes that would otherwise have been skipped.

Fix a bug where newer RenderMan shading nodes would be skipped when exporting Usd from Maya. There is a hardcoded map in maya-usd/lib/mayaUsd/fileio/shading/rfmShaderMap.h, and newer nodes that don't appear in that map were being skipped. I don't think the map is necessary for nodes that don't actually require a name mapping; it would be difficult to keep the list up to date. This change adds some code that falls back to assuming the rendermanForMaya writer is appropriate for nodes that would otherwise have been skipped.
@katpet
Copy link
Contributor Author

katpet commented Nov 14, 2024

This was my first time digging into this code, so there may be a better way to go about this. Or there may be some conditional necessary before going ahead and using the rendermanForMaya writer for unknown nodes. This change does fix the bug for my examples though. Let me know if you need advice on reproducing the problem.

@seando-adsk
Copy link
Collaborator

@katpet Thank you for submitting a pull-request, however before proceeding you will need to sign the Contributor License Agreement (CLA).

Sean

@seando-adsk seando-adsk added the do-not-merge-yet Development is not finished, PR not ready for merge label Nov 18, 2024
@seando-adsk seando-adsk closed this Feb 5, 2025
@seando-adsk
Copy link
Collaborator

@katpet Closing this PR as we never received a signed CLA from you. If you wish to continue please submit a signed CLA.

Sean

@katpet
Copy link
Contributor Author

katpet commented Apr 1, 2025

Hi, I believe a CLA has been submitted by my company. Can this pull request be reopened?

@seando-adsk
Copy link
Collaborator

@katpet Yes feel free to reopen. Can you verify if the CLA was sent (to email address). I haven't received any CLA yet.

Sean

@neilh-adsk neilh-adsk reopened this May 30, 2025
@neilh-adsk
Copy link
Collaborator

New updated CLA received, reopened the PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge-yet Development is not finished, PR not ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants