World of Warcraft

It's me again.  The latest WoW patch (1.5.1) broke stuff again, and now I'm unable to click on anything outside of menu items in game.  The issue seems to be related to camera angle, as I am able to click on items/people when I have my camera positioned just right.  It's basically unplayable at the moment though.

Anyway, I'd appreciate it if one of the OpenGL/D3D guys (it's most likely something that would be easily fixed by one of you) could take a look at it if they have some free time.

Thanks again,
Darckness

[Raphael]

Hi,

On Wednesday 15 June 2005 05:18, cyrix12(a)cox.net wrote:
> It's me again.  The latest WoW patch (1.5.1) broke stuff again, and now I'm
> unable to click on anything outside of menu items in game.  The issue seems
> to be related to camera angle, as I am able to click on items/people when I
> have my camera positioned just right.  It's basically unplayable at the
> moment though.

Well cedega seems to have the same problem (google) and they fixed it using 
specific memory layout for WoW (mmap begins at 0x10000000)
Seems more a WoW bug than wine/cedega bug :)
> Anyway, I'd appreciate it if one of the OpenGL/D3D guys (it's most likely
> something that would be easily fixed by one of you) could take a look at it
> if they have some free time.

I don't want to do ugly hack to ovveride memory layout so if any wine memory 
layout expert can look why it happened (Alexandre ?)
> Thanks again,
> Darckness

Regards,
Raphael

[Mike Hearn]

On Thu, 16 Jun 2005 09:44:34 +0200, Raphael wrote:
> Well cedega seems to have the same problem (google) and they fixed it
> using specific memory layout for WoW (mmap begins at 0x10000000) Seems
> more a WoW bug than wine/cedega bug :)

Yes, it's a WoW bug, some Windows users are affected too. Unfortunately it
seems very few Windows users hit the problem but all Linux/Wine users see
it.
> I don't want to do ugly hack to ovveride memory layout so if any wine
> memory layout expert can look why it happened (Alexandre ?)

There's something else going on here, the Cedega fix doesn't seem to work
for everybody.

Well, I don't think Alexandre has a WoW account or copy and there isn't
enough information here to see what's going on. It's odd that seems VM
layout related though. The issue looks like it's in OpenGL though, their
"1.5 patch hotfix" is a replacement of the opengl32 DLL.

thanks -mike

[Joseph Garvin]

Mike Hearn wrote:
> Well, I don't think Alexandre has a WoW account or copy and there isn't
> enough information here to see what's going on. It's odd that seems VM
> layout related though. The issue looks like it's in OpenGL though, their
> "1.5 patch hotfix" is a replacement of the opengl32 DLL.
>
> thanks -mike

Anyone tried overwriting the new opengl32 with the old one and seeing if 
it works? The game may still think it's patched depending on how it 
tracks versions.

[Ove Kaaven]

fre, 17,.06.2005 kl. 15.12 +0100, skrev Mike Hearn:
> Well, I don't think Alexandre has a WoW account or copy and there isn't
> enough information here to see what's going on. It's odd that seems VM
> layout related though. The issue looks like it's in OpenGL though, their
> "1.5 patch hotfix" is a replacement of the opengl32 DLL.

That OpenGL hotfix is for 1.5.0 (improved ARB_pixel_format, something
Wine already have). The VM issue this thread is about is in 1.5.1. This
is not the fix you're looking for.

[Mike Hearn]

On Sat, 2005-06-18 at 05:12 -0400, Ove Kaaven wrote:
> That OpenGL hotfix is for 1.5.0 (improved ARB_pixel_format, something
> Wine already have). The VM issue this thread is about is in 1.5.1. This
> is not the fix you're looking for.

Ah OK, thanks.

I guess you don't wish to tell us what the bug is? If not then I'd
understand completely.

Hopefully somebody will figure this one out. If not maybe a trip to the
local games shop is in order :)

thanks -mike

[Ove Kaaven]

søn, 19,.06.2005 kl. 16.07 +0100, skrev Mike Hearn:
> On Sat, 2005-06-18 at 05:12 -0400, Ove Kaaven wrote:
> > That OpenGL hotfix is for 1.5.0 (improved ARB_pixel_format, something
> > Wine already have). The VM issue this thread is about is in 1.5.1. This
> > is not the fix you're looking for.
>
> Ah OK, thanks.
>
> I guess you don't wish to tell us what the bug is? If not then I'd
> understand completely.

It looks like a game bug related to virtual memory to me, and it's
possible to do a couple of configuration changes in Cedega to provoke
different virtual memory layouts, which apparently makes a difference.
Exactly why, I don't know. Since workarounds exist for now, and it's not
a simple bug to track down, and it's possible Blizzard may simply fix
the bug themselves in a future update, this is not important enough that
I've been told to drop my current tasks and do an in-depth investigation
of this instead.

