Re: [2/5] WineD3D: Remove the FVF codepath from drawprim
Not specific to this patch, but will you remove the fvf field from the stateblock as well?
Am Dienstag, 19. Juni 2007 15:44 schrieb H. Verbeet:
Not specific to this patch, but will you remove the fvf field from the stateblock as well? I am thinking about that, but currently it has to be known to wined3d for reporting the proper fvf on GetFVF with state recording. A future patch could put an fvf field into the vertexdecl so GetFVF fetches the stateblock and reads the fvf from it.
On 19/06/07, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote:
Am Dienstag, 19. Juni 2007 15:44 schrieb H. Verbeet:
Not specific to this patch, but will you remove the fvf field from the stateblock as well? I am thinking about that, but currently it has to be known to wined3d for reporting the proper fvf on GetFVF with state recording. A future patch could put an fvf field into the vertexdecl so GetFVF fetches the stateblock and reads the fvf from it.
Assuming you're talking about the d3d8/d3d9 declaration, yeah, that could work.
Am Dienstag, 19. Juni 2007 18:46 schrieb H. Verbeet:
On 19/06/07, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote:
Am Dienstag, 19. Juni 2007 15:44 schrieb H. Verbeet:
Not specific to this patch, but will you remove the fvf field from the stateblock as well?
I am thinking about that, but currently it has to be known to wined3d for reporting the proper fvf on GetFVF with state recording. A future patch could put an fvf field into the vertexdecl so GetFVF fetches the stateblock and reads the fvf from it.
Assuming you're talking about the d3d8/d3d9 declaration, yeah, that could work. D3D7 has no SetFVF/GetFVF method, so yes. D3D7 would just call SetVertexDeclaration and be happy
participants (2)
-
H. Verbeet -
Stefan Dösinger