C2 r88 64bits; Intel Core i5-2500K — GHz (x4), 8 Go DDR3, NVIDIA GeForce GTX 560 Ti (driver 296.10), Win 7 Pro SP1
Firefox 12.0; Chrome 18.0.1025.168 m
Capx
There seem to be a problem with the "platform has wall" condition in this specific setup.
I first used a "or" block has currently in the demo capx. (event 5)
The intended logic here is that if the char sprite is either out of screen or faces a wall on its right, it's considered dead and after a 1 second wait "resets"
Obviously, this doesn't work as intended with event 5. Death is instant and continuous.
The first one is "normal" I guess, I did not "bullet proofed" the state system (a spawning character shouldn't die either, even if not on screen).
But the following/continuous deaths are rather strange.
Disable event 5 and enable event 6 and 7.
This is closer to the expected behavior, but on chrome and FF, the sprite will randomly "block" in the right solid Sprite but not be considered dead. Like if the "has wall" condition did not trigger.
On FF, clicking out of the browser seem to "help" getting the event fired. On chrome, it doesn't seem to have much effect.
At first I thought it was a problem with "OR", but it sounds like the platform behavior might be responsible.
Or maybe I'm missing something. Anyway, report is done, let me know your opinion on the issue.