Renderman Solaris UDIM tip
3167 6 2- BrianHanke
- Member
- 433 posts
- Joined: April 2018
- Offline
If anybody's ever wondering why their RenderMan scenes with UDIM textures display fine in the Solaris viewport but don't render via husk, the textures need to be referenced with <UDIM> not <udim> or anything else. I learned this the hard way today!
Subscribe to my Patreon for the best CG tips, tricks and tutorials! https://patreon.com/bhgc [patreon.com]
Twitter: https://twitter.com/brianhanke [twitter.com]
Behance: https://www.behance.net/brianhanke/projects [www.behance.net]
Twitter: https://twitter.com/brianhanke [twitter.com]
Behance: https://www.behance.net/brianhanke/projects [www.behance.net]
- Hamilton Meathouse
- Member
- 166 posts
- Joined: Nov. 2013
- Offline
- BrianHanke
- Member
- 433 posts
- Joined: April 2018
- Offline
Hmm, I have had that happen, but not recently. I think it's usually a result of an incorrect UDIM token or sometimes a renderer has a "Mari tiles" (paraphrasing) or some such checkbox.
Subscribe to my Patreon for the best CG tips, tricks and tutorials! https://patreon.com/bhgc [patreon.com]
Twitter: https://twitter.com/brianhanke [twitter.com]
Behance: https://www.behance.net/brianhanke/projects [www.behance.net]
Twitter: https://twitter.com/brianhanke [twitter.com]
Behance: https://www.behance.net/brianhanke/projects [www.behance.net]
- AndreasWeidman
- Member
- 127 posts
- Joined: Feb. 2021
- Offline
We've had this problem as well with Redshift. For some reason, the default token will be all jumbled with "%" and others things. Will render fine in hydra/viewport, but not at all in mplay/husk. Can't remember the the specific situation, could have been that the artist forgot to change the "type" in the drop down menu as well.
Edited by AndreasWeidman - July 24, 2021 15:35:49
- lewis_T
- Member
- 234 posts
- Joined: March 2013
- Offline
- AndreasWeidman
- Member
- 127 posts
- Joined: Feb. 2021
- Offline
tinyhawkus
That's literally all you do. Use that, and the expression is correct.
Yes, as I mentioned, that is what you should do to get the correct token.
What I, (and Brian), suggest is interesting though is that an incorrect token, (like using the default “framerange” or misspelling), will render fine in hydra/viewport but not in husk (will just be black). So when a mistake happens in lookdev you don’t catch it before it is too late and end up screwing your farm renders.
In our case when It happened once, I don’t remember if it was a misspelled token or if the drop down was set to the wrong thing when it happened. Either way, would be nice if hydra and husk interprets tokens the same “correct” way.
- Hamilton Meathouse
- Member
- 166 posts
- Joined: Nov. 2013
- Offline
-
- Quick Links