| Metric | Standard Preparation (HDD) | Extra Quality (SSD + Tweaks) | | :--- | :--- | :--- | | Load Screen Wait | 5–10 seconds | 15–25 seconds | | First Engagement FPS | 15 FPS (stutter) | 144 FPS (smooth) | | Texture Pop-in | Constant | None | | Late-game Army Fight | Freeze-frame for 1 sec | Zero stutter | | Input Lag | 50ms+ due to CPU stall | Sub-10ms |
Notice the trade-off. Extra quality requires patience before the game, but absolute perfection during the game. A competitive player will always choose 25 seconds of waiting over 25 milliseconds of stutter during a critical baneling split.
cacheDataSize=2048
This is where the feature gets interesting. The community, unwilling to accept a 15-second wait before every custom game, dug into the game files.
They discovered that the "Preparing Game Data" hang was often due to the way StarCraft II archives its data in CASC storage. This storage method packs files tightly to save space, but it makes retrieving individual assets slower. starcraft 2 preparing game data extra quality
Enter the "Local Files" modding scene.
Technically savvy players found that by forcing the game to store certain assets locally in an uncompressed state, they could shave seconds off the "Preparing" phase. This is the dark art of SC2 optimization: sacrificing disk space for speed. It turns the "Extra Quality" texture load into a "Pre-loaded Quality" shortcut. | Metric | Standard Preparation (HDD) | Extra
However, Blizzard has historically frowned upon altering core game files, as it can trigger anti-cheat flags. This leaves the average player in a limbo—wanting the high-quality visuals but resenting the "loading tax" required to render them.