Am Montag, 1. Oktober 2007 21:36:26 schrieb Roderick Colenbrander:
Call of Duty is popular but I would say that CounterStrike (+
CounsterStrike Source, the port to the Source engine) are way more popular.
More and more games these days are distributed using Steam. That's
something to watch
On Tuesday 02 October 2007 11:12:41 Stefan Dösinger wrote:
I think the main blockers for Wine as a gaming Platform isn't D3D any more.
A few months back sound used to be a blocker, but Maarten has done a great
job on that. Most issues seem to be located in the copy protection area,
and in
parties with friends.
You may have dusted off your copy of Settlers II or Lemmings,
installed DOSBox and are enjoying revisiting classic games.
The online multiplayer facilities of games like Starcraft, and the
MMORPG games like World of Warcraft and Guild Wars, have more
visibility because
On 01/10/2007, Dan Kegel [EMAIL PROTECTED] wrote:
On 10/1/07, Reece Dunn [EMAIL PROTECTED] wrote:
Searching Google is only really useful around the time of release
(with a suitable time window either side).
If that were true, I would expect World of Warcraft's google
search curve to have
popular, but I
haven't found any that beat World of Warcraft yet:
http://www.google.com/trends?q=world+of+warcraft%2C+guild+wars%2C+tomb+raider%2C+bioshock%2C+half-life+2
Is Google search popularity a bad measure, or does it
reflect the public's mood well?
- Dan
/bestsellers/videogames
(click on PC Games).
I tried to cross-check titles with Google Trends to
see which ones seem enduringly popular, but I
haven't found any that beat World of Warcraft yet:
http://www.google.com/trends?q=world+of+warcraft%2C+guild+wars%2C+tomb+raider%2C+bioshock%2C+half-life
On 10/1/07, Daniel Remenak [EMAIL PROTECTED] wrote:
No other single game has the market penetration and staying power of
WoW as things stand.
I think starcraft has it beat for penetration and staying power,
actually. But WoW is the current money maker.
money maker.
Call of Duty and Starcraft do show up pretty well, thanks.
Here's the best graph I was able to put together so far:
http://www.google.com/trends?q=world+of+warcraft%2C+guild+wars%2C+tomb+raider%2C+%22call+of+duty%22%2C+starcraft
On 10/1/07, Jesse Allen [EMAIL PROTECTED] wrote:
On 10/1/07, Daniel Remenak [EMAIL PROTECTED] wrote:
No other single game has the market penetration and staying power of
WoW as things stand.
I think starcraft has it beat for penetration and staying power,
actually. But WoW is the
On 10/1/07, Reece Dunn [EMAIL PROTECTED] wrote:
Searching Google is only really useful around the time of release
(with a suitable time window either side).
If that were true, I would expect World of Warcraft's google
search curve to have flatlined long ago, but instead it's
still going strong.
pretty well, thanks.
Here's the best graph I was able to put together so far:
http://www.google.com/trends?q=world+of+warcraft%2C+guild+wars%2C+tomb+raider%2C+%22call+of+duty%22%2C+starcraft
--
Vincent Povirk
Ahoy!
First off, I'd like to say happy 2007! Hope you all did some good
celebrating. I know I did ;)
Anyway, I've been doing some testing on World of Warcraft, and I noticed
some things of interest (Latest wine version from cvs/git, no patches
applied).
First off, the D3D (DX9) runs MUCH
Am 02.01.2007 um 09:51 schrieb darckness:
First off, the D3D (DX9) runs MUCH better (faster and more smoothly)
than the OGL mode. Big kudos to you guys; last time I played, the D3D
mode was completely unusable because there was no D3D support in wine.
Very impressive.
Nice :-)
The OGL
on the AppDb page for
World of Warcraft and has now been known for quite some time already. If
you apply the hack, you'll see that running in OGL and D3D mode won't
make a difference in the framerate.
I also noticed the modeswitch crash, but I didn't investigate it. I
always edit the Config.wtf
Jesse Allen wrote :
On 11/3/06, Bertrand Coconnier [EMAIL PROTECTED] wrote:
Hi,
After investigating a bit in the Wine code, it seems that the flickering
bug of WoW in OpenGL mode is due to wglGetPbufferDCARB that returns a DC
which type is OBJ_MEMDC while it should return a DC which type is
Hi,
After investigating a bit in the Wine code, it seems that the flickering
bug of WoW in OpenGL mode is due to wglGetPbufferDCARB that returns a DC
which type is OBJ_MEMDC while it should return a DC which type is
OBJ_DC. And since in the current git tree, the DC type of a Pbuffer is
Roderick Colenbrander wrote :
Hi,
After investigating a bit in the Wine code, it seems that the flickering
bug of WoW in OpenGL mode is due to wglGetPbufferDCARB that returns a DC
which type is OBJ_MEMDC while it should return a DC which type is
OBJ_DC. And since in the current git tree, the
Roderick Colenbrander wrote :
Hi,
After investigating a bit in the Wine code, it seems that the
flickering
bug of WoW in OpenGL mode is due to wglGetPbufferDCARB that returns a
DC
which type is OBJ_MEMDC while it should return a DC which type is
OBJ_DC. And since in the current
Roderick Colenbrander wrote :
Hi,
After investigating a bit in the Wine code, it seems that the
flickering
bug of WoW in OpenGL mode is due to wglGetPbufferDCARB that returns a
DC
which type is OBJ_MEMDC while it should return a DC which type is
OBJ_DC. And since in the
Roderick Colenbrander wrote :
Or perhaps a testcase isn't needed at all. I think the use of
CreateCompatibleDC in wglGetPbufferDCARB is incorrect. According to MSDN this
function creates a memory device context. Perhaps something like this works:
HDC hdc = CreateDC(...);
int format_orig =
Roderick Colenbrander wrote :
Or perhaps a testcase isn't needed at all. I think the use of
CreateCompatibleDC in wglGetPbufferDCARB is incorrect. According to MSDN this
function creates a memory device context. Perhaps something like this works:
HDC hdc = CreateDC(...);
int format_orig
Roderick Colenbrander wrote :
Roderick Colenbrander wrote :
Or perhaps a testcase isn't needed at all. I think the use of
CreateCompatibleDC in wglGetPbufferDCARB is incorrect. According to MSDN this
function creates a memory device context. Perhaps something like this works:
HDC hdc =
Roderick Colenbrander wrote :
Roderick Colenbrander wrote :
Or perhaps a testcase isn't needed at all. I think the use of
CreateCompatibleDC in wglGetPbufferDCARB is incorrect. According to
MSDN this
function creates a memory device context. Perhaps something like this
works:
HDC
Roderick Colenbrander wrote :
Roderick Colenbrander wrote :
Or perhaps a testcase isn't needed at all. I think the use of
CreateCompatibleDC in wglGetPbufferDCARB is incorrect. According to
MSDN this
function creates a memory device context. Perhaps something like this
works:
Roderick Colenbrander wrote :
Could you check if the attached patch works? It does more or less what I
explained in the last email. If it works I'll clean it up as right now it is a
bit hacky. I hope to find some apps to test it on.
Regards,
Roderick
Your patch fixes everything : WoW does
Hi,
After investigating a bit in the Wine code, it seems that the flickering
bug of WoW in OpenGL mode is due to wglGetPbufferDCARB that returns a DC
which type is OBJ_MEMDC while it should return a DC which type is
OBJ_DC. And since in the current git tree, the DC type of a Pbuffer is
On 11/3/06, Bertrand Coconnier [EMAIL PROTECTED] wrote:
Hi,
After investigating a bit in the Wine code, it seems that the flickering
bug of WoW in OpenGL mode is due to wglGetPbufferDCARB that returns a DC
which type is OBJ_MEMDC while it should return a DC which type is
OBJ_DC. And since in
I'm having the same problems with 0.9.21 here, World of Warcraft is
broken, no longer runs at all on ATI hardware, (confirmed on two
separate systems running with ATO 9550. (maybe ok on Nvidia hardware
although not tried it myself).
Upon trying to start WoW, a Blizzard dialog box appears
I'm having the same problems with 0.9.21 here, World of Warcraft is
broken, no longer runs at all on ATI hardware, (confirmed on two
separate systems running with ATO 9550. (maybe ok on Nvidia hardware
although not tried it myself).
Upon trying to start WoW, a Blizzard dialog box appears
Vitaliy Margolen wrote:
Nick Law wrote:
I'm having the same problems with 0.9.21 here, World of Warcraft is
broken, no longer runs at all on ATI hardware, (confirmed on two
separate systems running with ATO 9550. (maybe ok on Nvidia hardware
although not tried it myself).
Nick
Mike Hearn wrote:
Well if you can get the email address of a WoW developer then maybe we
can track down where the problem in WoW is and work with them to fix
it.
You might have some luck contacting Sam Lantinga. He is the creator and
current maintainer of the SDL library and works for Blizzard
On 5/30/06, n0dalus [EMAIL PROTECTED] wrote:
It would be really great if someone could document the patch and
explain what exactly is stopping WoW from working (as well as which
changes would cause problems for other programs).
It's a bug in WoW itself, it relies upon the exact way NT maps
Mike Hearn wrote:
It's a bug in WoW itself, it relies upon the exact way NT maps memory
which is different to how Linux does it. I guess they are storing
information in the high bits of a pointer somewhere or some similar
trick.
Since WoW also runs on MacOSX, how does the memory layout on
Message d'origine
Date: Tue, 30 May 2006 16:08:42 +0200
De: Tomas Carnecky [EMAIL PROTECTED]
A: Mike Hearn [EMAIL PROTECTED]
Copie à: wine-devel@winehq.com, n0dalus [EMAIL PROTECTED]
Sujet: Re: World of Warcraft (WoW) patch/more address space layout stuff
Mike Hearn wrote:
It's a bug
[EMAIL PROTECTED] wrote:
No, they have added this regressions after a little patch-set.
So they can fix it.
And as we can't download a playable demo ...
Interesting.. if MacOSX has a similar memory layout as linux, maybe we
could get Blizzard to include a workaround that is only active when
On Tue, 30 May 2006 16:08:42 +0200, Tomas Carnecky wrote:
Since WoW also runs on MacOSX, how does the memory layout on MacOSX
differ from NT and Linux?
I have no idea, but the MacOS and Windows versions of WoW will be
different; probably the bug is only in the Windows specific parts of the
Interesting.. if MacOSX has a similar memory layout as linux, maybe we
could get Blizzard to include a workaround that is only active when it
sees that it's running under wine/cedega.
Well if you can get the email address of a WoW developer then maybe we
can track down where the problem in WoW
Mike Hearn wrote:
It's a bug in WoW itself, it relies upon the exact way NT maps memory
which is different to how Linux does it. I guess they are storing
information in the high bits of a pointer somewhere or some similar
trick.
One can never be sure, but I suspect this is not do to a bug but
On 5/30/06, Mike Hearn [EMAIL PROTECTED] wrote:
This has been discussed previously. It looks likely that to fix this so
WoW works out of the box requires extensive and intricate changes to the
core of either Wine or the kernel to provide a more accurate match to the
NT memory layout model.
I
WoW Has a all chain of checks that go up all the way to rootkit reveler
to make sure the user is not aided by an automatic system, Given the
player an advantage other players do not have. The Memory layout checks
is for making sure the program is not loaded by a Debugger of sorts. Or
that core
On Tuesday 30 May 2006 16:37, Mike Hearn wrote:
Interesting.. if MacOSX has a similar memory layout as linux, maybe we
could get Blizzard to include a workaround that is only active when it
sees that it's running under wine/cedega.
Well if you can get the email address of a WoW developer
On Mon, 22 May 2006 19:18:07 +0100, Nick Law wrote:
Below is an email regarding this partiicular problem, I would be
grateful for any comments that I can pass back to Jan Riewe. Thanks
Hi Nick,
This has been discussed previously. It looks likely that to fix this so
WoW works out of the box
Opening up the debate again on the World of Warcraft ( WoW ) memory
patch.
Some facts about WoW that may explain why the AppDB page is pretty
active and the wow patch for wine 0.9.12 was downloaded over 1000 times
from the Appdb page during a 4 week period Wow has approximately 6
million
Well ever since me, Mike and Alexandre did the preloader work a few
years ago Wine itself has been execshield resistant, but the apps
themselves may not be (my guess is that this is why Microsoft have not
implemented it themselves ... that and they appear to be scared of
their own dynamic linker
(yeah i'm bored :/)
Seems the WoW appdb page (apart from being a great example of what an
appdb entry should be like!) recommends users patch their Wine to run WoW
properly.
The patch is this one, which I am SURE we discussed before but I can't
find the thread! So my questions are:
* Is this
Mike Hearn wrote:
(yeah i'm bored :/)
Seems the WoW appdb page (apart from being a great example of what an
appdb entry should be like!) recommends users patch their Wine to run WoW
properly.
The patch is this one, which I am SURE we discussed before but I can't
find the thread! So my
On Monday 01 May 2006 20:59, Mike Hearn wrote:
* Is this working around a bug in WoW? (my guess - almost certainly yes)
Perhaps, but there are other problems with the Linux kernel not using the
entire address space.
* What exactly is it doing?! No comments! It seems to be forcing the
On 5/1/06, Mike Hearn [EMAIL PROTECTED] wrote:
Seems the WoW appdb page (apart from being a great example of what an
appdb entry should be like!) recommends users patch their Wine to run WoW
properly.
The patch mentioned particularly causes problems on systems like
Fedora with randomized
At a certain point the screen just turns black, it's always at the same
point, and when looking through the +x11drv trace I can see these
messages at that point:
trace:x11drv:X11DRV_DCICommand (20,(12,2079885668,543712117),(nil))
trace:x11drv:X11DRV_DCICommand (20,(13,1792,543712117),0x7bf88d40)
Tomas Carnecky wrote:
At a certain point the screen just turns black, it's always at the same
point, and when looking through the +x11drv trace I can see these
messages at that point:
trace:x11drv:X11DRV_DCICommand (20,(12,2079885668,543712117),(nil))
trace:x11drv:X11DRV_DCICommand
so.. I know where the problem is.. WoW loads its own Survey.dll which
requires ddraw.dll, ddraw initializes itself and during that it creates
a drawable and a context and calls glXMakeCurrent(). After some tests
WoW unloads ddraw.dll but someone (ddraw, wine or WoW) fails to activate
the old
Tomas Carnecky wrote:
so.. I know where the problem is.. WoW loads its own Survey.dll which
requires ddraw.dll, ddraw initializes itself and during that it creates
a drawable and a context and calls glXMakeCurrent(). After some tests
WoW unloads ddraw.dll but someone (ddraw, wine or WoW) fails
Mike Hearn schrieb:
On Wed, 12 Oct 2005 21:16:05 +, Eddahbi Karim wrote:
Now the mouse problem comes back but the workarounds don't work this
time. It's not a regression, it's a bug enhancement.
ACK
The old workaround for WineX still work according to gentoo-forums [2].
It seems
Mike Hearn mh at codeweavers.com writes:
On Wed, 12 Oct 2005 21:16:05 +, Eddahbi Karim wrote:
Now the mouse problem comes back but the workarounds don't work this
time. It's not a regression, it's a bug enhancement.
The old workaround for WineX still work according to
Christoph cr2005 at u-club.de writes:
Hi
http://lists.transgaming.org/pipermail/winex-devel/2004-May/000259.html
With the attached patch WoW is working for me, clicks on the playfield
are now ok!
I used a derived work [1] of your patches and it worked for me but not
for others.
The
On Fri, 14 Oct 2005 19:02:02 +0200, Christoph wrote:
WoW really seems to relay on this magic address.
And yet it works in Windows which presumably does not have any WoW
specific appgoo in it. So I imagine it's actually some weird quick of the
NT kernel we're not emulating correctly here, but
, -1 = 0xbfe2
trace:loaddll:load_native_dll Loaded module
LC:\\windows\\system\\IMM32.dll : native
EXE not mmap 0x1000, 430080, 7, 50, -1 = 0x1000
trace:loaddll:load_native_dll Loaded module LE:\\World of
Warcraft\\DivxDecoder.dll : native
not mmap 0x7ff9
On 10/15/05, Christoph [EMAIL PROTECTED] wrote:
Mike Hearn schrieb:
Here is maybe a clue. Can anyone outline the role of imm32.dll and if it
can be involved in our problem?
imm32.dll seems to be a dll for internationalizing certain text.
= 0x7bc8
trace:loaddll:load_builtin_dll Loaded module Lkernel32.dll : builtin
set mmap 0x10124000, 73728, 3, 50, -1 = 0x10124000
trace:process:init_current_directory starting in LE:\\World of
Warcraft\\ 0x18
trace:process:find_exe_file looking for LWoW.exe
trace:process:find_exe_file Trying built
On Wed, 12 Oct 2005 21:16:05 +, Eddahbi Karim wrote:
Now the mouse problem comes back but the workarounds don't work this
time. It's not a regression, it's a bug enhancement.
The old workaround for WineX still work according to gentoo-forums [2].
It seems Warcraft relies upon
Mike Hearn schrieb:
On Wed, 12 Oct 2005 21:16:05 +, Eddahbi Karim wrote:
Now the mouse problem comes back but the workarounds don't work this
time. It's not a regression, it's a bug enhancement.
ACK
The old workaround for WineX still work according to gentoo-forums [2].
It seems
Hi,
[EMAIL PROTECTED] 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
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
The test realms are up, which lets players test the next patch. Anyone
tried it to see if the problem is fixed?
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.
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.
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
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
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 0x1000) Seems
more a WoW bug than wine/cedega bug :)
Yes,
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
pgpPMvZ8VJLuB.pgp
Description: PGP signature
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
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: 0xC005 (ACCESS_VIOLATION) at 001B:00650E16
The instruction at 0x00650E16 referenced memory at 0x33991588
Stupid kmail
Sorry
Raphael
pgpcJIYGhghQ6.pgp
Description: PGP signature
fixme:opengl:wglQueryPbufferARB unsupported WGL_PBUFFER_LOST_ARB
(need
glXSelectEvent/GLX_DAMAGED work)
Arg,
i didn't expect this fixme :(
I don't think we have to worry about this fixme. We can always return
GL_FALSE, since that is the way the OpenGL surfaces were created.
From
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
sn, 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,
Ove Kaaven schrieb:
sn, 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
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
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 0x1000) Seems
more a WoW bug than wine/cedega bug :)
Yes, it's a WoW bug, some Windows users are affected too.
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.
Hi,
On Wednesday 15 June 2005 05:18, [EMAIL PROTECTED] 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
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
On Sun, Apr 24, 2005 at 09:23:22AM +1000, Troy Rollo wrote:
On Saturday 23 April 2005 22:12, Alex Woods wrote:
I'm attaching to the process with gdb, but it's not catching things at
the point where they go wrong. Typically I am just seeing a stack like
this though:
#0 0x56752a01 in ??
are going
wrong? How are exceptions caught by wine? A lot of the time WoW
handles the error so can I work back from there?
A lot of the time I get a report like this:
This application has encountered a critical error:
Not enough memory
Program:C:\Program Files\World of Warcraft\WoW.exe
File
On Saturday 23 April 2005 22:12, Alex Woods wrote:
I'm attaching to the process with gdb, but it's not catching things at
the point where they go wrong. Typically I am just seeing a stack like
this though:
#0 0x56752a01 in ?? ()
If it's only giving one frame in the stack trace the cause is
On Thu, Mar 24, 2005 at 10:40:18PM -0500, [EMAIL PROTECTED] wrote:
I applied the two patches from bugzilla
(http://bugs.winehq.org/show_bug.cgi?id=2814#c8) which includes Raphael's
opengl32 fbconf patch and another one from Tim Savannah which looks like
this:
---
On Sat, 26 Mar 2005 11:35:58 +
Alex Woods [EMAIL PROTECTED] wrote:
On Thu, Mar 24, 2005 at 10:40:18PM -0500, [EMAIL PROTECTED] wrote:
I applied the two patches from bugzilla
(http://bugs.winehq.org/show_bug.cgi?id=2814#c8) which includes Raphael's
opengl32 fbconf patch and another
I applied the two patches from bugzilla
(http://bugs.winehq.org/show_bug.cgi?id=2814#c8) which includes Raphael's
opengl32 fbconf patch and another one from Tim Savannah which looks like this:
--- wine2/dlls/x11drv/opengl.c 2005-03-24 20:51:16.0 -0500
+++ wine/dlls/x11drv/opengl.c
Sorry to keep bugging you guys about this, but a recent patch broke the opengl
mode of World of Warcraft again. It simply fails to start, similar to the d3d
mode (except for the fact that I know why d3d mode doesn't work as of now). I
was scanning through the traces and saw no errors though
On Wed, 23 Mar 2005 16:15:18 -0500, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Sorry to keep bugging you guys about this, but a recent patch broke the
opengl mode of World of Warcraft again. It simply fails to start, similar to
the d3d mode (except for the fact that I know why d3d mode
What I meant to say in the previous message was something along the lines of
Here's an opengl trace; let me know if you need any others. Unfortunately,
it seemed to come out in some other language which I am not familiar in. So
here's the opengl trace.
On Wed, 23 Mar 2005 15:22:46 -0600
James Hawkins [EMAIL PROTECTED] wrote:
On Wed, 23 Mar 2005 16:15:18 -0500, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Sorry to keep bugging you guys about this, but a recent patch broke the
opengl mode of World of Warcraft again. It simply fails
On Wednesday 23 March 2005 22:15, [EMAIL PROTECTED] wrote:
Sorry to keep bugging you guys about this, but a recent patch broke the
opengl mode of World of Warcraft again. It simply fails to start, similar
to the d3d mode (except for the fact that I know why d3d mode doesn't work
as of now
On Wed, 23 Mar 2005 23:37:49 +0100
Raphael [EMAIL PROTECTED] wrote:
On Wednesday 23 March 2005 22:15, [EMAIL PROTECTED] wrote:
Sorry to keep bugging you guys about this, but a recent patch broke the
opengl mode of World of Warcraft again. It simply fails to start, similar
to the d3d mode
Hi again,
Hi,
can you try with this patch ?
Regards,
Raphael
Still doesn't work. I attached another opengl trace in case you can pick
out something that's changed though.
Darckness
Thx, intersesting :)
And this one ?
Regards,
Raphael
Index: wgl_ext.c
news and bad news. The good news is that the World of Warcraft
loads now, which is excellent. The bad news twofold: the performance is
AWFUL, and it crashes out in the same place as before (when wine was missing
pbuffer support). But it loads!
Darckness
Noticed this thread on the Rage3D Linux (ATI) Drivers forums:
Fix for WoW in OpenGL mode in wine/cedega (
http://www.rage3d.com/board/showthread.php?t=33807135 ).
Basically, it seems to involve hex-editing WoW.exe (!!!) to filter out a
couple of extensions (mainly GL_ARB_vertex_buffer_object),
On Tuesday 15 March 2005 10:47, Holly Bostick wrote:
Noticed this thread on the Rage3D Linux (ATI) Drivers forums:
Fix for WoW in OpenGL mode in wine/cedega (
http://www.rage3d.com/board/showthread.php?t=33807135 ).
Basically, it seems to involve hex-editing WoW.exe (!!!) to filter out a
On Wed, 2 Mar 2005, Alex Woods wrote:
[...]
Sound works about the same under both alsa and oss (again alsa oss
emulation). It's strange that you get no sound from oss.
Sound depends a lot on the sound card. Some sound cards support only
specific sampling rates while others are more accomodating.
On Fri, Feb 25, 2005 at 11:07:03AM +1100, Troy Rollo wrote:
On Fri, 25 Feb 2005 09:22, Alex Woods wrote:
Over the course of 13 (unlucky for me ;)) crashes, these are the only 3
addresses it has given. My question is what can I do to debug [target
application SEGVs].
I can't find any
1 - 100 of 168 matches
Mail list logo
