System is running low on RAM with breakdown

[mamukaok]

Hi Guys,

I just want to get this error message with the breakdown of memory usage for geometry and textures and I can't figure it out why it doesn't show. I've seen on helpdesk that it is possible, here: https://coronarenderer.freshdesk.com/support/solutions/articles/12000023310-i-am-getting-a-sudden-rise-in-ram-usage-

[TomG]

What host software are you running (Max or C4D) and which version, which OS, and which version of Corona?

[mamukaok]

What host software are you running (Max or C4D) and which version, which OS, and which version of Corona?

Thanks for the answer! I'm using 3ds max 2020, Windows 10 and the latest corona

[TomG]

Latest could mean the latest Corona 6 Daily Build from March 16th, or latest final build, Corona 5 :) Not sure which one you mean.

[romullus]

Are you...

a) ...running low on RAM, but don't get low mem warning from Corona?
b) ...have enough RAM, but want to see the window with memory usage breakdown?

[mamukaok]

Latest could mean the latest Corona 6 Daily Build from March 16th, or latest final build, Corona 5 :) Not sure which one you mean.

Sorry, it's the version 5

[mamukaok]

Are you...

a) ...running low on RAM, but don't get low mem warning from Corona?
b) ...have enough RAM, but want to see the window with memory usage breakdown?

Yes I'm running low on RAM and I get the warning message but I don't get the details, I want to see which part of my scene takes most of the memory, textures or geometry

[TomG]

Also sorry, I could have seen it was version 5 in your first image :(

There is a known issue where the details are getting truncated, we have that logged and tracked, so we are looking into it. At the moment, I don't have any info on workarounds, or when the fix will be out, but we'll share anything along those lines as soon as we know.

[mamukaok]

Also sorry, I could have seen it was version 5 in your first image :(

There is a known issue where the details are getting truncated, we have that logged and tracked, so we are looking into it. At the moment, I don't have any info on workarounds, or when the fix will be out, but we'll share anything along those lines as soon as we know.

Thanks for the answer, Tom!

[rowmanns]

(Internal ID=487871457)