[5/8] WineD3D: Readd the strided data trace
stefandoesinger at gmx.at
Thu Jan 4 06:29:42 CST 2007
Am 04.01.2007 um 02:07 schrieb Ivan Gyurdiev:
> Stefan Dösinger wrote:
>> I removed that call accidentally in one of my former patches, but
>> I think it is still a good idea to trace the final strided sources
>> used by drawprim
> You removed it from a d3d8 fixed function FVF-only codepath, and
> are adding it back into a shared codepath.
> That function doesn't work properly with vertex declarations, it
> will only work with FVFs, which have different strided layout.
> FVFs use fixed semantic index [u.s.position], vdecl asks the shader
> for an index [u.s.input[idx]].
> Furthermore, the trace isn't needed for declarations, because they
> have their own (better) traces.
The idea was to have a trace of the final vertex declaration that
drawprim gets from the state manager. But you are right, for indexed
vdecls the trace is rather pointless.
More information about the wine-devel