Method to reduce screenfreezes
Posted: 11 Dec 2011, 05:42
Screenfreezes are a mulithreading problem. We know that much, but it's never been really discovered where the sources come from. This means is due to having a dual/quad core computer and the game process communicating with both cores on your processor.
Now, many of us run on different processors so this "mitigation" will work WONDERS for some, and other others offer little improvement. For myself, on both my PC's Intel Core 2 Duo 3.0Ghz and iMac's Intel Core 2 Duo 3.06Ghz this works wonders, but like I said, for others maybe not so much.
In the past I've told people every time they run the game to open Task Manager and "Set Affinity" on WoW.exe to 1 CPU. This is an annoyance as you have to run it EVERYTIME YOU RUN THE GAME. Well I discovered there was a WoW setting for this that can be stored in the game files so you no longer have to do that. This also is a viable fix for Mac OS X since you cannot set affinity on Mac binaries.
1. Make sure WoW is completely closed
2. Go to your WoW installation folder
3. Go into /WTF/ and open Config.wtf in Notepad or some text editor program
4. Add the following line:
Now, many of us run on different processors so this "mitigation" will work WONDERS for some, and other others offer little improvement. For myself, on both my PC's Intel Core 2 Duo 3.0Ghz and iMac's Intel Core 2 Duo 3.06Ghz this works wonders, but like I said, for others maybe not so much.
In the past I've told people every time they run the game to open Task Manager and "Set Affinity" on WoW.exe to 1 CPU. This is an annoyance as you have to run it EVERYTIME YOU RUN THE GAME. Well I discovered there was a WoW setting for this that can be stored in the game files so you no longer have to do that. This also is a viable fix for Mac OS X since you cannot set affinity on Mac binaries.
1. Make sure WoW is completely closed
2. Go to your WoW installation folder
3. Go into /WTF/ and open Config.wtf in Notepad or some text editor program
4. Add the following line:
NOTE: If you already have a "processAffinityMask" in there, MAKE SURE IT'S SET TO "1"!SET processAffinityMask "1"