I've got an nVidia 8800GTX, using the 177.80 drivers, and having the same problem.

It may be irrelevant, but every report I've seen about this so far is from users with nVidia cards.  Any ATI users out there who can report in?

I've somehow gotten it working with much higher fps (from 5fps in Black Temple, up to 40-80 now) after a reboot and tweaking multiple config options (Multisampling and fullscreen glow mostly).

Attached is my Config.wtf. Can you try this?

Created attachment 17121 [details]
Config.wtf

I am also NOT allowing Pixel Shader in winecfg.

I gave Adys' configuration a try and still have very poor framerates (7-15 fps in battlegrounds, opposed to 60 fps in Windows on the same hardware). Running wine-1.1.7 on Ubuntu 8.10 with NVIDIA UNIX x86_64 Kernel Module  177.80 on a GeForce 7600 GT. The Pixel Shader option in Winecfg doesn't seem to have any effect.

If this is a regression please run a regression test:
http://wiki.winehq.org/RegressionTesting

This is not really a regression, since the problem is related to a new version of the program, not of wine. Blizzard did a serious overhaul of their graphics engine for the new expansion, and this code has just gone into the live version in preparation for its release.

Since 3.0 came out, I have upgraded from a geforce 7900gs to a 9800gt, with essentially no effect on framerates. What I would like to see, however, is if someone has compared wine framerates with windows framerates when the windows version is running in opengl mode as well (since the slowdown could be in blizzards opengl interface, not in wine)

Created attachment 17129 [details]
Wow Config.wtf

my wow Config.wtf as generated by the game. no manually added lines

I have 54-60 fps simply by adding  -OpenGl in the launch line ( e.g. ~$ wine /path_to_wow/Wow.exe -OpenGl ) 

No tweak/modiff made in [url="http://bugs.winehq.org/attachment.cgi?id=17129"]Config.wtf[/url]  .

GF 7300 GT 256Mb on Ubuntu Hardy ( 32 bits version ) with 177.80 drivers

