Any World of Warcraft / Wine successes with 8.42.3?

[chrisr]

Previous versions of fglrx ran World of Warcraft's login screens fine, but then crashed when I tried to enter the Realm. However, 8.42.3 just gives me a blank black window and nothing else (apart from music...).

Does anyone have any Warcraft success stories to share, please?

[chabo]

I play WoW with Cedega and run fine except FPS :)

[chrisr]

I play WoW with Cedega and run fine except FPS :)

Can you post your ATI hardware model and xorg.conf, please? Also, are you using the SLUB or SLAB memory allocator in your kernel?

Also, have you tried playing using just Wine instead of Cedega?

Thanks,
Chris

[chabo]

ATI 1950XTX, x86_64 2.6.22-gentoo-r8, SLUB, Cedega 6.0.2
I've tried Cedega only. I have to check Frame Buffer Objects option in Cedega(without, it has much more FPS, but it flicks).

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "DesktopSetup" "horizontal"
Option "XAANoOffscreenPixmaps" "true"
Option "TexturedVideo" "on"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "MaxGARTSize" "256"
Option "UseFastTLS" "1"
Option "UseInternalAGPGART" "no"
EndSection

[givemesugarr]

Option "UseFastTLS" "1"

try setting this to 0. it should run a little faster with fglrx.

[Zargoon]

SWEET! I got it working. I purged wine from my harddrive then reinstalled it after I had installed the new drivers. Then I made the following changes in my xorg.conf

Under "SeverLayout"
Option "AIGLX" "False"

And Under "Extensions"
Option "Composite" "Disable"

And it worked. Tell me if you have any luck.

[Zargoon]

Oh I realize that having AIGLX and Composite may not make a difference at all I just did it at the same time that I disabled vertex shaders in wow. When vertex shaders are enabled it doesn't work right.

Once I reinstalled wine It was like half the game would render and I could log in and only see certain graphics like the menu. If was from there that I disabled vertex shaders logged out and it started working. You may need to fine the code that disables vertex shaders in the config.wtf file as I don't know what it is.

[teroedni]

Previous versions of fglrx ran World of Warcraft's login screens fine, but then crashed when I tried to enter the Realm. However, 8.42.3 just gives me a blank black window and nothing else (apart from music...).

Does anyone have any Warcraft success stories to share, please?

You need to edit the wine register

Registry Tweak for FPS Boost

Open a terminal window, (konsole/terminal/x terminal etc..), type regedit and press enter. This will start the Wine equivalent of the windows registry editor. If you are familiar with using the registry editor under windows then this is pretty much the same.

1. Find HKEY_CURRENT_USER\Software\Wine\
2. Highlight the wine folder in the left hand pane by left clicking on it. The icon should change to an open folder.
3. Click right on the wine folder and select [NEW] then [KEY].
4. Replace the text "New Key #1" with OpenGL (CaSe Sensitive).
5. Right click in the right hand pane and select [NEW] then [String Value].
6. Replace "New Value #1" with "DisabledExtensions" (CaSe sensitive).
7. Then double click anywhere on the line, a dialog box will open.
8. In the value field type "GL_ARB_vertex_buffer_object" (without the quotes).

Note: If you are unable to rename the newly created key "New Key #1" to "OpenGL" then expand the left hand pane of the regedit window using the vertical divider bar. You should now be able to change it. A known bug in Wine is causing this unwanted behavior.

You should see a significant performance gain.




This was taken from http://www.wowwiki.com/Linux/Wine

I had to add a second option to number 8 in order to get my hd2600 working.

GL_ARB_vertex_buffer_object;GL_ARB_vertex_program

And heres an image showing it:)

http://img484.imageshack.us/my.php?image=screenshotregistryeditonf0.png

[W.Russell]

Have you tried working with WoW in a window or in a emulated desktop?

[chrisr]

Oh I realize that having AIGLX and Composite may not make a difference at all I just did it at the same time that I disabled vertex shaders in wow. When vertex shaders are enabled it doesn't work right.

So I get a completely black screen if I have

SET pixelShaders "1"

and I get a corrupt / incompletely rendered screen if I have

SET M2UseShaders "1"

However, I can at least use

SET M2UsePixelShaders "1"

The game is also refusing to run for me in D3D mode, and I've needed to disable the GL_ARB_vertex_buffer_objects extension for OpenGL mode via the Wine registry.

[cjr2k3]

I have the same problem, refusing to start in D3D.

Anyway my Mobile X1400 get the all black textures except inside structures and I can see the menus and stuff.

Does the things described here correct the problem? Or should I stay with 8.37? (or should I move to 8.40?)

I had great faith in this latest release from ATI but since I only need my graphic card for WoW, no use to change if I can't play.

[chrisr]

Anyway my Mobile X1400 get the all black textures except inside structures and I can see the menus and stuff.

