protonscr

Tales of Vesperia: Definitive Edition

protonopen appid 738540Game compatibility - UnofficialRegressionXAudio2
ValveSoftware/Proton#2578 · opened 2019-04-21 by BillFleming · updated 2026-07-03 · 9 comments · github · game page · search this game
1 matching comments, n / p to jump
BBillFleming 2019-04-21 github

Whitelist Request

  • Name of the game to be whitelisted: Tales of Vesperia: Definitive Edition
  • Steam AppID of the game: 738540

System Information

I confirm:

  • [X] that pressing the Play button in the Steam client is sufficient.
  • [X] that no workarounds other than PROTON_* env variables are necessary.

Issues

  • [ ] I haven't experienced any issues.
  • [X] There are no issues left open for this game.
  • [ ] Although I consider the gaming experience equal to Windows there are remaining issues:

Notes

This game originally had some crashing issues back in proton 3.1X and the original version of the game on steam. But the game itself was patched and proton has improved so the game now (without modifications) runs better OOTB than on Windows. (less stuttering than on Windows, but game has bad coding)
One of the old crashing issues was it would always crash at a specific point, but they fixed it with the game update.
I haven't yet completely beaten the game on proton (its long) but getting close. In the final chapter part now. I believe that you can now play the game for many hours (5-10) without having any crashing issues.

Kkisak-valve maintainer 2020-01-15 github

Tales of Vesperia: Definitive Edition (738540) stability degradation

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3434.
@Dvakote posted on 2020-01-15T17:39:13:

Compatibility Report

  • Name of the game with compatibility issues: Tales of Vesperia: Definitive Edition
  • Steam AppID of the game: 738540

System Information

I confirm:

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

I found whitelist request https://github.com/ValveSoftware/Proton/issues/2578 and would totally support it if stability problems on newest proton would be fixed.

Proton log: steam-738540.log

Symptoms

Game have become very unstable after release of proton 4.11-11. Proton 4.11-12 didn't fixed the problem either. All worked fine on 4.11-10 and there weren't any problems before update.

I tried to launch game on proton 4.2-9 and it worked flawlessly like on 4.11-10.

Reproduction

There are several ways to cause game crash:

  1. Launch the game
  2. Try to move to different location
  3. Engage in combat
Ddoitsujin 2020-01-15 github

Crashes should (hopefully) be fixed as of https://github.com/doitsujin/dxvk/commit/18450f4643c6cb5534f6cdfd44492138ed8294f3.

SSeongGino 2022-07-20 github

Small update: Though the game itself doesn't have any major issues, I've found two that are related to windowing:

  • When the windowed mode is set to Fullscreen, pulling the focus away or doing anything else to cause it to minimize will start leaking memory like a broken bucket - eventually OOM'ing even on a 16GB system if left alone in a minimized state for maybe ten-to-twenty seconds. Does not happen outside of Exclusive Fullscreen specifically.
  • When set to Borderless Windowed, the cursor (which is integrated with the game's feather pen pointer) starts jittering with mouse movement. It doesn't affect usability per-se, but is very visually distracting if playing with a kb+m. Does not happen outside of Borderless specifically.

I realize that dismissing fullscreen apps is still temperamental in Linux, but this is the only game, Wine or otherwise, that I've had an inactive ram leak happen from doing this. I've checked with Berseria (same series/engine) and Zestiria (same port developer), neither reproducing this effect.

Observed as of current Proton Experimental (2022/07/19).

SSeongGino 2022-08-24 github

Update: FWIW, latest Proton Experimental (~2022/08/22) seems to break compatibility with the SpecialK patch that improves game's bad frame pacing/stuttering. Using the last stable release to resolve this.

AAJuujarvi 2022-08-25 github

Update: FWIW, latest Proton Experimental (~2022/08/22) seems to break compatibility with the SpecialK patch that improves game's bad frame pacing/stuttering. Using the last stable release to resolve this.

I'm not familiar with running SpecialK in Proton. Do you have a guide or know the steps to get it all set up? I'd like to try and take a look at this for testing. @SeongGino

CChaosBlades 2026-06-28 github

The game locks up on the initial loading screen on anything Proton 10 or newer or anything based on Proton 10 or newer.

The latest version of Proton that this game works with is Proton 9.

By default, Steamplay tries to launch the game with Proton10. At the least, the default should be changed to Proton9.

Kkisak-valve maintainer 2026-06-28 github

Hello @ChaosBlades, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

CChaosBlades 2026-07-03 github

Was too hot to have a my main PC on and I wasn't going to make all these gist on the Steam Deck.
Github kept saying all my uploads failed. Can't be bothered investigating the issue. So a gist for everything is needed.
Only the proton 9 log is a successful launch of the game. All other logs are basically identical.
proton9.0-4-steam-738540
proton-experimental-steam-738540
proton11.0-beta-steam-738540
proton10.0-4-steam-738540
I have the same issue on my Desktop PC, HTPC, and Steam Deck. All running Bazzite. All AMD builds. Here is the log from my Desktop PC, which is what all these logs are from.
Steam Runtime Diag Desktop PC

Ssimifor 2026-07-03 github

@ChaosBlades can you install a more recent mesa? something based git rather than stable releases? I can only reproduce the issue with mesa stable on my end.

Proton versions

Launch options

Upstream links