Dawn of War - Dark Crusade, graphics problem

halp · Post by **halp** » Sun May 17, 2009 4:13 pm

Hello,

I have some graphics problems with Dark Crusade. I have tested both windowed and fullscreen with lowest settings, it makes no difference. It plays fine in highest settings in Windows, so my graphics card is not the problem. Maybe the drivers for linux is crappy or something, but i havent experienced anything like this before in any other game.

http://appdb.winehq.org/objectManager.p ... n&iId=6051 says wine v0.9.35 is working and newer versions may cause problems.
Is there any chanse that downgrading wine to 0.9.35 would make it better? I cant test this myself because i dont know how do downgrade properly.

Its pretty strange because some of the graphics works alright, but some parts does not. I have some screenshots:

Main menu, most looks fine except menu.

Loading screen.

Campaign menu, doesnt look too good.

In-game.

Thank you for your support! I really appriciate it.

Danila Sentiabov · Post by **Danila Sentiabov** » Sun May 17, 2009 5:39 pm

Hi.

It plays fine in highest settings in Windows, so my graphics card is not the

problem.

You're not quite right. Playing fine in Windows doesn't mean it will (or
should) play in Wine. First, Linux uses different drivers. Second, some
DirectX features in Wine work through different internal mechanisms (for
example, shaders of higher level).

Anyway, no one will help you until you provide your computer configuration
(most importantly - your video card model, name and version of your video
driver - all this information could be obtained via glxinfo console
utility).

--
Best regards,
Danila Sentiabov aka dsent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

halp · Post by **halp** » Mon May 18, 2009 10:37 am

Code: Select all

anton@anton ~ $ glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
    GLX_OML_swap_method, GLX_SGI_swap_control, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_swap_control, 
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_visual_select_group
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 965GM 20061102 x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 7.2
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, 
    GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, 
    GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_point_parameters, 
    GL_ARB_point_sprite, GL_ARB_shader_objects, GL_ARB_shading_language_100, 
    GL_ARB_shading_language_120, GL_ARB_shadow, GL_ARB_texture_border_clamp, 
    GL_ARB_texture_compression, GL_ARB_texture_cube_map, 
    GL_ARB_texture_env_add, GL_ARB_texture_env_combine, 
    GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, 
    GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two, 
    GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, 
    GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, 
    GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, 
    GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, 
    GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract, 
    GL_EXT_clip_volume_hint, GL_EXT_cull_vertex, GL_EXT_compiled_vertex_array, 
    GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, 
    GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, 
    GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_polygon_offset, 
    GL_EXT_rescale_normal, GL_EXT_secondary_color, 
    GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_wrap, 
    GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, 
    GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, 
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, 
    GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, 
    GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, 
    GL_EXT_vertex_array, GL_3DFX_texture_compression_FXT1, 
    GL_APPLE_client_storage, GL_APPLE_packed_pixels, 
    GL_ATI_blend_equation_separate, GL_ATI_separate_stencil, 
    GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, 
    GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, 
    GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent, 
    GL_NV_point_sprite, GL_NV_texture_rectangle, GL_NV_texgen_reflection, 
    GL_NV_vertex_program, GL_NV_vertex_program1_1, GL_OES_read_format, 
    GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, 
    GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture, 
    GL_SUN_multi_draw_arrays

Danila Sentiabov · Post by **Danila Sentiabov** » Tue May 19, 2009 4:04 am

So, it's Intel.

As I see it (I may be wrong, but unlikely), there are two possibilities:
1. It will not work until Intel fixes its drivers.
2. It will never work (if 965GM doesn't support features that Wine uses to
emulate some DirectX calls).
Sad but true.

--
Best regards,
Danila Sentiabov aka dsent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

stimpak · Post by **stimpak** » Tue May 19, 2009 6:38 pm

Danila Sentiabov wrote:So, it's Intel.

As I see it (I may be wrong, but unlikely), there are two possibilities:
1. It will not work until Intel fixes its drivers.
2. It will never work (if 965GM doesn't support features that Wine uses to
emulate some DirectX calls).
Sad but true.

--
Best regards,
Danila Sentiabov aka dsent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

Code: Select all

Some of the key features in 2.6.29 are:

    * Kernel-based mode setting for graphics adapters - for Intel hardware in particular, at this time. The addition of this code is the beginning of the end of a multi-year effort to rationalize our handling of 3D graphics hardware and provide a top-quality graphical experience to Linux users

kernel 2.6.29 was released at March 23, 2009 so if you havent tried the updated kernel you might want to give it a try[/code]

DL · Post by DL » Wed May 20, 2009 6:27 am

Unless it's a laptop, you should just buy a nvidia card.Wine really only works well with nvidia cards (although ATI support is starting to get better supposably)

Danila Sentiabov · Post by **Danila Sentiabov** » Wed May 20, 2009 12:09 pm

On Wed, May 20, 2009 at 03:38, stimpak <[email protected]> wrote:

kernel 2.6.29 was released at March 23, 2009 so if you havent tried the
updated kernel you might want to give it a try[/code]

According to some reports (Phoronix, for example), the new Intel driver
infrastructure (in kernel, Mesa and Xorg) is build on a better foundation
than old one, but still in early stage of development. It actually contains
more bugs and performs much slower than the old one in most cases. There is
still a long way for it to show its benefits.

--
Best regards,
Danila Sentiabov aka dsent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

Danila Sentiabov · Post by **Danila Sentiabov** » Thu May 21, 2009 3:50 am

On Wed, May 20, 2009 at 15:27, DL <[email protected]> wrote:

Unless it's a laptop, you should just buy a nvidia card.Wine really only
works well with nvidia cards (although ATI support is starting to get better
supposably)

Talking about NVIDIA cards - there is another advantage in using them.
NVIDIA proprietary driver supports VDPAU to offload video decoding (MPEG2,
MPEG4, WMV and AVC) to graphics card (8xxx series and newer). It's already
working and stable (playing FullHD video with 5% CPU load on my 3 years old
machine).

--
Best regards,
Danila Sentiabov aka dsent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

stimpak · Post by **stimpak** » Fri May 22, 2009 3:05 pm

Danila Sentiabov wrote:On Wed, May 20, 2009 at 03:38, stimpak <[email protected]> wrote:

kernel 2.6.29 was released at March 23, 2009 so if you havent tried the
updated kernel you might want to give it a try[/code]
According to some reports (Phoronix, for example), the new Intel driver
infrastructure (in kernel, Mesa and Xorg) is build on a better foundation
than old one, but still in early stage of development. It actually contains
more bugs and performs much slower than the old one in most cases. There is
still a long way for it to show its benefits.

--
Best regards,
Danila Sentiabov aka dsent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

sigh... and i was happy for a sec about those all poor folks with ati in their riggs

-but never-the-less the ati issue is not abandoned