What you're describing sounds like what I was seeing when the vertex shaders were enabled, so

SET M2UseShaders "0"

would probably help you. Alternatively, you could tell Wine to ignore GL_ARB_vertex_program, with probably the same effect.

[cjr2k3]

The bottom line is:

Do I get any improvement? Or I'm good as I am?

Anyway thanks for the help, finding this foruns very informative :D

[chrisr]

The bottom line is:

Do I get any improvement? Or I'm good as I am?

8.42.3 is the first driver that has worked at all on my FireGL chipset, and I've had to hack it to believe it's a X1700 to get this far! So I cannot possibly say whether your situation would improve, but mine is infinitely better :).

[cjr2k3]

Ok!

I'm trying again with the tips above. Since envy is released is easy to rollback now :D

Anyone else has something to say about if I should change or stay with what I have?

[Bigon]

I have some problems too (mobility 9700)

in opengl mode some textures are missing and in d3d the textures are completely mixed

edit: disabling shaders fix the problem in opengl mode

[Merritt]

SET M2UseShaders "0"

fixed the missing textures problem I was having and for the first time I can run WoW in opengl mode... however when I started the game I was running 60 - 90 FPS... but after 5 or 10 mins it dropped to 4 fps... anyone know how this can be improved? (Yes I've followed the guide for Ubuntu, with the registry settings and all that to improve performance).

[eoceoc]

Wine not run for me; Cedega works however the FPS is low. I got about 10-20 FPS in town, with a Q6600 + 2900XT!!! I guess software renderer could even be faster:(

[wylfing]

Does the things described here correct the problem? Or should I stay with 8.37? (or should I move to 8.40?)

I had great faith in this latest release from ATI but since I only need my graphic card for WoW, no use to change if I can't play.

All I can say is that WoW runs (that is, after disabling vertex shaders). However, the FPS is noticably worse than 8.40, which wasn't great to begin with, and the minimap doesn't display inside major cities. Stick with 8.40 until they get things sorted out.

Edit: Oops, forgot to say that I use wine. Card is Radeon Mobility X300.

[Alistair]

8.42.3 is the first driver that has worked at all on my FireGL chipset, and I've had to hack it to believe it's a X1700 to get this far! So I cannot possibly say whether your situation would improve, but mine is infinitely better :).


Chris!
are you telling me the X1650Pro AGP is now running with AGPMode=8???
PPLlllleeeeaase!

[Malikith]

Chris!
are you telling me the X1650Pro AGP is now running with AGPMode=8???
PPLlllleeeeaase!

Well you know my old story, it was the same as yours, and mine runs at 8x now instead of 0x with 8.42. So yours SHOULD run at 8x now too.

[MagicTempest]

Where can I find the agpmode? My xorg.0.log says the following:


root@meradin:/home/tempest# less /var/log/Xorg.0.log | grep agp
(II) fglrx(0): [agp] Mode=0x1f00421b bridge: 0x10de/0x00e1
(II) fglrx(0): [agp] AGP v1/2 disable mask 0x00000000
(II) fglrx(0): [agp] AGP v3 disable mask 0x00000000
(II) fglrx(0): [agp] enabling AGP with mode=0x1f00431a
(II) fglrx(0): [agp] Remapping MC AGP space (new MCAGPBase = 0xc0000000)
(II) fglrx(0): [agp] AGP protocol is enabled for graphics board. (cmd=0x1f004312)
(II) fglrx(0): [agp] graphics chipset has AGP v3.0 (native mode)


Already found something :)


[ 85.575272] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode


WoW runs for me. The only strange thing I have is the fact that XFCE ( or XFWM ) appears to block 3d rendering for WoW. Whenever I use XFCE I only get 1-4fps, but when I use gnome for instance my fps leaps up to about 40.
Does anyone have any experience with this?

[vultaire]

WoW runs for me. The only strange thing I have is the fact that XFCE ( or XFWM ) appears to block 3d rendering for WoW. Whenever I use XFCE I only get 1-4fps, but when I use gnome for instance my fps leaps up to about 40.
Does anyone have any experience with this?

I'm just gonna throw this tidbit out there. I haven't read everything here that you've posted, so if I missed an important detail, sorry.

XFCE uses a compositing window manager. I know from experience using Compiz on my Nvidia system that opengl frame rates seem to take a considerable dive while such a WM is enabled. If you have compositing on and XFCE is using it, that -could- be why you're experiencing slowdown. Since you say Gnome works fine, I'm betting that's the problem.

Hope this helps.

[Ren Höek]

I just wanted to ask for some experience with the 7.11 (8.43) driver.
With the 8.42 I had to switch of shaders to get WoW running. But this made the game really slow.
Does 7.11 solve this problem? What about the frame rate? Any increase?

I hope someone has tried the new one out yet, so I won't have to install it and than reinstall 8.40 again :)...

[vultaire]

