-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ULES-00516 MOH Heroes Vulkan bad vshader cached #16612
Comments
Can't reproduce this on my phone might be a windows issue only. |
Thanks for reporting this one! No, we just ignore the error on Android (debug asserts aren't on there by default) but it's still a bug, even though there might not be any big graphical consequence. Will look into it. |
We hit the case where the game uses GE_PRIM_KEEP_PREVIOUS where prevPrim_ == GE_PRIM_INVALID. Think this might later somehow confuse CanUseHardwareTransform(prim) leading us to generate a different useHwTransform flag, for what should be the same inputs to the shader cache ID generators. Haven't quite understood this yet. Hm, yeah, we end up calling CanUseHardwareTransform(GE_PRIM_INVALID) which can't be good.. I think maybe we shouldn't set prevPrim_ to GE_PRIM_INVALID in Flush, btw... not doing that is enough to fix this. |
That sounds right to me. It seems like -[Unknown] |
For continuing previous verts, see hrydgard#16612. We still don't handle these quite accurately (outside software rendering), but this should be better.
Okay, I saw it so opened up #16614. We were never setting -[Unknown] |
#16614 fixes this, closing. |
Game or games this happens in
ULES-00561 - Medal of Honor Heroes
What area of the game / PPSSPP
After title screen emulator prompt Vulkan vshader cached error.
What should happen
No vshader error.
Logs
DebugLog.zip
Platform
Windows
Mobile phone model or graphics card
NVIDIA Geforce RTX 3070
PPSSPP version affected
v1.14-37-g4942ab7d8
Last working version
v1.12.3-1469-gcc197415b
Graphics backend (3D API)
Vulkan
Checklist
The text was updated successfully, but these errors were encountered: