Working on Linux

[NoeLennon]

Figured somebody may find this useful... I was able to run V Rising on Manjaro Arch today using Bottles. Ill update this as more information becomes available.

Install Bottles https://github.com/bottlesdevs/Bottles

Go into preferences and install the latest Runners: Wine-GE I installed the latest for each, to have them available.

Go into preferences and install the latest DLL Components: DXVK, VKD3d, DXVK-NVAPI (for nvidia)

Create Windows 10 bottle for Gaming

Go to the windows 10 bottle preferences and turn on the following: DXVK, VKD3d, DLSS (for nvidia), FSR, Discrete GPU

Go to installers and install Steam

Launch Steam, login, download V Rising

Good to go!

Notes: The main into (which you can skip) and main menu has orange scanlines, but everything else seems to work. The game itself runs awesome except for some shuddering when new shaders are used for the first time but clear up quickly. I also had a hung process trying to exit it once, but Bottles allows you to kill all processes. One last item of note is Steam seems to disconnect frequently, but doesn't appear to affect game play... but I only used offline mode.

EDIT: Selecting the 'caffe-7.8-1' Runner (Prefs>Components Version) seems to eliminate the intro and menu issues. Significant improvements in performance and network stability too. Still testing though.

I got this from /u/WunSick on reddit! Works great doing exactly what they said! Plays as good as in windows.... Havnt spent too much time yet though.. Oya, also confirmed using Fedora 36 and a GTX1660 super.

[Bunuffin]

wow... it's just a question of time for Proton to work, thanks for sharing!

[The Ashen One]

Can also confirm that this works perfectly. You can massively reduce the shader compilation stuttering by using dxvk-async with DXVK_ASNYC set to 1.

[Tuxicoman [FR]]

thanks for the info

[Bunuffin]

Originally posted by Hecate:

Can also confirm that this works perfectly. You can massively reduce the shader compilation stuttering by using dxvk-async with DXVK_ASNYC set to 1.

yup yup i saw it on reddit, will be trying it soon

[WelshPixie]

Tried this and I can run the game and get in, but it's not accepting input for 'press space to wake up' XD

So close!

[rockyjvec]

I managed to get it to work in regular Steam. I had to install Battlerite Royale (free) and copy the stun_steamnetworking.dll file from the Battlerite Royale game folder under BattleriteRoyale_Data/Plugins/ to the VRising game folder under VRising_Server/VRisingServer_Data/Plugins/x86_64/ AND VRising_Data/Plugins/x86_64/ the game then launches perfectly and the solo mode works perfectly for me. I haven't tried multiplayer. This is using standard Proton 7.0-2 with no launch options.

EDIT: Be sure to use the ROYALE version of Battlerite, the standard version will not work.

[Misha]

im running the game thru lutris steam windows runner but it doesnt remember servers im active on and the game freezes my system when trying to exit it. anyone with similar problem? are joined servers saved locally?

[NoeLennon]

Originally posted by rockyjvec:

I managed to get it to work in regular Steam. I had to install Battlerite Royale (free) and copy the stun_steamnetworking.dll file from the Battlerite Royale game folder under BattleriteRoyale_Data/Plugins/ to the VRising game folder under VRising_Server/VRisingServer_Data/Plugins/x86_64/ AND VRising_Data/Plugins/x86_64/ the game then launches perfectly and the solo mode works perfectly for me. I haven't tried multiplayer. This is using standard Proton 7.0-2 with no launch options.

I just tried this, it definitely gets father for me then ever before. get the in game cursor and a white then black screen. and steam in game loads fine etc... so close. anything else special you might have done?

[rockyjvec]

Originally posted by NoeLennon:

Originally posted by rockyjvec:

I managed to get it to work in regular Steam. I had to install Battlerite Royale (free) and copy the stun_steamnetworking.dll file from the Battlerite Royale game folder under BattleriteRoyale_Data/Plugins/ to the VRising game folder under VRising_Server/VRisingServer_Data/Plugins/x86_64/ AND VRising_Data/Plugins/x86_64/ the game then launches perfectly and the solo mode works perfectly for me. I haven't tried multiplayer. This is using standard Proton 7.0-2 with no launch options.

I just tried this, it definitely gets father for me then ever before. get the in game cursor and a white then black screen. and steam in game loads fine etc... so close. anything else special you might have done?

Just to verify, I just uninstalled the game, deleted the game folder, deleted the compatdata folder for the game, reinstalled, then did the same fix above. It works perfectly for me. Did you copy the dll file to both locations?

[rockyjvec]

