OTOY Forums

Juan is "use priority" command broken in RC5 ? I have my machine cursor going very jaggy/slow and everything is slow on response when i'm renderinn F9/F10 with my display GPU also (use all GPUs checkmark). I have low priority ON but seems like it's not working. In 3.08 my machine with same scenes is fully responsive when i turn on low priority on display GPU.

Can you please check that in 4.x
Thanks

Same issue for me on my Maxwell Titan X and my bi-xeons on Dell T7500 W10 Pro 1809.

When I'm lauching a render in the IPR it looks 2x more slower than 3.07 or 3.08...At the end, W10 crashes and reboot the PC, like an hard reset...

Ok. Let see if the RC6 build that I want to release this week has these problems fixed.

Thanks,
-Juanjo

Hi JuanJo,
Pb here with animation rendering. Crash after 150 frames (denoising o, AI light on) !
Waiting for R6 !
Thanks

I'm getting out of memory errors in RC5, but when I look at the stats I'm only using 1.3Gb of the 6Gb available. I do have 48M TFD voxels, do those not show in the memory footprint?

00:02:11 (0131.69) * OCTANE API MSG: CUDA error 2 on device 1: out of memory
00:02:11 (0131.69) | ++++++++++++++++++++++++++
00:02:11 (0131.69) * OCTANE API MSG: -> could not get memory info
00:02:11 (0131.69) | +++ IPR RENDER FAILURE +++ processing the failure callback
00:02:11 (0131.69) * OCTANE API MSG: CUDA error 2 on device 3: out of memory
00:02:11 (0131.69) | ++++++++++++++++++++++++++

It actually works the first time, but then crashes when I try to reload. I've built these scenes in earlier versions of v3, but am transitioning them to v4 to see how they fair. This scene ran fine with my 980ti, but with v4 is only seems to run on my 1080ti.

I did notice on another forum (C4D) they had to rollback nvidia drivers to an earlier version (391), but I'm already on 391.24...

thanks,

bruce

Couldn't edit my previous message for whatever reason, but my issue seems to be resolved in RC6. YAY juanjo!