Octane v3 won't render scene that was fine in 2.25

[3dmikee]

Was wondering if anyone could help. This issue maybe because the Poser plugin could still be in beta and the issue may get fixed but it could be something that I'm doing incorrect.

When I upgraded Windows 7 to Windows 10, a scene I was working on fine in Windows 7 would no longer render, the viewport would open after loading the scene and nothing would happen. By turning on out of core textures this work around did the job but was still a bit annoying having to miss out on 1GB of RAM for my card. I upgraded to Octane 3 to see if this issue was fixed but when I open the scene I was working on in 2,25 the viewport is blank and nothing renders. Out of Core textures is on and says it's being used and it also says I have free memory on my card. If I start a new scene it will render fine. I'm using the latest Nvida drivers 368.22.

I'm using the Poser Plugin version 3.0.12.72

If I need to roll back do I need to roll back the Standalone as well as the Plugin?

Thanks

Mike

[face_off]

Are you on Poser10? If so, try Nvidia driver 358.50. See the link in my signature for details.

Paul

[3dmikee]

Thanks for replying, I'm using Poser Pro 2014 Game Dev.

I was running the previous nvidia drivers before 368.22 and that failed so updated them last night hoping they would work but still no joy.

Do I need to roll back to 358.80 as its quite a few versions previous.

[face_off]

Yes, you need Nvidia driver version 358.50.

Paul

[3dmikee]

Will try and Roll back the Nivida drivers.

Just a quick mention, when I start new scene in poser or open a substantially less heavy scene it will render with the current drivers I've installed, is there an issue with the latest drivers and fairly heavy scenes?

Thanks for your help

[3dmikee]

Just did a test with the scene I'm having issues with, it has four characters in total. I deleted three of them and it now renders that's using the 368.22 drivers. It doesn't solve the problem as I need all the characters but leads me to think that it may not be the Nvidia drivers. Are there any new settings in the Version 3 that effect how it renders?

Thanks again

[face_off]

What does the Octane log show when you have the error rendering the scene?

Paul

[3dmikee]

Thanks for getting back to me. Due to deadline I had to roll back to 2.25 which works fine. I will try to reinstall 3 and later on and get the log report.

Cheers

Mike

[Zay]

First of all Octane 3 uses more Vram than Octane 2.25.
Second - you have installed Windows 10 which eats a part of your Vram and therefor you have less available Vram for rendering on windows 10. Windows 7 doesn't have that problem.
viewtopic.php?f=12&t=51992

In your Kernel you can try to set Parallel Samples and Max Tile Samples to 1. It will slow down the rendering speed but free up Vram.

You can also free up more Vram by turning down Preview textures to 128. In big scenes this can really free up some Vram.

[3dmikee]

First of all Octane 3 uses more Vram than Octane 2.25.
Second - you have installed Windows 10 which eats a part of your Vram and therefor you have less available Vram for rendering on windows 10. Windows 7 doesn't have that problem.
viewtopic.php?f=12&t=51992

In your Kernel you can try to set Parallel Samples and Max Tile Samples to 1. It will slow down the rendering speed but free up Vram.

maxsamples.JPG

You can also free up more Vram by turning down Preview textures to 128. In big scenes this can really free up some Vram.

textureres.JPG

Thanks for this information, I was aware of the Windows 10 issue with eating up the VRAM, with the out of core textures on this was worked around but still annoying. I can imagine Octane 3 would use more VRAM but surely with the out of core textures and it telling me I have memory available it would still try and render. I did try reducing parallel samples to 4 from 8 but will try reducing it to 1, but if this makes it a lot slower seems no point to update yet to v3. Didn't know about the previews textures will give this try as it's a very useful tip.

Thanks again for your help.