OTOY Forums

I still have this bug with the new build v4.02.1, bug got a screen grab of the mem usage after the scene has loaded to GPUs & starts to render.
Lots of headroom, as the image is only 1920x1080. Fails on the GPUs that have the most RAM too.

The same scene in the standalone renders without any problems.

Hmm so it is LW plugin problem not Octane core issue then ?

Yes, this seems the main mystery here. The weird issue is that Standalone doesn't have this problem, while it should share the same Octane core code used by the plugin. We know that even LWSN crashes, so the problem can't be related to the Layout viewports, the code used to preview the image, or something like that.

Thanks,
-Juanjo

My local shop has offered to loan me a 2080ti, just one. So I will swap out one of the 1080ti's and see if I can push the number of cards to 5. As of right now, the plug-in will only run with 4 of the 2080ti cards, as soon as I add a fifth or sixth, currently both 1080ti's, I get out of memory errors.
Will be able to test this on Monday.

I can confirm that mixing pascal and Turing causes errors. Now both of 2080ti fail with errors and pascal works fine. Not even sure if it is software or hardware. It worked great for a month. Link to video in the post viewtopic.php?f=80&t=70641&start=10

Not sure it's the same bug as Octane 4.x is running solid when I just use the four 2080ti cards.

My plan of replacing a 1080ti with a 2080ti has to wait due to spare being sold.

Updated to the new driver 419.17 and this has fixed my problem.

Now running on all 6 GPUs & renders fine.

NemesisCGI wrote:Updated to the new driver 419.17 and this has fixed my problem.

Now running on all 6 GPUs & renders fine.

Thanks for the update!