http://bugs.winehq.org/show_bug.cgi?id=13225
Summary: Sacrifice Demo: black sqare behind the mouse Product: Wine Version: 0.9.61. Platform: PC URL: http://downloads.gamezone.com/demosfiles/t1699.htm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: jb.faq@gmx.de
If you start Sacrifice you get a masking problem with the mouse. You have a black square behind it. In this bug http://bugs.winehq.org/show_bug.cgi?id=201 we find out, that this is not the same problem. (Have a special look at the comments 36 up to 40). It seems that this is a problem of the (opengl?) rendering: With the vesa driver (or using (export) LIBGL_ALWAYS_INDIRECT=1) this bug doesn't exists, but it is present with the nvidia drivers. I test this with the demo (link in URL above).
My system Set-Up: Software: Gentoo, Kernel 2.6.24-gentoo-r8 vesa-driver (in this test-case, usually nvidia-drivers-96.43.05) git yesterday
Hardware: lspci: 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 440 Go 64M] (rev a3)
http://bugs.winehq.org/show_bug.cgi?id=13225
Jan Buecken jb.faq@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jb.faq@gmx.de Severity|normal |minor Keywords| |download Summary|Sacrifice Demo: black sqare |Sacrifice Demo: black square |behind the mouse |behind the mouse
http://bugs.winehq.org/show_bug.cgi?id=13225
Jan Buecken jb.faq@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |liquid.acid@gmx.net
http://bugs.winehq.org/show_bug.cgi?id=13225
Alexander Dorofeyev alexd4@inbox.lv changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexd4@inbox.lv
--- Comment #1 from Alexander Dorofeyev alexd4@inbox.lv 2008-05-14 16:17:44 --- (In reply to comment #0)
It seems that this is a problem of the (opengl?) rendering: With the vesa driver (or using (export) LIBGL_ALWAYS_INDIRECT=1) this bug doesn't exists, but it is present with the nvidia drivers.
Can you attach glxinfo output with vesa?
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #2 from Tobias Jakobi liquid.acid@gmx.net 2008-05-14 16:23:14 --- At least on the first machine where Jan tested this with VESA glxinfo does NOT work, it simply quits with error message:
tjakobi@yui09:~$ glxinfo name of display: :0.0 X Error of failed request: GLXBadContext Major opcode of failed request: 142 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 17 Current serial number in output stream: 17
yui09 has an Matrox card installed, but our computer lab isn't able to properly setup the mga driver on that system without making the screen unusuable. So vesa is hardcoded into xorg.conf and we only get software mesa on this one (and poor 2D performance also).
We still have yen08 in our office (the Intel i945 system), I could do a test on that one with indirect rendering...
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #3 from Tobias Jakobi liquid.acid@gmx.net 2008-05-14 16:25:53 --- Sorry but I had to switch systems for that:
glxinfo from i945 system:
tjakobi@yen08:~$ LIBGL_ALWAYS_INDIRECT=1 glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: No 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_make_current_read, 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_copy_sub_buffer, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) 945G 20061017 x86/MMX/SSE2 OpenGL version string: 1.3 Mesa 6.5.2 OpenGL extensions: GL_ARB_depth_texture, GL_ARB_fragment_program, GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_point_parameters, 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_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_program, 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_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, 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_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_3DFX_texture_compression_FXT1, GL_APPLE_packed_pixels, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_light_max_exponent, GL_NV_texgen_reflection, GL_NV_texture_rectangle, GL_NV_vertex_program, GL_NV_vertex_program1_1, GL_SGI_color_matrix, GL_SGI_color_table, 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
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x23 24 tc 0 32 0 r y . 8 8 8 8 0 0 0 0 0 0 0 0 0 None 0x24 24 tc 0 32 0 r . . 8 8 8 8 0 0 0 0 0 0 0 0 0 None 0x25 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x27 24 tc 0 32 0 r y . 8 8 8 8 0 0 0 16 16 16 16 0 0 Slow 0x28 24 tc 0 32 0 r . . 8 8 8 8 0 0 0 16 16 16 16 0 0 Slow 0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2a 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2b 24 dc 0 32 0 r y . 8 8 8 8 0 0 0 0 0 0 0 0 0 None 0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 0 0 0 0 0 0 0 0 None 0x2d 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x2f 24 dc 0 32 0 r y . 8 8 8 8 0 0 0 16 16 16 16 0 0 Slow 0x30 24 dc 0 32 0 r . . 8 8 8 8 0 0 0 16 16 16 16 0 0 Slow 0x31 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x32 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x5b 32 tc 0 32 0 r . . 8 8 8 8 0 0 0 0 0 0 0 0 0 Ncon
Going to do a check on my i915 system at home.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #4 from Jan Buecken jb.faq@gmx.de 2008-05-15 04:24:47 --- Created an attachment (id=13071) --> (http://bugs.winehq.org/attachment.cgi?id=13071) glxinfo with vesa driver
Output of glxinfo on my system with the vesa driver.
Hint: I recognized that LIBGL_ALWAYS_INDIRECT=1 doesn't work with the proprietary nvidia drivers, probably because it doesn't use mesa...
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #5 from Jan Buecken jb.faq@gmx.de 2008-05-15 04:26:50 --- Created an attachment (id=13072) --> (http://bugs.winehq.org/attachment.cgi?id=13072) glxinfo with nvidia driver
To complete the outputs of glxinfo and see differences between it I post the output of glxinfo with the nvidia drivers, too.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #6 from Alexander Dorofeyev alexd4@inbox.lv 2008-05-15 16:54:30 --- Created an attachment (id=13086) --> (http://bugs.winehq.org/attachment.cgi?id=13086) float precision hack
This seems to be some float precision issue. It depends on how hardware converts integer values to floating point or vice versa or how it compares it. So it's not surprising this could be different depending on a driver or depending on if it falls back to software rendering (I guess what LIBGL_ALWAYS_INDIRECT=1 is doing). Attached hack fixes it on my machine (geforce6100). At the moment, I'm not sure how to fix it properly, without possibly breaking some other games (or some other hardware) :(.
Please test it (the more hardware tested the better) and let me know how it works there.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #7 from Alexander Dorofeyev alexd4@inbox.lv 2008-05-17 03:43:15 --- Unrelated to this particular bug, but i'm looking into a crash that some people are having. If you are running Sacrifice without crashes, please let me know if you are testing demo or full game, maybe there are some differences. Better post the answer in http://bugs.winehq.org/show_bug.cgi?id=12322.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #8 from Tobias Jakobi liquid.acid@gmx.net 2008-05-17 05:35:59 --- We are only testing the demo Alexander. None of us has the full version available for testing.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #9 from Alexander Dorofeyev alexd4@inbox.lv 2008-05-23 16:42:16 --- Can someone confirm the hack is working, especially if so on non-nvidia hardware?
The frustrating thing about this bug is that as far as I can tell this hack shouldn't make any difference by OpenGL 2.1 specs, because specification suggests that alpha reference and fragment alpha are rounded to integers for the purpose of comparison. I could understand the difference if it was doing something like floor(), but if it's rounded then 1/255 and 1/255 + some very small value shouldn't make difference. But it does, on my machine at least. I would otherwise say it's a driver bug, but it's happening on nvidia, which usually has a very correct opengl and also on other hardware, so maybe I'm not reading specs right.
Another strange thing about it is I can't reproduce it in a test. The basic functionality usually seems to work, but there must be something else in the program that triggers it.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #10 from Tobias Jakobi liquid.acid@gmx.net 2008-05-24 07:14:14 --- Sorry Alexander, I was kinda busy with preparations for my oral exams so I had no time to test this. I'm going to test a patched GIT this evening and report back then!
Greets, Tobias
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #11 from Jan Buecken jb.faq@gmx.de 2008-05-25 17:12:02 --- Sorry, I have a new system (gentoo, amd64, ati mobility radeon hd 2600) and I cannot test this since this problem holds: http://bugs.winehq.org/show_bug.cgi?id=12836
My old system does not exists any longer.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #12 from Tobias Jakobi liquid.acid@gmx.net 2008-05-27 05:50:59 --- Wine GIT with applied hack works on my mobile Intel i915 with mesa GIT. I'm gonna do another test on the i945 system in my office.
So this seems to not only fix problems on nvidia hardware.
Greets, Tobias
http://bugs.winehq.org/show_bug.cgi?id=13225
Alexander Dorofeyev alexd4@inbox.lv changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|directx-d3d |directx-ddraw Ever Confirmed|0 |1 Summary|Sacrifice Demo: black square|Sacrifice: texture |behind the mouse |transparency problems (alpha | |test)
--- Comment #13 from Alexander Dorofeyev alexd4@inbox.lv 2008-05-27 08:33:09 --- (In reply to comment #12)
Wine GIT with applied hack works on my mobile Intel i915 with mesa GIT. I'm gonna do another test on the i945 system in my office.
So this seems to not only fix problems on nvidia hardware.
Thanks.
BTW The problem isn't limited to mouse cursor, there are problems in multiple places in the game with model and GUI textures that have black areas instead of transparent (I guess wherever it relies on alpha test). Also component is directx-ddraw, because it's a d3d7 game. Updating bug data.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #14 from Tobias Jakobi liquid.acid@gmx.net 2008-05-27 11:18:43 --- Confirming that the hack also works on the Intel i945 (with ancient drivers).
I have currently time to test patches so bring it on Alexander! ;-)
http://bugs.winehq.org/show_bug.cgi?id=13225
Alexander Dorofeyev alexd4@inbox.lv changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #13086|0 |1 is obsolete| |
--- Comment #15 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-09 14:28:32 --- Created an attachment (id=13849) --> (http://bugs.winehq.org/attachment.cgi?id=13849) fix for fpu mode problem
I would appreciate if someone tests this patch. Without the previous hack, of course.
I believe this is the right fix for this bug.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #16 from Tobias Jakobi liquid.acid@gmx.net 2008-06-09 16:14:11 --- Tested patch with latest GIT on my Intel i915: works perfectly
Quite some patch for such a "minor" visual error. I didn't expect this to be related to the FPU mode... (read about it on the wine-hackers IRC channel)
Going to do another check with my nvidia GeforceFX...
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #17 from Tobias Jakobi liquid.acid@gmx.net 2008-06-09 16:57:44 --- Tested on my FX, also works there.
I didn't really test it on my desktop system in the past, so maybe I didn't notice this, but there are a lot of these messages on the console: err:d3d_surface:d3dfmt_p8_init_palette This code should never get entered for DirectDraw!, expect problems
Attaching a log...
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #18 from Tobias Jakobi liquid.acid@gmx.net 2008-06-09 16:59:17 --- Created an attachment (id=13855) --> (http://bugs.winehq.org/attachment.cgi?id=13855) sacrifice running with GIT and FPU patch applied
hardware is: 01:00.0 VGA compatible controller: nVidia Corporation NV35 [GeForce FX 5900] (rev a1)
nvidia-drivers-100.14.19
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #19 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-09 17:16:15 --- (In reply to comment #17)
Tested on my FX, also works there.
Thanks.
I didn't really test it on my desktop system in the past, so maybe I didn't notice this, but there are a lot of these messages on the console: err:d3d_surface:d3dfmt_p8_init_palette This code should never get entered for DirectDraw!, expect problems
Attaching a log...
Hmm weird I've never seen this error on my system. Is my patch causing it somehow or it's unrelated? The error itself is not always really an error. It happens under some circumstances (like because of game bugs). Unless there are visible rendering issues it can be ignored. Strange I'm not seeing it though.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #20 from Tobias Jakobi liquid.acid@gmx.net 2008-06-11 14:07:27 --- (In reply to comment #19)
Hmm weird I've never seen this error on my system. Is my patch causing it somehow or it's unrelated? The error itself is not always really an error. It happens under some circumstances (like because of game bugs). Unless there are visible rendering issues it can be ignored. Strange I'm not seeing it though.
It doesn't seem to be related to the patch. I tried Sacrifice.exe with wine-1.0rc3 and I still get these error messages on the console. I don't get them on my Intel though.
Should I open a new bug for this "harmless" error messages (as I'm not seeing any obvious visual errors)? However I have another problem on my Intel now: I can't run Sacrifice.exe in non-vdesktop mode with getting my whole X server to crash when entering in-game (I get to the menu, but as soon as loading for the tutorial is finished and the engine gets in-game X restarts - currently bisecting, maybe this is also a driver bug).
Cheers, Tobias
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #21 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-11 14:18:50 --- (In reply to comment #20)
(In reply to comment #19) Should I open a new bug for this "harmless" error messages (as I'm not seeing any obvious visual errors)?
I would say, no. Surely, it does look kind of strange that this doesn't happen on my machine (game takes some different codepath for some reason maybe??). But there are tons of serious problems in Wine, so, unless it somehow hurts game's functionality, it's not worth it IMO.
However I have another problem on my Intel now: I can't run Sacrifice.exe in non-vdesktop mode with getting my whole X server to crash when entering in-game (I get to the menu, but as soon as loading for the tutorial is finished and the engine gets in-game X restarts - currently bisecting, maybe this is also a driver bug).
AFAIK if it crashes X server or whole system then it's driver bug because this should never happen no matter what Wine / game does.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #22 from Tobias Jakobi liquid.acid@gmx.net 2008-06-11 14:48:24 --- However it doesn't crash with wine-0.9.61, that's what I know currently. I haven't finished bisecting though.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #23 from Austin English austinenglish@gmail.com 2008-06-11 15:51:14 --- (In reply to comment #21)
(In reply to comment #20)
(In reply to comment #19) Should I open a new bug for this "harmless" error messages (as I'm not seeing any obvious visual errors)?
I would say, no. Surely, it does look kind of strange that this doesn't happen on my machine (game takes some different codepath for some reason maybe??). But there are tons of serious problems in Wine, so, unless it somehow hurts game's functionality, it's not worth it IMO.
If the behavior differs between wine and windows, file a bug. Mark it as trivial, and don't worry about it much, but if the bug is never filed, no one will know to fix it.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #24 from Tobias Jakobi liquid.acid@gmx.net 2008-06-12 06:44:08 --- Filed a new bug here: http://bugs.winehq.org/show_bug.cgi?id=13860
What about this one? I think it's fixed now, right? Jan won't be able to set it to fixed because his old system is no longer in use, so someone else from the admin staff should do it.
Greets, Tobias
http://bugs.winehq.org/show_bug.cgi?id=13225
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #25 from Austin English austinenglish@gmail.com 2008-06-12 07:38:43 --- Reported fixed, reopen if it's not.
http://bugs.winehq.org/show_bug.cgi?id=13225
Alexander Dorofeyev alexd4@inbox.lv changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |
--- Comment #26 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-12 11:24:01 --- No the fix isn't in the git yet so it can be considered officially fixed yet. I haven't yet properly tested it with my collection of old d3d games and demos, so I didn't even bother trying to submit. As it is somewhat extensive and affecting many routines (biggest part is repetitive wrappers and shouldn't break anything, but you never know) and lacking a test (unfortunately it's impossible to test because it is hardware dependent and undefined), it probably will be rejected due to the ongoing code freeze anyway.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #27 from Tobias Jakobi liquid.acid@gmx.net 2008-06-12 15:08:28 --- So we wait until the code freeze is over, right?
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #28 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-13 07:04:56 --- Yes, that's the plan so far.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #29 from Jan Buecken jb.faq@gmx.de 2008-06-22 07:07:24 --- mmh, I used wine-1.0 and the new ati-driver-8.501 (card: ati mobility radeon hd 2600) I don't have the trancperancy problem with this, hence I cannot test the hack.
http://bugs.winehq.org/show_bug.cgi?id=13225
Alexander Dorofeyev alexd4@inbox.lv changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED
--- Comment #30 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-23 16:32:38 --- OK, patch committed, so this should be fine now. Marking fixed.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #31 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-24 13:52:46 --- hash of commit cb5e06c944251a5de16e12ecd2253c158764ee4c (as recommended in post 1.0 development note).
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #32 from Tobias Jakobi liquid.acid@gmx.net 2008-06-25 09:36:21 --- Reporting fixed in latest GIT (on Intel i915).
@Jan: As far as I'm concerned you can close this one.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #33 from Alexander Dorofeyev alexd4@inbox.lv 2008-06-25 10:39:14 --- AFAIK status should be left intact, otherwise it will interfere with the "bugs fixed in release ..." statistics. It will be closed on release.
http://bugs.winehq.org/show_bug.cgi?id=13225
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #34 from Alexandre Julliard julliard@winehq.org 2008-06-27 10:15:43 --- Closing bugs fixed in 1.1.0.
http://bugs.winehq.org/show_bug.cgi?id=13225
--- Comment #35 from Tobias Jakobi liquid.acid@gmx.net 2008-07-02 08:43:14 --- (In reply to comment #20)
However I have another problem on my Intel now: I can't run Sacrifice.exe in non-vdesktop mode with getting my whole X server to crash when entering in-game (I get to the menu, but as soon as loading for the tutorial is finished and the engine gets in-game X restarts - currently bisecting, maybe this is also a driver bug).
I can confirm that this is NOT a wine bug. I downgraded xorg-server yesterday from current GIT master to 1.4.99.905 and the problem is gone now.
http://bugs.winehq.org/show_bug.cgi?id=13225
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-ddraw |directx-d3d
-
wine-bugs＠winehq.org