Edited by MConwell on 9/5/12 7:40 AM (PDT)
I continue to have the following 4 issues on my Mac using the latest SC2 patch 1.5.2. I'm hoping that I am not the only one and hopefully Blizzard is already aware of all of them.
While I'm not a fan of the new 1.5 interface and generally find it more difficult to find the maps I'm looking for and creating custom games, the 1.5 patch seems to have not followed the Blizzard mantra of "not releasing a game until it is done". This by far has been the worst round of patches I've seen out of Blizzard since in some cases it effectively break the game making it unplayable.
1. LAG - When a user in a game with a large army moves his army, my screen becomes unresponsive. So unresponsive that I cannot select a unit, I cannot message, I cannot scroll the screen and I cannot use the mini-map. It does not seem to matter if the army is visible to me or not. This appears to affect Windows users as 3 friends and I did some testing and all of us had the same issue. The game becomes unplayable.
2. Extended Login/Launch times - The amount of time to login to Battle net has grown. The little launcher app (I'm not sure what it is called) is shown and generally it takes 5 minutes from pressing the PLAY button until I'm prompted to login to Battle net. Then I spend a another 1 or 2 minutes waiting to actually get to a point where I'm able to play.
3. Custom games sometimes show a "canceled by" screen but start anyway. This randomly occurs and when it does SC 2 skips showing me the map, teams screen (where you can pick your race). The game then jumps directly to the loading screen.
4. In game Allied chat is sometimes broken - Whispers seem to work but I am sometimes unable to chat with team mates. Restarting SC2 has been the only fix I've been able to find to resolve this.
My system specs just in case they are wanted:
Model Name: iMac
Model Identifier: iMac7,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: IM71.007A.B03
SMC Version (system): 1.21f4
ATI Radeon HD 2600 Pro:
Chipset Model: ATI,RadeonHD2600
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9583
Revision ID: 0x0000
ROM Revision: 113-B2250F-219
EFI Driver Version: 01.00.219
Resolution: 1920 x 1200
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
I don't know how to capture all of my SC2 in-game settings, but all of my Graphic settings are set to either LOW or OFF
Support Forum Agent
What OS version are you using?
If you're running additional apps when running SC2, this may be why it has long load times. I notice this when I am running VMware to run Windows apps.
Also, if you haven't restarted your Mac in awhile, try it and see if it helps.
Finally, try these additional troubleshooting steps and see if they help.
Repairing StarCraft II
2. Delete the Battle.net.MPQ file
3. Launch StarCraft II
This will force the game to see it is missing data and self repair.
Clearing your Battle.net Cache
2. Move the Battle.net folder to the trash.
3. Empty the Trash.
4. Launch Starcraft II
Mac OS 10.7.4
I restart everything prior to launching SC2 (Mac and Cable modem - directly connected using ethernet)
No other programs are running on the Mac while playing SC2.
I will try the REPAIR and the CACHE steps you've listed and will make an update to this thread with the results.
I've performed the changes you asked and it seems that the long login time may have been positively affected. While the login certainly takes longer under 1.5.x than under 1.4.x, I only experienced a 2 minute login to Battle net rather than a 5+ minute login.
But the Lag issue persists.
In game chat continues to intermittently fail.
And there were 2 occasions last night where the custom game I was trying to join showed "canceled" only to then drop me into the game (no team/pick your race screen was shown).
One additional item I noticed is that when a game starts, the play clock routinely says 10 seconds and it appears that I'm missing the first 10 seconds or so of the game. I don't think this is new as I've seen reaction delays in replays. I don't recall seeing that prior to 1.5.x.