Then run the script with sudo.
could sudo be added to the script?
And now I get a blank Xserver.
I can switch back with crtl+alt+f keys.
AlsoI ran the script with out the sudo to make sure I got a error that I could get to.Code:
X: user not authorized to run the X server, aborting.
cd: 5: can't cd to /home/drezliok/.wine/drive_c/Program Files/World Of Warcraft
wine: could not load L"c:\\windows\\system32\\WoW.exe": Module not found
Ok I got it to work for me but I have to use crtl+alt+f7 keystroke to get back into my other Xserver. the game ends up on f9.
Here is my script edited to work for me.
I took out the change of directory and told it where to go at the display line.Code:
X :3 -ac & # Launches a new X session on display 3
sleep 2 # Forces the system to have a break for 2 seconds
DISPLAY=:3 /usr/X11R6/bin/wine ~/.wine/drive_c/Program\ Files/World\ Of\ Warcraft/WoW.exe -opengl # Launches WoW
this fixes a resolution issue I have with wine and games. Wine would all ways throw me into 1600X1200. And I hate that.
Now I would like to know how to add sudo to the script.
Anyone know how I can kill the Xserver when I'm done playing?
I tried the first tweak, yet I haven't seen any increase in framerate. In fact, I have about 18-22 fps. I have a pretty decent rig:
AMD Athon64 3800
250 GB harddrive
So I feel like I have decent enough hardware to run at a better speed than what I get.
I'm currently using Wine 0.9.22, and have no problems what so ever.
Just wondering if my framerate should be where it's at, or maybe higher.
EDIT: Sorry, I'm running Dapper, as well.
try using the latest wine 0.9.25 (not sure but it may help)
1. Make sure you're using 0.9.25.
2. Make sure you're using OpenGL (simplest method is to open wow with: wine WoW.exe -opengl)
3. Make sure you're using tweak #1.
4. Make sure your color depth is set to 24 bits.
5. Try tweak #2.
I've got roughly the same setup as you and I'm getting between 40-100 FPS with the exception of 25 in Grom'gol.
Really seemed to help. Now when I'm indoors, I get around 70fps! Much better!
A work around for the sudo problem is making a launcher to the script.
You will need the launcher to run it in a terminal, so it can prompt for the password.
add the following line to the file:Code:
$ sudo visudo
Where "username" is your username. Duh. This line allows "username" to run /usr/bin/X (which is the command that requires root privileges in the wow launcher script) without a password. This will allow you to run the launcher without opening a terminal.Code:
username ALL=NOPASSWD: /usr/bin/X
Now, I'm no expert. For all I know, this is a major security hole. So use at your own risk. :P
I think I'll leave it as it is.