Sponsorship and wmode

[Draxus]

I'm planning on trying sponsorship for the first time soon... when I began the game I wasn't planning on having it sponsored so I've been designing it at 50fps. Of course the swf on my computer runs just fine, and it looks like crap in Firefox or IE. I read up on wmode and discovered setting it to opaque lets it run perfectly, but breaks Key.isDown... which I eventually figured out how to work around.

Now I realized I probably won't have any control over the way my swf is presented after I give it to my sponsor, and therefore will be unable to use wmode, right? Should I just give it up and take it down to 31fps?

Thanks

[smith1302]

I personally just use 31 fps. And good luck on getting your game sponsored, I got mine sponsored for the first time a couple of weeks ago. Its exciting when you get that first payment.

[Draxus]

Thanks for the reply smith... I'll take it down to 31 if I have to.

Anyone else have any experience using using wmode=opaque or transparent, with a sponsor?

[Estartic]

You may be able to sell a license for use on a single site.
Since most sites don´t use and support wmode selling a distribution license (sponsorship) won´t work.

[Squize]

wmode breaks on every browser aside from IE, so it's best to avoid it all together.

Squize.

[Alluvian]

Noob question, and I don't want to get too far off topic. Does anyone have a link to a more detailed discussion about wmode and what is so magical about this 31 fps? When you say 'looks like crap' what does that mean?

Just wondering since my game is currently setup for something like 60 fps (I forget) but without much art and hardly no frame based animation I could pretty easily change it at this point.

I didn't plan on sponsorship for the game, instead I just planned on putting it on our site to maybe increase traffic for the 10 people that might like it. I can't predict the future though, so maybe one day I WOULD want to sponsor it.

[Squize]

31 fps is used 'cause historically it was one of the few frame rates that the mac Flash player could cope with ( Setting a fps of 30 would result in 19 fps on the mac ).
Just to cover it to death, it was a case of 31-58 fps on the mac would run at 29fps, so 31 became the norm as a happy medium.

It's probably not been valid since F6, but it's a habit thing for a lot of developers.

Pushing the fps artificiality high isn't the way to go to get the best playback. It means the screen is updated more often, which can take cpu cycles from the actual code.

wmode does give a performance increase, but in the case of FireFox it stops the arrows keys ( Amongst others I believe ) from being registered in Flash.

Squize.