Hi, just got the pop yesturday. so can be i am doing something wrong. I saw that if i have a texture 3d with N depth connected to a polygonize POP, when i incerese N gpu mem rise… that is ok… but when i drop it down mem does not get free. deleteing the polygonize POP is solving the issue (mem goes back to normal usage). do we have some base line of how much we can polygonise ?? like 1 milion points = tot VRAM ??
Thanks!!
Hi @Unveil_studio,
So gpu memory not being freed until the POP is deleted or toe file restarted is intentional (allocating memory is somewhat slow so we try to avoid doing it too much).
We’ll most likely add some way to force freeing the memory, or different styles of memory allocation to streamline workflow a bit.
Otherwise the memory allocated is proportional to number of voxels, so doubling resolution of the 3d texture means 8x more memory so it goes up fast.
The middle click popup menu info doesn’t take into account all memory used by the POP currently, another thing to improve, but otherwise I’m seeing 100 MB for 64x64x64 and 700 MB for 128x128x128 currently.
Last but not least, the memory allocated is currently the max that could be used, so in most case it’s a lot less than that, so a possible improvement would be to allow the user to specify a max memory to allocate (which would glitch if the max is hit). (especially since any downstream POP will use that amount as baseline)
Polygonize POP was an early prototype that might benefit from some improvements
Is there any python method to free a POPs memory yet? That would be super helpful, thanks!
Not currently, but that’s a good suggestion!