OTOY Forums

SergKlyosov wrote:

paride4331 wrote:
Hi SergKlyosov,
do wheels disappear or they seem like clipped?
Regards
Paride

Completely disappear in the rendering viewport
Sometimes when I press the render - they are visible, but after 20-50 samples they are disappearing
Sometimes they are not visible since beginning of the rendering

thanks,
did you try using 3.08x? Same issue?
Regards
Paride

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

Hi, Paride, if this test is for scene evaluation speed; waiting 2mn in front of a "black screen", hoping nothing crash when you are in a hurry is very very long....

I asked about the insanely slow collecting nodes phase numerous times. Good luck trying to find an answer. Anything more than a product render in 3ds Max/Octane is currently useless.

What are guys complaining for? I usually wait 10-15min evaluation time with 3.07, sometimes only to see a render failed. Ranging from 16 - 44 million polies per scene with forest packs and all such objects.
Tried FStorm and had around 2min for same scene...but without proper scene setup to be honest.


I will bite my way through the next time mattering projects the next months and then see if I switch render engine to another. Maybe FStorm or Vray Next...depends on how good I can convert my model library. Really fed up how development goes. The overbright scene error just killed my patience and answer from support "life with it". And I use Octane since 6 or 8 years now and consider myself a long time user.

mbetke wrote:What are guys complaining for? I usually wait 10-15min evaluation time with 3.07, sometimes only to see a render failed. Ranging from 16 - 44 million polies per scene with forest packs and all such objects.
Tried FStorm and had around 2min for same scene...but without proper scene setup to be honest.


I will bite my way through the next time mattering projects the next months and then see if I switch render engine to another. Maybe FStorm or Vray Next...depends on how good I can convert my model library. Really fed up how development goes. The overbright scene error just killed my patience and answer from support "life with it". And I use Octane since 6 or 8 years now and consider myself a long time user.

Hi mbetke,
I think my test is very good; don't forget my 15.800.000 polys are not instanced
15.800.000 polys > GPU mem 3.85 GB
4554 objs
time to voxel > 1:45 min.

why not update OctaneRender® for 3ds max® v3.08.2 - 5.13?
overbright scene error using from 3.07x to 3.08x?

Regards
Paride

HHbomb wrote:Hi, Paride, if this test is for scene evaluation speed; waiting 2mn in front of a "black screen", hoping nothing crash when you are in a hurry is very very long....

HHbomb,
if your scene exceeds Vram size available then it is obvious to crash.
bearing in mind that 1 GB Vram = +/- 5700000 Polys
Regards
Paride

paride4331 wrote:
HHbomb,
if your scene exceeds Vram size available then it is obvious to crash.
bearing in mind that 1 GB Vram = +/- 5700000 Polys
Regards
Paride

Hi Paride

Since Octane 4 was announced to the world - Jules said that we won't suffer from VRAM limitation anymore due to Out of Core feature. And speed reduction using this feature will be so little, about 20% less
And with latest XB4 SA we see sentence which claims that we even don't need to change out of core settings - Octane will automatically sett all properties and work fine

So if we were promised to have instant realtime evaluation and using billions of polygons in our scenes - why are issues described above still happening?

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

verbright scene error using from 3.07x to 3.08x?

Yes and the evaluation time is killing me here.
Its not just simple adjusting a slider with the overbright scene. I have to tune it again from ground on.