https://bugs.winehq.org/show_bug.cgi?id=55794
Bug ID: 55794 Summary: DX10 Far Cry 2 crashes when loading round Product: Wine Version: 8.18 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs@winehq.org Reporter: svyatpro@gmail.com
Created attachment 75278 --> https://bugs.winehq.org/attachment.cgi?id=75278 Crash window
When you start a game in DX10 mode it crashes at the end of round loading.
0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. 0924:fixme:d3d_shader:shader_glsl_input_pack Unhandled sysval semantic 0x2. 0924:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #813: 0924:fixme:d3d_shader:print_glsl_info_log Vertex info 0924:fixme:d3d_shader:print_glsl_info_log ----------- 0924:fixme:d3d_shader:print_glsl_info_log 0(31) : warning C7050: "R2.zw" might be used before being initialized 0924:fixme:d3d_shader:print_glsl_info_log 0924:fixme:d3d_shader:print_glsl_info_log Fragment info 0924:fixme:d3d_shader:print_glsl_info_log ------------- 0924:fixme:d3d_shader:print_glsl_info_log 0(43) : warning C7050: "R0.zw" might be used before being initialized 0924:err:d3d:wined3d_debug_callback 050A0FD0: "GL_INVALID_ENUM error generated. Invalid buffer format.". 0924:err:d3d:wined3d_debug_callback 050A0FD0: "GL_INVALID_ENUM error generated. Invalid buffer format.". 0924:err:d3d:wined3d_debug_callback 050A0FD0: "GL_INVALID_ENUM error generated. Invalid buffer format.". 0924:err:d3d:wined3d_debug_callback 050A0FD0: "GL_INVALID_ENUM error generated. Invalid buffer format.".
https://bugs.winehq.org/show_bug.cgi?id=55794
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- Can you try to get a log with WINEDEBUG=+d3d11,+dxgi,+d3d?
https://bugs.winehq.org/show_bug.cgi?id=55794
--- Comment #2 from Zeb Figura z.figura12@gmail.com --- Also, you've marked the OS as "Windows", are you actually using wined3d.dll on Windows?
https://bugs.winehq.org/show_bug.cgi?id=55794
--- Comment #3 from Svyatpro svyatpro@gmail.com --- Yes, I compile wined3d by my own and test it on Windows. It seems to be a regression because I remember it worked for me some time ago on several machines.
-
WineHQ Bugzilla