OTOY Forums

again, got a freeze/crash while browsing to zdepth on octane viewport.. while lock resolution turned on

- also running into some strange instability issues, everything runs stable and then I just copy paste all the objects in the scene, and the 3dmax viewport freezes, sort of runs as I can save, and after a minute or two crash..
- no idea what could be causing this, anyone else has this?

Hi acc24ex,
thanks for reported. I could not find issue with z-depth, but I'll try again.
I will check other issues also, just finished checking other issue.
Regards
Paride

What wrong with render instances?
I have to wait 1 minut to see the image:
https://dl.dropboxusercontent.com/s/a2y ... 164711.gif

(fstorm and corona show it after 1 sec).

In standalone I dont have this problem also. Only in 3ds Max 2016 and 2014.
I also tried older versions from 4.10 to 4.23.

Update: Bug only with OctaneRender Viewport. When i hit F9 (standart render) it render without delay.

ramone163 wrote:What wrong with render instances?
I have to wait 1 minut to see the image:
https://dl.dropboxusercontent.com/s/a2y ... 164711.gif

(fstorm and corona show it after 1 sec).

In standalone I dont have this problem also. Only in 3ds Max 2016 and 2014.
I also tried older versions from 4.10 to 4.23.

Update: Bug only with OctaneRender Viewport. When i hit F9 (standart render) it render without delay.

same here OCtane viewport opens very very slow with lots of instances but also when it renders we have to wait 1 minute every frame just to load the scene every frame (viewtopic.php?f=24&t=57474)

paride4331 wrote:Hi acc24ex,
thanks for reported. I could not find issue with z-depth, but I'll try again.
I will check other issues also, just finished checking other issue.
Regards
Paride

- yup, confirmed, opened a empty screen, works ok, then clicked lock resolution - while on zdepth, crash
- also I have the conversion system activated (still a lot of old projects to convert so it's always on)
max2017, win10, gtx980ti

- exact same crash on other computer win7 980gtx

so it only crashes while lock resolution activated

@ramone163
Hi ramone163,
The movable proxy command is not command corresponding to vray proxy, corona proxy or fstorm proxy.
If you wanted to use octane proxy, please refer to: Exports Octane proxy (screeshot)
The movable proxy allows you to edit objects etc, without refresh the octane view.
Activate indiscriminately all of movable proxy in the scene is no sense, except to slow down performance and render time.
About the speed difference between SA and Octane Render Octane 3dsmax plugin: 3dsmax eats RAM and Octane too.
Octane SA is essential and it does not weigh on the Ram as 3dsMax, so it is faster.
Regards
Paride

Hi Paride.
From the beginning "movable proxy" is a manner to save memory for rendering too : mesh is loaded one time for all instances, and so, there is less time to evaluate. (dixit Karba)
Evaluation time is now very slow, and this is dramatic...

I waited for 20 minutes, the scene that renders 20 seconds
That's why I advise mu developers install an older version 2.25, check the speed, now in 3.0 we got the old lady)

I wouldnt noticed it if you guys didn mention it. it s very bery slow. Didnt have time to go back to 2.5

I was thinking generally I have large scenes some railclone some forest but. Not that ultra much.. But the render takes tooooo much time to start..
I agree. Devs should check this...

Hi Paride.
From the beginning "movable proxy" is a manner to save memory for rendering too : mesh is loaded one time for all instances, and so, there is less time to evaluate. (dixit Karba)
Evaluation time is now very slow, and this is dramatic...

Agreed on that, instancing is useless without checking movable proxy ...