Managing VRAM while using multiple POPs scenes - Disabling Cooking

POPs
1

Hello colleagues, I’m preparing for a 2 hour show, meaning I have a lot of scenes to manage.

I have run into an issue, where my VRAM gets full due to using mostly POP networks inside my scenes. The methods that I had been using, or have read about don’t really help me here:

I understand that TouchDesigner is generally a pull-system and managing scenes using sceneChanger or other custom systems ensure that the scenes not displaying are also not cooking, resulting in smooth FPS. But the problem is an oversaturated VRAM.
**
I can successfully manage VRAM only by disabling cooking on the unused scenes, and enabling them while displaying. But this naturally leads to frame drops.**

I feel like this isn’t really a perfect way to go about managing multiple POP scenes and am interested if there is something really obvious that I’m missing, or if there are some better practices out there.

Thanks,

Mariam

2

Do you know about this new function: **COMP.progressiveUnload(totalFrames=None, timePerFrame=None, nodesPerFrame=None, gpuMemPerFrame=None, opsToExclude=None)**→ None:

This frees memory of a component, over the time of several frames to minimize the perceivable impact. progressiveUnload() allows you to try to release the CPU and GPU memory allocated for the child nodes of this component, with the unloading staggered over several frames.

4 Likes