thirdparty/ppsspp
2
0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

GPU: Avoid stencil force pass when writing depth.

Browse source 
There's a risk if the stencil test failed, it might cause a depth write
unless it's also masked.  Hunter x Hunter doesn't in this case.
This commit is contained in:
Unknown W. Brackets 2022-08-10 23:11:16 -07:00
parent f80dd088b8
commit a321aba68c
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
GPU/Common/GPUStateUtils.cpp
View file

@ -1511,10 +1511,12 @@ void ConvertStencilFuncState(GenericStencilFuncState &state) {
state.testRef = gstate.getStencilTestRef();
state.testMask = gstate.getStencilTestMask();
if ((state.sFail == state.zFail || !gstate.isDepthTestEnabled()) && state.sFail == state.zPass) {
bool depthTest = gstate.isDepthTestEnabled();
if ((state.sFail == state.zFail || !depthTest) && state.sFail == state.zPass) {
// Common case: we're writing only to stencil (usually REPLACE/REPLACE/REPLACE.)
// We want to write stencil to alpha in this case, so switch to ALWAYS if already masked.
if ((gstate.getColorMask() & 0x00FFFFFF) == 0x00FFFFFF) {
bool depthWrite = gstate.isDepthWriteEnabled();
if ((gstate.getColorMask() & 0x00FFFFFF) == 0x00FFFFFF && (!depthTest || !depthWrite)) {
state.testFunc = GE_COMP_ALWAYS;
}
}