Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Maya Looks: support for renderman PxrTexture #3189

Closed
antirotor opened this issue May 16, 2022 · 2 comments · Fixed by #3190
Closed

Maya Looks: support for renderman PxrTexture #3189

antirotor opened this issue May 16, 2022 · 2 comments · Fixed by #3190
Assignees
Labels
host: Maya type: enhancement Enhancements to existing functionality

Comments

@antirotor
Copy link
Member

antirotor commented May 16, 2022

Feature

We need to add support for Renderman's texture node PxrTexture in look collector.

[cuID:2aua37p]

@antirotor antirotor added type: enhancement Enhancements to existing functionality host: Maya labels May 16, 2022
@antirotor antirotor self-assigned this May 16, 2022
@BigRoy
Copy link
Collaborator

BigRoy commented May 16, 2022

Actually - can you test whether this works for PxrTexture?

I would recommend refactoring the Look Collector to that. It will basically support any plug-in's File nodes or nodes that contain input files which the Plug-in maintainers have registered with Maya's system.

It would likely allow us to avoid this whole "if type == x" shebang in the Collect Look and be more Maya generic in general.

@antirotor
Copy link
Member Author

antirotor commented May 16, 2022

I think we must refactor collect/extract look in more depth - add more generic renderer support, better support for various "maketx" tools and so on. For now, I used "old" style just to quickly add support for renderman for the client. We'll still need to handle various attribute names for file path on texture node, fact that sometime (in case of renderman) there isn't for example colorspace attribute and it's equivallent and so on. And I agree it would be nice to get rid of those pesky conditions.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
host: Maya type: enhancement Enhancements to existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants