libretro / libretro/RetroArch

LRPS2 Vulkan Rendering Regression on Latest RetroArch Nightly

Open
#19,085 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Image

System Specs:

  • CPU: AMD Ryzen 7 9800X3D
  • GPU: AMD Radeon RX 9070 XT
  • OS: Windows
  • RetroArch Nightly Build
  • LRPS2 Core

Issue:
After updating to the latest RetroArch nightly build, Vulkan appears to have rendering issues across multiple PS2 games. The issue presents as previous frames remaining visible on subsequent frames, causing ghosting/trailing artifacts and graphical corruption.

Troubleshooting Performed:

  • Reinstalled RetroArch
  • Reinstalled the LRPS2 core
  • Reset core settings
  • Tested multiple PS2 games
  • Tested different internal resolutions
  • Tested different dithering modes
  • Tested blending accuracy settings
  • Tested Vulkan and D3D11 renderers

Results:

  • Vulkan consistently exhibits frame persistence/ghosting artifacts across multiple games.
  • Switching the renderer to D3D11 immediately resolves the issue.
  • Games render correctly under D3D11 with no visible ghosting or frame retention.
  • The issue appears to be specific to Vulkan.

Example Game:

  • Crash Tag Team Racing
  • Mortal Kombat: Shaolin Monks
  • (and other tested PS2 titles)

Additional Notes:
The issue was not noticed prior to updating to the latest nightly build. Because D3D11 resolves the problem across multiple games, this appears to be a Vulkan-specific regression rather than a game-specific issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the LRPS2 core using Vulkan on Windows, then compare the same games with D3D11. Trace the Vulkan rendering path implicated by the latest RetroArch nightly and identify the regression; it is done when tested PS2 games no longer retain previous frames or show ghosting under Vulkan.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.