Also, the black screen is the start of the intro cinematic. You could try skipping it by editing the config file in the compatdata folder for the game at:
compatdata/1604030/pfx/drive_c/users/steamuser/AppData/LocalLow/Stunlock Studios/VRising/Settings/ClientSettings.json

Here is what mine contains with the intro cinematic disabled:

{
  "General": {},
  "Sound": {},
  "Interface": {
    "Language": "english",
    "SkipIntroCinematic": true
  },
  "GameClient": {
    "EnableGameAnalytics": false,
    "HasSeenCinematic": true,
    "HasCompletedFirstStartup": true
  },
  "GraphicSettings": {
    "Resolution": {
      "x": 1920,
      "y": 1080
    },
    "DynamicResolutionQuality": 0.77
  }
}

Edit:

It seems like that setting doesn't do anything. When I launched the game it still displayed the intro. You could also try holding down the left mouse button which skips it manually.

[NoeLennon]

Originally posted by rockyjvec:

Originally posted by NoeLennon:

I just tried this, it definitely gets father for me then ever before. get the in game cursor and a white then black screen. and steam in game loads fine etc... so close. anything else special you might have done?

Just to verify, I just uninstalled the game, deleted the game folder, deleted the compatdata folder for the game, reinstalled, then did the same fix above. It works perfectly for me. Did you copy the dll file to both locations?

I did copy to both... I never deleted and re-installed first. I will try that.

[Bunnyhop]

Can confirm both solutions work (steam via wine to begin with and native steam with copied Battlerite Royal steamwork dlls (in my case, with latest Proton Experimental (bleeding edge beta)). Performance wise, they seem the same - though you'll have to live with stuttering until the cache is made. It's enjoyably playable, after that.

I've only tested online play on official servers. Stability wise I've not played long enough with the native solution to say it's stable. The steam-through-wine way of doing it was very stable. I had one client freeze/hang that did not end until killed after probably 4-5 hours and more of having the client open ingame.

I have not tried dxvk-asynch. It might fix both the stuttering and the hang that happened.
I have not tried any voice comm, so any potential additional issues with sound, pulse, and whatnot that might lead to instabilty hasn't been applicable.

On the .dll issue, there seems to have been a recent update to steamworks and I'm guessing it's that version change and implementation of it in V Rising that's causing the problems with proton, as others have said. The Battlerite Royale version works, but there's another Battlerite that's also listed - I don't know if they use the same working .dlls, so check to make sure it's the 'Royale' one.

If you use the steam through wine solution, I noticed there were a lot of very annoying flickering in the steam internal windows (using caffee, at least) so launching steam - after the install of vrising is done - with 'steam -no-browser +open steam://open/minigameslist' to turn off the whole internal browser thing might be a safer bet than not, stability wise.

[teh_inquirerer]

Thanks! I would have never found this if you didn't post it to the Steam forums. Everything works perfectly!


I played 8hrs straight on my friends MP private server. No glitches or hiccups.

[NoeLennon]

Originally posted by Bunnyhop:

Can confirm both solutions work (steam via wine to begin with and native steam with copied Battlerite Royal steamwork dlls (in my case, with latest Proton Experimental (bleeding edge beta)). Performance wise, they seem the same - though you'll have to live with stuttering until the cache is made. It's enjoyably playable, after that.

I've only tested online play on official servers. Stability wise I've not played long enough with the native solution to say it's stable. The steam-through-wine way of doing it was very stable. I had one client freeze/hang that did not end until killed after probably 4-5 hours and more of having the client open ingame.

I have not tried dxvk-asynch. It might fix both the stuttering and the hang that happened.
I have not tried any voice comm, so any potential additional issues with sound, pulse, and whatnot that might lead to instabilty hasn't been applicable.

On the .dll issue, there seems to have been a recent update to steamworks and I'm guessing it's that version change and implementation of it in V Rising that's causing the problems with proton, as others have said. The Battlerite Royale version works, but there's another Battlerite that's also listed - I don't know if they use the same working .dlls, so check to make sure it's the 'Royale' one.

If you use the steam through wine solution, I noticed there were a lot of very annoying flickering in the steam internal windows (using caffee, at least) so launching steam - after the install of vrising is done - with 'steam -no-browser +open steam://open/minigameslist' to turn off the whole internal browser thing might be a safer bet than not, stability wise.

Ahhhh Yes ,this was my problem. I was using Battlerite, not the Royale version. Now it works both ways. I do get orange bars in the opening cutscene, but everything else works perfectly.

[aronorth]

Originally posted by tankerer:

Thanks! I would have never found this if you didn't post it to the Steam forums. Everything works perfectly!


I played 8hrs straight on my friends MP private server. No glitches or hiccups.

By the way thanks for contributing to the protonDB page, Recent reports are really helpful to track if a game is working.