Philipp Buschauer

While working with python states I've recently bumped into an issue where the displayed geometry in the viewport is offsetting my hou.GeometryDrawable guides.

The values that are set on the guide geometry do not change but their position in the viewport does.
The attached gif will show the behavior.

Has anyone experienced something like this before?

Cheers!

Yeah, I am used to HDAs cooking a bit longer due to their size, expressions, python scripts etc.
That is expected and can be optimized, but in this case, there are dops evaluating no matter what, which makes me wonder if that is preventable.

Sorry for reviving this old thread but I recently came across this issue with the sop version of the vellum solver.

I have a vellum solver inside a subnet inside of an hda.
The subnet is bypassed and everything inside of the subnet is bypassed as well, including the vellum solver.
The display flag is not on the vellum solver and there is no output sop that would influence the cooking.
Additionally, there is no incoming geometry, simulations are deactivated and I am in manual mode.
When I create the hda, the vellum sop still gets cooked for quite a bit(1.5 seconds).

Looking further into this I realized that putting down any of the sop versions of vellum, pyro, rbd, seems to cause the dop net inside to cook, no matter what I try.
Is this behaviour expected?
(using 18.5.462)