Octane viewport stops after some samples (w.lights)

[mbetke]

I'm experiencing an annoying bug here which came out of nowhere and keeps me busy for hours now.
using Octane daily here for many hour and never had such a problem before.


I have a simple scene with 40 lights in it. Nothing which keeps my Vram full or occupies system ram.
First I tried an Octane light, then just a plane with an emission.
When I fire up the Viewport it starts and just stopped after 1 sample, sometimes 86 samples or another early random number.

I then close the viewport but one or two of my four GPUs are still keeping working.
I have to restart 3dsmax to make it work again.

As soon as I remove the lights or turn of the power in the material it renders as it should.
Tried several versions of the plugin now and also some graphic drivers (older and new ones). SLI is deactivated of course. But had no success with this issue.

Ideas? How can I sent the scene to a dev?

[mbetke]

I solved it!!

After killing all materials it worked, so I took a closer look at the materials.

One material had a mix-material with displacements in the texture slots.
As soon as I cut the "master displacement" the scene renders fine.
When I paste the displacement back in, the scene instantly stops rendering or shows the strange behavior.

100% a reproducable bug with my material setup.

[3dgeeks]

We have a policy of never using displacement for this reason it will just freeze your render and you wont know why. They can be really hard to track down. Its unfortunate that no diplace override checkbox has ever been introduced.