[Christoph Rudorff]

Ove Kaaven schrieb:
> søn, 19,.06.2005 kl. 16.07 +0100, skrev Mike Hearn:
> > On Sat, 2005-06-18 at 05:12 -0400, Ove Kaaven wrote:
> > > That OpenGL hotfix is for 1.5.0 (improved ARB_pixel_format, something
> > > Wine already have). The VM issue this thread is about is in 1.5.1. This
> > > is not the fix you're looking for.
> >
> > Ah OK, thanks.
> >
> > I guess you don't wish to tell us what the bug is? If not then I'd
> > understand completely.
>
> It looks like a game bug related to virtual memory to me, and it's
> possible to do a couple of configuration changes in Cedega to provoke
> different virtual memory layouts, which apparently makes a difference.
> Exactly why, I don't know. Since workarounds exist for now, and it's not
> a simple bug to track down, and it's possible Blizzard may simply fix
> the bug themselves in a future update, this is not important enough that
> I've been told to drop my current tasks and do an in-depth investigation
> of this instead.

:(
>

Hello!

To me it looks like an overoptimized geometry problem. As long there is 
only sky and no terrain or building behind the objects, you can klick 
them. This is mostly the case, when you look up. Just like users reported.

I just wrote a lousy mmap wrapper which sets start to 0x10000000 . This 
works for me with wine 20050601 and the latest from cvs.

Latest cvs raises another bug. When the wow window looses focus, it 
minimize and maximizes again and stays on top. More worse, the graphics 
is shifted to approx. +2+2 pixels every time. Here's the output from 
console:

fixme:opengl:wglQueryPbufferARB unsupported WGL_PBUFFER_LOST_ARB (need 
glXSelectEvent/GLX_DAMAGED work)

... and the TODO becomes a bit longer again.

chris

[Raphael]

Hi,
> To me it looks like an overoptimized geometry problem. As long there is
> only sky and no terrain or building behind the objects, you can klick
> them. This is mostly the case, when you look up. Just like users reported.
>
> I just wrote a lousy mmap wrapper which sets start to 0x10000000 . This
> works for me with wine 20050601 and the latest from cvs.

Interesting
> Latest cvs raises another bug. When the wow window looses focus, it
> minimize and maximizes again and stays on top. More worse, the graphics
> is shifted to approx. +2+2 pixels every time. Here's the output from
> console:
>
> fixme:opengl:wglQueryPbufferARB unsupported WGL_PBUFFER_LOST_ARB (need
> glXSelectEvent/GLX_DAMAGED work)

Arg,
i didn't expect this fixme :(

And it's so boring to handle (needs some x11drv work too)
I'll let Lionel (or Alexandre) trying to fix this case, i have already find 
the way to handle (see the fixme text) :)
> .... and the TODO becomes a bit longer again.

yes really longer ...
> chris

Raphael

[Raphael]

On Monday 20 June 2005 09:40, Raphael wrote:
> Hi,
> > To me it looks like an overoptimized geometry problem. As long there is
> > only sky and no terrain or building behind the objects, you can klick
> > them. This is mostly the case, when you look up. Just like users
> > reported.
> >
> > I just wrote a lousy mmap wrapper which sets start to 0x10000000 . This
> > works for me with wine 20050601 and the latest from cvs.
>
> Interesting

After some investigation (using interesting users dumps at 
http://home.gci.net/~slipster5/WowError/ and in many others places)

looks like more an ugly WoW bug

For example seeing this typilical error:

This application has encountered a critical error:

ERROR #132 (0x85100084)
Program:	C:\Program Files\World of Warcraft\WoW.exe
Exception:	0xC0000005 (ACCESS_VIOLATION) at 001B:00650E16

The instruction at "0x00650E16" referenced memory at "0x33991588".
The memory could not be "read".


While registers was:

EAX=00000001  EBX=13991500  ECX=00A49658  EDX=00000003  ESI=1399155C
EDI=00000000  EBP=0012FC58  ESP=0012FC38  EIP=00650E16  FLG=00210202
CS =001B      DS =0023      ES =0023      SS =0023      FS =003B      GS =0000


The must interesting is that error address was always (EBX + 0x20000000) + 
something little (usually between 0x10-0x88). 

for info 0x20000000 => 512Mb :)

So who go to blizzard to fix the bug ? :)


Raphael

[Raphael]

Stupid kmail

Sorry
Raphael

[Stefan Dösinger]

On Monday 20 June 2005 22:22, Raphael wrote:
> Stupid kmail
> I updated to KDE 3.4 and kmail seems to do a fine job now.
> *Reply replies to the list
> *Reply to all replies to list + Sender
> *Reply to Author replies to the author only
> *Reply to Mailing list replies to the mailing list only.

I think that's how it should work

Stefan

[Christoph]

