summaryrefslogtreecommitdiffstats
path: root/src/gallium/state_trackers
diff options
context:
space:
mode:
authorAxel Davy <[email protected]>2019-04-09 23:57:37 +0200
committerAxel Davy <[email protected]>2019-04-30 19:18:50 +0200
commit1fc0714039ce5fced2317d258fbc467af39f3dca (patch)
tree30140e31727897b16ee076f478c239436bb76e95 /src/gallium/state_trackers
parentd9a4025fa3232876b586fd80f4d77681abf923ec (diff)
st/nine: Always return OK on SetSoftwareVertexProcessing
This would need more tests to know exactly if INVALIDCALL can be returned in some situations. It seems some games expect D3D_OK, even when noop and illegal. Fixes: https://github.com/iXit/Mesa-3D/issues/302 https://github.com/iXit/Mesa-3D/issues/338 Signed-off-by: Axel Davy <[email protected]>
Diffstat (limited to 'src/gallium/state_trackers')
-rw-r--r--src/gallium/state_trackers/nine/device9.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gallium/state_trackers/nine/device9.c b/src/gallium/state_trackers/nine/device9.c
index f165f24ee46..e7317238e6c 100644
--- a/src/gallium/state_trackers/nine/device9.c
+++ b/src/gallium/state_trackers/nine/device9.c
@@ -2716,7 +2716,7 @@ NineDevice9_SetSoftwareVertexProcessing( struct NineDevice9 *This,
nine_context_set_swvp(This, bSoftware);
return D3D_OK;
} else
- return D3DERR_INVALIDCALL; /* msdn. TODO: check in practice */
+ return D3D_OK; /* msdn seems to indicate INVALIDCALL, but at least Halo expects OK */
}
BOOL NINE_WINAPI