<br><br><div class="gmail_quote">2009/3/12 tparker <span dir="ltr"><<a href="mailto:tparker@etherstorm.net">tparker@etherstorm.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Thu, 2009-03-12 at 11:34 +0200, Kalle Last wrote:<br>
><br>
> I seem to be having somewhat similar issues lately. Unfortunately I<br>
> haven't been able to pin down the problem yet as lots of things<br>
> changed. I went from 64 bit Kubuntu 8.-something, older NV drivers,<br>
> wow 3.0.3 to 64bit Gentoo with 180.-something NV drivers, latest Wine<br>
> and wow patch 3.0.9.<br>
<br>
Mine seems to be finally becoming stable again, a couple things that<br>
might be worth trying to see if they help on your system (no promises):<br>
<br>
-go into WINE config, graphics tab and look for a box that says 'allow<br>
pixel shader', be sure it is not checked. You may have to go back in and<br>
reselect it if you have another game that uses it, but for some odd<br>
reason my WoW runs better without that, even though I use opengl<br>
</div></div></blockquote><div><br>That's worth a try for sure<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="h5">
<br>
-if you start the game from a desktop shortcut be sure that "-opengl"<br>
without the quotes is at the end of the Command line, sometimes updates<br>
take it out.<br>
</div></div></blockquote><div><br>I'm quite sure I had the option in my cfg.wtf file, it's again a good idea to recheck it.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="h5"><br>
-for stability you might want to try limiting your system to 3G ram as<br>
mentioned on the WINEappdb page, not a favorite work around but it does<br>
help some people until a better solution is found.<br>
</div></div></blockquote><div><br>That's kind of complicated as I need the RAM for other background tasks. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="h5"><br>
-check your /ect/X11/xorg.conf, in the Files section for a line that<br>
says either ModulePath "/usr/lib64/xorg/modules/extensions/fglrx"<br>
or ModulePath "/usr/lib64/xorg/modules/extensions/nvidia". If yours<br>
says nvidia at the end try commenting it out and putting in the line<br>
ending with fglrx. When I upgraded to the 180.x drivers it changed that<br>
line and I got graphics glitches until I changed it back to ending in<br>
'fglrx'.<br>
</div></div></blockquote><div><br>That doesn't sound logical at all. fglrx is or ATI aka AMD video cards but I have NV one. Could anyone explain why would such a change be needed?<br><br><br>I'll try those changes out in a few hours when I get home, I'll try to let you know of my progress.<br>
</div></div><br><br clear="all"><br>-- <br>Kalle Last<br>