Version 3.07-R2 (previous stable) update on 01.11.2017 Tweet

[DanielPaul]

After installing 3.07 R2 on every machine, we noticed much lower fps in our 3D applications while rendering with octane slave daemons.

We set our octane slaves to use only 2x 1080 TI, 1x titan x is for viewport exclusive (alsomost no usage maybe 1-5% but still laggy).
3.06 does not have this problem.

Any suggestions? Thx

[bepeg4d]

Hi DanielPaul,
which Nvidia drivers have you installed in the Slave?
ciao beppe

[DanielPaul]

Hi beppe

we are on 388.31 (win 10 64 Bit)

[bepeg4d]

Hi DanielPaul,
do you mind to try to roll back to 383.13, or even 382.33 with a clean installation?
ciao beppe

[DanielPaul]

Hey beppe,

thx for the tip. Im unable to install 382 because win installs 384.94 directly after reboot.
But with this version it works fine, buttery smooth feedback in all viewports while rendering.

cheers
Daniel

[BCres]

Daniel,

It may be this selection in your system properties under the Hardware tab. It's windows 10 way of always updating drivers. If you know how to do this...turn it off (as shown) before you test the older driver.

That should keep windows from going back to the newer driver.

[VVG]

Gone?

[divasoft]

Gone?

No strength to endure all these bugs. So I moved to RedShift.

[aoktar]

Gone?

Yes gone! I've removed this parameter. Thanks!

[VVG]

Gone?

No strength to endure all these bugs. So I moved to RedShift.

I started to study redshift and cycles4d in parallel because the development of octane for the last six months is simply awful.

it's sad to say.