haha, you know the amusing thing about what you have just said? No? I am the one who is providing the documentation, albeit, very, very, bloody slowly. I don't get paid to write up the documentation. It's provided in my spare time, as & when I can. Lately not very much as I'm busy with other things.Also the thing with the documentation is that I will not be providing a step by step guide on how to do this, or that. It will just be an overview of the engine/editor & what each thing (button, action, menu etc) is for, or what it does. It does already contain things like tips, scripts/snippets & a few tutorials though.Tutorials in my opinion should be created by members of the community, although I don't mind providing one or two, but they are quite time consuming to create, write-up, record & edit.There's actually quite a few people on this forum who, these days send me direct pm/emails for help instead of posting in the forum first. I believe that there are plenty of capable people on the forum who can provide support besides myself.P.S: There is loads of documentation on the old [url=http://wiki.visionaire2d.net/index.php?title=Main_Page]2d wiki[/url], but I can't say how much of it is still valid as most of it is from years ago. Visionaire Studio has change a fair bit since whenever most of the stuff in the old wiki was written. We now have for instance: multi-platform export support, windows/mac versions of the ide (linux on the way at some point), a new sound engine, ttf font support, updated script (text) editor, updated lua handler, openGL shader support, loads of new lua functions & data structure tables, bundle of new action parts, mobile support, 3D character support etc etc. 3.7.1 to 4.0 was quite a big jump & there's more new features on the way in the upcoming build.P.P.S: There's loads of documentation on the new wiki, unfortunately a lot of it is to do with Lua script as it's the side of developing in VS that interests me the most. I often add new scripts, workflow functions & snippets to the wiki. Writing overviews of the editor is, well bloody boring to tell the truth, thus I tend to focus more on the scripting side of documentation, even though I know I should probably provide some new pages for the editor related stuff.

Not unless you write your own GLSL shader code. The blur in the shader toolkit is currently only applicable to the entire scene.

Hello guys,Is it possible to apply the Simon's great shader effects to an object in scene instead of whole scene? For example; the blur effect

most of [url=http://easings.net]these[/url] can be used. Remember though that in VS the names are slightly different, so instead of easeInQuint it is easeQuintIn.ease > name > direction.shaderZoom just zooms into the current viewport position.shaderFollowCharacter will zoom into character position & follow him around the screen until you call stopFollow function, or whatever it is called - I forget.You have added the latest version of the shader toolkit as a definition script to your project?

Thank you :)It's pretty simple and straightforward to generate normal maps for 2D art with the tool, and the intensity, volume and other things can be adjusted with sliders.Thanks for the nice words, things are going quite well and there's already some engines that are ready to use this technique. But unfortunately no adventure game engine yet ;)The previews of the shader thread are absolutely amazing, so I really hope, Simon will do some more work on the shader toolkit, particularly adressing normal maps.