OTOY Forums

coilbook wrote:Hi Paride,
were you to reproduce stuck on evaluation/slow eval. When we have a lot of cloned cars as instance octane stuck on eval

it seems that it evaluates 3ds max instances like copies very slow. It now eventuates as slow as octane 3 again

I have 10 unique cars total poly count is 2 mil. If I clone then 50 times as INSTANCE it wont even render. stuck on processing even thought these are instances

I attached another video. I just don't understand why 3ds max copied instances are so slow. Itoo forest with thousands of instances loads in seconds. This is in both rc6 and rc7. I though some versions started to speed up geometry processing now it is back to slower than v3
And as I mentioned earlier the scene only uses 0.9 GB

UPDATE:
Ok I did some previous versions tests. So it takes RC6 and RC7 3 min 14 sec to open 50 instances (1GB vram)

RC4 takes only 1 min 50 seconds to open 50 instances (1GB vram). Still very slow for just 1 Gb of vram but newer version got even worse. This is far from what they said 20mil polys in under 5 seconds. Please otoy fix it. Denoiser won't matter if I spend 2 min per frame just processing geometry. I am not sure what to even think about real time brigade rendering anymore

Thanks

ramone163 wrote:When I save scene during render, render reset.
Check my video:

neonZorglub wrote:

coilbook wrote:Hi Paride,
were you to reproduce stuck on evaluation/slow eval. When we have a lot of cloned cars as instance octane stuck on eval

it seems that it evaluates 3ds max instances like copies very slow. It now eventuates as slow as octane 3 again

I have 10 unique cars total poly count is 2 mil. If I clone then 50 times as INSTANCE it wont even render. stuck on processing even thought these are instances

I attached another video. I just don't understand why 3ds max copied instances are so slow. Itoo forest with thousands of instances loads in seconds. This is in both rc6 and rc7. I though some versions started to speed up geometry processing now it is back to slower than v3
And as I mentioned earlier the scene only uses 0.9 GB

UPDATE:
Ok I did some previous versions tests. So it takes RC6 and RC7 3 min 14 sec to open 50 instances (1GB vram)

RC4 takes only 1 min 50 seconds to open 50 instances (1GB vram). Still very slow for just 1 Gb of vram but newer version got even worse. This is far from what they said 20mil polys in under 5 seconds. Please otoy fix it. Denoiser won't matter if I spend 2 min per frame just processing geometry. I am not sure what to even think about real time brigade rendering anymore

Thanks

Hi coilbook,
The solution for your scene is to use cloning objects as Instances, and set all objects as Movable proxy. That would avoid to the slow re-load of each object, and duplication of geometry in memory..
Opening 50 instances took me ~3.5 sec with this setting.
Currently, the use of Octane Proxy (octprx file) require a load from disk if it's set as static geometry, even if it is an instance.
We'll look into optimizing this case soon.
Thanks

ramone163 wrote:When I save scene during render, render reset.
Check my video:

coilbook wrote:

neonZorglub wrote:

coilbook wrote:Hi Paride,
were you to reproduce stuck on evaluation/slow eval. When we have a lot of cloned cars as instance octane stuck on eval

it seems that it evaluates 3ds max instances like copies very slow. It now eventuates as slow as octane 3 again

I have 10 unique cars total poly count is 2 mil. If I clone then 50 times as INSTANCE it wont even render. stuck on processing even thought these are instances

I attached another video. I just don't understand why 3ds max copied instances are so slow. Itoo forest with thousands of instances loads in seconds. This is in both rc6 and rc7. I though some versions started to speed up geometry processing now it is back to slower than v3
And as I mentioned earlier the scene only uses 0.9 GB

UPDATE:
Ok I did some previous versions tests. So it takes RC6 and RC7 3 min 14 sec to open 50 instances (1GB vram)

RC4 takes only 1 min 50 seconds to open 50 instances (1GB vram). Still very slow for just 1 Gb of vram but newer version got even worse. This is far from what they said 20mil polys in under 5 seconds. Please otoy fix it. Denoiser won't matter if I spend 2 min per frame just processing geometry. I am not sure what to even think about real time brigade rendering anymore

Thanks

Hi coilbook,
The solution for your scene is to use cloning objects as Instances, and set all objects as Movable proxy. That would avoid to the slow re-load of each object, and duplication of geometry in memory..
Opening 50 instances took me ~3.5 sec with this setting.
Currently, the use of Octane Proxy (octprx file) require a load from disk if it's set as static geometry, even if it is an instance.
We'll look into optimizing this case soon.
Thanks

Yes I did. All these numbers you see are cloned objects with movable proxy on. There is a bug since rc4 does it faster than rc6 and rc7. But even Rc4 is slow 1 min 50 sec for 0.9 gb of mesh to load
I attached the scene. There are 12 unique cars. They scene loads in 5 seconds. IF I clone it 50 times as instance it loads in 3 min and 40 seconds That's a 1gb vram scene. Same amount of vram is used. This is a bug. I never had this problem in octane 3 with cloned mesh.

I am sorry but it is getting annoying. So many beta versions came out and RCs and still slow eval times with cloned mesh. Please fix it once and for all.

Thanks

paride4331 wrote:

ramone163 wrote:When I save scene during render, render reset.
Check my video:

Hi ramone163,
you should deactivates "use same scatter node for compatible istances" in Octane global preference > Trouble shooting.
Regards
Paride

ramone163 wrote:

paride4331 wrote:

ramone163 wrote:When I save scene during render, render reset.
Check my video:

Hi ramone163,
you should deactivates "use same scatter node for compatible istances" in Octane global preference > Trouble shooting.
Regards
Paride

Thx Paride.
But where is logic? How "use same scatter node for compatible instances" = "Save"?
And if I deactivate it, will I lose better performance for instance object?

ramone163 wrote:
Confirm.
My time is:
Standalone RC7 - loads in 5 seconds
3ds Max 2019 RC7 - loads in 6 MINUTES!
3ds Max 2017 3.07-4.43 - loads in 7 second (and viewport performance much better than RC7)

And if I rotate some object, I see a duplicate.