protonscr

Metaphor: ReFantazio

protonopen appid 2679460Game compatibility - Unofficial
ValveSoftware/Proton#8616 · opened 2025-04-18 by Oncemarco · updated 2026-04-10 · 5 comments · github · game page · search this game
OOncemarco 2025-04-18 github

Game: Metaphor: ReFantazio
Platform: Steam Deck
Issue: The game used to run until recently, but now fails to launch with the error: "Something went wrong, for possible solutions visit..." (translated from Italian Steam message).

Tested on:

  • Proton 7.0-6
  • Proton Experimental
  • Proton GE

Also tried:

  • Reinstalling the game
  • Deleting compatdata and shadercache
  • Installing on both SD card and internal storage
  • Launching manually via terminal
  • Forcing Vulkan resolution and custom launch parameters

Behavior: Vulkan shader precompilation no longer starts. Game fails silently or with standard error message. Other games on the Deck work fine.

Likely cause: DRM/Anti-tamper system rejecting Proton, or a recent game update breaking compatibility.

Kkisak-valve maintainer 2025-04-18 github

Hello @Oncemarco, please grab the Compatibility Report template, copy it here, and fill out the requested details.

OOncemarco 2025-04-18 github

Compatibility Report

  • Name of the game with compatibility issues: methaphor re Fantazio
  • Steam AppID of the game: 2679460

System Information

  • Steam deck
  • Proton version: I’ve tried almost all of them

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.
    Il giorno ven 18 apr 2025 alle 17:12 kisak-valve @.***>
    ha scritto:

Hello @Oncemarco https://github.com/Oncemarco, please grab the Compatibility
Report template
https://github.com/ValveSoftware/Proton/issues/new?template=compatibility-report.md,
copy it here, and fill out the requested details.


Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8616#issuecomment-2815620716,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BRUHVU7VDOHXVU7H4R7FZV322EI55AVCNFSM6AAAAAB3NF7OLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJVGYZDANZRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>
kisak-valve left a comment (ValveSoftware/Proton#8616)
https://github.com/ValveSoftware/Proton/issues/8616#issuecomment-2815620716

Hello @Oncemarco https://github.com/Oncemarco, please grab the Compatibility
Report template
https://github.com/ValveSoftware/Proton/issues/new?template=compatibility-report.md,
copy it here, and fill out the requested details.


Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8616#issuecomment-2815620716,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BRUHVU7VDOHXVU7H4R7FZV322EI55AVCNFSM6AAAAAB3NF7OLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJVGYZDANZRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ggalacticaledge 2025-06-04 github

steam-3130330.log

This happens to me in several games, but this game has been freezing for me during the first area whenever I load in. It could be an Nvidia driver bug, but I want to see if anyone here could point me in the right direction.

EEoin-ONeill-Yokai 2026-03-09 github

Regarding boot issues, I have found that this can be resolved by forcing a lower resolution (720p) via steam game setting and starting the game. Once you're in and you see the main menu, rebooting with a higher (target) resolution should consistently work as long as you force that resolution (800p on deck, 1440p on my htpc). I think what happens here is that the game doesn't seem to think it has a adequate amount of space to spawn a 800p screen because gamescope opens a smaller resolution window first on boot and then the game mistakenly saves that to the configuration. Forcing a resolution (you can see this in the game settings) will effectively remove this issue. Alternatively, you can probably fix this by going into desktop mode and deleting the game configuration, but I haven't tried that.

Obviously Valve might need to make some adjustments to this particular game's default gamescope parameters, assuming that's within the scope of their own compatibility control. Targeting a default internal resolution that matches the device/display resolution would make a lot of sense here.

There are other problems with this game, though. (Tested on the Deck and a custom machine with an AMD GPU, using Proton Experimental and reproducible on Proton Stable)

  • Frame rate issues on first "in-game" scene is very common, where the game runs at about 15fps. I think this is actually tied to the refresh rate of the UI elements somehow, and likely a driver or vulkan bug. This doesn't always happen when first starting the game, but does happen more often than not.
    • You can fix this easily by simply going to the in-game display settings and changing resolutions, exiting the menu to confirm the framerate improvements, and then change the display resolution back again. Notably, resolution scaling changes does not affect performance, so I think it's tied to the perceived "refresh rate" of the display. Additionally, forcing a refresh rate via the right hand panel does not force the game to update, so it's likely getting the wrong refresh rate information for whatever reason.
  • Heavy Rain weather in certain cities causes major performance drops. This might be tied to the rather CPU constrained hardware I tried it on, but it should be relevant for potential deck optimizations. What's difficult about this is reproducing it, as I noticed it only on rainy days in certain cities (particular Port Brilehaven on rainy days in the Inn district) and it's a bit hard to plan around this based on the games mechanics to capture the log (if I see rain coming up in the in game weather forecast, I'll make a note to try to make a save for reproduction and log capture. IIRC forecast checking does take up in game time, so YMMV.) If I were to take a guess, the rain also has it's own refresh rate issues, which might make this tied effectively to the first issue as well.

Overall, the game is "playable", but I think it should be a game Valve targets for the steam machine as I don't think it's good enough. This is going to be a game some audiences want to A/B test against the Playstation 5, and I imagine the refresh rate issues here will eventually solve other weird issues that occur in other games, so it might be worth investigating that as a DXVK, wine or driver improvement point.

Ssimifor 2026-04-10 github

@Eoin-ONeill-Yokai I'm not seeing the boot issue. Can you be more explicit with how it happens? Like, starting from a fresh prefix what series of step do you need for the problem to manifest.

  • I tried on deck with steamos stable and preview with proton 10 and no extra launch parameters and the game launched fine.
  • I tried on my amd desktop, launching the game with gamescope with no extra parameters, and proton experimental, and that also worked fine.

Would be worth noting what your desktop setup like, what os, are you using steam in desktop mode, game settings and anything else you might consider worth sharing.

About the framerate issues, can you be more clear about your wording? I didn't initially see anything odd with the framerate, but I'd like to know what you mean by the first scene. Do you mean specifically when you fall down the desert? Or do you mean any first scene when you continue with your game?

Proton versions