As a note, be careful with the fade in fade out function. For some reason if you set it too long, Visionaire does not like it and causes the game to crash if the player left clicks while it happens. Had this problem for Paradigm. For any fades that went longer than 4 seconds, I just used a black image. Honestly doesn't take up much more resources since its not on the screen constantly and a single black image is pretty small in terms of file size. You could also set it as an interface so you don't have to put black images for each scene. Exactly! haha... I thought I'd mentioned using an interface, but I must have forgot to type it up or removed it from one of my replies for some reason. Oh well...Interface would be fine Thomas, just fade interface in/out as needed.Anyway, as you said, Visionaire should be as easy to use as possible & also as flexible as it can possibly be without having to resort to scripting. For me, the shader stuff should all be internally added to the engine source code, rather than being a script we have to add, then Simon would hopefully be able to create various action parts with tweakable parameters for various shader effects that can be applied to scene, scene objects or characters. Check out Construct 2 game engine, as they use a similar action part system to VS, but already have premade action parts for shaders & sound effect modules. If that could be sorted out along with the damn mouse cursor thing I asked for & some reorganizing of some of the current form layouts of the editor then VS would be near perfect. ;)

You could use the shader also & adjust shaderLightness value.[code]shaderLightness(-1, 1500)[/code]I'm not sure if it will affect particles though & as for using an image. It would be fine. You can create the image at say 25% or 10% or something & scale it up with Lua script. In combination with webp format the image would be tiny in both file-size & VRAM usage I think.[code]local obj = game.CurrentScene.SceneObjects["black"]obj.ObjectScale = 4 -- scale up 4x (if default size was 25% of scene width/height)obj:to(1500, {ObjectVisibility = 100})[/code]

I have no clue, how these new shaders can be incorporated, so tried the way i understand it must work, after reading into shader toolkit source. It's no hurry, i'll wait for SimonS comments, as i can see, he's getting now a lot of questions and bugs to hunt.Accessing it this way doesn't work:shader_effects.test = { shader = Shaders.rc_zero_shader }

@Lee: no that's just wrong. The quotations are there because it's calling this every frame.I found the error there is a space in line 225 that should be removed. There are also some other things to fix in the script. You can fix the space yourself for now. I will publish the updated script with the documentation.If you say so mate. I'm not savvy with the shader stuff. ;)

Don't know mate. Just try replacing the shader toolkit script & see if it works - I have terrible short term memory, so don't remember any specifics about the thread/post about the bindings. Sorry.