Page 1 of 1
Not full load GPU even at priority HIGH
Posted: Wed Jun 01, 2016 5:37 am
by bertritude
Hi,
I installed the last V3 version and whe I render even at high priority, my GTX980 SLI don't work both cards over 89 load %.
during the beta tests version it was possible to reach 99%. Is there something I missed ?
Thanks
Bertrand
Re: Not full load GPU even at priority HIGH
Posted: Wed Jun 01, 2016 5:39 am
by bertritude
With the screen capture it's better...
Re: Not full load GPU even at priority HIGH
Posted: Wed Jun 01, 2016 6:37 am
by ChrisMills
Un-tick the "Use Priority" boxes if you want to devote all the GPU power to rendering.
Re: Not full load GPU even at priority HIGH
Posted: Wed Jun 01, 2016 7:25 am
by bertritude
ok , I'll try this evening.
and for use for tonemap, if checked on one card, it uses some "power" for display ?
Re: Not full load GPU even at priority HIGH
Posted: Wed Jun 01, 2016 8:35 am
by ChrisMills
The Tonemap tick-box is new. I haven't seen any documentation on that.
The Priority system makes Octane leave some processing power spare so you can keep working on a scene while the Octane renderer is running.
For the card that isn't connected to the monitor, always keep Use Priority off.
If the card connected to your monitor, use Priority while you're working on a scene. You can turn Priority off while you do a full render, but it will make your screen very sluggish.
Re: Not full load GPU even at priority HIGH
Posted: Wed Jun 01, 2016 10:22 am
by bertritude
ok thanks, it's clearer

Re: Not full load GPU even at priority HIGH
Posted: Wed Jun 01, 2016 7:59 pm
by aggiechase37
Or you can run the monitor off the iGPU if you have an iGPU and let the Nvidia do it's work in the background. That's the solution that I use and it works great. I've got 4770 with the 4600 iGPU built in, and running the monitors to that, and I have a Titan X that does all the render crunching.
Re: Not full load GPU even at priority HIGH
Posted: Fri Jun 03, 2016 11:06 pm
by Notiusweb
Tonemap was given as an option to us users who were experiencing crashes with multi-GPU rigs, where we had some GPUs connected via splitters to the motherboard at 1x.
While tonemapping was originally on by default for all GPUs in V2, devices would freeze on V3 and cause the PC to crash when Post Processing was used. We were able to figure out the crashing occurred when the 1x cards were used, and if post Processing was used while using those cards.
But now with the ability to disable tonemapping per GPU, we can have the GPUs directly connected to the motherboard at 16x set with tonemapping enabled, and disabled for those GPUs connected at 1x. Thus, avoiding crashes.
So, in a nutshell, it doesn't add power, rather it is the default if on. It allows you to remove a 'problem' GPU from the Post Processing computation on V3.