Problem description
The scale of our project requires us to have granular control over the object images that are loaded into memory. For sprites, the "Unload unused images from memory" action is extremely useful for this purpose. However this action does not seem to affect the images used by the Model3D plugin.
I appreciate that this could be a bug, or it could just be a feature request (depending on dev intentions). All I can say is that this feature would be incredibly useful for us in terms of optimisation and stability, especially on mobile devices where VRAM is limited.
Related to this report is my suggestion for a memory management script interface (Scirra/Construct-feature-requests#777) which would make the existing event sheet memory management actions accessible from scripts.
Attach a .c3p
Repro.c3p.zip
Steps to reproduce
- Run the project and observe how the VRAM usage changes (or rather doesn't) as models are changed and destroyed.
Observed result
The models change, are destroyed, and images are cleared, but this has no impact on VRAM usage.
Expected result
The VRAM reduces after models are destroyed and unused images are cleared.
Problem description
The scale of our project requires us to have granular control over the object images that are loaded into memory. For sprites, the "Unload unused images from memory" action is extremely useful for this purpose. However this action does not seem to affect the images used by the Model3D plugin.
I appreciate that this could be a bug, or it could just be a feature request (depending on dev intentions). All I can say is that this feature would be incredibly useful for us in terms of optimisation and stability, especially on mobile devices where VRAM is limited.
Related to this report is my suggestion for a memory management script interface (Scirra/Construct-feature-requests#777) which would make the existing event sheet memory management actions accessible from scripts.
Attach a .c3p
Repro.c3p.zip
Steps to reproduce
Observed result
The models change, are destroyed, and images are cleared, but this has no impact on VRAM usage.
Expected result
The VRAM reduces after models are destroyed and unused images are cleared.