TiAm , my system has an old Intel Core2 Quad CPU (Q9550) overclocked to 3.7 GHz, 16 Gb of DDR3 ram and a nVidia GTX 660 Ti with 3 Gb ram. I know that it's not by any means a high end system, but my original concern was about the jerky movement of a single moving square

As for your full screen canary results, while they look somewhat the same as mine (having a few prominent scattered spikes), if you look closely you'll notice that there are a lot small lines evenly distributed from 13.3 ms up to around 19 ms or so. In my cursed tests I get only integer numbers or floats that have .99 in the decimal places (like 15.99, 17.99 etc).

Colludium's tests by the way look awesome and pretty professional

TiAm , unfortunately it's the same:

Canary 40.0.2209.0

The frame rate is fixed at 60, the object count fluctuates between 60 and 62 (with most frequent been 61, after that after that 62 and less often 60) and in a small browser window there is little but still noticeable frequent jerkiness in the scrolling background.

Perhaps I am cursed..? Am I the only one that has this results? Everybody else gets a graph that looks like Colludium and TiAm?

rony Sueliton , have you even tried my example..? It already does exactly what you ask for.

A0Nasser , yes, as Aurel said, the bloom effect is a post process effect. Unfortunately there isn't an easy way to fake this. What I was able to come up with is using gradient sprites overlayed on top of the background and foreground elements (to create the misty-look effect) and an Adjustment layer on top (term loosely taken from After Effects) that ads blurs and brightness to the layers below. If the game has scrolling camera like limbo, you should fix the gradient Sprites with an every tick set position x,y, or overlay them on top of the background&foreground on layers with 0 parallax values.

I wish there was a webGL shader for that...

Bloom example

I'm putting a capx for my example, you'll need the modified radial bur effect that has some extra features and blurs a bit differently than the original radial blur. I'm posting that too.

1) Use clamp.

2) Make sure your object (the black square) is a Global object (you can set this on the Object type properties of the Sprite).

See the attached capx

saf , That would be indeed great and insanely difficult to do at the same time. Taking into account all the jumping trajectories and all the complexity that the solids/jump-through platforms could have, is just insane! I bet that for the most part the poor CPU will jump like crazy trying to avoid 1 px overlaps and smashing it's head on narrow height corridors.

For the most part, using triggers to set gaps, slopes, edges and stuff will do. For logic that decides which way should be more practical for the AI to go, then you'll cave to hardcore those parts by occasion. There isn't a make AI button (unfortunately) and AI is probably the most difficult thing to make!

Colludium , today I get this from firefox:

Chrome & Canary are still the same: Either integer values or 15.99, 17.99 etc... Running your capx with node-webkit also produces the same thing, as expected i guess...

TiAm , it doesn't matter if I run the tests in windowed mode or not. The same thing happen. My Chrome version is 38.0.2125.111 m and it tells me that it's up to date. Canary is 40.0.2208.0 canary (64-bit). I don't know why Chrome doesn't display the 64bit thingy, perhaps it isn't a 64bit version. Is there a normal Chrome 64bit version available...? Anyway, I don't think that has do do anything though.

I don't know what to get out of this, I've even disabled my secondary monitors as was suggested by Tylermon at page 7 and nothing changed on the chrome based browsers. On the other hand, with the secondary monitors disabled, IE11 runs the waterfall benchmark with no scatter what so ever!!!

Aurel ,

Dalal ,

A0Nasser ,

iceangel ,

Thank you guys!

Colludium ,

I am afraid that the first test also gives similar results for some reason. Here are some screen shots:

Firefox

Chrome

Canary

IE11

Firefox is just a mess with no red dots at all, Chrome and Canary produce almost straight lines with occasional dots all around and only IE renders a graph that resembles the expected result. Of course, as always, in all tests the jitter is there like a common factor...

Colludium , I am sorry, I just don't know how to use dropbox Please look again in my post above!

To be totally honest, I'm also waiting for someone who understands what the mouse.absolute(x/y) expression does in practice to answer this!

Boohoohoooo , yet an other request of mine bites the dust