Version 3.06-TEST4.1 (WORK IN PROGRESS BUILDS) Tweet

[bepeg4d]

Hi Tag12345,
sorry, but I guess that you are hitting the limit, 39 millions poly are roughly 79 millions triangles, and are roughly 8.5 GB only for geometry. You don't even have enough VRAM to render it.
ciao beppe

[Tag12345]

Man that sucks :/


Guess ill probably need a titan

[Tag12345]

Whens the next update?

[Tag12345]

UPDATE: more on Memory failure, etc.


Is there no way around this for larger scenes?

Polys & objects



LOG:




anyway to reduce the amount of polys or get rendering to work with 2x GTX 1080's (Not SLI)


Any help or advise would be great!!!



Settings: Not using multicore. Not sure if I should as it completely crashes when I do. Itll get more into rendering though but wont complete the render.

[aoktar]

Whens the next update?

Do you mean this release?
viewtopic.php?f=85&t=60816

[bepeg4d]

Hi Tag12345,
please, try by setting the Parallel sampling at 1 in the kernel settings, and by enabling the Out-of -core option.
ciao beppe

[Tag12345]

Hi,

What does parralel samples do exactly?

And I actually fixed the issue by cutting my geometry from 20+ mil triangles to 8mil



I'm on a time limit sorta. But I feel that knowing that octane has these limits feels discouraging as buying a titan or quarto would be the only things for the vram and at that price point AMD will have their 16core processors soon for under 1K

So it really begs the question of when will octane start to improve with more features and much better/Performance and optimization.

Because honestly even the use of fog -- or material based systems to add layers to objects when u have multiple objects etc, just seems very inefficient ATM.

Granted, I bought octane as a user who saw it for its speed- materials- & IPR

But I'm hoping we get that OSL update soon...we've been promised it every since 3.0 launch and its never came -- that being like 6 months ago ; . ;