Re: [PATCH 5/6] d3d9: Handle stateblocks in d3d9_device_SetVertexShader().

[Henri Verbeet]

On Tue, 26 Feb 2019 at 00:35, Zebediah Figura  wrote:
> Right, okay, thanks. So then would the translation happen on the wined3d
> side? I.e. would we have d3d[789] call wined3d_device_set_render_state()
> as now, and that would forgo invalidating state for things like depth
> bias until a draw call occurs? Or would the client d3d libraries be
> responsible for calling wined3d_device_set_render_state() only for
> states that actually correspond to wined3d render states?

Eventually, we'd like to just get rid of
wined3d_device_set_render_state(). Until that happens, we'd probably
have to do some filtering in the client libraries. I don't think the
exact approach for that is critical at this stage though.