Wondering if someone bumped into this problem. Solaris keeps updating scene non-stop which makes things barely working. During this the pencil icon keep flashing and the CPU is at high load.

The problem seems to be coming from the materials. If I disable some of them (narrowed it down to 3 of them but still not sure, there's 100+ of them) it stops, if I disable their first textures it stops. I tried everything like rebuilding the materials from scratch, renaming whatever I can and replacing the files, but it returns again and again.

This behavior inconsistent, sometimes I manage to stop it, and it's back after Houdini restart. Sometimes I see a warning that the material have time dependency, but it does not. This never happened in 20.5, now I am simply stuck and unable to find the source of it to properly bug report.

H 21.0.559-566 on Win 11

UPD. There's another suspect - karmafogbox LOP, i think it hasn't been updated for H21

I've had that issue before when I had more than one viewport open at once.

pixelninja
I've had that issue before when I had more than one viewport open at once.

Hey, thanks for the hint!
I definitely have just one viewer open.
Actually I more confident now that the culprit is the fogbox LOP, seems like its setup interferes with the other material parameters (including the material time dependency which is on for it). I recreated a simpler setup of it, will see from here.

I have encountered this issue. The scene did contain a fogbox. I also use two viewports most of the time while working in Solaris.

If I remember correctly this error https://www.sidefx.com/forum/topic/102050/ [www.sidefx.com] did also constantly print. Making the light linker node crash Houdini, when I tried to use it.

Well, it's even more weirder.
I added a curve box as a guide object (same way as the fogbox uses) and the problem returned even with my simplified setup. As soon as I delete these curves the problem goes away.
I have no idea what this is, but if the devs come by here, please pay attention to this weirdness.

Is that a reproducible error setup? If so, I'd suggest filing an RFE.

It’s a known bug and there was an RFE open cant remember the number.

It’s an issue with the usdpreview surface you can get rid of it temporarily if you make sure your materials are set to render purpose only. Thats the only thing seems to work for me!

edlgm
It’s a known bug and there was an RFE open cant remember the number.

It’s an issue with the usdpreview surface you can get rid of it temporarily if you make sure your materials are set to render purpose only. Thats the only thing seems to work for me!

oh my, thanks a lot, it's been poisoning my work for weeks now, and I wasn't able to isolate the problem exactly

Disabling "Auto-generate Preview Surface Shaders" on the Material Library LOP seems to help too