Memory Consumption - Load/Unload scene

This topic has 3 replies, 2 voices, and was last updated 6 months, 3 weeks ago by kdv.

Viewing 4 posts - 1 through 4 (of 4 total)

Author

Posts
2024-05-29 at 11:51 am #74429

David Duperron
Customer

Hi,
I’ve searched quite a bit in the forums, but I cannot get a clear answer to this question:
does the “Unload Scene” puzzle free the system memory from all the unloaded scene data (meshes, materials, buffers, etc…)
In other words: is it a good solution to keep better performances when dealing with large models that have some parts that can be used (shown) or not? I mean better than just showing/hiding these elements from the main scene?
Thanks for the clarification! :)

Cheers

David

2024-05-29 at 7:03 pm #74430

kdv
Participant

Use Windows Task manager or MSI Afterburner (preferred) to monitor memory consumption (RAM/Video) and you’ll get an exact answer.

Puzzles and JS coding. Fast and expensive.

If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

2024-05-31 at 9:45 am #74458

David Duperron
Customer

Thanks, I tried on the “load/unload scene” example app, but I can see no difference in the memory consumption… So it’s still unclear to me what this puzzle does exactly in terms of memory.

2024-05-31 at 10:01 am #74461

kdv
Participant

David Duperron wrote:

what this puzzle does exactly in terms of memory

nothing.

Puzzles and JS coding. Fast and expensive.

If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.
Author

Posts