World Of Warcraft Howto/Support UPDATED 11/10/05! (old)

Message

discomfitor · Post by **discomfitor** » Tue Oct 11, 2005 4:13 pm

Mod edit: Split from [topic]246098[/topic]. --kallamej

Split for 1.8.

Hooray for patch day!

mopomi · Post by **mopomi** » Tue Oct 11, 2005 8:28 pm

Darckness wrote:Split for 1.8.

Hooray for patch day!

Hooray. . . /sigh

Except, that they've reintroduced the mouse-over bug that had gone away for the test client (on AMD64). This happened with the 1.7 test client to released client as well.

My guess is that it's a bug or feature in one of the .MPQs that resides in the Data directory and that remains unchanged between patches.

Oh, well. Back to work, I guess.

PseudoKrazy · Post by **PseudoKrazy** » Tue Oct 11, 2005 11:20 pm

Ok... so i got WoW working last week, and after seeing how awesome it ran in wine, decided to go and purchase 6 months of it.

...

There was an update today

. And it broke my WoW.

My sound was fixed,but now sucks once more, and i can no longer target anything other then myself.

someone help me fix my WoW and tell me i didnt waste money on 6 months of this.

ikataii · Post by **ikataii** » Wed Oct 12, 2005 1:58 am

Right, I've had it running smoothly since I got wine-20050830 installed, then this patch came out and everything came apart. I got WoW to start smoothly a couple of times under 20050830, then found the mouseover bug and hoped 20050930 would fix it. Now I get the following every time I start up wine, including the last line unique to winecfg trying to apply my drive_c setting, even with an absolute path (/home/kate/.wine/drive_c)

Code: Select all

Warning: the specified Windows directory Lc:\windows is not accessible.
Warning: the specified System directory Lc:\windows\system32 is not accessible.
Warning: could not find DOS drive for current working directory '/home/kate/.wine', starting in the Windows directory.
err:winecfg:apply_drive_changes   unable to define devicename of 'C:', targetpath of '../drive_c'

Some help would be greatly appreciated before I just give up and install WinXP on a spare partition and give up with wine and all the coolness inherent to it.

ikataii · Post by **ikataii** » Wed Oct 12, 2005 3:09 am

scratch that. Uninstalled 20050930 and reinstalled 20050830 and it works (sorta) again.
Now we just need a way past this mouse bug. Anybody tried the old fixes?

morrowyn · Post by **morrowyn** » Wed Oct 12, 2005 12:20 pm

Ok, i have WoWW 1.8.0 running via the latest wine (20050930), i also experience the mousebug problem. Btw, i run it on slackware 10.2, but then again this is beyond the linux distro's this is about gaming

I also have a question, i have 2 monitors and if i dont run a windowed mode, WoWW runs 1280x1024 resolution on both screen. The nice part is that it is the first game on linux that im aware of that doesnt do weird stuff when running dual screens.
However, does WoWW support a resolution of 2560x1024?

Regards

cfempa · Post by **cfempa** » Wed Oct 12, 2005 2:18 pm

ikataii wrote:Now we just need a way past this mouse bug. Anybody tried the old fixes?

None works for wine

For cedega "MemoryLayoutOverride" = "0x10000000" does it.
Someone should find out what this line actualy does, and implement it to wine asap.

shamus13 · Post by **shamus13** » Wed Oct 12, 2005 3:35 pm

Ello all,

I guess, it was naive in the extreeme to think, blue had actually fixed their
heap corruption problems causing the mouse bug. Any way, i have tracked
down an old post with a patch to add this override feature to winex. Its not
terribly big, but it is still going to be a bit of work to figure out, how to hack
that into wine.

The post with the old patch can be found at:
http://lists.transgaming.org/pipermail/ ... 00259.html

I for one will be tinkering with a bit of source this evening:D

Shamus

RabbidFrogLobotomy · Post by **RabbidFrogLobotomy** » Wed Oct 12, 2005 10:35 pm

PseudoKrazy wrote:Ok... so i got WoW working last week, and after seeing how awesome it ran in wine, decided to go and purchase 6 months of it.

...

There was an update today . And it broke my WoW.
My sound was fixed,but now sucks once more, and i can no longer target anything other then myself. someone help me fix my WoW and tell me i didnt waste money on 6 months of this.

