new to wine, Guild Wars don't display correctly

[Stefan Dösinger]

Am Freitag, 31. März 2006 09:12 schrieb BONNEL Christophe:
>  Hi everyone,
>
>  Sorry in advance not to know where to post, but I'm new to wine.
It would be better to post requests like this to wine-users at winehq.com

>  First of all, I'm under debian stable and i'm using the debian package
> wine_0.9.10~winehq1-2_i386.deb. My kernel is 2.6.8 and my graphic card is
> an ati radeon 9000pro (I know ...ouch...)
The fglrx driver you mentioned doesn't work any more on those cards. PPracer 
has problems too: Start the "Doing" course. Head to the yellow arrows on the 
left. They will disapper when you come really close.

>  So i first try with the dri driver and , although my 3D was ok(openGL1.2
> it seems), it was too slow to be playable and my mouse didn't appear.
So it basically worked with the open source driver?

>  So i use now the official ati last driver(openGL 1.3 it seems). Now, most
> of the images doesn't appear. If you know guild wars, in the login screen,
> i have only rocks, the background image behind rocks and the "window" for
> login in front of rocks don't appear.
You hit the bug ati introduced with 8.19.10. I think it's related to opengl 
display lists, and I've reported it to ati months ago. Didn't get a reply so 
far

>  I can send you the lasts many "fixmes" that appears but for some seconds,
> i have approximatively 1Mo file. However, i have no "err". The lasts line
> are : fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(190,15)
> not handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(191,15) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(192,15) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(193,-1) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(194,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(198,0) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(199,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(200,0) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(201,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(202,0) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(203,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(204,0) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(205,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(206,0) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(207,2) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(208,1) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(209,1) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(162,-1) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(163,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(164,1065353216) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(165,1) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(172,3) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(173,1) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(178,1065353216) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(179,1065353216)
> not handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(180,0) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(181,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(182,1065353216) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState (0x4d290020)->(183,0) not
> handled yet fixme:d3d:IWineD3DDeviceImpl_SetRenderState
> (0x4d290020)->(184,0) not handled yet
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState >>>>>>>>>>>>>>>>> 500 from
> glStencilOp(...) @ device.c / 3809
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState >>>>>>>>>>>>>>>>> 500 from
> glStencilOp(...) @ device.c / 3809
> fixme:d3d:IWineD3DDeviceImpl_SetRenderState >>>>>>>>>>>>>>>>> 500 from
> glStencilOp(...) @ device.c / 3809
These are harmless, they are fixmes from the direct3d initialization. Some 
render states aren't supported by wines d3d implementation, but when wined3d 
initializes, it sets them to the default value, which causes such messages. 
The last three fixmes are fixed in the current cvs version, and they are 
harmless too.

>  There are also in the upper-middle of the log file many :
>  fixme:d3d:IWineD3DDeviceImpl_EvictManagedResources (0x4d290020) : stub
EvictManagedTextures is a windows-related video memory management thing, and 
it won't have much impact too. If it has, then it will only show slightly 
reduced performance for a few secounds after loading. It should remove the 
managed textures from the video card, to make the memory free for new 
textures.

>  Hope this can help a bit....
>  My command line to launch the games is :
>  wine "E:/toph/games/GUILD WARS/Gw.exe" 2>gw.wine
>  I use win98 version per default because sometimes with win2k i have some
> ntdll errors when connecting to internet(areanet). I don't use anything
> else. I try display by hardware or emulation, with simple or double buffer,
> in a window or in directly, with pixel shader or not, but nothing works.
> Per default, my screen is 1024*768*24bits
Should be fine

>  Note that tuxracer (or ppracer) works so i don't think it comes from the
> driver, but i can make mistakes...
See above

WineD3D has serious performance problems, somehow related to textures. I hope 
that I can debug them during the weekend, but I can't give garantees. These 
problems seem to be related to textures. My tests with 3dmark2000 show that 
texture rendering should be 10 times faster than it is.

I hope I could help you,
Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20060331/7351a39f/attachment.pgp