Page 1 of 1

CUDA Error, RTX, Out of Core. HELP! =)

Posted: Wed Aug 19, 2020 1:58 pm
by andrey.krivulya
Hello everyone and dear OTOY developers =)

Help me to fix this issue =) Because OTOY support doesn't want to fix it about 6 months =)) ahhaha.

So, the main thing - that I can render this dog with Redshift and V-ray without any problem. =) on my 2x2080Ti with NVlink.

Today I recorded a video to show this for Otoy Support -> https://www.youtube.com/watch?v=s7zgRqhrjZk

But I can't do this in Octane. Why?

Every time I have Cuda Error, or "Scene Evaluation..." or "Out of Core". 6 months spend for tests and etc and fighting with support =)

But as I know NVLink should work fine now in the latest OCtane. Right?

I want to do this with NVlink because I plan to create something new with fur and want to record a tutorial... But! 6-month guys, 6 months- I can't do this =)

1st video with this issue -> https://www.youtube.com/watch?v=va0upBR ... e=youtu.be

2nd video -> https://www.youtube.com/watch?v=CvKtZXX ... e=youtu.be

3rd video - https://www.youtube.com/watch?v=iHaqEdt ... e=youtu.be

Scene -> https://bit.ly/2XNBZRm

Sorry for V-Ray and Redshift video... This is just for motivation. I like all renders and as you know I create tutorials with each. And now I want to create something big with fur or hair in Octane... But still can't do this...

Is it possible to fix this? Or I should continue to fight with the Support team? =) ahhah.

Earlier V-Ray GPU can't render this dog... Yeah, this dog is a test scene for Nvlink =) Because it eats 11-16 GB VRAM

But after a good fight with ChaosGroup developers - I win =)) And now V-ray GPU can render this scene.

So let's fight with OTOY developers to make this possible in OCtane.

Octane should work with this scene. Do you agree with me?

Thank you and have a great day.

Best regards,
Andrew.

Re: CUDA Error, RTX, Out of Core. HELP! =)

Posted: Wed Aug 19, 2020 2:43 pm
by divasoft
+1

Re: CUDA Error, RTX, Out of Core. HELP! =)

Posted: Thu Aug 20, 2020 4:28 am
by andrey.krivulya
Facebook Topic - https://www.facebook.com/groups/OctaneR ... 026671902/

So, as I understand - the main problem now is the RAM issue and OTOY will fix this asap. Estimated release date - late summer-autumn. Thanks for Jules and Tom for the answers 8-)

Today I will check Tom's advice to increase the Virtual Ram on my SSD to 128 GB and then will check this issue on Maya too... Maybe this is 3ds max problem only...

If you have similar problems - do not hesitate, write about it.

Describe them in detail to help developers with a solution

Re: CUDA Error, RTX, Out of Core. HELP! =)

Posted: Thu Aug 20, 2020 8:28 am
by neonZorglub
andrey.krivulya wrote:Facebook Topic - https://www.facebook.com/groups/OctaneR ... 026671902/

So, as I understand - the main problem now is the RAM issue and OTOY will fix this asap. Estimated release date - late summer-autumn. Thanks for Jules and Tom for the answers 8-)

Today I will check Tom's advice to increase the Virtual Ram on my SSD to 128 GB and then will check this issue on Maya too... Maybe this is 3ds max problem only...

If you have similar problems - do not hesitate, write about it.

Describe them in detail to help developers with a solution
Hi andrey,
Thanks for your scene and explanations.
I had similar problem to render your scene.
One problem is the use of Ornatrix and the need to process hairs to be used by Octane. This takes some extra intermediate memory,
and the settings for your objects (non movable proxy) make it try to fit all polygons / hairs in a single big mesh..
Examining the Windows task manager, I could see that I reached 40+ GB, and it begins to swap memory to disk..
The solution for this scene is to set all objects as movable proxy (Octane object properties, select all, turn on Movable proxy)
That helps a lot to reduce the use of intermediate memory.
I could render your scene on my system (48 GB ram, 2 GTX 780 Ti, no RTX), and export the scene as an orbx file (1.8 GB)
I hope that helps
Best regards
2020-08-20 21_11_26-OctaneRender Viewport - Rendering.png

Re: CUDA Error, RTX, Out of Core. HELP! =)