Raphael schrieb:
> Hi,
> > To me it looks like an overoptimized geometry problem. As long there is
> > only sky and no terrain or building behind the objects, you can klick
> > them. This is mostly the case, when you look up. Just like users reported.
> >
> > I just wrote a lousy mmap wrapper which sets start to 0x10000000 . This
> > works for me with wine 20050601 and the latest from cvs.
>
> Interesting
> More interesting:
> http://forums.gentoo.org/viewtopic-t-246098-postdays-0-postorder-asc-start-2...

Gamers are playing with lib. wrapper ... just like me!
But I came to the same conclusion:

static void initialize() __attribute__ ((constructor));

static void initialize() {
	printf("Hurra !!!\n");
	// _mmap = dlsym(RTLD_NEXT, "mmap");
}

Finaly it is the printf who does the magic and not the wrapped mmap! The 
above example also worked for me. Can we still solve this problem with 
logic?

But I still do believe, that blizzard will release a new patch soon :=)
> > Latest cvs raises another bug. When the wow window looses focus, it
> > minimize and maximizes again and stays on top. More worse, the graphics
> > is shifted to approx. +2+2 pixels every time. Here's the output from
> > console:
> >
> > fixme:opengl:wglQueryPbufferARB unsupported WGL_PBUFFER_LOST_ARB (need
> > glXSelectEvent/GLX_DAMAGED work)

... and this "bug" reminds me to a config option which I set to n many 
years ago:

[x11drv]
"UseTakeFocus" = "n"

Does this no more work in cvs version? I dont have another picky 
application here to test. sol.exe does not have that min/max effect.
> Arg,
> i didn't expect this fixme :(
>
> And it's so boring to handle (needs some x11drv work too)
> I'll let Lionel (or Alexandre) trying to fix this case, i have already find 
> the way to handle (see the fixme text) :)
> > .... and the TODO becomes a bit longer again.
>
> yes really longer ...
> > chris
>
> Raphael

chris

[Mike Hearn]

On Tue, 21 Jun 2005 23:07:00 +0200, Christoph wrote:
> Finaly it is the printf who does the magic and not the wrapped mmap! The
> above example also worked for me. Can we still solve this problem with
> logic?

Hehe, I highly doubt it's the printf. More likely, the LD_PRELOADed shared
library is modifying the address space in such a way that the WoW bug is
no longer triggered. I expect you could put anything there (that won't be
optimised out) and it'll still work.

[Raphael]

Hi,
> Hopefully somebody will figure this one out. If not maybe a trip to the
> local games shop is in order :)

lol
what about asking blizzard support :)
> thanks -mike

Regards,
Raphael

[Andreas Mohr]

Hi,

On Mon, Jun 20, 2005 at 09:34:52AM +0200, Raphael wrote:
> Hi,
> > Hopefully somebody will figure this one out. If not maybe a trip to the
> > local games shop is in order :)
>
> lol
> what about asking blizzard support :)
> I'd really recommend doing exactly that.
> Those game publishers'd better get used to us having issues with their
>  awkward patches all the time ;)
> That way they might go as far as testing it on Wine themselves before release
> or mailing it to interested Wine people beforehand.

We need to get on the radar of those companies...

Andreas Mohr

[Raphael]

Hi,

On Friday 17 June 2005 16:12, Mike Hearn wrote:
> On Thu, 16 Jun 2005 09:44:34 +0200, Raphael wrote:
> > Well cedega seems to have the same problem (google) and they fixed it
> > using specific memory layout for WoW (mmap begins at 0x10000000) Seems
> > more a WoW bug than wine/cedega bug :)
>
> Yes, it's a WoW bug, some Windows users are affected too. Unfortunately it
> seems very few Windows users hit the problem but all Linux/Wine users see
> it.

Yes seems a strange WoW optimization :)
> > I don't want to do ugly hack to ovveride memory layout so if any wine
> > memory layout expert can look why it happened (Alexandre ?)
>
> There's something else going on here, the Cedega fix doesn't seem to work
> for everybody.
>
> Well, I don't think Alexandre has a WoW account or copy and there isn't
> enough information here to see what's going on. It's odd that seems VM
> layout related though.

as me, i haven't a WoW account 
but seems that WoW do some checks using presumption on VM layout (and wine VM 
layout is really different)
> The issue looks like it's in OpenGL though, their 
> "1.5 patch hotfix" is a replacement of the opengl32 DLL.

1.5.O WoW patch used to work (with my openGL patces to get 1.4.1 working)
we are speaking about 1.5.1 problem
> thanks -mike

Regards,
Raphael

[Joseph Garvin]

The test realms are up, which lets players test the next patch. Anyone 
tried it to see if the problem is fixed?

[Christoph]

Joseph Garvin schrieb:
> The test realms are up, which lets players test the next patch. Anyone 
> tried it to see if the problem is fixed?

Yes, I'm going to test.

