I’ve perceived that the mac web player seems to have seriously impacted performance compared to standalone builds or playing the same game in a web player on a pc. Has anyone else noticed this or is it just me?
It also varies massively depending on what browser I use. Firefox being seriously good, safari being poor, and chrome rendering most web players unplayable.
Is this a known issue or possibly a problem with my machine setup?
Thanks
This is most definitely a known issue (case number 391253, if you should need to check up on it) and is currently undergoing testing.
andeeee, this is very good news !
thanks andy 
how do I check the bugs? You got a public issue tracker somewhere?
has this been fixed yet? I’m testing webplayer builds across different laptops on win/os and it would be good to know.
Like bweiers, any news about this case? I have just run some tests under Firefox 6 on Mac OS 10.6 and Windows XP and I am still experiencing huge performance hit on mac compared to windows. However the same scene builded as a standalone application on mac is as fast as the standalone application on windows.
did you ensure to not enable static batching in case you are on pro and in case your mac has an ati gpu?
Thank you for your answer dreamora.
Is there a way to disable static batching globally? I though it was configured per Gameobject. Anyway there are not any static gameobject in the tested scenes and I am using Unity pro to build the web player.
The graphic card on the iMac on which I am running the tests is the geforce 9400 as reported by the OS but I think it is most likely a geforce 9400M. However the tested scenes are very simple in terms of geometry and shader complexity and from my tests the framerate especially depends on the screen resolution. But at the same screen resolution the standalone player is by far faster than the web player on mac.
I think that when the screen resolution is higher than a certain limit hardware capabilities can’t handle it and may fall back to software emulation. I need to test on other apple devices but I would be glad to know if Unity developers did something since this case was reported and which was/were the cause(s).
I am interested in this since we’re seeing issues with Chrome/Unity Web Player/Mac OSX 10.6.x.
How can I find/view case number 391253?
One thing I have also noticed: When I run the Unity Web Player in Chrome on Mac OS X 10.6.8, the ‘mds’ process (which I gather is related to Spotlight) also ends up using quite a bit of cpu and memory. When the Web Player is then stopped, the mds cpu usage drops again.
Actually, disregard my comments about the mds daemon, that turned out to be unrelated.
However, I am still seeing issues with the web player and chrome: specifically, the web player seems to starve chrome’s UI handling.
So, I just did another test: I created a test scene with just a single cube and ran it. If you then bring up the developer console and try moving around between tabs, you’ll notice that the UI is very slow, rendering chrome almost unusable.
I am running:
Late 2009 2.26 Ghz MacBook Pro / 8GB RAM
Mac OS X 10.6.8
Chrome 16.0.912.63 Beta
Unity 3.4.2f3