Eventually, the FVF path should be removed from wined3d completely. We should convert the FVF in d3d8 to a vertex declaration, just like in d3d9.
Am Montag 19 Februar 2007 16:42 schrieb H. Verbeet:
Eventually, the FVF path should be removed from wined3d completely. We should convert the FVF in d3d8 to a vertex declaration, just like in d3d9.
Agreed.
But I think we should keep the FVF->decl conversion at a central place instead of having 3 copies of it(d3d9, d3d8, ddraw). I think we could make a single exported function to convert a fvf->wined3d decl which does not depend on any other code in wined3d
On 20/02/07, Stefan Dösinger stefan@codeweavers.com wrote:
But I think we should keep the FVF->decl conversion at a central place instead of having 3 copies of it(d3d9, d3d8, ddraw). I think we could make a single exported function to convert a fvf->wined3d decl which does not depend on any other code in wined3d
Sure. I think it should be easy enough to just add another constructor for the wined3d vertex declaration that takes an FVF instead of an array of WINED3DVERTEXELEMENT's.