Replying to:Andrew TateIs there a limit where you can’t use anymore memory or?
Bec
memory = temporary storage space. More nodes = more memory, and Android/IOS usually limit devices to use upwards of 256MB or 512MB, or in rare cases 1024MB+ (all of thse approximate values) of memory per app, and there’s nothing you can do about it. If you hit this level, the app may crash.
cpu = lag, unrelated to memory (unless memory usage is very near the limit then you can get some bad stuttering as the app is taking its last breaths). Usually caused by too many nodes being rendered on the SCREEN (not just, across all frames) or filters, etc. Basically, rendering.
2021-03-31 08:26:18 UTC 
User Banned
No idea
nodes
a plethora of nodes
Is there a limit where you can’t use anymore memory or?
Because my phone hasn’t lagged in the slightest yet
memory = temporary storage space. More nodes = more memory, and Android/IOS usually limit devices to use upwards of 256MB or 512MB, or in rare cases 1024MB+ (all of thse approximate values) of memory per app, and there’s nothing you can do about it. If you hit this level, the app may crash.
cpu = lag, unrelated to memory (unless memory usage is very near the limit then you can get some bad stuttering as the app is taking its last breaths). Usually caused by too many nodes being rendered on the SCREEN (not just, across all frames) or filters, etc. Basically, rendering.
So impending doom is coming, good to know
Oooooh, is that why you still limit the node count? That makes sense.
I can barely get to 100 frames and here you come with a *looks at the frames* 490 frames!? Just gotty damm thats impressive and goddam 571mb wow