Re: [Flashcoders] wmode performance headache

[Digg Yeah]

In normal situation, flash player draws directly to the rectangular area of
screen it resides in . But when wmode is set, the job is routed through
browser.
So basically, the setting wmode value puts performance at the mercy of the
browser . If the browser has a bad implementation of wmode, then it would
result in poor performance.

Its a well known fact that setting wmode to transparent results in extremely
bad performance in Gecko browsers.


On 6/18/07, Martin Klasson [EMAIL PROTECTED] wrote:



Hi Everyone,

I got a campaign which is using some intense animations,
and everything works well and fast as usual in the flash IDE.

but in the browser it doesnt reach the same speed, as usual,

BUT,
in Firefox, when setting wmode to opaque, than it really goes
great, the fps-counter I have really shows the same fps as the movie.

but in Internet Explorer, opaque makes the flash player to freeze in
some of
the intense animations, the framerate doesnt go down -the whole flash
just freezes for a short time. That is so strange. So window mode makes
the best performance in Internet Explorer.

Anyone who can clarify why, how and what I should do to make the
best performance out of this?

Martin
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

RE: [Flashcoders] wmode performance headache

[John Dowdell]

I don't have full details about changes in each browser version.

There are two performance hits described here:
  (a)  running things in a browser (Projectors (and presumably Apollo) are 
fastest; different browsers have different strategies in allocating processor 
cycles to plugins);
  (b)  piping the plugin's content to the browser for compositing, rather than 
directly-to-screen (WMODE).

If your tests show that a particular version of Microsoft Internet Explorer 
performs much worse than other browsers do, then a good first step is to 
generalize the observation... confirm it with basic barebones SWF/HTML (no 
plugin-in-DIV, no rapidfire messaging etc), and confirm it on multiple machines.

I haven't heard many people previously report IE freezes w/WMODE -- if that 
were *always* the case then we'd see more of an uproar on the lists. That's 
what makes me wonder whether there's a particular dependency in this case, that 
gives you dramatically worse performance than what others see.

But there *will* be a performance degradation when playing within a browser, 
and when asking the browser to blend the plugin's content into its own 
rendering engine. It shouldn't cause an outright freeze, but there will indeed 
be a cost to performance.

jd


___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com