Kevin Su

kevin07041214

About Me

EXPERTISE
VFX Artist
INDUSTRY
Film/TV

Connect

LOCATION
Taiwan
WEBSITE

Houdini Skills

Availability

Not Specified

Recent Forum Posts

usd transform affecting pscale/width in render view? April 15, 2024, 3:41 a.m.

tamte
I don't know if HoudiniGL is displaying the actual width, but to me the scaling looks correct

when importing to LOPs:
- your large hair geo has length 1 and pscale about .0075 so width about 0.015
- your small hair geo has length 0.01 but the same width, about 0.015

scaling 100x will not change proportion of length/width so your scaled small hair will render as 1 long (100x0.01) and 1.5 wide (100x0.015)


you can also just zoom in to your small hair before Transform and you will see the proportions are the same

Thank you so much for the explanation, at first I think since pscale didn't change so the width shouldn't change, but I forgot to take length into account

usd transform affecting pscale/width in render view? April 12, 2024, 6:32 a.m.

Hi, I'm currently running on Houdini version 20.0.590

I came across an interesting problem(?), I tried to create hair then import into solaris, after that I scale them 100 times bigger.
In the scene view, everything seems normal, but when I go in karma render view, it looks like the pscale/widths has been also scaled 100 times, and vice versa, is there any explanation why this is happening?

this is the sence viewport:



and this is when I enter karma render view:




I've attached a simple demo file, any help would be appreciated, thanks!

USD stitch clip render issue Oct. 4, 2023, 5:50 a.m.

robp_sidefx
Looking at the hip file, it looks like it was using a fairly old build of 19.5 (19.5.368?). Can you please upgrade to the latest production build and try this again? I can reproduce the issue in .303 but not in more recent builds.

Thanks for reply!

Yes, this issue was found in version 19.5.303, which is our studio's current Houdini version, Glad to hear the issue is gone in recent build.

I'll try this again once we update to a newer version.


####UPDATE####

After upgrading to version 19.5.752, this issue no longer exist.