I'm pretty sure they all ran the same... Taking a screen shot is a good idea - my memory and eyesight are not what they used to be! I'll let you know...
Mmmmm, I've not seen anything like that before. Are you willing to post a capx do we can take a look at the events?
Try a hard-refresh (ctrl + F5). Maybe that will make a difference by forcing the browser to re-upload all of the files... I hope....
I don't see a difference..... W8.1 IE v11.0.9600.17416.
Check your character set - it sounds like there's a mismatch with the image.
hundredfold, ah - yes, I see. Some way of ensuring it is not given a default rectangle on import.
You could pin the sprite with the new image to another (invisible) that holds the collision polygon you want, then use that for collision checking.
I have just put together a simple tutorial here that shows you a way of inputting css values as a single data string - no plugins required. Hope this helps...
TiAm, I'll post images from the test tomorrow but I saw Canary was worse performing than Chrome 39... Window residing made no difference to the results in either case.
Weird..... Consistently inconsistent!
When I run my data gathering test on Canary 41.0.2225..0 the spread of dt values is quite depressingly similar to chrome 38. However, Chrome 39.0.2171.65 m is very good, with only a small rate of frame drops....
You might find this useful as well if you revert to r187. Until Ashley updates the nw loader, you can download a copy of the old version in this thread at the bottom of the page.
Develop games in your browser. Powerful, performant & highly capable.
Revert back to r187 if you can - the newer version of nw is broken (because it's based on chrome 38).
Sorry dude - have you a copy of Ease Tween behavior - I don't have it and cannot open the capx....?
Hilarious!! And I thought you were going to mention a 5 stage Kalman Filter, — However, I've come to realize that no-one understands how they work (just like no one knows how they built their browser engines, it would appear....).