Meh. Me too mate.
Just updated to WoW 1.8.0 and I cant select anything. I cant [TAB] and [T] so I can still grind, I guess, but I can't select anything by point-n-click, not corpses, NPCs, PCs or mailboxes.
The buttons on the toolbars work, but that's about it. I'm running the latest CVS (I just updated and recompiled wine after the patch to check, and it still doesn't work)

*sob*

[EDIT]: typo

PseudoKrazy · Post by **PseudoKrazy** » Wed Oct 12, 2005 10:44 pm

ikataii wrote:scratch that. Uninstalled 20050930 and reinstalled 20050830 and it works (sorta) again.
Now we just need a way past this mouse bug. Anybody tried the old fixes?

I had everything working in 20050725-r1. I just updated to 20050830 to see if it fixed the mouse bug problem that arised when i updated WoW to 1.8. It didnt fix anything for me, however, i am now able to run the game without -opengl. it just doesnt look as good, but there is no mouse bug. Also, a cheap way to be able to select stuff with the mouse bug is to sort of look at the sky, or look up while trying to target things.

ikataii · Post by **ikataii** » Wed Oct 12, 2005 11:11 pm

Yeah. Precisely as it happened before, it only affects opengl and it causes either the mouse to think it's in the background or for it to think that the background items are in front of the target (basically, reversing the order, which I think we had figured out last time).
I'll see what it looks like in d3d, but last time, I got absolutely no text in that mode.

Edit: Yeah, under wine-20050830 and d3d, no character textures and no text loads, which, while I suppose theoretically playable, would not be fun. On a side note, Cedega doesn't even load for me. I try running it and it seems to start up the processor to about 20%, then just vanishes and gives me a blank line in my command prompt.

Marneel · Post by **Marneel** » Thu Oct 13, 2005 1:01 am

ikataii wrote: Edit: Yeah, under wine-20050830 and d3d, no character textures and no text loads, which, while I suppose theoretically playable, would not be fun. On a side note, Cedega doesn't even load for me. I try running it and it seems to start up the processor to about 20%, then just vanishes and gives me a blank line in my command prompt.

Funny, but I have exactly the same issue. I thought it was because my version was quite old (3.3 i think), but it behaves exactly as you just described. If Cedega have a trail version I might give it a go, just to keep me playing! The alternative is switching to XP, but that's a bit extreem.

GoldDog · Post by **GoldDog** » Thu Oct 13, 2005 3:22 am

The 1.8.0 patch broke my WoW too. I just updated to WINE20050830 and, for me, the mouse bug is still there for openGL and d3d. So now, I am not able to play, no matter what I try. I've tried with those little memory fixes and without, and nothing works.

System Specs:
AMD Athlon 2.4
512MB of memory
NVIDIA GeForce FX 5200
Running Fedora Core 3 (with all updates DLed and installed)

Marneel · Post by **Marneel** » Thu Oct 13, 2005 5:19 am

Has anybody tried the solution given in this thread: http://forums.gentoo.org/viewtopic-p-26 ... ml#2690553

The only Win32 application I run is WoW, so if it totally breaks Wine for other applications, that's no big deal. If nobody has, I'll try it tonight (please). Failing that, it'll be the weekend. :-/

discomfitor · Post by **discomfitor** » Thu Oct 13, 2005 5:23 am

Cursor bug confirmed.

Cedega still playable.

I'll see if I can dig up anything on the wine end, but no guarantees. I'm absolutely swamped with work at the moment.

teidon · Post by **teidon** » Thu Oct 13, 2005 7:44 am

Marneel wrote:Has anybody tried the solution given in this thread: http://forums.gentoo.org/viewtopic-p-26 ... ml#2690553

Yes, it does what it's meant to do. And Blizzard didn't fix that OpenGL bug this time either.

And I got my precious mouse bug back too...

shamus13 · Post by **shamus13** » Thu Oct 13, 2005 1:40 pm

Ello all,

Just wanted ask if any of you have experienced the arcane missiles bug at 1.8.0?
I didnt see it at all during 1.7, but yesterday during my mucking around in the
wine memory allocation system, i saw arcane missiles bug out and fail to fire
missiles.
You dont suppose, they fixed the bug with the range indicator by putting the old
buggy code from 1.6 and earlier back in?

Yours sincerely,

Shamus

spectra · Post by **spectra** » Fri Oct 14, 2005 4:35 am

Hey all,

I too have the cursor bug, however if I just logout and log back in (don't exit the game), it fixes it. I haven't seen mention of that "fix" anywhere, so I thought I'd share.

*shrug*

lord_ph · Post by **lord_ph** » Fri Oct 14, 2005 5:33 am

That little fix didn't work for me

. But thanks for offering it up.

lord_ph · Post by **lord_ph** » Fri Oct 14, 2005 5:34 am

BTW, this is for cedega version 4.4.2 & 4.4.3 that i'm having the mouse problem with.

ikataii · Post by **ikataii** » Fri Oct 14, 2005 6:25 am

@lord_ph: have you tried the MemoryLayoutOverride fix for Cedega?

@spectra: I tried logging all the way in and trying to look at IF, then out to char select and right back in, then out to login screen (name / pass) and back to IF. Then I killed it and got to char select, then back to login, then into IF. None of the above fixed my mouse.
What sort of specs / card / API are you using?

Marneel · Post by **Marneel** » Fri Oct 14, 2005 2:17 pm

spectra wrote:Hey all,

I too have the cursor bug, however if I just logout and log back in (don't exit the game), it fixes it. I haven't seen mention of that "fix" anywhere, so I thought I'd share.

*shrug*

Could you give some details on your system please? I've tried this a few times and it doesn't fix anything on my machine.

Thanks.

Jonasx · Post by **Jonasx** » Fri Oct 14, 2005 2:37 pm

shamus13 wrote:Ello all,

Just wanted ask if any of you have experienced the arcane missiles bug at 1.8.0?
I didnt see it at all during 1.7, but yesterday during my mucking around in the
wine memory allocation system, i saw arcane missiles bug out and fail to fire
missiles.
You dont suppose, they fixed the bug with the range indicator by putting the old
buggy code from 1.6 and earlier back in?

Yours sincerely,

Shamus

The AM bug is location specific. It's been in the game since the beta but Blizzard has yet to fix it. I did quite a bit of research into it a while back and even had a rather extensive dialog with tech support via email and provided a video along with a list of spots that AM was bugged at. I've been able to reproduce it every patch since day one release

. Don't think this has anything to do with their patching, maybe you just weren't at spots that were bugged during the last patch ...This is my experience anyways

ThE_TemPLaR · Post by **ThE_TemPLaR** » Fri Oct 14, 2005 4:47 pm

spectra wrote:Hey all,

I too have the cursor bug, however if I just logout and log back in (don't exit the game), it fixes it. I haven't seen mention of that "fix" anywhere, so I thought I'd share.

*shrug*

It doesn't work here.

lord_ph · Post by **lord_ph** » Fri Oct 14, 2005 6:26 pm

@ikataii: yes, i used that fix for the 1.6 update, and that did fix the problem(at the time). But it no longer works for me in cedega 4.4.2 & 4.4.3 and WOW 1.8.