World of Warcraft 0.10 Public Test Realm (PTR)

Tomas Carnecky tom at dbservice.com
Sun Mar 5 13:47:02 CST 2006


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 (20,(13,1792,543712117),0x7bf88d40)
> trace:x11drv:X11DRV_DCICommand (20,(11,1792,543712117),0x7bf88d60)
> trace:x11drv:X11DRV_DCICommand (20,(10,1792,543712117),0x7bf88ea8)
> 
> also, these messages don't appear in version 1.9.4 (which is the 'live'
> version). So I suspect that Blizzard added something related to this
> function to the 0.10 version which breaks something.
> 
> When the screen turns black, its just the screen, everything else works,
> keyboard for sure, I can press 'Esc' to get out of the game, not sure
> about the mouse though..
> 

It seems that Blizzard added DDraw HAL.. right after these CDICommand
calls I see:

trace:x11settings:X11DRV_Settings_CreateDriver Setting up display
settings for DDRAW (NoRes)
trace:x11drv:X11DRV_DDHAL_SwitchMode (0,(nil),(nil))

which changes the display setting, but I disabled xvidmode and xrandr so
this really shouldn't do anything.

also, it seems like WoW draws to a completely different buffer after
that because I see two different pictures changing, like the application
would call SwapBuffers() on two buffer that are not updated.. like WoW
would set up a new drawable but not switch to it..

tom




More information about the wine-devel mailing list