StarCraft
The StarCraft II: Wings of Liberty multiplayer Beta opened yesterday - and already Blizzard has detailed several known bugs with the game. This is a private beta, so only invited players are getting their chance to play the game during this initial period. While I can't say how many of these new players are taking advantage of bugs in the multiplayer beta, it is known that several tips and tricks have leaked in the form of a FAQ as well. Further, we've gathered some common-sense strategy and tips that you can use to your advantage as you explore the multiplayer beta for StarCraft II. More on the FAQ in a bit, but first let's talk about the bugs that are known in the StarCraft II Multiplayer Beta.
Blizzard has released the following list of bugs for StarCraft II in their Beta forums, pay close attention to the effects of one particular bug (emphasis mine).
General Issues:
• The Intel Core i7 processor occasionally runs StarCraft II slower than usual.
• ATI x1800/x1900 cards display black box shadows with Medium lighting. - Try lowering your graphics settings to temporarily resolve this issue.
• Some objects are visible through the fog of war on low graphics settings.
• The mouse cursor is not always confined to the game window when running windowed fullscreen mode with dual monitors.
• StarCraft II microphone settings are overwriting Windows' microphone settings.
• Unsupported aspect ratios can become available when using a portrait style monitor.
• Some letters are being cut off in the message log at certain resolutions.
• The game can close when switching to another program shortly after starting StarCraft II. - If you experience this issue please try updating your systems drivers.
• Samsung 2253LW monitors experience an issue with the 1600x1200 resolution not stretching properly to fit the screen.
• Resolution issues can occur when rapidly changing between display modes. - Changing display modes can correct the issue.
Paged Pool Memory:
Players may experience a drop of performance or odd graphical issues after playing for long periods of time. Usually when this occurs a message will appear mentioning the players page pool memory. If you receive the overlay messages informing you of the problem you can try to lower your graphic settings and restarting your client/machine, or increasing the system’s memory. Also ensure your drivers are up to date and all OS updates have been applied.
So here's the deal - if you notice that your Fog of War isn't working as well as you'd think it should in the StarCraft II Multiplayer Beta, you now know why. While Stage Select does not encourage exploitation of bugs, it would seem that lowering one's graphics settings isn't exactly what you could call a hack for the StarCraft II beta. After you check out the game on the higher settings, consider lowering your graphics settings, or avoiding Fog of War until Blizzard fixes this bug. This isn't about exploitation of a bug, or even a long term strategy, this is about leveling the playing field.
The problem with the i7 processors affects only a few players, but here the strategy is the same. Lower your settings until the speed difference goes away, if you have an Intel i7 processor. It's basic stuff - if you're not able to react quickly because the game isn't responding, you're going to lose. Eliminate that disadvantage by using the appropriate settings for your computer.
It's come to my attention that a FAQ was published yesterday as well. Likewise, let's explore some tips and tricks that new and experienced players can use to improve their game.
Story continues...
Sort By:
No comments were found for this thread.