Manually preloaded animations need to be manually unloaded. Animations regularly loaded will get added to the cache until they are removed at end of scene or get pushed aside to make space for newer animations, I think.As for character animations: I believe that the standard animations (idle, talk & walk) for your playable character (not sure about npc characters) are stored in the cache indefinitely. If your character has tons of character animations, I don't really think it's a good idea to preload the character as it will store animations from all outfits associated with that character to the cache (according to the action parts page of the wiki manual - I wrote the page, but I think I mostly rewrote in my own words what it said on the old 2d wiki).The case in question in this thread will more likely than not have been lag caused by too many animations on the screen (playing / loading) at the same time. If the system lags then it will still cause slow-down in animations currently on the screen & you will probably experience the mouse cursor moving / jerking slowly across the screen if you try moving it while lag is occurring. All in all it's all down to optimizing your game, to the best of your, or your teams ability, whether that's by scaling down animation sprites, reducing the amount of frames in certain animations, converting images / animations to webp or removing certain non-important animations, images & openGL shader effects entirely, is up to you to figure out what works best for your game. It is after all, all about compromise. Is this specific feature vital to your game? or can it work without it?

sliding requires less cpu / memory than playing an animation. The fisheye effect for me seems to work, but returns an error to the log constantly. Shader stuff requires a fair bit of memory I think - especially the shaderEffects of which the fisheye effect could be classed under.If I remember correctly, you used some kind of animation or long winded method for setting up the mini-game, no? If I knew how you set it up fully, then maybe I could make some suggestions to make it run a bit smoother. It could just be that your machine isn't powerful enough to run everything on the scene all at once? 2D is a bigger memory hog than 3D, which is why 2D animation artists tend to use significantly less frames than in 3D animations.As for your way border question: no, it's not an issue. I extend way borders outside of the background a lot of the time - so character can walk through doors etc & out of the scene or for hiding character behind an entrance in the next scene & so on.

Hi, if you use multiple shaders on objects you need to use multiple ShaderSets:The second call would be:[code]local eff="ripple3"shaderAddEffect(eff)shaderRemoveEffect(eff)shader_effects[eff].num.strength=1bind(eff, "time", field("shader_iTime"))shaderSetOptions({{shader = shader_effects[eff].num(), comp_dst=5, comp_src=4 }}, 2)Objects.object5.ShaderSet = 2[/code]Just change the id.

But is it possible to exclude the balance animation? I guess i can create it as an interface otherwise.And btw the shader is really cool thing :P

The shader toolkit is very extensible, I've coded a small test part (include the shader toolkit before running this)[code]shader_effects["fisheye"] = {shader=basic_fsh..[[uniform float amount;void mainImage( out vec4 fragColor, in vec2 fragCoord ){ vec2 p = fragCoord.xy / iResolution.x;//normalized coords with some cheat //(assume 1:1 prop) float prop = iResolution.x / iResolution.y;//screen proroption vec2 m = vec2(0.5, 0.5 / prop);//center coords vec2 d = p - m;//vector from center to current fragment float r = sqrt(dot(d, d)); // distance of pixel from center float power = ( 2.0 * 3.141592 / (2.0 * sqrt(dot(m, m))) ) * (amount - 0.5);//amount of effect float bind;//radius of 1:1 effect if (power > 0.0) bind = sqrt(dot(m, m));//stick to corners else {if (prop //Weird formulas vec2 uv; if (power > 0.0)//fisheye uv = m + normalize(d) * tan(r * power) * bind / tan( bind * power); else if (power uv = m + normalize(d) * atan(r * -power * 10.0) * bind / atan(-power * bind * 10.0); else uv = p;//no effect for power = 1.0 vec3 col = texture2D(iChannel0, vec2(uv.x, uv.y * prop)).xyz;//Second part of cheat //for round effect, not elliptical fragColor = vec4(col, 1.0);}void main(){ vec4 color; mainImage(color, texcoord.xy*iResolution.xy); gl_FragColor = color;}]]}shaderAddEffect("fisheye")shaderEffectParam("fisheye", "amount", 0.45)[/code]I've based this on [url=https://www.shadertoy.com/view/4s2GRR]https://www.shadertoy.com/view/4s2GRR[/url]. You can change the amount on the botton, with 0.5 being no change and 0.0 maximum fisheye and 1.0 being maximum bulge.You can even easily animate that:[code]fisheye_amount = 0.5bind("fisheye", "amount", field("fisheye_amount"))startTween("fisheye_amount", fisheye_amount, 0.44, 1000, easeQuadInOut, true, true)[/code]