radeon+wine+game intro fine, in-game black

[_______0]

hi,

Playing a game with wine yields weird results. The menu is perfectly rendered at very high cpu, options, settings etc all work.

When the game starts the HUD shows up for a second then dissapears, and some others effects remain (during intro). When the game actually begins it shows the fonts for instructions but no picture.

Code: Select all

app-emulation/wine-1.5.21

I am using open source radeon driver. And here some log from wine:

Code: Select all

fixme:shell:SHGetKnownFolderPath flags 0x0000a000 not supported
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
fixme:win:EnumDisplayDevicesW ((null),0,0x32e0dc,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32e020,0x00000000), stub!
fixme:wbemprox:client_security_SetBlanket 0xf4f8af28, 0x13b800, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0xf4f8af28
fixme:win:EnumDisplayDevicesW ((null),0,0x32d22c,0x00000000), stub!
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x798de0c,0x00000000), stub!
ERROR: 
Could Not Find D3DKMTEscape in gdi32.dll
Could Not Find D3DKMTOpenAdapterFromHdc in gdi32.dll
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:win:EnumDisplayDevicesW ((null),0,0x798da6c,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x434f5441 (as fourcc: ATOC) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x434f5441) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x42563252 (as fourcc: R2VB) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x42563252) in the format lookup table
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000016
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:state_zfunc D3DCMP_NOTEQUAL and D3DCMP_EQUAL do not work correctly yet.
fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x13410568 stub!
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x13390218 stub!
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x133d03c0 stub!
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x13450710 stub!
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

I've played with some regedit settings to no avail.

[evgeniusx]

You need to use proprietary driver

[HolgerB]

You need to use proprietary driver

A pretty general reply but so was the question of the TO.

A less general reply:
Similar to Noveau the 3D feature set provided by the free Radeon driver is sometimes / often not good enough to run more demanding games (be it WINE or native). YMMV...depending on driver version, WINE version and the AMD card used.

The best place to get valuable informations for running games under WINE is often enough the Wine AppDB. Check out the entries for your game. May be someone with identical or similar hardware had the same issue and even has posted a solution.

[Hu]

You need to use proprietary driver

That depends on the game. As HolgerB noted, for some games, the open drivers are insufficient. For others, they work quite well.

[fpemud]

I want to ask another related question, hope it's not rude

For the case when open drivers are insufficient, I'd like to know a more detailed reason. like which feature is lacking?
For one thing, I'm curious, for another, It may help me to file a better bug report.

The first step is to know what opengl feature a game need.
But it is a big obstacle.
In games docs, there's generally only some simplest description like "requires directx 9.0c".

The second step is to know mesa's feature status.
It is easier (relatively), at least there's code and comment.

Below is how to do this in more detail in my imagination:

for games using opengl:
1. list all the opengl api a executable file calls by a static analyse. (which command?)
2. read mesa doc to see which mesa feature every gl-api maps to. (which doc?)
3. read mesa doc to see the feature status. (mesa feature status page)
4. read mesa doc to see if the gl-api is fully implemented (which doc?)

for games using directx:
1. list all the directx api a executable file calls by a static analyse. (which command?)
2. read wine doc to see what gl feature is used to implement a dx-api. (which doc?)
3. read mesa doc to see the gl feature status.

Generally, there's only error phenomenon and some test results on wine-appdb, no deeper analyze.
So I don't think wine-appdb is helpful on this level.

[_______0]

glxinfo

^^^ that provides all info possibly needed by ones card and xorg's log.

What's the repercusion of having radeon without LLVM option with the new option?

The new mesa update has disabled both llvm and r600-llvm-compiler USE flags which where good for I don't remember what.

What about glamor USE flag, is it worth it?

It's so damn hard to get an open source graphics driver just right :/

[fpemud]

Yes, glxinfo and xorg.log can show what gl version / extension a video card supports.

But how to know what gl feature a game need?

Does xorg.log contain information like some program failed to find a gl-ext?

[_______0]

by checking which DirectX the game uses. By the way some games can be played with more than one DirectX for compat reasons. Although the latest ones might be DirectX11 only.

[alex6]

_______0 > You should check this page : http://wiki.winehq.org/UsefulRegistryKeys

I had some games which was not running before using this.Now most of games are running thanks to that page.

The idea is launching "regedit" in console and trying different values of the direct3D keys and try again to run the game.

You can also try to ask the same question on winehq forums, some wine developpers hanging aroud on that forum can sometime know exactly what it comes from

[alex6]

Another usefull link :
http://wiki.winehq.org/Performance