first gotcha the bizzard char copy page. The page did not work in 
Firefox. Clicking in a circle, not accepting a new char name. Looked at 
page source. What a joy. The europe/german Version of the page contains 
a bag full of typos ... such as not closed tags ! Thanks to the 
Webdeveloper plugin in Firefox I got finally a test char :-P

second download tool. 100% cpu and 'nothing' happens until winedbg came 
up with seg fault. Simply retried 5 times, now it's downloading and 
uploading with 3040MB/s . Great speedup :=)

third, ... hey I have to cvs the latest wine ;-)


chris

[Christoph]

Christoph schrieb:
> Joseph Garvin schrieb:
> > The test realms are up, which lets players test the next patch. Anyone 
> > tried it to see if the problem is fixed?

No, it is not fixed.
> >
>
> Yes, I'm going to test.
>
> first gotcha the bizzard char copy page. The page did not work in 
> Firefox. Clicking in a circle, not accepting a new char name. Looked at 
> page source. What a joy. The europe/german Version of the page contains 
> a bag full of typos ... such as not closed tags ! Thanks to the 
> Webdeveloper plugin in Firefox I got finally a test char :-P
>
> second download tool. 100% cpu and 'nothing' happens until winedbg came 
> up with seg fault. Simply retried 5 times, now it's downloading and 
> uploading with 3040MB/s . Great speedup :=)
>
> third, ... hey I have to cvs the latest wine ;-)

K. First test run with wine-20050628 with WoW-1.5.1
The "I cannnot click on any NPC" is still there.
Audio is not working (artsdrv) also not with sndrec32.exe ("no sound 
device"). artsd is running and no conn from wine.
Mh, something rotten with wineconfig/registry?! I can see wine is 
loading wineoss.drv instead. Regedit shows me correctly 
WineMM/Drivers=winearts.drv

Tried alsa, that is working.

New bug in wine-20050628: if WoW looses focus, it minimizes and 
maximizes automatically and steals focus again (I'm using WMaker) more 
worse graphics becomes shifted about +1px+1px every time. Makes game 
unplayable after this. Is the option "UseTakeFocus" = "n" no more working?!

So, now I'm going to patch the game.

K. patched fine. creates a new folder WoWTest with empty wtf/ 
config-Folder so have to adjust settings after a quick run.

Game is up. Still has the "cannot click on NPC"

The cheap wrapper trick is still making it working.


further testing needs now lots more time ;)
> chris

[Christoph]

Some more impressions from the test server and coming patches.

First the server was heavy crowded. Funny but net latency about 1200ms. 
Hard to play. Blizz added a lot new game content and that is to be 
tested. They happily rebootet the servers several times while I was on 
and also applied a tiny patch to the clients.

The "1.6-test" patch is not a bugfix at all. Not yet ...
All the ingame bugs that I know are also in the test version. E.g. stuck 
loot bug, still the same typos in the localized text. I found a new game 
bug (graphics) but the GM ticket system is not working.

I used wine-20050524 because latest 20050628 broke these thinks:

- arts sound (I use this with artsd TeamSpeak)
- loose focus minimize/maximize bug

Can anyone confirm this?

One good thing: The game used to crash on exit and wine is stuck until 
ctrl-c (Threadlock?). But this time, I noticed it while patching, the 
game now exits without crashing. I can't say if it was due the patch. I 
haven't hunted this bug. I do believe, this bug patched himself :)

chris
> Christoph schrieb:
> > Joseph Garvin schrieb:
> > > The test realms are up, which lets players test the next patch. 
> > > Anyone tried it to see if the problem is fixed?
>
> No, it is not fixed.

[Jacob Emcken]

Hi,

cyrix12(a)cox.net wrote:
> It's me again.  The latest WoW patch (1.5.1) broke stuff again, and now I'm unable to click on anything outside of menu items in game.  The issue seems to be related to camera angle, as I am able to click on items/people when I have my camera positioned just right.  It's basically unplayable at the moment though.
>
> Anyway, I'd appreciate it if one of the OpenGL/D3D guys (it's most likely something that would be easily fixed by one of you) could take a look at it if they have some free time.

For me the bug has disappeared after upgrading to Ubuntu Breezy with a 
2.6.12 kernel and the lastest release of WINE.

I stumbled upon a post on a Gentoo forum where a few people said that 
they didn't need the ugly cadega workaround to play WoW after using 
kernel 2.6.12.

So after I got Ubuntu upgraded from Hoary to Breezy (which uses a 2.6.12 
kernel instead of a 2.6.10) I tested WoW with a clean WINE 20050725 
(Debian packages from wine.df.net/apt).

The bug hasn't shown itself since. I belive it is the kernel upgrade.
I dunno, I might have just been lucky.


Just wanted to let you know, dunno if I have just been lucky.


Regards
--Jacob