construct really needs a way to handle big animations.
i dont know exactly how construct does it now but i think it just dumps everything into vram and runs?
i read a bit on this stuff and it looks like ever since 2d games existed, only background texture type stuff was loaded into VRAM, and then for animations, everything not needed isnt loaded, only the current animation frames needing to be drawn would be loaded into vram that game frame. so that would mean that vram usage isnt a problem unless the total amount of texture data needing to be rendered at a given frame would be really big. the problem most people are having is dealing with alot of frames, and no vram space to put it in, its rare that the total amount of texture data needing to rendered in one screen is too much for vram.
does construct have an option to this right now, or is it already?
what would be the advantage/disadvantage of this method.
and do you think it would be a good idea to have it for frame heavy games?
id like to see the devs' view on this and what the community thinks etc. discuss!