(In reply to comment #8)
> I have 54-60 fps simply by adding  -OpenGl in the launch line ( e.g. ~$ wine
> /path_to_wow/Wow.exe -OpenGl ) 
> 
> No tweak/modiff made in
> [url="http://bugs.winehq.org/attachment.cgi?id=17129"]Config.wtf[/url]  .
> 
> GF 7300 GT 256Mb on Ubuntu Hardy ( 32 bits version ) with 177.80 drivers
> 

Does your fps hold reasonably in highly populated areas? (such as Ironforge or Shattrath)

Tested FPS in higly populated areas as asked ( sorry i didn't do'it before) and the reult is:  Orgrimmar - 17-20 fps and latency 38 ms ( so is not caused by latency) / Shattrath 15-20 fps latency 43 ms .At this point i can only say that i confirm the bug. 

Could users having this problem try this?

- Go in winecfg, graphics and disable pixel shaders
- In game, go in graphic options and disable Triple Buffering as well as Full Screen Glow
- Eventually, try disabling the GL_ARB_vertex_buffer_object extension with http://www.wowwiki.com/Wine_(software)#Registry_Tweak_for_FPS_Boost

For me, it fixed this bug as well as bug 15926 and bug 15927

(In reply to comment #12)
None of those suggestions had any effect for me except the registry tweak, which actually had a negative impact on my framerates.

(In reply to comment #12)
> Could users having this problem try this?

I had no effect from shaders, glow or triple buffering (though I have vertical sync disabled for performance anyway). I had a negative effect from the registry change to disable the GL_ARB_vertex_buffer_object extension.

In shattrath I'm holding 9-14 fps with all of the suggestions above, 15-20 with all of them except the registry change.

I have also tried changing back to Wine 1.1.5, with and without the above. In 1.1.5 I still have low framerates, but not *as* low. It's most pronounced in Alterac Valley, where I had 7-10 fps in 1.1.7 and 15-20 in 1.1.5.

Ah, that's an important point. we should add our wine versions to any data we've posted.. 1.1.4 here, since it's what's marked stable in gentoo atm. I'll try out other versions and see what info I can get.

I have seen a minor FPS drop with 3.0. I have however, seen massive stuttering (100ms freezes every few seconds)

I posted more info on the seeming-more-related bug here:
http://bugs.winehq.org/show_bug.cgi?id=15926

(In reply to comment #12)
> Could users having this problem try this?
> 
> - Go in winecfg, graphics and disable pixel shaders
> - In game, go in graphic options and disable Triple Buffering as well as Full
> Screen Glow
> - Eventually, try disabling the GL_ARB_vertex_buffer_object extension with
> http://www.wowwiki.com/Wine_(software)#Registry_Tweak_for_FPS_Boost
> 
> For me, it fixed this bug as well as bug 15926 and bug 15927
> 

Following the instructions on the http://www.wowwiki.com/Wine_(software)#Registry_Tweak_for_FPS_Boost dropped my fps from  17-20 in Shattrath to 4-8fps (witch make the game almost impossible to play ).
Wine 1.1.7 
Restored previous settings.

I get really low frame rates 15-20 and I have had realy bad shuttering. It was so bad in instances that I could not play. I changed to -OpenGl on my wine wow.exe line and the shuttering went away. I still get lousy performance out of my GeForce 8700GS 512MB Vram and my AMD 64 x 2 4200+   It's worse where I see for long ranges like the top of the aldor sanctuary, however adjusting the graphics settings don't do much for the frame rates. So I get crappy frame rates whether I actually see far or not.

*** Bug 15926 has been marked as a duplicate of this bug. ***

Only confirming.

Went from a reasonable 20 - 100 to 2.0 - 10.

Lowest I saw was 1.1 in MH .... Yes, that's ONE point ONE. It was really scary.

Can confirm the fps drop.

Using 32Bit Debian with amd quad phenom - NV8800GT/8600GT (with 177.80 driver)
Wine-1.1.7 and 1.1.8. (Verified on 2nd system with amd dualcore and NV7600/wine 1.1.7). Wine compiled with gcc-4.3 and target optimization für amd cpu's.

10-20 fps in OpenGL mode (Shat and other crowded places).

Also, changing ingame graphic options doesn't solve the problem.

Sometimes i also see the stuttering as noted above.
My (old) trick to reduce stuttering in WoW in a multicore setup (=> pin the wow-processes/threads to a dedicated CPU-core (=>set cpu affinity with schedtools)) won't work here and has nearly no impact in this situation. (As opposed to pre 3.0x version).

if there's anything i can do (eg. compile with special options, debugging sessions...etc... tell me and i'll volunteer)

btw: wine can't fix BETA quality software - only trying to reduce the impact -  salute to all wine developers, your doing a very good job :-)

I've tried compiling with different levels of optimization, though now I'm faced with crash after crash in little to no playtime. I'm going to get a new graphic card either way.

Disabling shaders definitely helps a lot though, the fps drop is minimal since then. At least for me...

I'm running 8800gtx with the 177.80 drivers, 2 gigs of ram, AMD 6400+ dual core running under opensuse 11 and Wine 1.1.8 in OpenGL mode(D3D crashes the game). I've noticed a big FPS drop with the new patch. BT was perfectly playable with about 40-60 fps during intense boss battles and trash. After the patch it chugs along at 15 fps, which is playable its just hard on the eyes. Sunwell, Battle for Mount Hyjal, and Serpentshrine Cavern also surfer.

Also since the time I've been in Northrend (only lvl 72 ATM) when inside Warsong Hold I get decent FPS but it jitters every 2 seconds. Enabling or disabling GL_ARB_vertex_buffer_object shows no obvious difference ether. 

When its all said and done, I confirm this bug.

I recently installed the latest TryWoW.exe on windows and then copied it to Linux. I got it working with opengl and some extra settings like 'fxGlow 0'. I am on a laptop with an ATI Mobility Radeon X700 chipset and the framerate is in 800x600 around 10 fps with all effects low. I have tried many different settings in wine.. Pixelshader off, sound off, all settings, fxGlow 0, fxSpecial 0, etc.

On windows I can run the game in 1280x800 at a 30 to 40 fps. I will check if I can run the game on Windows in opengl and see if that has a bad performance too.

So I think this problem is not only limited to Nvidia chipsets.

Tried to use config.wtf posted by adys on an Athlon64 3400+ & radeon x1900.  Significant framerate improvement (from 5-10 fps in IF, to  25-40).  Minimap will not display while inside and something seems to be triggering some tearing a few seconds into the game.  Running ubuntu intrepid and wine 1.1.9.  Tearing seems to be related to the minimap error as it will only occur when transitioning indoors.

I've now tried running Wow in OpenGL and D3D mode on Windows XP. My experience is that while both modes provide higher framerates than Wine, D3D is much better performing for my hardware in Windows than OpenGL. In particular, I've seen framerates of:

(all in the horde stronghold of Alterac Valley)
Windows XP, OpenGL: 29 fps average
Windows XP, Direct3D: 51 fps average
Wine 1.1.5, OpenGL: 14 fps average

(In reply to comment #26)
> I've now tried running Wow in OpenGL and D3D mode on Windows XP. My experience
> is that while both modes provide higher framerates than Wine, D3D is much
> better performing for my hardware in Windows than OpenGL. In particular, I've
> seen framerates of:
> 
> (all in the horde stronghold of Alterac Valley)
> Windows XP, OpenGL: 29 fps average
> Windows XP, Direct3D: 51 fps average
> Wine 1.1.5, OpenGL: 14 fps average
> 

(In reply to comment #23)
> I'm running 8800gtx with the 177.80 drivers, 2 gigs of ram, AMD 6400+ dual core
> running under opensuse 11 and Wine 1.1.8 in OpenGL mode(D3D crashes the game).
> I've noticed a big FPS drop with the new patch. BT was perfectly playable with
> about 40-60 fps during intense boss battles and trash. After the patch it chugs
> along at 15 fps, which is playable its just hard on the eyes. Sunwell, Battle
> for Mount Hyjal, and Serpentshrine Cavern also surfer.
> 
> Also since the time I've been in Northrend (only lvl 72 ATM) when inside
> Warsong Hold I get decent FPS but it jitters every 2 seconds. Enabling or
> disabling GL_ARB_vertex_buffer_object shows no obvious difference ether. 
> 
> When its all said and done, I confirm this bug.
> 

Could you try the new nVidia 180.11 beta drivers? I've had *huge* performance improvements with them.

If you're faced with further crashes with those beta drivers, please have a look at bug 16311.

(In reply to comment #24)
> I recently installed the latest TryWoW.exe on windows and then copied it to
> Linux. I got it working with opengl and some extra settings like 'fxGlow 0'. I
> am on a laptop with an ATI Mobility Radeon X700 chipset and the framerate is in
> 800x600 around 10 fps with all effects low. I have tried many different
> settings in wine.. Pixelshader off, sound off, all settings, fxGlow 0,
> fxSpecial 0, etc.
> 
> On windows I can run the game in 1280x800 at a 30 to 40 fps. I will check if I
> can run the game on Windows in opengl and see if that has a bad performance
> too.
> 
> So I think this problem is not only limited to Nvidia chipsets.
> 

I think when you do this, you will see that windows suffers a bit using onenGL framework..  The problem is not so much windows versus wine than it is DirectX support versus OpenGL support of WoW.  

Do not expect wow to run as good in wine as it does on windows unless some extreme progress on DirectX support on wine is made.  Blizzard

I'm running kubuntu x64 bit, Geforce 8800-GTX using 180.11 NVidia drivers.  The new beta drivers did actually provide a lair level of inprovement in overall gameplay, but in "pretty" areas where there is plenty of lighting, shading, and density to draw, they still suffer on the OpenGL platform far worse than they would on DirectX.

Blizzard would have to almost re-write the openGL extensions of its game to truly fix the issues we are experiencing, so I think there is only so much improvement to yield by new NVidia drivers or new versions of Wine.  Your best bet?  Better DirectX support in wine... 

(In reply to comment #28)
> (In reply to comment #24)
> > I recently installed the latest TryWoW.exe on windows and then copied it to
> > Linux. I got it working with opengl and some extra settings like 'fxGlow 0'. I
> > am on a laptop with an ATI Mobility Radeon X700 chipset and the framerate is in
> > 800x600 around 10 fps with all effects low. I have tried many different
> > settings in wine.. Pixelshader off, sound off, all settings, fxGlow 0,
> > fxSpecial 0, etc.
> > 
> > On windows I can run the game in 1280x800 at a 30 to 40 fps. I will check if I
> > can run the game on Windows in opengl and see if that has a bad performance
> > too.
> > 
> > So I think this problem is not only limited to Nvidia chipsets.
> > 
> 
> I think when you do this, you will see that windows suffers a bit using onenGL
> framework..  The problem is not so much windows versus wine than it is DirectX
> support versus OpenGL support of WoW.  
> 
> Do not expect wow to run as good in wine as it does on windows unless some
> extreme progress on DirectX support on wine is made.  Blizzard
> 
> I'm running kubuntu x64 bit, Geforce 8800-GTX using 180.11 NVidia drivers.  The
> new beta drivers did actually provide a lair level of inprovement in overall
> gameplay, but in "pretty" areas where there is plenty of lighting, shading, and
> density to draw, they still suffer on the OpenGL platform far worse than they
> would on DirectX.
> 
> Blizzard would have to almost re-write the openGL extensions of its game to
> truly fix the issues we are experiencing, so I think there is only so much
> improvement to yield by new NVidia drivers or new versions of Wine.  Your best
> bet?  Better DirectX support in wine... 

I tested the game in windows using opengl and I cannot play the game decently as I get opengl corruption in the 3d characters but that is probably due to old catalyst 7.12 drivers I have on this laptop using the omega drivers.

I have 1Gb RAM in my laptop and in Windows WoW runs perfectly fine with all details on low (the laptop is not the best). But to have a decent frame rate on Linux and Wine 1.1.9 I had to upgrade to 1.5Gb RAM. Running Kubutu 8.10 (KDE4) and Wine 1.1.9 and WoW 3.0.2 is too much for 1Gb of RAM. So if you experience stuttering when walking around but the framerate is okay if you don't walk and don't have other players around it might be you need more RAM.

The only other problem I have is that when entering a cave or a home with the minimap turned on, that I get random frames on the screen and text is not displayed correctly before. But that is a diferent bug I think.

I used the config.wtf of Adys to get it running properly in 1024x768. In windows I can do 1280x800.

Some updates on this - I currently get NO FPS issues, but I do get some crashes.

As of nVidia 180.11, in OpenGL mode I get *great* FPS now - maybe 3-5 less than in windows OGL mode. All settings maxed, shaders, bloom, 1680x - no advanced shadows (which arn't supported in blizzards OGL engine yet). Loading from disk can be a little slower, but other than that this game runs VERY well on linux. The disabling vertex buffers doesn't seem to do anything anymore.

The only problem for me now is crashes - Every now and then, especially reproducible in certain areas of the game world - I'll get massive graphical corruption. Polygons everywhere, textures all wonky, 2FPS. This'll last for a few seconds before a segfault. However, I am more inclined to believe this is an issue with nVidia's newest drivers, which suffer from some internal-state degradation issues for me in Non-wine programs, and generally are not very release quality.

Also, something WoW/NTFS-3g is doing makes running this game off an NTFS partition load/unload *extremely* slow - like 10-20x vs an XFS partition (though it works fine at full FPS once loaded).

There's been a fair few changes to shaders in recent git commits (post 1.1.10). Since shaders seemed to be the problem, could this be retested by more users with last git?

(In reply to comment #31)
> There's been a fair few changes to shaders in recent git commits (post 1.1.10).
> Since shaders seemed to be the problem, could this be retested by more users
> with last git?
> 

I just compiled the latest wine-git and the minimap doesn't break anymore. However it does show the minimap of outside the building/cave and not the internal minimap. No garbled polygons etc.

Good thing is you can play it. I will do some endurance testing later in the evening.

(In reply to comment #32)
> (In reply to comment #31)
> > There's been a fair few changes to shaders in recent git commits (post 1.1.10).
> > Since shaders seemed to be the problem, could this be retested by more users
> > with last git?
> > 
> 
> I just compiled the latest wine-git and the minimap doesn't break anymore.
> However it does show the minimap of outside the building/cave and not the
> internal minimap. No garbled polygons etc.
> 
> Good thing is you can play it. I will do some endurance testing later in the
> evening.
> 

After more testing it still is not working well. I tested it in other buildings and it still break. So it is not better.

Running on a E6600 core 2 duo OC'd to 3ghz, 9800GTX nvidia card and 2GB of ram, getting 60-100FPS out in the open when no people are around, but in dalaran/orgrimmar/shattrath with 20+ people, or in 25 man raids the FPS drops down to 5-15. Pretty unplayable.

Using nvidia-drivers-180.11, wine-git from the 11th of december and the 2.6.27-gentoo kernel. Running -opengl (-d3d gives even worse performance).

Confirming that the bug is still not fixed as of the 11/12 wine.git.

After reading one of the last comments in AppDb i tried booting with the nopat kernel boot parameter. To my own suprise I got a big performance boost of 20-25 fps.

I can now play with all settings maxed except the new shadows.

My System:
Intel Core2 Duo T7700, 2.4 GHz
3Gb Ram
nvidia Quadro FX 570M (nvidia binary drivers 177.82-1)
Arch Linux 64bit, kernel 2.6.27.8-1

(In reply to comment #35)
> After reading one of the last comments in AppDb i tried booting with the nopat
> kernel boot parameter. To my own suprise I got a big performance boost of 20-25
> fps.
> 
> I can now play with all settings maxed except the new shadows.
> 
> My System:
> Intel Core2 Duo T7700, 2.4 GHz
> 3Gb Ram
> nvidia Quadro FX 570M (nvidia binary drivers 177.82-1)
> Arch Linux 64bit, kernel 2.6.27.8-1
> 

I just tried it. No change whatsoever.

Hello guys,

I compared Windows Wow (direct3d) and Debian wine WoW (opengl) and here are the data:

=== WHAT I DID:

* I copied Windows installation of WoW 100% to ReiserFS harddisk in Debian.

* I removed "Config.wtf" and after that I got my graphic options to full quality (disabled options: "Full-screen glow effect", "Death effect", "Triple buffering" disabled too although I never noticed difference with or without it).

* I use "-opengl" option.

* Pixel shaders are disabled in "winecfg".

* I removed the so-called "registry hack for FPS boost", and I found out its presence actually impacted my performance, although slightly (4-5 FPS difference, which is still much in raids). Removing the registry key helped.



=== ENVIRONMENT:

* Debian version: 5.0 (lenny)

* WoW version: 3.0.3

* Wine version: 1.1.10

* NVIDIA driver version: 173.14.09

* NVIDIA videocard: 7600GS (256 MB RAM)

* kernel: 2.6.26-1-amd64

* RAM: 3GB DDR-2 800MHz

* CPU: Pentium D 3.40GHz (dual-core)


=== OBSERVATIONS:

* Inside Dalaran, in front of Alliance bank, staying still and looking at a myriad of people running around: 13-16 fps (same in Windows)

* Running around inside Dalaran: 12-15 fps (same in Windows, sometimes even worse).

* Flying from Dalaran to K3 in Storm Peaks: 26-45 fps (Windows hardly ever gets above 30 fps while flying anywhere in Northrend). Seems to vary VERY MUCH, cannot really determine what from... still puzzled.

* Walking on ground mount outside K3: 25-50 fps (Windows hardly gets more than 35 in any ground riding at all in Northrend).

* Entering in high speed from outside to inside K3 *always* results in huge FPS drop: if I was at 45 fps, it drops to 20 fps in a second. I am suspecting network latency is the issue.

* Flying from K3 to Brunnhildar Village on swift flight mount (and back), maintaining low altitude from ground (20-30 meters so there are still lots of details to render): 35-60 fps! Windows gets 50-60 fps only outside Northrend, like riding in Azeroth or most of Outland. Windows NEVER gets above 40 fps in Northrend ANYWHERE.

* Ironforge bank: 13-21 fps. Windows can't beat that as well, it tops 18 fps there.


Something like conclusions:

Debian wine WoW setup works quite well, although the minimum FPS values are lower than Windows (generally). If Windows varies 20-40 FPS in an area, wine WoW varies 12-50. Also, as a general feeling, wine WoW seems bit more sluggish, meaning that entering new areas, quickly diving in populated area etc., gives you huge drop in FPS very quickly. I suspect the network stack is the culprit in this issue, but I really don't have the patience to do the necessary measurements with kernel-level tools.

But in overall, wine WoW is actually more responsive, meaning that when WoW "sleeps" for a short period because of doing screenshot, entering AH etc., wine WoW reacts considerably quicker. I blame the kernel resolution timer for that, but again, cannot be sure.

The last test I did was to try running wine WoW in another computer, far worse in hardware means, and was amazed to find out it actually held 10 fps inside Dalaran while lots of people were riding around! Pretty conclusive for me...

So, my conclusion would be that the struggle which wine WoW experiences in most setups is OpenGL support problems, or huge network latencies in populated areas. But in the end, think about it -- twice as worse computer compared to mine performed almost the same in Dalaran. It's gotta be the network.


Hoping to have given you some valuable data. Ask for more if I missed something crucial.

And finally -- I am not drawing conclusions for another's setups. I also found that certain options (see above) did improved my performance as well.


Dimitar P.

I have no proof for this, maby just call it a gut feeling; I think the/one of the reason(s) for the bad performance people are reporting here is caused by wine+wow not using multiple threads correctly. It spawns them allright, (about 10-15 of them), but only 1 of the threads are at 50% usage, while the others are at 0-1%.

Considering that WoW is CPU-bound on anything but a very very bad gfx card, this is going to cause a MAJOR FPS problem, especially in crowded conditions where addons and stuff is hogging a lot of CPU time.

Something to keep an eye out for when bug 11674 is solved maby?

(In reply to comment #38)
> I have no proof for this, maby just call it a gut feeling; I think the/one of
> the reason(s) for the bad performance people are reporting here is caused by
> wine+wow not using multiple threads correctly. It spawns them allright, (about
> 10-15 of them), but only 1 of the threads are at 50% usage, while the others
> are at 0-1%.
> 
> Considering that WoW is CPU-bound on anything but a very very bad gfx card,
> this is going to cause a MAJOR FPS problem, especially in crowded conditions
> where addons and stuff is hogging a lot of CPU time.
> 
> Something to keep an eye out for when bug 11674 is solved maby?

it seems that the conclusion of bug 11674 is that WoW does not multithread the rendering code. This has also been mentioned in the WoW official forums several times over the years; wow currently does not use multiple cores to the fullest extent.

While I notice the same FPS's posted in the busy areas you mentioned, I have seen them for quite some time.  I would LOVE to get better frame rates, but lets do a little reality check:

1) The Game supports OpenGL, but most people who develop in OpenGL will tell you its done rather sloppily in WoW.  This has been common knowledge for years. 

2) The target audience for this game is Windows users.  Therefore, most of the performance enhancing fixes for the game will be surrounding the DirectX extensions.

3)  Don't think Running a Geforce 8800GTX-OC or any other nice gaming card means the same thing in Linux as it does in windows.  Those gaming cards have unbelievable power when it comes to shaders, but without DirectX you cannot really unlock that power in your card in a Linux Operating System.  Case in point, my laptop has an internal Quadro-FX 1600M card and my FPS is almost double that of my Geforce 8800 in my desktop, both linux based.  Quadro-FX cards were designed with OpenGL acceleration in mind, Geforce cards were not.  Ergo, you WILL NOT have the same performance levels from platform to platform.

If you're getting 4-5FPS in a highly populated area, there is likely a fix for you, unless you are running a ridiculously old card or system.  If you're getting over 15-25FPS in highly populated areas, and getting upwards of 25-30FPS in non-populated areas, you're doing about the best you're going to do on a Geforce card with any sort of moderate graphical detail enabled.  If you want higher than that, my recommendation is to invest in a Quadro-FX card.  In the long run, if you want to game on linux, you will be happier with it.

  

Created attachment 20104 [details]
ugly wow perfomance hack

This hack prevents my fps drop below 10 in high action, highly populated aeras like 1k, av, sarth25 3D. It speeds up memory allocation and avoids excessive thread bouncing. I'm not sure whats the real cause of the thread scheduling issue, but apparently wow works fine without any scheduling at all.

(In reply to comment #41)
> Created an attachment (id=20104) [details]
> ugly wow perfomance hack
> 
> This hack prevents my fps drop below 10 in high action, highly populated aeras
> like 1k, av, sarth25 3D. It speeds up memory allocation and avoids excessive
> thread bouncing. I'm not sure whats the real cause of the thread scheduling
> issue, but apparently wow works fine without any scheduling at all.

Markus,

In my oprofile runs on .22 I did not see a lot of time being used in HeapAlloc/HeapFree while in "established state" (1/2 minute after loading game). As I said somewhere else I only see libGL processing.

Do you believe this bug may be have been fixed another way ?
Do you still see this behaviour ?

Thanks,

Update on this bug.

The performance drop is minimal, now. This may be improvements in Wine, or Blizzard improving their engine, or more likely both. 
Disabling or enabling vertex shader/pixel shader no longer has any visible impact on the game's performance.

Both in D3D and OpenGL modes, WoW has improved a LOT recently. Running the 180-185.x nvidia driver branch also helps, which may mean the nvidia driver had some bugs as well.

I think it's safe to close this bug as fixed.

Reported fixed.

Closing bugs fixed in 1.1.24.

It doesn't seem fixed to me at all. With wine 1.1.24 and nvidia-drivers both 180.60 and 185.18.14 I still get that unreasonable slowdown in crowded areas (like 4fps in a 25man raid). Normally I have like 50fps.  Can anyone else still confirm it?

Should this bug be reopened or should i file a new one?

(In reply to comment #46)
> It doesn't seem fixed to me at all. With wine 1.1.24 and nvidia-drivers both
> 180.60 and 185.18.14 I still get that unreasonable slowdown in crowded areas
> (like 4fps in a 25man raid). Normally I have like 50fps.  Can anyone else still
> confirm it?
> 
> Should this bug be reopened or should i file a new one?

You should first confirm if this is a real bug... 

Let me explain:
=> WoW, even on Windows has real slowdowns on crowded cities like dalaran. This game basically _does_ not scale. These cities are too small, and most of game cycles are lost in the game code itself (do an oprofile to check it !). Blame blizzard.
=> The GL drivers on linux are not as performant as windows ones. Bascially they are not threading command buffer generation. Blame ATI/NV !

Have you tried to dual-boot and test WOW in the same box on windows with -opengl ? I did not notice that a huge difference myself. Maybe you will... 

Truth is this game does not take profit of multicore, has a sub-par (compared to its DX) GL backend, and that wine does not account for a lot of the cycles (it is just wrapping some FS and GL calls)

PS: remove the VBO disable flag in regedit if you added any ! That's reducing FPS by removing access to modern GL interfaces ! What a bad advice...