Can't speak for WoW personally; but I seem to have other issues with the 7.11 Catalyst driver. On my ATI Xpress 1100 system I play another game (StepMania) as well, and once I upgraded to the 7.11, I was getting constant hard-locks of the system when running that. Downgraded to the 8.42 driver again, and the problem went away. Didn't try WoW since the problems with SM were pretty well a deal-killer. YMMV of course; maybe you'll get lucky. =)

[Redeeman]

And here i thought the new drivers would actually work... guess it was naive to think ati/amd could actually make working drivers..

oh well, no ati/amd for my next computer which ill purchase soon

[cjr2k3]

I did got a huge performance increase with 7.11. But with the memory leak issue I could only play like 10min before the game lock down. Hopping for a fix in the next release. Using 8.40 now with no issues.

[oliver]

I had the same problem after installing 2.3. I just closed it out (via esc so it would resceive a proper quit) and restarted it and all was fine again.

You may want to try logging in once via directx (omit the -opengl flag) so the new config settings are saved and then restart using the -opengl flag, works like a charm aswell.

[cjr2k3]

I tried that. No luck for me, the leak is associated with every frame rendered. I let glxgears running for 10~15min and when I got back I got full ram (1Gb) + swap full (3Gb)

Waiting for 7.12, but 8.40 is fine anyway.

[Tsume]

So I get a completely black screen if I have

SET pixelShaders "1"

and I get a corrupt / incompletely rendered screen if I have

SET M2UseShaders "1"

However, I can at least use

SET M2UsePixelShaders "1"

The game is also refusing to run for me in D3D mode, and I've needed to disable the GL_ARB_vertex_buffer_objects extension for OpenGL mode via the Wine registry.

Same story here and I'm on 7.11

Lucky I found this post or it would never ever ever run.

Ubuntu 7.10 (Gutsy) w/ Wine 0.9.50 and Catalyst 7.11

[oliver]

Same story here and I'm on 7.11

Lucky I found this post or it would never ever ever run.

Ubuntu 7.10 (Gutsy) w/ Wine 0.9.50 and Catalyst 7.11

didn't do any of that shader stuff, only the opengl thing in the registry, but had that for ages. After loging in and stuff successfully it's all fine

i'm having some graphical glitches on the menuscreen etc (not after a fresh reboot however) lik ehalf the screen being renderd, textures missing, but it's all fine in game. I HAVE noticed that when i lgo in a toon WITHOUT ct_viewport mod (set to something a little smaller, i hide the bottom where the buttons are) it's all fine, but do have the half screen being drawn with the toon though. I blame the addon itself, as i doubt a vanilla addonless game would have that bug, but if you have only half a screen drawn INgame, try gettind ct_viewport mod and change the size of your viewport (you do need ct_core with it to configure it)

[krnlg]

I'm using a PCI-E Radeon X1650 on a 64-bit platform and with the new drivers (having tried 7.11 and 8.42.3) Warcraft runs with noticably improved FPS when I disable shaders, however it likes to randomly crash with loads of this error output to the terminal:

fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x2e at ctx(0x328b68,L"fglrx_dri.so"), for debug_info(abbrev:0x5bf01b8,symt:0x5c04074)

before doing a traceback.

I've tried various other versions of Wine all with the same result.

The frustrating thing is that I get the nicely improved fps for random periods of time before it crashes, and then I have to go back to the old, slow drivers and cry..
I've tried both amd64 and i386 wine packages with the same result; is this something specific to these drivers with 64-bit?

Has anyone else had this problem?

I should add that I'm running Debian Etch (for the most part) which uses Xorg 7.1.

[oliver]

64 bit may be your problem then mostlikly. Or your having serious memleak issues, as the 7.11 is known to be leaking memory.

For me, I can play it hours uppon hours. Though some water parts do make it crash (the little pool with the two fishies before the wailing cavern instance, took me 6 reboots to get out of the water, and then went on again for hours without a hitch.)

[krnlg]

Well its not the memory leak issue, because although it does consume more and more memory for me, I think it would probably crash after maybe an hour or so rather than a few minutes or (sometimes) less; it doesn't run for long enough to use all my RAM.

*sigh* running a 64-bit system can cause so many niggling issues it seems.
A google search on that error message (well the first part of it) turns up about 5 results, only one of them in english, which was talking about a different application under Wine.

Hopefully the new version will work :rolleyes: but even so, this new driver series is a big improvement performance-wise at least.

no-one else with any information?

[teroedni]

I found some important settings that may help us when it comes to wow crashes

in the device section put

Option "Capabilities" "0x00000800"
Option "UseFastTLS" "off"
Option "KernelModuleParm" "locked-userpages=0"

[Spydr4590]

I thought I would bump this with the working guide (http://ubuntuforums.org/showthread.php?t=654681) I made for 7.12 driver install of ATI.