I think this is so, because main loop is not render loop... So. correct FPS can make only Gio

this show CPU load not GPU, 

i think you must use chrome rendering tools in console  in

console - more tool - rendering 

But it is possible to show real FPS in wade. In three.js it is made with stats.js https://github.com/mrdoob/stats.js/

It shows real FPS (viewable by user on screen) in onRender cycle. This cycle works not 60 times per sec, but right away from previous cycle (60fps is maximum for webgl. But if there is brakes - it will update slower)

function animate() {

                    requestAnimationFrame(animate);                   
                    render();
                    stats.update();

                }

You can use stats.js too!

Bookmarklet
You can add this code to any page using the following bookmarklet:

Stats js will be works with wade 

I tried, but with no result )))) May be my fault, or may be wade restrictions... I simply don't see it. Also, I can't add stats.update() to render cycle...

just open console and paste bookmarklet code

I have a question - why you use a 

var k = wade.getScreenWidth()/wade.getScreenHeight();
	    wade.setLayerCustomProperty(1,"kScreen",k);

If you change wade layer mode to 'container' - there is no need in this property

Next question - if you make an platformer game - why your snow stick to layer? 

In real game player move, and all background move to him, i.e. you must stick snow to player object, and move layer with snow with player speed

>If you change wade layer mode to 'container' - there is no need in this property

I didn't know, thanks!

>Next question - if you make an platformer game - why your snow stick to layer? In real game player move, and all background move to him, i.e. you must stick snow to player object, and move layer with snow with player speed

Yes, this will be new shader uniform "scroll speed", wich just will be added inside shader to wind. But there is more difficult thing - you must stick snow posteffect to different layers with different params, if you want real depth-imitation. I'll show such demo, but later. It will be real true render, but firstly my friend-designer have to draw layers content.

Stats.js works with bookmarklet code in console. But don't work from app.js. May be my fault, don't know... Such simple things, but very hard for me )) If it were integrated statistic in wade...

Gio,

I fill currently my own shaders library and think...

Why not allow to select custom user shader from list? Maybe files with extension *.glsl? It would be very conviniently.

And more convinient - if custom shader uniforms will be loaded too...

Just to be sure I understand, do you mean that we should look for files with a glsl extension in the project, parse them and add them to the list?

If that's what you mean, I think it's a great idea. Certainly worth doing.

Yes, thanks!