Brand new "Boxer"

[Baun]

Im running with an extended desktop, and the bat file does work.

REM batch file to launch 5 evenly spaced wows
REM Left monitor
E:\Boxing\WoW1\maximizer.exe --margin 0,0,0,1280
REM upper left of right mon
E:\Boxing\WoW2\maximizer.exe --margin 0,512,1280,0
REM lower left of right mon
E:\Boxing\WoW3\maximizer.exe --margin 512,0,1280,0


So when i boot it up then it does look fine exept for the gfx errors and the shatter effects as i mentioned before, so basicly its only the shatter effects thats keeping me from starting, and i just cant figure out what the are caused by.

[Hippieman]

Ah, sorry, I missunderstood your post completely... *bashes his head in*

Anyways, I'd recommend looking into some new drivers, possibly some from TweaksRUs (they tend to either fix the problem or make it worse :P but then agian, you can just remove 'em again).

[Baun]

I got the newest (and only so far as i could find) driver for my gfx card (ATI Radeon HD 3870).

[Hippieman]

Looking at the screenshot again, it reminds me a lot of an old NVIDIA-card related bug that used to be in wow and it was fixed changing some graphical settings in wow... So that's all I've got: tinker with the graphical settings and see what works.

[Baun]

Thanks for the help, ill try and tamper with it, if anyone got any specific things to do, turn on, remove or what ever, then please let me know

[Baun]

Im pretty sure ive tryed every single option for setting up the gfx different, and i still have this annoying shatter effect, and other options?

[Xzin]

Your card is likely either overheating or is a bad card with corrupted/bad memory.

[Baun]

Well its a brand new card, and its running with sandard cooling and i havnt been able to see any bad memory, its running with norm memory and everything

[Baun]

Could this maybe be caused by that i have DirectX 9.0c when my gfx card is a DirectX 10 card (same with driver), and if so, does anybody know how to install DirectX 10 on Windows XP 64? only been able to find anything about it, only for Windows32

[kalih]

I consider it highly unlikely that it has anything to do with directx 9 vs 10.