Adam Gerber

Not sure if I'm asking the same question as above, but I'm trying to use the restructure scene graph node to tidy up an older usd stage that I have without having to go back to the original graph and re-author everything. Unfortunately I'm running into an issue when reparenting some instancable prims and their respective prototype prim. When I reparent the instances, they retain their reference path, but when I move the prototype as expected this breaks the instances. Is there any way to change that path with vex after reparenting or is it a python thing?

Thanks, yeah that's what I was thinking initially, but it doesn't seem to make any difference. I killed all the camera prims with restructure scene graph node, cached out the USD with those changes, and then added fresh cameras via a merge, which still had the exact same behavior.

Hi, just wondering if anyone else has experienced something like this/ has a solution:

I have a basic architectural environment in a scene with some scattering and props etc. All is fine and good, it renders snappy in the viewport until I hop into a camera....any tweaks I make will take an eternity to update and I have no idea why. It's not switching render prims as far as I can tell and I have it set to half res in the viewport (this is happening with Redshift and karma)

thanks in advance!