Page 3 of 17

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 2:09 pm
by Cheiser
tim_grove wrote:
Cheiser wrote:Cant figure out how to make octane work with heavy scenes. For test i created a scene with a couple of highpoly models, 30m polys in my scene.
And octane keep crashing with a message "Try to decrease polygon counts". How should i work with heavy scenes, if octane cant handle 30m polygons?
GTX1070+1080 (8gb VRAM), 40gb RAM.

I want to use octane render, but i cant do any heavy scenes with it. I know, i should optimize my scene, use proxies etc. But im working with a team and often i have a bunch of locations done in 3dsmax. Octane cant handle it, always random crashing. I am forced to use another GPU render in this case. Any tips? What should i do, to make octane work with heavy scenes? Looks like my VRAM run out of memory, but why octane do not use my RAM? It's only 1,7-2gb.

Have you tried enabling out of core?
Out of core enabled, and i even increased it to 12gb. Info panel at post above says, 1.7gb out of core using

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 2:13 pm
by pxlntwrk
Hourray !!!!

Many thanks v4 c4d rocks, always a pleasure to work with :mrgreen:

We can read this on the blog https://home.otoy.com/octanerender-4/
"Native Substance PBR Texture Integration
OctaneRender 4 now provides Substance PBR texture integration in DCC tools such as C4D and 3ds Max."



how does this translate it at the c4d plugin side ?

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 2:21 pm
by Cheiser
Cheiser wrote:Cant figure out how to make octane work with heavy scenes. For test i created a scene with a couple of highpoly models, 30m polys in my scene.
And octane keep crashing with a message "Try to decrease polygon counts". How should i work with heavy scenes, if octane cant handle 30m polygons?
GTX1070+1080 (8gb VRAM), 40gb RAM.

I want to use octane render, but i cant do any heavy scenes with it. I know, i should optimize my scene, use proxies etc. But im working with a team and often i have a bunch of locations done in 3dsmax. Octane cant handle it, always random crashing. I am forced to use another GPU render in this case. Any tips? What should i do, to make octane work with heavy scenes? Looks like my VRAM run out of memory, but why octane do not use my RAM? It's only 1,7-2gb.
30m polys. Loaded scene ok. Can move around. Even can create HDR light.
But when i choose to create a new Octane material - LiveViewer stops. And if you try to refresh it, when octane Render Failure. Latest Nvidia drivers. Tested on my PC and my friends PC. I am using 8.1, my friend uses 10

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 4:19 pm
by lucioing
lucioing wrote:When I say: Ahmet the great, I'm right!
You've done a miracle, as always!
Thank you for your HARD work.

Now... If I understood correctly, there was a chance to perform a net render using a single license... isn't it?
Well... I think I've done all the steps to reach, finally, the net render:
1) install v4 to the Master (TheCube)
2) install v4 s.a. on the slave (TheTower)
3) run on the slave the daemon
4) then? what else?
Schermata 2018-11-22 alle 14.02.06.png
No one can help me? :cry: :roll: :(

L.

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 4:22 pm
by Hatsize7
I'm having the same problem as Cheiser. Frequent crashes (red Render Failure errors) when the live viewer is running and I try to work on the materials. Log says out of memory.
The scenes don't even have to be big (1M polys).

I followed GIOLETS' suggestion, changing the TDR parameters (viewtopic.php?f=30&t=69304). It helped, but out of memory render failures still occur, just not as often. VRAM is not full, as visible in live viewer. Out of core is enabled.

Any ideas?

I'm running Win7 (I know, I know, will change it soon) R16 with 3x Gtx1080s and 32Gb RAM.

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 4:53 pm
by aoktar
Hatsize7 wrote:I'm having the same problem as Cheiser. Frequent crashes (red Render Failure errors) when the live viewer is running and I try to work on the materials. Log says out of memory.
The scenes don't even have to be big (1M polys).

I followed GIOLETS' suggestion, changing the TDR parameters (viewtopic.php?f=30&t=69304). It helped, but out of memory render failures still occur, just not as often. VRAM is not full, as visible in live viewer. Out of core is enabled.

Any ideas?

I'm running Win7 (I know, I know, will change it soon) R16 with 3x Gtx1080s and 32Gb RAM.
Did you read and apply notes in first page? I cannot help if you don't give enough information.

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 6:18 pm
by Greggers
Hi guys,

Ive had to revert back to the last build 4-rc7-r4.
I had to fix a render I made yesterday using 4-rc7-r4 but this morning I upgraded to the new 4 stable release and I found with the new release octane was calculating much much slower. It was saying the time to render was 3x as long using the new 4 stable build. Cinema 4d was slowing down navigating and when opening the node editor it was lagging with my cursor. I could see the live viewer was taking a long time to render. I was using path tracing just like yesterday so no changes to my octane settings. Reverted back to4-rc7-r4 and Its back to normal speed and no lag when navigating.

I use a MacBook Pro with an egpu 980ti. CD4 R19.

I am fine with the rc7-r4 build for now but hope you guys can look into it or fix the issue in the next build. I hadn't change anything in my scene I just needed to re-render to fix an issue in my final image.

Hope all the information I gave you helps.

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 7:18 pm
by ChrisVis
BCres wrote:Followed the instructions for upgrading, but the upgrade page is suggesting I "Deactivate" my version 3 before proceeding.

Is this necessary? It wasn't mentioned in the first post.

I thought we could keep our version 3 as well. Thanks.

Looking forward to using it. Love version 4. The denoiser saved me on a spot I just did.

Thanks for this advice.
I just wanted to upgrade, too, because they also have a Black Friday discount for the "All Access Extension (1Year) for 179$. (instead of 238$ I think). Seems like a good deal.

For the licence ppgrade:
Can you or anybody confirm that it is still possible to work with version 3 after the upgrade to version 4?
I understand the procedure to deactivate V3 licence before upgrading, but is it possible to activate it again after upgrade to V4?

I really like to work with both, because I still have some old fermi gtx 590 cards working here, that do still a great job for small animation projects :).

Thanks for all the hard and continous work, Ahmet!! :) ;)

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 7:28 pm
by aoktar
Cheiser wrote: 30m polys. Loaded scene ok. Can move around. Even can create HDR light.
But when i choose to create a new Octane material - LiveViewer stops. And if you try to refresh it, when octane Render Failure. Latest Nvidia drivers. Tested on my PC and my friends PC. I am using 8.1, my friend uses 10
Could you test it without using monitor connected gpu? It's most likely a problem between opengl drivers and cuda.

Re: Cinema 4D version 4.00 (stable)

Posted: Thu Nov 22, 2018 7:46 pm
by screamerclauz
I'm still Cuda getting errors when rendering any scene using Out Of Core. I'm using 4x2080 ti and have tried every nvidia driver there is available, starting from the oldest to newest. Power supply is a brand new EVGA 1600 watt and 64 gb of DDR (with 32 for out of core enable with 1024 overhead) . I've tried a variety of different scenes, some only using a gig or so of out of core, some using more. Any scene not using out of core renders without issue

Errors codes include:

Failed to allocate page-locked memory
No device pointer for out-of-core memory 000001A5B3E7F060
No device pointer for out-of-core memory 000001A5B2E60060
No device pointer for out-of-core memory 000001A5B1E56060
CUDA error 2 on device 2: out of memory
-> failed to create link
device 2: failed to create OSL compile context:
device 2: failed to compile module 1

I also tried every TDR registry trick suggested, starting with delay at 20 all the way up to 60. Anything else to try?