This is usually a problem in the houdini.env configuration file. You must define a single environment variable to include all the plugin paths separated by semicolons. The definition of the same variable twice or more doesn't work.

-Juanjo

Currently, you need to edit the RenderTarget HDA and link the texture node to the camera node yourself.

-Juanjo

I'm afraid that Octane 2022.1 only supports M1/M2 Apple Silicon machines. For AMD GPUs under macOS Monterey, you need to install the old PR14 version.

-Juanjo

Hmm, do you have an example scene with this behavior, or does it happen in any complex scene?

Thanks,
-Juanjo

I think that right now, once you connect a node including vertex attributes to the bump input, the bump doesn't work, probably because the core can't compute the right shading derivates information for bump/normal mapping from vertex data. I don't know the details, but it sounds like this kind of ...

Hmm, I think the vertex attributes don't work for bump, do they?

-Juanjo

Sorry to double post, but my IPR in Houdini is not displaying any image.

I'm running on a Mac Pro with OS12.6.3 on an AMD 6900XT GPU.

In Houdini, I can't get any image to appear in the IPR, and I'm sure it's user error but I was wondering if anyone had a clue as to what I'm doing wrong?

I have ...

So it's pretty weird, I didn't manage to narrow down to a specific issue. The first time I opened up Houdini and submitted a sequence render, got a crash after 4 frames. Opened up again, same scene, same settings and manually stopped the render at 60 frames - all went fine, no crash.

Not sure what ...

+1 for crash when rendering out as a sequence - Win11 + H19.5.569.

No error, no console messages, Houdini just quits. Scene and render works fine with 2022.1.0.6.
Can you share the scene to reproduce the problem here? It is clear that the latest fixes to avoid memory leaks while cleaning the ...

Houdini crash when sequence render, work fine in previous version.
You are working in full-scene reload mode, right? As a workaround, you could try to render the scene in update mode, if possible.

Can you please share the scene to reproduce this problem? All my unit tests work fine here.

Thanks ...