ValveSoftware / ValveSoftware/Proton

Amazing Princess Sarah (315850)

Open
#5,617 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

.NET .NET-XNA Game compatibility - Unofficial
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Compatibility Report

  • Name of the game with compatibility issues:Amazing Princess Sarah
  • Steam AppID of the game:315850

System Information

  • GPU: AMD Vega 56/64
  • Driver/LLVM version: Mesa 21.3.5
  • Kernel version: 5.16.11
  • Proton version:7.0

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

Symptoms

Game crashes after initial logo, before reaching title.

There is a crash information pointing at FAudio:XNA_PlaySong (Managed stacktrace).
After that Proton log shows stacktrace pointing at FAudio_close() as the location of crash.

Reproduction

  1. start game
  2. observe game exit

steam-315850.log

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 reviewing the attached steam-315850.log and the reported FAudio:XNA_PlaySong and FAudio_close() crash locations. Reproduce the launch sequence with Proton 7.0 and compare the crash information with the log. Done means Amazing Princess Sarah starts past the initial logo and reaches the title screen without exiting.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.