Hayate no Gotoku!! Nightmare Paradise - characters show through background

[IrfanH495]

Game or games this happens in

ULJM05416 - ハヤテのごとく！！ナイトメアパラダイス

What area of the game

At the beginning when all the characters scatter
OpenGL & Vulkan

What happens

this is taken from software rendering

What should happen

.

GE frame capture

ULJM05416 (1).zip

Platform

Android

Mobile phone model or graphics card

Samsung M20

PPSSPP version affected

ppsspp-v1.15.4-923-g50ea506b6-android

Last working version

.

Graphics backend (3D API)

Vulkan

Checklist

• Test in the latest git build in case it's already fixed.
• Search for other reports of the same issue.
• Try resetting settings or older versions and include if the issue is related.
• Try changing graphics settings to determine if one causes the glitch (especially speed hacks or enhancements/replacements.)
• Include logs or screenshots of issue.

[hrydgard]

Ha, took me a while to see what's wrong - it's the background characters somehow showing through the background.

Probably another fun depth-buffer-manipulation case...

[IrfanH495]

@hrydgard sorry, is this normal?
Debug Stats blocking menus
https://youtu.be/EBvgjGN42jc

[hrydgard]

I wanted to show a different type of debug stat on top of menus (frame timing) so I enabled that. You're right that those debug stats don't make much sense to overlay on menus, and I'm gonna fix that.

[hrydgard]

OK, finally got around to looking at this.

From the dump, it uses 32-bit color, framebuffers at VRAM offsets 00000 and 88000, depth at 110000, this is standard. After filling the color buffer with a background image, it uses a block transfer to initialize a precomputed depth buffer:

Fortunately it does the transfer to a "auto-swizzling" VRAM address (04600000, note that 04710000 = 04600000 + 110000), so probably the source of the copy is a plain depth image and not something pre-swizzled.

We currently do not handle block transfer copies from RAM to depth buffers, but adding that will not be particularly difficult. We can be pretty restrictive, for example requiring the swizzled VRAM address.