libretro / libretro/ps2

xbox series x/s crash on d3d12, black screen with audio on d3d11

Open
#40 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
85
Forks
26
Avg merge
6h 43m
Merged PRs (30d)
6

Description

I had to use retroarch 1.17 stable to get a log since logging is broken with mesa versions on xbox. Tested with all core versions that the gitlab artifacts provide, from https://github.com/libretro/ps2/commit/243b5629943cc4557c0d74f78e4ab9c3a62c667c to https://github.com/libretro/ps2/commit/007daaa8d470de963c0ae36cc7bf8a4793220301 d3d11 produces a black screen with audio, d3d12 crashes the app. Retroarch versions i tested are (https://github.com/libretro/RetroArch/commit/0a7b409a0465ad2fed9e374e6c06d22715f98395) and 1.17 stable, i have attached a log for D3D11 and D3D12, retroarch.cfg was default for all testing

D3D11.log
D3D12.log

the d3d12 log had this which may be of interest:
[libretro INFO] Failed to get cached PSO data: 887A0005
[libretro INFO] Creating cached PSO failed: 887A0005
[libretro INFO] Failed to compile utility pipelines

Old versions of pcsx2 d3d11 core from a few years ago where fine on xbox, new versions of xbsx2 emulator also work fine with d3d11/12 on xbox which uses the latest pcsx2 code

Contributor guide

No contributing guide indexed for this repository

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 comparing the attached D3D11.log and D3D12.log for the tested Xbox Series X/S runs, then review the referenced libretro/ps2 commits and RetroArch versions. Investigate the reported cached PSO and utility-pipeline failures; done means the PS2 core renders through D3D11 and no longer crashes through D3D12 on the Xbox platform.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.