http://bugs.winehq.org/show_bug.cgi?id=19128
Summary: UseGLSL=disabled stops FIFA WM 2006 with vertex shader error Product: Wine Version: 1.1.24 Platform: PC OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: hoehle@users.sourceforge.net CC: stefandoesinger@gmx.at
With UseGLSL="disabled", FIFA WorldCup 2006 freezes with a black screen as a zillion GL_INVALID_OPERATION scroll by.
Noteworthy log messages at the beginning are: fixme:d3d_shader:shader_arb_generate_vshader HW VertexShader Error at position 0: "Error on line 28: missing comma (hint: '[')" fixme:d3d_draw:drawStridedFast >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION (0x502) from glDrawElements @ drawprim.c / 50 fixme:d3d_shader:shader_arb_generate_vshader HW VertexShader Error at position 0: "Error on line 33: missing comma (hint: '[')"
Later, it is this exactly this fixme:drawStridedFast >>>>>>>>>>> which scrolls by continuously. I've used wine-1.1.24, although Stefan added a few patches since. I prefer to stick to releases for tests.
Hmm, I already encountered that drawStridedFast message (with GLSL) in 2weistein Demo in wine-1.1.21 (there it was "only" reported ~ thousand times). BTW, 2weistein Demo works great with or without UseGLSL -- even better without it in the main menu, but that's another issue.
With (default) GLSL, FIFA WC 2006 works flawlessly on the MacOS -- the children have totaled hours of game play. (Alas, I'd need to perform a full install prior to submitting AppDB results about the Mac).
Using nVidia "early 2009" Mac Mini with OS X 10.5.7 and XQuartz 2.3.3.2
http://bugs.winehq.org/show_bug.cgi?id=19128
--- Comment #1 from Stefan Dösinger stefandoesinger@gmx.at 2009-06-29 11:10:13 --- MacOS does not support the result.clip[n] syntax that GL_NV_vertex_program2_option adds. This is a bug in MacOS. I haven't filed a radar yet, but it is nicely reproducible.
If you hack up use_nv_clip() in dlls/wined3d/arb_program_shader.c to return FALSE the ARB problems should go away. I don't know about the GLSL problem though. The drawStridedFast() errors are a pretty generic symptom, and it essentially means that the driver does not like some state we set. There are thousands of different ways to get them.
http://bugs.winehq.org/show_bug.cgi?id=19128
--- Comment #2 from Jörg Höhle hoehle@users.sourceforge.net 2009-09-15 03:57:21 --- When use_nv_clip returns FALSE in wine-1.1.29 then WC 2006 works equally well with or without UseGLSL. I observed no difference.
The number of GL errors in the console increases from 2 to 4 with UseGLSL=disabled. I thought I had copy&pasted them into my notes but I'm sorry I can't find them right now.
http://bugs.winehq.org/show_bug.cgi?id=19128
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #3 from Jörg Höhle hoehle@users.sourceforge.net 2010-06-12 15:06:58 --- Forgot to mark this fixed long ago.
As of wine-1.2rc3, no difference with UseGLSL disabled or default; very few logs from Wine: fixme:d3d:device_resource_released Vertex buffer released while bound to a state block, stream 0 err:d3d:IWineD3DDeviceImpl_Reset Cannot change the back buffer count yet
http://bugs.winehq.org/show_bug.cgi?id=19128
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Alexandre Julliard julliard@winehq.org 2010-06-18 12:46:54 --- Closing bugs fixed in 1.2-rc4.
http://bugs.winehq.org/show_bug.cgi?id=19128
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Mac OS X 10.5 |Mac OS X