Bug With MoveTo Animation

[Taenick]

Hello,

I have a simple scenario that has a box moving to the right then reseting back to the beginning. This animation is on a loop. The animated box is a child of the background...

If you run in chrome, when the box resets, the background jitters. But if you run in safari version 5.1.7 the background jitters and the label also jitters.

The animation of the child box should have no effect on its parent or a fellow child box label.

I posted a repro case on pastebin: http://pastebin.com/228NxAhv

Thanks,
Nick

[fariazz]

I've experienced this as well, but only when rendering with canvas, it seems the background is forced to redraw very often during the animation, this makes these animations slow in Android.

[fariazz]

It doesn't happen if you render with the DOM

[Taenick]

I ran into this problem when I rendered DOM elements... Basically, to get around this problem, I had to give up on the lime animations and just use setPosition on the DOM element... It's a pain, but it was the only way to get what i wanted from the lime engine...

[lorddarq]

Here's some interesting facts which i noticed in windows 7 x64. May apply to 32 bit as well, dunno:

• in firefox latest (14.0.1) it works without a glitch, more fluent than in chrome. average of 58fps
• in chrome latest (21.0.1180.79 m), crappy redraw which leaves white artefacts, bad flickering of the sprite during redraw. Average of 62 fps
• in safari latest (Safari 5.1.7) works flawless like in firefox, but has an average of 30 fps which is close to IE9

[stringa]

Chromes newest update doesn't have the problem anymore.

Stringa
On Aug 18, 2012 4:50 AM, "Sorin Jurcut" [email protected] wrote:

Here's some interesting facts which i noticed in windows 7 x64. May apply
to 32 bit as well, dunno:

• in firefox latest (14.0.1) it works without a glitch, more fluent
  than in chrome. average of 58fps

• in chrome latest (21.0.1180.79 m), crappy redraw which leaves white
  artefacts, bad flickering of the sprite during redraw. Average of 62 fps

• in safari latest (Safari 5.1.7) works flawless like in firefox, but
  has an average of 30 fps which is close to IE9

  —
  Reply to this email directly or view it on GitHubhttps://github.com/Bug With MoveTo Animation #28#issuecomment-7843908.

[lorddarq]

I very much doubt it. The version I run is the latest one. And when i tried to install the latest version, i got Error 0x00000003
which is google chrome's way of telling me i already got the software installed and running the latest version. If you mean the canary version, then I have to disappoint you. It looks broken there too.
http://i1263.photobucket.com/albums/ii624/thedarq/3d5d4c4d.png this is how it looks running the latest version of chrome.

[stringa]

We are on esx at work and we don't see these issues anymore as of the last
update. Maybe the wondows client is behind?

Stringa
On Aug 18, 2012 1:25 PM, "Sorin Jurcut" [email protected] wrote:

I very much doubt it. The version I run is the latest one. And when i
tried to install the latest version, i got Error 0x00000003
which is google chrome's way of telling me i already got the software
installed and running the latest version. If you mean the canary version,
then I have to disappoint you. It looks broken there too.
http://i1263.photobucket.com/albums/ii624/thedarq/3d5d4c4d.png this is
how it looks running the latest version of chrome.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/28#issuecomment-7847739.

[lorddarq]

could be. could also be a combo of bad videodriver + bad code in chrome. Not sure. I tried deactivating the advanced rendering feature but the result was the same. What's odd is that this afternoon the effect was more pronounced, and i had left chrome open for quite a while doing some heavy browsing, which is why it leads me to believe there may be a connection between that and the rendering performance.

[stringa]

The bug just reappeared tonight with some new chrome updates on osx.
On Aug 18, 2012 1:47 PM, "Sorin Jurcut" [email protected] wrote:

could be. could also be a combo of bad videodriver + bad code in chrome.
Not sure. I tried deactivating the advanced rendering feature but the
result was the same. What's odd is that this afternoon the effect was more
pronounced, and i had left chrome open for quite a while doing some heavy
browsing, which is why it leads me to believe there may be a connection
between that and the rendering performance.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/28#issuecomment-7847925.