Animation rendering problem in Firefox

[EricLesch]

I'm seeing flickering/leftover stuff from previous frames in Firefox for the demo .... http://www.goodboydigital.com/pixijs/examples/12/.

Please let me know if you don't see this on your machine. It might be just my laptop....

Thanks,
Eric

[mattdesl]

Works fine here.

Try it with WebGL disabled to narrow down which renderer is causing the issue. Also make sure to try the example from the latest dev branch since there have been lots of bug fixes since the last major release.

[EricLesch]

This happens with the code in the current dev branch.

However, it only happens on my laptop when I have an external monitor connected to it. It also only happens when using the WebGL renderer. The canvas renderer works fine.

I am using the Intel HD Graphics 4000 Graphics on my Ivy Bridge processor, so if this is an issue with the graphics card, it will be fairly common.

[EricLesch]

Just checked again and this bug still persists as of 1.5.3.

[GoodBoyDigital]

Hi @EricLesch is this still an issue on the current dev branch? cheers!

[EricLesch]

Yes, I just checked and this is still happening in the current dev branch.

Thanks,
Eric

[gabrielenosso]

Is it still an open issue?

I found something strange: on my new laptop (bought 3 months ago) there are some examples from this page that don't work - www.pixijs.com/examples/
The numbers 12, 12B and 17 don't work.
Strangely, the 12C and other examples work well.

I don't know if it is a PIXI problem or a WebGL problem.

[edcarstens]

I also see this problem on my laptop. I got an Ultrabook with Intel corei5 vPro processor running Windows 7. The other weird thing is the Firefox browser pauses the animations very briefly, but still noticeably, every few seconds. Chrome doesn't do this. Of course, IE doesn't work right at all.

[EricLesch]

@edcarstens So if you are running an i5 laptop, you are using integrated Intel 4000 Graphics?

[GoodBoyDigital]

closing for now as this seems like a bit of an edge case. ta!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.