Jonathan de Blok - JDBgraphics

While putting it houdini.env will probably work, better put it in a json package file. That is the more modern replacement for the error prone houdini.env

It gives much more control and can even contain some of basic if/then logic.

https://www.sidefx.com/docs/houdini/ref/plugins.html [www.sidefx.com]

Ideally the houdini.env is just an empty file.

One solution is to render using te clones, they output directly to the render gallery and don't use a viewport. You get your render in the correct/fixed resolution. And they are locked to a lopnet/camera/frame so it gives a predictable output as you'd expect.

The interesting bit is you can have multiple clones rendering at different frames for example, so when doing lookdev you can check lighting at different frames at the same time. There is still no 'render button" so you have to pause/enable them if you don't want trigger a new render at every single thing you adjust.

These things, lack of a VFB and render button, have been mentioned here by a lot of people so they are definitely aware of it. I assume/hope this will be fixed at some point.

That makes sense from a technical perspective but from a user perspective the renders simply don't show up. Maybe the render gallery can have a 'all databases from this hipfile' checkbox or something like that? or use multiple paths/wildcards?

(Workflow wise it could be a bit less rough when exclusively using clones for rendering and using multiple LOP networks)