zhang xianhao

ccyzkk

About Me

Expertise
CG Supervisor
Location
China
Website

Connect

Recent Forum Posts

LOP Instancer Copy Custom Point Attributes April 13, 2022, 9:05 a.m.

Thanks jsmack!

LOP Instancer Copy Custom Point Attributes April 12, 2022, 8:02 a.m.

hi!
I got a problem about LOP Instancer.
if i set "Target Points Location Source" to "First Input's Points",it dosen't copy any attributes except pscale and orient.
i can use LOP Copy Property to fix this,but I don't think it is a best way.
so,How did you solve this problem?

About usd animation cache and virtual memory April 11, 2022, 9:08 a.m.

mtucker
I've never seen the performance degredation you're talking about when using value clips. I assume you're just referencing in the template file generated by USD Stitch Clips to load the value clip? All this talk of the Value Clip LOP and using python/VEX to author value clips has me wondering if you're actually authoring the value clip manually, which I would recommend against once you've used USD Stitch Clips.

In particular, your use of relative paths to the manifest file has me concerned... If you're authoring this USD metadata in LOPs, you should always use full paths to external files (USD files, texture maps, whatever). Houdini can convert those absolute paths to relative paths when you write out the USD with a USD ROP. Relative paths authored by LOP nodes into anonymous in-memory layers will be interpreted as relative to the "current working directory" of Houdini, which is a process-wide global settings that is often equal to $HIP, but can easily get changed to something else, and therefore should never be assumed.

hi,mtucker!
Sorry, I was too busy to reply.
you are right,using python/VEX to author value clips is no a goodidea and it's inefficient.
Maybe that's not the right way to use Value Clip,So,finally,I used alembic file as an alternative.
just reference alembic file in usd.
a little sad but maybe this is the better way for our pipeline on windows.
Many Thanks!