Because menu scenes can be used for other things like mini-games, loading screens, credits etc. I suppose it would make sense to allow for inactive & active image / animation states but what if the developer wants to use a different method, such as: changing the opacity of the button, or changing between a static & animated button, or apply an openGL shader effect to said button on mouse over / out, etc... The current method is more flexible.If you wanted to create a quick & dirty snap between images on mouse over / out then you could create a single animation containing 2 frames; the inactive state & the active state. In the first frame add an execute a script action part containing...[code]ActiveAnimations["anim_name"].AnimationFirstFrame = 1ActiveAnimations["anim_name"].AnimationLastFrame = 1[/code]... the rest is simple enough. Copy / paste the execute a script action you just created above into a on mouse enter & on mouse leave action part for each of the buttons. You should change the values in the on mouse enter action part from 1 to 2. You also need to make sure the animations are set to infinite loop & that you have assigned the animation to the properties tab. You don't have to do this, of course. It's just an alternative method for the condition & 2 objects method, as it only requires one object, instead of 2 & a condition. Plus you don't have to waste time aligning the images in the 2 objects together.

Possible via the config.ini. [i]see [url=http://wiki.visionaire-tracker.net/wiki/Ini_File]here[/url][/i].Or via the [url=http://wiki.visionaire-tracker.net/wiki/SetWindowBrightness]setWindowBrightness()[/url] function.Or via the openGL shader @ [url=http://wiki.visionaire-tracker.net/wiki/ShaderLightness_(CMS)]Lightness[/url] & [url=http://wiki.visionaire-tracker.net/wiki/ShaderContrast_(CMS)]Contrast[/url]. ([i]shader toolkit script is required[/i]).

I had a quick look at the shader toolkit and shaderFollowCharacter() seems indeed the way to go, but yeah, there is the viewport overflow problem with the backgrounds. I'll see if I can manage to modify the function to not go over the limit and behave like the standard camera :)

Okay, I see you already figured it out. We'll handle the particle system later, the shader toolkit should work, tested that very intensive. If you got dumps, please send them to me ;)Also if it's a submission for the competition and your program crashes, we will fix it and you won't get negative points by that ;)

Nice that to function is much neater, when did that spring up? :)I think I've found the bug, its actually a different scene which uses the blur shader, and I think I had a value of 0.8 as the blur.Weirdly the scene with the blur works fine and a totally unrelated scene without any shader effects was crashing..It hasnt happened for the last 30 minutes, so fingers crossed that was it.Thanks for the fast (and late) responseJust to check ..Demo game submissions need to be by midnight tomorrow (UK time) don't they? :)