OctaneRender® for 3ds max® v4.00-XB4 - 6.04 [OBSOLETE] Tweet

[matthewcastiglia]

Hi guys,
I tested xb4 making a stress test:
win10
1 x Gtx1070
i7 16GB

TEST A)
15.800.000 polys > GPU mem 3.85 GB
4554 objs
time to voxel > 1:45 min.

I did a pc hardware limit deadly TEST B)
26.430.000 polys > GPU mem 6.3 GB
7587 objs
time to voxel > 6 min.
after render was started, GPU failed, it's logically enough.

that sounds good, what do you think?
Regards
Paride

My issues has nothing to do with poly count, it is purely object count. Octane in 3ds Max collects nodes at about 20 object per second. That is why your test scene of 7587 objects is taking over six minutes. It should not take longer to collect nodes than it is to complete the render itself. If it does, the code needs to be optimized. Redshift, Arnold, Fstorm all finish "collecting nodes" within seconds with the same object count.

The other issue is that amount of times scene evaluation crashes during these high object count scenes.

[coilbook]

Hi guys,
I tested xb4 making a stress test:
win10
1 x Gtx1070
i7 16GB

TEST A)
15.800.000 polys > GPU mem 3.85 GB
4554 objs
time to voxel > 1:45 min.

I did a pc hardware limit deadly TEST B)
26.430.000 polys > GPU mem 6.3 GB
7587 objs
time to voxel > 6 min.
after render was started, GPU failed, it's logically enough.

that sounds good, what do you think?
Regards
Paride

i thought otoy promised us almost real time and no more processing time

[HHbomb]

@matthewcastiglia
yes, 5500 simple boxes take 2mn23 at 8% CPU (i have 12 cores)... to be processed. 33000 polys....

[paride4331]

Hi Guys,
I think it is necessary to clarify:
1 Octane v4 is experimental version, not stable, it makes no sense to speak as if this version is stable.
2 my test is done using GPU, not out-of-core.
3 Crashes over 26.000.0000 polys are a consequence with 16 GB Ram on board, and 3dsMax is notoriously a Ram eater.
4 Octane for 3dsMax XB4 was released unfinished because XB3 licenses were discontinued.
5 "Octane will automatically sett all properties and work fine".. > it means automatic memory distribution between textures and geometries.
6 What Jule says is true, Octane V4 will work as he says:
Same test I did but using SA XB4
> 15.800.000 polys > GPU mem 3.85 GB 4554 objs time to voxel > 20 secs.
> 15.800.000 polys > full out-of-core 4554 objs time to voxel > 24 secs.
When Octane V4 will be released, I think there won't be much more for any of render engines.
Said That I will send my test to developers, to get closer to the SA performance.
Regards
Paride

[matthewcastiglia]

@matthewcastiglia
yes, 5500 simple boxes take 2mn23 at 8% CPU (i have 12 cores)... to be processed. 33000 polys....

Yep - insane. This is a 3.08 issue as well. Let alone V4

[HHbomb]

@matthewcastiglia and Paride, yes in fact it is same in 3.08, but as next version is V4.... and I'm "sure" it will not be fixed in 3.xxxxx

[paride4331]

quick question. Does the denoiser work well on out of focus areas?

Hi darkline,
yes it is, but blurred depth of field requires more samples.
Regards
Paride

[HHbomb]

Hi,
in XB4 6.04, is "Min. denoiser samples" work ? I can change value, octane begin denoising at different values.

- if I set 50, octane begin to denoise when I see Smp/px 1024/1024/16000 ( because render is very fast )
- if I set 50, and then set Max denoiser interval to 1s it begin to denoise at 112 Smp/px, but then octane denoise at each 1s...

Need a fix ?

[RobSteady]

> 15.800.000 polys > GPU mem 3.85 GB 4554 objs time to voxel > 20 secs.
When Octane V4 will be released, I think there won't be much more for any of render engines.

Meanwhile the competition stays lightyears ahead. This is “another gpu renderer“ on the market:

[HHbomb]

Hi, I tested my 5500 boxes in "another GPU renderer" : < 5 secondes to process.....