ppsspp
ppsspp copied to clipboard
hrydgard
[Vulkan] Project Diva 2nd - Missing graphics (depth issue)
This occurs even on desktop. It appears to be caused by draw 686/1893 (a src >= dst test.) It draws correctly if that is skipped.
Depth clamp is enabled. Verts (triangle strip):
- -2184.754639, -25494.019531, 565026.812500
- 2448.613770, -20518.970703, 455450.062500
- 2111.076416, -81579.367188, -436066.343750
- -2356.259521, -100212.601563, -535462.250000
It's using a standard viewport/offset, so each of these points is outside the frustrum in some way (by virtue of Y alone.) However, since the depth is also outside, clipping is happening.
That being said, all vertices have negative Y, so both triangles should be cleanly outside the viewport no matter what.
-[Unknown]
As much as i know Vulkan in PowerVR too is not so optimized for some games.I was facing many issues on my old phone and this new one running PowerVR Rogue Ge8320
It this GE dump same happens in latest builds. The graphics works ok for rest of PVs.
But with this part in magnet PV the graphical glitch triggers here.
This should be fixed with the latest depth clamp changes, I think. Sorry, forgot to link it.
That said, it's only on devices that support user clip/cull, which I think excludes Mali.
-[Unknown]
~This is possibly another Adreno 5xx driver bug.~ Vulkan:
OGL:
Frame dump: recording (1).zip
Cannot reproduce this issue using the dump.
Adreno 506 GPU Vulkan
ppsspp https://github.com/hrydgard/ppsspp/commit/3ff400e40e122dcba771d32b8a064a3b42e7e371
Cool, maybe we can close then. Or quite likely, this might not be fully fixed on Mali yet...
This was a negative Z issue, like the others it's fixed on devices with clip/cull distance support.
We could probably close most of them and leave a single issue open noting Mali. But retesting them with Adreno devices is not going to help. I already validated it in 2021 when I posted that this was fixed by the depth clamp changes.
-[Unknown]
I cannot also reproduce this in my redmi 4x v1.18.1-1955-ga85f748677 Release CPU: Qualcomm Technologies, Inc MSM89 ABI: arm64 Page Size: 4096 bytes RW/RX exclusive: No Board: QC_Reference_Phone 3D API: Vulkan API version: 1.0.0 Device API version: 1.0.31 Vendor: Qualcomm VendorString: Adreno (TM) 505 Driver: 55.277.3829 (0dd15ef5) Depth buffer format: D24_S8 Refresh rate: 60.00 Hz
Your Redmi has an Adreno though, while above it seems the problems are mainly on Mali.
However, since we haven't gotten any more reports, I'll close this.
Looks good on my phone with MALI GPU v1.18.1-1955-ga85f748677 Release CPU: MT6769Z ABI: arm64 OS: Xiaomi:M2003J15SC Page Size: 4096 bytes RW/RX exclusive: No Board: merlin 3D API: Vulkan API version: 1.1.0 Device API version: 1.1.131 Vendor: ARM VendorString: Mali-G52 Driver: 26.0.0 (06800000) Depth buffer format: D24_S8 Refresh rate: 60.00 Hz
Looks good on my phone with MALI GPU v1.18.1-1955-ga85f748677 Release CPU: MT6769Z ABI: arm64 OS: Xiaomi:M2003J15SC Page Size: 4096 bytes RW/RX exclusive: No Board: merlin 3D API: Vulkan API version: 1.1.0 Device API version: 1.1.131 Vendor: ARM VendorString: Mali-G52 Driver: 26.0.0 (06800000) Depth buffer format: D24_S8 Refresh rate: 60.00 Hz
Nope. Still happens for my Samsung Galaxy A35 using Vulkan.
Looks good on my phone with MALI GPU v1.18.1-1955-ga85f748677 Release CPU: MT6769Z ABI: arm64 OS: Xiaomi:M2003J15SC Page Size: 4096 bytes RW/RX exclusive: No Board: merlin 3D API: Vulkan API version: 1.1.0 Device API version: 1.1.131 Vendor: ARM VendorString: Mali-G52 Driver: 26.0.0 (06800000) Depth buffer format: D24_S8 Refresh rate: 60.00 Hz
Nope. Still happens for my Samsung Galaxy A35 using Vulkan.
Does geometry shader or disable hw transform doesn't help this issues?
Here:
For some reason, Enabling geometry shader culling fixes this.
This similar to issue https://github.com/hrydgard/ppsspp/issues/20104
My Huawei Nova 3i which doesn't support geometry shader culling can't reproduce this issues.
My Huawei Nova 3i which doesn't support geometry shader culling can't reproduce this issues.
Have you tried default settings to reproduce this issue and disabling geometry shader culling makes the difference?
My Huawei Nova 3i which doesn't support geometry shader culling can't reproduce this issues.
Have you tried default settings to reproduce this issue and disabling geometry shader culling makes the difference?
Nova 3i does not have a geometry shader culling option and yes I was default settings when I test your ge frame dump.