Well, I cannot give you an easy Solution, but I can tell from looking at the new Shadertoolkit that it does not actually include the several Shaders inside the Script -- which makes Sense, because in Vis5 that does not work anymore. Strangely, I know that shaderBlur() still works fine, so I have no Idea how that works exactly (is it not Part of the Shader-Toolkit??). But if these Shaders you want do not work anymore, then go to the old Shadertoolkit-Script, look for the Areas which are huge Piles of different-looking Code inside of Strings, and copy those Parts into separate Shaders (in the Editor's new "Shader"-Category), and change the Codes until you get no Error-Messages at the Bottom anymore (I guess that is easier said than done, seems like most People on the Forum haven't looked much into GLSL-Coding, and I am also but a mere Amateur). Once you have done that, you can call the Shader with a Script very similar to how it worked in Vis4:local eff = "NAME_OF_THE_SHADER"
shader_effects[eff] = { shader = Shaders[eff].Compiled }
shaderAddEffect(eff)All of that might seem as of little Use if you do not know GLSL, but I personally tend to say that People should use their own Shaders if they can, it's actually kind of fun -- connects Coding, which I do not like so much, with creating visual Art, which I enjoy.
