http://bugs.winehq.org/show_bug.cgi?id=12641
Summary: WineD3d does not respect GL_EXT_fog_coord Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: markus.amsler@oribi.org
WineD3D usex vertex.fogcoord, fragment.fogcoord, even if GL_EXT_fog_coord is not supoorted. That's the case e.g. with the r300 mesa drivers.
http://bugs.winehq.org/show_bug.cgi?id=12641
--- Comment #1 from Austin English austinenglish@gmail.com 2008-10-17 14:55:19 --- Is this still an issue in current (1.1.6 or newer) Wine?
http://bugs.winehq.org/show_bug.cgi?id=12641
--- Comment #2 from H. Verbeet hverbeet@gmail.com 2008-10-17 15:02:37 --- Yes.
http://bugs.winehq.org/show_bug.cgi?id=12641
--- Comment #3 from Markus Amsler markus.amsler@oribi.org 2008-10-17 16:02:07 --- I'm not sure anymore if this is a bug.
copied from ARB_vertex_program specification:
Dependencies on EXT_fog_coord
If EXT_fog_coord is not supported, references to fog coordinates should be removed from Table X.1, and the description of ArrayElement in section 2.8. The line "fogcoord" should be removed from the <vtxAttribItem> grammar rule, and "vertex.fogcoord" should be removed from Table X.2. Also, the use of FOG_COORDINATE_SOURCE_EXT in section 3.10 should be removed.
Even if EXT_fog_coord is not supported, the fog coordinate output (result.fogcoord) still operates as specified. When in vertex program mode, there are no well-defined eye coordinates that could be used for fog. This means that the functionality of EXT_fog_coord is required to implement ARB_vertex_program even if the EXT_fog_coord extension itself is not supported.
For me this looks like paragraph 1(vertex.fogcoord not supported) contradicts paragraph 2 (EXT_fog_coord is required to implement ARB_vertex_program).
http://bugs.winehq.org/show_bug.cgi?id=12641
--- Comment #4 from H. Verbeet hverbeet@gmail.com 2008-10-17 16:22:06 --- The way I read that is that vertex.fogcoord and fragment.fogcoord are unavailable, while result.fogcoord is available. The implication is that the hardware still needs to be able to source the fogcoord from something else than the fragment depth. Iow, even though the behaviour would be well defined, it doesn't make a whole lot of sense to implement ARB_vertex_program but not EXT_fog_coord.
http://bugs.winehq.org/show_bug.cgi?id=12641
Markus Amsler markus.amsler@oribi.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX
--- Comment #5 from Markus Amsler markus.amsler@oribi.org 2008-10-17 17:54:41 ---
it doesn't make a whole lot of sense to implement ARB_vertex_program but not EXT_fog_coord.
Agreed. Resolving as wontfix as the sensible thing to do is implement EXT_fog_coord in mesa. Changing wine because of some obscure specification details would be way overkill.
http://bugs.winehq.org/show_bug.cgi?id=12641
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from James Hawkins truiken@gmail.com 2008-10-17 18:01:33 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=12641
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|CVS/GIT |unspecified
-
wine-bugs＠winehq.org