OTOY Forums

this itoo problem is so bad I am not sure how to render anymore. I can isolate one itoo object lets say trees it will render it. Then unhide the whole scene and start rendering and i won't have trees anymore even though I made my reference geometry renderable. I can have cam 1 render trees and camera 2 will not.

and after rendering if you try to switch from direct to legacy mode it crashes max

Good to see I'm not the only one with itoo problems.

It seems that these new versions have major memory leak. After rendering it still uses 60 go if ram. When rendering another scene it I used all 128 gun of ram crashing pc


UPDATE
after each rendering QtWebEngineProcess eats all the RAM. Not sure why

Hi Paride,
1. It looks like texture emission ramp (color animation) is not updated during rendering.

[b]2. There is a very strange bug with large scenes and maybe related to itoo and phoenix. We started rendering the scene it took 40 sec to process geometry after 40 frames or so processing dropped to 7 seconds. It's again related to itoo and its reference mesh that now has to be renderable. I think it rebuilds it every frame

coilbook wrote:It seems that these new versions have major memory leak. After rendering it still uses 60 go if ram. When rendering another scene it I used all 128 gun of ram crashing pc


UPDATE
after each rendering QtWebEngineProcess eats all the RAM. Not sure why

qtwebengine?? sounds like a quicktime web engine hehe
i can't find that process here...

coilbook wrote:It seems that these new versions have major memory leak. After rendering it still uses 60 go if ram. When rendering another scene it I used all 128 gun of ram crashing pc


UPDATE
after each rendering QtWebEngineProcess eats all the RAM. Not sure why

Sorry i said something... but maybe you have a malware in your machine? i would give a try malware antimalware byte or something like that..
it has a free version.. always helped me.
good luck!

javierluisbravo wrote:

coilbook wrote:It seems that these new versions have major memory leak. After rendering it still uses 60 go if ram. When rendering another scene it I used all 128 gun of ram crashing pc


UPDATE
after each rendering QtWebEngineProcess eats all the RAM. Not sure why

Sorry i said something... but maybe you have a malware in your machine? i would give a try malware antimalware byte or something like that..
it has a free version.. always helped me.
good luck!

Thanks.
I checked 3ds max forum and it uses qt services. https://forums.autodesk.com/t5/3ds-max- ... -p/8996850
Webroot didn't detect any malware. I remember I never had this process in the past. Maybe new max update

Hi Paride,
for some reason every time we render the second time (different camera angle) or if we adjust emission ramp color when octane viewport is opened and then start rendering 3ds will crash. I will try to send the scene

It seems that anytime we try to do the second rendering we have cuda 700 illegal memory and max must be rebooted. Maybe ram/vram leak?

why is it not worth it by default?

coilbook wrote:Hi Paride,
1. It looks like texture emission ramp (color animation) is not updated during rendering.

[b]2. There is a very strange bug with large scenes and maybe related to itoo and phoenix. We started rendering the scene it took 40 sec to process geometry after 40 frames or so processing dropped to 7 seconds. It's again related to itoo and its reference mesh that now has to be renderable. I think it rebuilds it every frame

Hi coilbook,
check quick update mode, uypdate geometry, then will work.
Regards
Paride