I’m experimenting with converting an OBJ-based workflow to LOPs, but I’m struggling to provide guide geometry for my users (see my previous post on purpose=guide). What’s the officially-sanctioned way to provide useful guides in LOPs?

Cheers,
Tim

When you say "converting", are you looking to lift existing OBJ content over to LOPs, or are you wanting to "start from scratch" in LOPs?

After years of standing on the sidelines I wanted to "give LOPs a chance", so I'm starting from scratch. Most of my assets are a straightforward repackaging of objects like lights, with scientist-friendly / domain-specific parameterizations, but in a couple of cases - such as a stereo camera rig - I'd like to provide some simple guide geometry, where a full-blown viewer state would be overkill.

I should mention that the early results are pretty good: the core idea of Solaris - generate a scene graph procedurally - does a good job of simplifying and clarifying an inherently branchy workflow, while eliminating the need for takes or similar workarounds. I just wish LOPs weren't buried in a mountain of USD jargon.

Cheers,
Tim

I just discovered by accident that you can generate guide geometry for a LOP asset, using the Node > Guide Geometry setting in the type properties window, even though the documentation claims it's only for SOPs. Note that the geometry is only visible when you show the handles for the asset. Between this and getting schooled on purpose=guide (see https://www.sidefx.com/forum/topic/93051), I'd say that that creating custom LOPs is looking pretty good.

Cheers,
Tim