Page 1 of 1

3ds max 2019 CPU memory not shown

PostPosted: Mon Oct 08, 2018 11:50 am
by jan kudelasek
Hi,
I´m working with very huge scene, I enabled CPU memmory 16G, but CPU memory is not shown in render statistic like in other projects.
So I´m not sure if CPU memory is running. Any toughts?

3ds max 2019
3.08.03
42 mil polys

Thank you
Jan

Re: 3ds max 2019 CPU memory not shown

PostPosted: Mon Oct 08, 2018 1:55 pm
by paride4331
Hi jan kudelasek,
Octane 3.08.x CPU mem works only with textures, not geometry.
Octane 4.0.x CPU mem works automatically when needed (textures + geometry).
If it is working you can check this as in the screenshot.
Regards
Paride

Re: 3ds max 2019 CPU memory not shown

PostPosted: Mon Oct 08, 2018 5:40 pm
by jan kudelasek
paride4331 wrote:Hi jan kudelasek,
Octane 3.08.x CPU mem works only with textures, not geometry.
Octane 4.0.x CPU mem works automatically when needed (textures + geometry).
If it is working you can check this as in the screenshot.
Regards
Paride

Hi Paride,
thank you for reply, but I have a lot of textures in the scene as well. Everytime I can see tag in render statistic but not now. I reach maximum of my GPU ram, bt CPU still not working. Why?

Jan

Re: 3ds max 2019 CPU memory not shown

PostPosted: Wed Oct 10, 2018 6:24 am
by paride4331
Hi jan kudelasek,
I made many tests yesterday, Octane V3.08.03 cpu memory option does not work.
I sent reports to developers they fixed it and will be in the next release V3.08.x.
Thanks for your report.
Regards
Paride

Re: 3ds max 2019 CPU memory not shown

PostPosted: Wed Oct 17, 2018 9:14 am
by jan kudelasek
Hi Paride,
thank you too. 3.08.02 is ok with CPU memory?
Jan

Re: 3ds max 2019 CPU memory not shown

PostPosted: Wed Oct 17, 2018 12:24 pm
by paride4331
Hi jan kudelasek,
it would seem so, not sure using 5.13
Regards
Paride

Re: 3ds max 2019 CPU memory not shown

PostPosted: Thu Oct 25, 2018 8:35 am
by jan kudelasek
Hi Paride,
sorry, but what is the answer? Who else should know if one of the most important functions works? At a minimum, you should inform the user, or not keep this version stable. I got into trouble with the client. I can accept some minor bugs, but not the malfunction of one of the most important features. Why do not you try these features before you designate it as stable? I am really annoyed by your company, because your actions are not fairplay. Absolutely cough on users who use octane on arch visualizations. According to my CPU tests, the memory last worked in version 3.08-5.08. I expect you will test and evaluate the situation and also notify the user about this and correct the error as soon as possible. Full Version 3.08. + is a big problem for big scenes! :cry:

Jan