Page 4 of 9
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Thu Feb 28, 2019 6:50 am
by mbetke
I still have the problem with crashing scenes when I batch render files. Its a bit of random appearance. They work fine when I use the Viewport but crash when I click render button.
Sometimes I open up 3dsmax whit a click in file explorer and they crash during load.
It may related to 3dmax but also to Octane. I'm a bit confused and researched but was not abel to nail it down.
Is it possible to sent you the 3dsmax_minidump.dmp files for evaluation? I know the Vray and itoo guys can analyse them and tell where the error comes from.
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Thu Feb 28, 2019 7:52 am
by paride4331
Hi mbetke,
send me .dmp in PM, I will send it to developers.
Regards
Paride
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Thu Feb 28, 2019 8:01 am
by paride4331
coilbook wrote:Hi Pairde,
Could you give an advice on HDR Sky. In RC7 version I never had this problem with the Sun being too bright
Thanks
Hi coilbook,
I will try comparing RC7 and 3.07.
Regards
Paride
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Thu Feb 28, 2019 4:56 pm
by coilbook
Ok
After some tests 3ds max slowdown is definitely related to octane. Something to do with octane viewport (opening /closing), textures (working with textures, converting them) and working with mesh (changing element ids, etc) and eventually it slows down. Please see the video.
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Thu Feb 28, 2019 7:28 pm
by senorpablo
coilbook wrote:Ok
After some tests 3ds max slowdown is definitely related to octane. Something to do with octane viewport (opening /closing), textures (working with textures, converting them) and working with mesh (changing element ids, etc) and eventually it slows down. Please see the video.
I second this. It's absolutely caused by Octane. I've never had an issue with Max slowing down like this prior to using Octane, or when I use scanline render.
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Fri Mar 01, 2019 6:37 am
by mbetke
Looking the same here like in Coilbooks video.
I noticed things get faster when using editable mesh instead of editable poly. But this applies not to the material editors slowdowns.
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Fri Mar 01, 2019 9:55 am
by nick73
Hello,
my 2018.1-RC1 - 7.01 studio - all access has expired two days ago and asking for a newer version, but there is no one available in downloads page. Please make this one available for subscription or allow keep using 7.01. Thank you.
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Fri Mar 01, 2019 10:18 am
by paride4331
nick73 wrote:Hello,
my 2018.1-RC1 - 7.01 studio - all access has expired two days ago and asking for a newer version, but there is no one available in downloads page. Please make this one available for subscription or allow keep using 7.01. Thank you.
Hi nick73,
you can find it here:
https://render.otoy.com/account/downloa ... oduct_id=1
Regards
Paride
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Fri Mar 01, 2019 1:06 pm
by Rik
Not had this before....
I have 3 1080s, 8gb each. I understand that gives me 8gb vram total.
Octane has been crashing when building scene.
In the render statistics the GPU Mem figure gives a total available as 19.3GB
This is whacky as the cards are only 8gb.
Plus, using 1 card and the render works, gpu usage stat is around 3gb/19.3
using 2 cards doubles the gpu usage
using 3 cards triples the gpu usage
so I think I'm running out of vram as a result.
Why is the gpu usage going up with each extra card?
Why is it saying the total available is around 20gb? (should be around 6-7gb)
Using max14, octane 4.02 - 6.13, nvidia driver 388.13.
'use CPU memory' is not ticked.
Happens in even a fresh scene and after restarting max
Re: OctaneRender® for 3ds max® v2018.1-RC4 - 7.03 [TEST]
Posted: Fri Mar 01, 2019 1:53 pm
by paride4331
Hi Rik,
there is a VRam counter issue, it will be fixed asap.
Said that, the amount of RAM available to OctaneRender is not equal to the sum of the RAM on the existing number of GPUs, but it is restricted to the GPU with the smallest amount of RAM. It is recommended that you disable GPUs that don’t have enough RAM to allow for rendering large scenes that can fit in the RAM of the remaining GPU.
Using Octane 4.02.1 6.14 you could update to latest Nvidia driver 419.17
Using GTX 1080 and windows 10, VRam available is 6.5 GB.
you should fix your crashes activating cpu memory option .
Regards
Paride