I'm downloading this game from fileplanet atm and I'll be giving it a shot in linux too.Darckness wrote:This will be divided into three separate sections now: the install section, the Cedega section, and the Wine section. First will be the Cedega section.
Install:
First, make sure you're using REGULAR WINE to start this off. I tried it with cedega a few times and things were buggy (4.1 and 4.2), so I'll be sticking with wine for the install. Also, non-gentoo users should make sure that they have the following installed:
xorg-x11-devel
freeglut-devel
fglrx-devel (for ati users)
I've tried using the latest wine in portage and wine-cvs, and they both work perfectly, and I've also used it back to the September version, so don't worry too much about that.
My windows version is set to win98.
Insert your cd, mount it, and then executeThat should be all you need to do in order to get it installed. If cedega fails to install (such as here), I've heard that copying all the files from the cds to a directory on your hard drive and executing it from there will solve the problem. This is, however, untested by me.Code: Select all
wine /path/to/cdrom/install.exe
Next, we'll be updating to the latest version. This can be done via one of two ways. The first is to use the Blizzard updater, which can be slow for some (it can also be amazingly fast as well). We'll try that.
All you have to do to get this started is cd into your WoW directory in your wine home (probably ~/.wine/fake_windows/Program Files/World Of Warcraft/). ExecuteWorld of Warcraft should start soon. If you're having issues with this, try running the appropriate opengl-update command and making sure your glx is working.Code: Select all
wine WoW.exe -opengl
The goal of openging WoW now is to get the updater going, which is why we're still using regular wine. I've had cedega die a few times at this point (their WoW support is still fairly limited :-/) . Anyway, try logging on, and it should kick you back into the updater. Now you can choose which method of getting the update you want to do.
1) Wait for the Blizzard updater to download it.
2) Use google to find the file (just copy and paste the name of the file into it.
If the updater is going quickly, choose the first option. If it's going slowly, choose the second option.
Now that you've got the update, you'll need to run it manually. It should be in the same directory that your WoW.exe is in, so I'll assume that it is. RunThis will take a bit of time.Code: Select all
wine <patch name.exe>
Now you're all set to play! Well, almost. The last thing you need to do is add the following line to the WTF/Config.wtf file in your WoW directory:That will prevent your screen from glitching out if you die.Code: Select all
SET ffxDeath "0"
Cedega:
Now is when we'll switch to cedega. Run WoW.exe with cedega (without -opengl for now). Everything should start up as normal. If you don't have a cursor, skip down a bit for that fix. Now you should be able to play the game normally though.
D3D Cursor fix
Download this file. Untar it, then go into that directory. You'll need to run the game to see what the EXACT name of the WoW window is called in your desktop environment/window manager. If you're using the D3D version, you can probably just leave it as it is to have it work, but no guarantees about that.
Anyway, there's 3 files. Makefile, wowfix, and wowfix.c. This is so that you can rebuild wowfix if the window name is set incorrectly. You can change the name of the window that it looks for in wowfix.c on line 20 where it says #define WINDOW_NAME. If you do that, you'll need to delete wowfix and run 'make' to build it again.
What this file does is simple. It forces the cursor to show up in cedega since sometimes it gets buggy and decides to hide itself. To use it, you just fire up WoW, then execute the wowfix. I put it somewhere in my PATH so that I don't have to type the directory that it's in every time.
Performance fixes/tweaks:
Firstly, turn off all pixel shaders and filters in the game settings. I turned off vsync too since it was getting uppity. Also turn off the pixel shaders manually in the cedega config. You can find this in ~/.transgaming/config. SetThis turns off the pixel shaders in cedega itself. Just to be certainCode: Select all
"VertexShaders" = "Y" "VertexShaderMode" = "Hardware" "PixelShaders" = "N". You may also notice AA filtering just above these two options. It's up to you whether or not you enable it. Things may look nicer, but it may slow things down as well. I run with max AA.
Cosmos:
Works perfectly. Just download a version and copy the Interface directory to the appropriate place. That's all there is to it.
OpenGL mode:
The reason I don't use -opengl with cedega is simple; it causes the game to crash any time you enter a building because of a minimap-related glitch. Pretty big glitch, eh? To get around this, you can do one of two things:
NEEDS COSMOS
1) Edit the MiniMap.xml file in Interface/FrameXML. You'll be making the following change:Where the line with a '+' is the line that is being added. That should hide the minimap automatically when you enter a building, but I can't guarantee it works since I'm running happily in the d3d version with my wowfixCode: Select all
<Scripts> <OnLoad> Minimap.timer = 0; + ToggleMinimap(); Minimap_Update(); this:RegisterEvent("MINIMAP_ZONE_CHANGED"); </OnLoad> <OnEvent> Minimap_Update(); </OnEvent>.
EDIT:
Apparently with cedega 4.3, opengl mode is fixed so that the minimap no longer causes this crash. If you're using 4.3, disregard the above section.
DOESN'T NEED COSMOS
2) Use the d3d version (without -opengl).
Those are your two options as far as opengl mode is concerned.
I can't remember any other things that need to be said on the topic (except to remember that you're running X in 24 bit mode and WoW is set to do the same), so I'll just say that I've been playing since the final stress test before the open beta and I haven't noticed any performance changes along the way. It still runs perfectly.
I play in 1280x1024 resolution with maximum detail in the game config, and I play it inside E (enlightenment 16.7.2) without issues. There are a couple things that might irritate you if you aren't aware of them prior to doing them though. If you alt+tab out of the game while holding a button (the walk forward button, for instance) you will continue to do whatever that button makes you do (walk forward in this case) until you switch back to the game and press that button again.
Another slightly irritating issue is when you do the abovementioned button pushing, and then turn caps lock on or off while outside the game. For me at least, that had the effect of creating two different caps lock environments. In one (the game) the caps lock was disabled, but everything was uppercase. In the other (outside the game) the caps lock was disabled, but everything was lowercase. That meant that to speak in game without pissing everyone else off I had to keep the caps lock on. To fix this, I just had to recreate the situation (switch out with a key pressed and toggle the caps lock). Or something like that anyway. If it's really irritating you, just restart the game.
Have fun!
EDIT:
Water slowdown fix:Seems to work on some systems, mine didn't need it. YMMV.Code: Select all
;; WoW [AppDefaults\\WoW.exe\\Version] "Windows" = "win98" [AppDefaults\\WoW.exe\\d3dgl] "FixedProgram" = "No"
Wine section:
Very simple. Just build wine-cvs using this patch, install using the above method, and then run with. Works perfectly here and I won't be using cedega any more.Code: Select all
wine-cvs WoW.exe -opengl
I'm curious if it will work with standard wine since the other linux guys hacked up some special version of wine to make it work with the wow beta earlier.
MOD EDIT: Added quote.
-- Deathiwng00
.