Posted: Fri Aug 21, 2020 12:54 pm
by andrey.krivulya
neonZorglub wrote:
andrey.krivulya wrote:Facebook Topic - https://www.facebook.com/groups/OctaneR ... 026671902/

So, as I understand - the main problem now is the RAM issue and OTOY will fix this asap. Estimated release date - late summer-autumn. Thanks for Jules and Tom for the answers 8-)

Today I will check Tom's advice to increase the Virtual Ram on my SSD to 128 GB and then will check this issue on Maya too... Maybe this is 3ds max problem only...

If you have similar problems - do not hesitate, write about it.

Describe them in detail to help developers with a solution
Hi andrey,
Thanks for your scene and explanations.
I had similar problem to render your scene.
One problem is the use of Ornatrix and the need to process hairs to be used by Octane. This takes some extra intermediate memory,
and the settings for your objects (non movable proxy) make it try to fit all polygons / hairs in a single big mesh..
Examining the Windows task manager, I could see that I reached 40+ GB, and it begins to swap memory to disk..
The solution for this scene is to set all objects as movable proxy (Octane object properties, select all, turn on Movable proxy)
That helps a lot to reduce the use of intermediate memory.
I could render your scene on my system (48 GB ram, 2 GTX 780 Ti, no RTX), and export the scene as an orbx file (1.8 GB)
I hope that helps
Best regards
2020-08-20 21_11_26-OctaneRender Viewport - Rendering.png
Hi, @neonZorglub

I tried movable proxy and disabled RTX and NVLink. And YEAH! Now I see the dog in IPR, but it is so laggy... We should fix this too in the next build.

And yeah, when I turned on "Movable" proxy for the all objects - ORBX was exported without any error.

Then I tried to import this ORBX to the scene and render. =)

And YEAH! It working, but viewport still laggy without RTX and NVLINK.

Then I tried to turn on the RTX and NVLINK, and yeah! The viewport is very fast and NVLINK helped to work without "Out of Core". I disabled it in this scene and saw P2P - 4Gb. So, as I understand, this scene need 16GB VideoRam and NVLink helped in this case.

And 128 GB SSD Virtual Ram Helped me to render without OOC and CUDA Errors with RTX ON.

YEAH! Horray. Thank you for your help!

Video with laggy viewport without RTX and NVLINK and all my tests - https://www.youtube.com/watch?v=mzm_xWr ... e=youtu.be

ORBX file for tests -> https://bit.ly/2CS5j28

So, the solution in my case is:

1. Virtual memory on SSD - 128GB
2. Turn on "movable proxy" for all scene objects. (Octane object properties, select all, turn on Movable proxy)
3. Export to ORBx proxy and import it to the new scene
4. To speed up the viewport "RTX ON", NVLINK ON (peer to peer in Device settings)
5. Parallel samples = max, Max Samples = max.
6. Disable "Out of Core", because 2x2080Ti is enough for this scene (P2P - 4GB) =)
7. GPU HeadRoom - 1024MB

Done =)

Thank you and have a great day
Best regards,
Andrew.

Re: CUDA Error, RTX, Out of Core. HELP! =)

Posted: Fri Aug 21, 2020 1:13 pm
by andrey.krivulya
But sometimes, without ORBx in a main scene - IPR closed and I saw this:
octane_log.jpg

Re: CUDA Error, RTX, Out of Core. HELP! =)

Posted: Fri Aug 21, 2020 2:25 pm
by andrey.krivulya
Hi, dear OTOY developers

So, I tried to catch this issue and recorded a video. In the end, you will see it... Sometimes it happens when I change the resolution and sometimes - when I just rotate camera =) Sometimes when just start an IPR =)

Video with the issue -> https://www.youtube.com/watch?v=z7_X_kTdLcM

The scene for investigation -> https://bit.ly/31hDt8T

Thank you and have a great day

Best regards,
Andrew.

Re: CUDA Error, RTX, Out of Core. HELP! =)

Posted: Mon Aug 24, 2020 2:26 pm
by andrey.krivulya
Sorry, I forgot this =)

A. Win 10 2004
B. 2x2080Ti + NVLink
C. 64 GB
D. Latest Nvidia Studio 452.06
E. OctaneRender Standalone version 2020.1.4
F. OctaneRender plugin version (v2020.1.4 - 10.15)
G. 3ds max 2020

Thank you and have a great day.
Best regards,
Andrew.