Open FilBot3 opened 2 years ago
The game has a public-beta branch with linux fixes. It solves that JavaScript error and runs natively without proton.
The game works fine for me with Proton but not on the latest Plasma 5.25 beta (several other games are broken too). It gives the exact error message shown. Game works for me with Proton on 5.24.5, but interesting to see that it's getting a native port.
Hello @sonic2kk, if a bleeding edge build of your desktop environment is causing a regression, then that should be mentioned to the DE devs.
Replying to https://github.com/ValveSoftware/Proton/issues/5846#issuecomment-1131463969
Setting my game to the public beta version did not work for me, even after a fresh install. I had to set to Proton GE 7.20, then PROTON_LOG=1 %command%, then launch with Steam Overlay. Then the game launches and I can use my PlayStation 5 Dual Sense controller.
Replying to #5846 (comment)
Setting my game to the public beta version did not work for me, even after a fresh install. I had to set to Proton GE 7.20, then PROTON_LOG=1 %command%, then launch with Steam Overlay. Then the game launches and I can use my PlayStation 5 Dual Sense controller.
Maybe the public beta didn't work for you because your steam is a flatpak installation. See flathub/com.valvesoftware.Steam#897
The advice there is to add --no-sandbox
to launcher.sh
But, launcher.sh can get overwritten by future game updates.
Same problem for me. Same error. No flat pack.
Looks like this problem still exists (or, according to some players, went away and came back) with v1.0. For reference, it's mentioned in a few places, including here: https://steamcommunity.com/app/1794680/discussions/0/3489752656784679654/
Probably, it's not relevant but still, I was managed to run Vampire Survivors using electron v15.5.7 (as far as it was written on this platform) with:
./electron ~/.steam/steam/steamapps/common/Vampire\ Survivors/resources/app
https://github.com/electron/electron/releases/tag/v15.5.7
Note that, steam achievements and overlay won't be enabled using this way
Lol. @tarvitz That's fun. So that become native app isntead of Proton. Why hadn't dev done that? :-(
And I guess you lost acheivement support by doing that?
@Mart-Bogdan I have no idea why.
By the way, steam syncs saved data properly and it's possible top "achieve" the achievements just run the game using Windows or Mac.
By the way, @tarvitz @nightblade9 post author have posted workaround:
Works seemingly with
PROTON_LOG=1 %command%
And I confirm that it works!
I am continually having issues where Vampire Survivors is supposedly running, but no window comes up. I've tried Proton 8.x, Proton Experimental, I've tried adding "PROTON_LOG=1 %command%" or removing to launch flags, and some other things I'm forgetting. I've also now tried with "new engine", same thing.
The only "somewhat reliable solution" I have is just cancel and relaunching after a few seconds, and doing that repeatedly until it EVENTUALLY comes up. Sometimes takes 2-3 attempts, sometimes it doesn't at all.
This is so confusing, as I don't have this weird inconsistency with any other games I rock on Linux. Anyone have any ideas what's up with this? And this isn't a recent thing. It's been going on a while, I'm just now actually trying to do something about it.
It works for me perfectly for a while. I'm using [steam-deck] branch of a geme.
Previously used Proton 7.06
Currently disabled proton version tweak and used default one, and it worked for me.
There seems to be some kind of bug with the current release of the game and it crashes on startup. I have so far tried Proton 8 and Experimental.
I can play the game if I switch to the public-beta channel.
Anyone else have issues with getting xbox controller working? I can press start but can't navigate menus or move characters once in.
Compatibility Report
System Information
I confirm:
PROTON_LOG
Symptoms
Game would not launch without PROTON_LOG=1 set. Would throw the following error with all listed versions of Proton.
Reproduction
Install Vampire Survivors. Use default Proton, or Proton Experimental, or GE-Proton.
Works seemingly with
PROTON_LOG=1 %command%
set and using Proton Exp and GE-Proton. Default proton would say that launcher.sh. However now upon relaunching with the configurations I did before, it is now working. So, inconsistent behavior.