I've recently released a large game coded in Flash Builder with Air (www.lonesurvivor.co.uk), and I used Air 3's captive runtime feature to bundle it for Mac and PC.
The initial build used Air 3.2 and for a large proportion of OSX users, there were no visuals at all, just sound and the game obviously working underneath. This caused a very large support issue, and took several weeks to deal with, as well as having to maintain a seperate Projector version for those for whom the Air version wouldn't work. I wish I had known that the game would fail on some Macs, but unfortunately the issue showed up on none of the ones tested.
I'm about to launch the updated build of the game which uses Air 3.3 beta 1, as it seems to fix the black screen issue for all those who experienced it. I was very happy that Adobe have managed to iron this out, even if there was no response to the bug I entered into bugbase.
The problem is, on a final test on XP SP2, the 3.3 beta version produces what appears to be filtered graphics... which is how the Mac version has always appeared, but the PC version of the game seemed to use what looked like nearest-neighbour sampling in Flash's fulllscreen upscaling, which looked good for the zoomed pixel art in this game.
This is a small cosmetic issue, but there is another one whhich is far more severe - the audio has become extremely distorted, and is now unlistenable.
So with 3.2 giving me no visual on Macs and 3.3 giving me unlistenable audio on PCs, I will now have to maintain two versions again. I really would like to keep one project I can quickly make changes to, but the seperate problems in different platforms means I lose out on the great cross-platform functionality of Air. I'm hoping this is a known issue, but I couldn't find it on google / bugbase / these forums.
Could these two issues be related - is hardware acceleration not working or something? Somehow I think it is, because the XP test machine is quite old, and tended to fall over with the game running in software mode in a Flash projector.
I tried swapping out the Air 3.3 runtime for the previous 3.2 I shipped with, and editing the XML desciption to make sure it was set to use that and, sure enough, the game worked as it did before. So there is definitely something up with the beta. I'm just glad I caught this problem before I shipped as going to save me thousands of emails of support!
So I guess my question is - is this a known issue? And if so, do you have any workarounds / or are Adobe working on a fix?