Yes, there's a team project / save export option thing, but I recommend only one person at any given time working on the actual project file.For me the simplest option is to use something like dropbox or google drive & work on your project in a folder you are sharing to one of those services, then when you are done, you let the next person know & they have immediate access to download / sync over your most recent changes & carry on with whatever they need to do.Ideally you should really only have 1-2 developers working on the development side of of your game otherwise things can quickly become unorganized & inconsistent as most people have their own methods & ideas on how to achieve things & with Visionaire Studio, there's often multiple solutions to achieving the same goal.Scripting if you are planning on extending your project through Lua script &/or with the openGL shader is best done initially in a third party text editor such as Sublime Text, Github Atom or Notepad++ (I personally recommend sublime text. Atom is almost as good as Sublime & as a bonus it's 100% free unlike Sublime). You can then load external scripts into VS with a small loadfile function or better yet, just copy/paste your finished scripts directly into the editor itself.As for graphics, videos, music & sound, it's best if you let the people sorting out that side of things do so in whatever applications they use to create them & then you have whoever is sorting out the development side of things (editor stuff) imports & implements them into your ved project file rather than allowing more people than necessary to mess about with your project file. There's an old saying, which goes something along the lines of this... "Too many cooks spoil the broth!".P.S: sorry for the epically large response. I did actually intend to keep it short, but I tend to ramble on a bit sometimes.

I'm using the 4.2. Where can I find a working shader script for that version? I think this might be source for my worries.About those action parts, I've tried all the possible zoom related functions in all the possible places, but with zero luck. Is it possible, that this is an Open GL related issue, since I'm using a Mac?

Okay, now I'm ready to ask some help, as I've tried to get the shaders - specifically the zoom functions - to work, with no damn luck. I've copied the definition script from wiki multiple times, just to make sure I didn't screw anything up. I finally got the effects from the shader demo toolkit to work with my project, but the zooming doesn't work.So, this might be a pretty dumb question, but could someone please explain me - a n00b, how do you get the friggin' effect to work. I'm running Visionaire 4.2 on Macbook Air (is this an issue?). As I understand, I should be able to use the zoom for example in action areas to zoom the scene in just a little when player is around exit. Am I able to do this by adding the script to Action Area using the 'execute script' action part, or do I need to do something fancier?I've tried to run shaderZoom function in console, but I get an error message saying "invalid syntax for command startTween". Could this possibly be an issue relating to Open GL? I haven't tried my luck on Windows computer, but if you guys can't help me out, that's probably my next move..I'm going to stop pulling hair from my head and get a cup of coffee...

I think Simon is about the only one that has a clue about the shader stuff. It's way beyond me as I'm not very savvy in any of the C languages.Bind is a function though, so you can put it anywhere you like. There's probably some examples of bind function floating about on the forum, but as to whether you can find them (search engine is pap) is another question entirely.

Since you're using the functions of the shader toolkit, it counts.How do you want to change the values ? Depending on that you need to call it every frame or only once, after the shader is compiled (happens in shaderAddEffect). If it's done repeatedly you can also use bind(). bind("daynight", "uniform", field("Values.Daylight.Int"))Once the shader is compiled information about that is saved in the num object of the shader_effects. So with shader_effects["daynight" ].num you can set uniforms without using the shaderUniform function (happens internally). It must be an uniform, that are the only variables that are exposed.Yes, it's Values.Daylight.Int .Also note that the shader is written a bit inconvinient. You should always put every calculation in a function and only constants outside the main function, so it's better to be understood and with the new version of the engine cross-compiled for DX.