Can confirm that with recent GE builds the game similarly to the OP starts and then fails with "Steamworks initialization failed".

I can also confirm this behaviour with all recent proton and GE builds. Installs fine but crashes to desktop immediately on launch.

OS: Pop!_OS 22.04 LTS
KERNEL: 5.17.8-xanmod1-x64v2
CPU: AMD Ryzen 7 3800X 8-Core
GPU: NVIDIA GeForce RTX 2080 Ti
GPU DRIVER: NVIDIA 510.68.02
RAM: 32 GB

Same issue here.

OS: Pop!_OS 22.04
LTSKERNEL: 5.17.5-76051705-generic
CPU: Intel Core i5-10300H @ 2.50GHz
GPU: NVIDIA GeForce GTX 1650
GPU DRIVER: NVIDIA 510.68.02
RAM: 16 GB

Using Proton-7.0rc2-GE-1 starts and then fails with "Steamworks initialization failed".

After quick post on Reddit, few more people confirming same issue (crashing silently before or in loading screen). I am having same issue as well.

Fedora 36
AMD Ryzen 5
AMD 6800 XT
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.0.0-git
RAM 32 GB

Confirmed, same issue

Confirmed, same issues.

OS: Arch
Kernel: 5.17.7-arch1-2
CPU: AMD Ryzen 5 3600XT
GPU: AMD 5700 XT
RAM: 32 GB

Have at least one report of the "Steamworks initialization failed" thing happening on Windows too.

https://steamcommunity.com/app/1604030/discussions/0/5154944131336583253/

Same crash on 7.0-2, Experimental, and GE 7-17. On Proton 6.3-8, I get the SteamWorks initialization problem, but I see others on the Discord having the SteamWorks problem on Windows as well.

CPU: AMD Ryzen 9 5950X
RAM: 128 GB
Ubuntu 22.04 LTS (64 bit)
Kernel Version: 5.15.0-27-generic
X Server Release: 12101003
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20220315.0
Video Card: NVIDIA GeForce GTX 1080
Driver Version: 4.6.0 NVIDIA 510.60.02

FWIW, it was also doing this on the closed beta, but I was only in the last phase. I see Discord posts that say it worked in earlier stages of the closed beta, but don't have personal experience with it. I don't know if it was something the game devs updated, or a minor update to Proton that happened to break it (e.g. maybe 7.0-1 to 7.0-2?)

Proton Experimental now seems to be able to get past the "Steamworks initialization failed" thing, but now once you start a server, it gets stuck on a screen that says "Connecting" and then crashes after a while. Apologies I am not able to post a log right now.

Still not starting for me with Proton Experimental [bleeding-edge]

Can't luanch the game at all so far I've got a blue screen and then crashes again

Proton 7.0-1
Distro:Pop!_OS 22.04 LTS
Kernel:5.17.5-76051705-generic
RAM:16 GB
GPU Driver:NVIDIA 510.68.02
GPU:NVIDIA GeForce GTX 1070
CPU:Intel Core i5-10600K @ 4.10GHz

This is a log of the game for when the game actually gets to the screen that says Steamworks initialization failed.

steam-1604030.zip

Can confirm it launches, crashes when joining a server then stop launching

Proton 7.0-1, GE-7, Experimental
Distro: Gentoo
Mesa-git
Kernel: 5.17.7-xanmod1-pineapple
RAM: 28 GB
GPU Driver: xf86-video-amdgpu
GPU: RX 5700
CPU: R7 1800X, 3.6 Ghz

Managed to get into the menu one time but it crashed trying to get into the game:
https://imgur.com/a/57ekCBx

Proton experimental [Bleeding edge]
Distro: Arch Linux
Kernel: 5.17.7-arch1-1
RAM: 16 GB
GPU Driver: NVIDIA 515.43.04
GPU: NVIDIA GeForce RTX 2070 SUPER
CPU: AMD Ryzen 5 3600 6-Core

This log is Proton Experimental bleeding-edge, opens on white screen and then crash. RX 6700 XT using radv.

VRising.zip

It seems someone got it working by using Windows version of Steam and Bottles
https://www.reddit.com/r/linux_gaming/comments/uuary2/v_rising_arch_working_minor_gfx_issues/?utm_source=share&utm_medium=web2x&context=3

Confirmed. Running Steam through Wine is super buggy and not a fun experience, but I was able to start the game and play, so it's definitely a Proton issue.

Tried using Bottles+Windows Steam and the latest caffe runner. Seems to work more or less, but on the screen that says "Press space to wake up" it seems to not be taking and input. Particle effects are still going so it's not a crash.

Worked for me using bottles. Also tested on Steam Deck. Had no problems pressing space to wake up either with keyboard and mouse plugged in.

Worked for me using bottles. Also tested on Steam Deck. Had no problems pressing space to wake up either with keyboard and mouse plugged in.

Which runner did you use?

Worked for me using bottles. Also tested on Steam Deck. Had no problems pressing space to wake up either with keyboard and mouse plugged in.

Which runner did you use?

I just followed the guide posted above by LordJakki including the edit at the bottom of the post

Worked for me using bottles. Also tested on Steam Deck. Had no problems pressing space to wake up either with keyboard and mouse plugged in.

Which runner did you use?

I just followed the guide posted above by LordJakki including the edit at the bottom of the post

Weird, same - I'm the one that can't press space to wake up (screwylightbulb was posting on my behalf)

For me it just gets stuck on loading screen... if I move mouse i can hear sound effects of buttons and by clicking I can open Terms of Service and Privacy policy but screen just stays on loading image.

I tried the windows version of steam yesterday, installed it via Lutris. The recommended settings for my game were high, but no matter the settings I used, the game ran like shit. I spent 4-5 hours yesterday working on it, but deemed it wasn't worth my time because the poor performance.

Just tried with bottles. Steam won't move past steam guard. Followed everything to a T. As a Unity dev myself, I dont understand why they just wont port it to Linux.

yeah steam guard doesn't pop up for me too

Just tried with bottles. Steam won't move past steam guard. Followed everything to a T. As a Unity dev myself, I dont understand why they just wont port it to Linux.

I disabled Steam Guard to make it work. You can also try enabling the Virtual Desktop feature in Bottles, it seems to render the steam guard screen correctly. You'll want to turn it off again when actually playing the game.

It's not that I have an issue getting steam guard to come up. Once I enter in my code, steam crashes. I tried running it as a virtual desktop, I tried disabling steam guard, the result is the same.

It does narrow down the problem to Steamworks via Proton specifically though.

I don't think that this thread needs more info today.
No one can use V-Rising on Linux, which means that they can reproduce this issue very easily, and work until they get the game playable.

I mean they showed an example of someone getting it working in bottles.

https://steamcommunity.com/app/1604030/discussions/0/3272440173689684567/?tscn=1653172869#c3272440173692073685

Confirmed that copying stun_steamnetworking.dll from Battlerite Royale into the two specified V Rising folders works - game now launches and plays with Proton 7.0-2

https://steamcommunity.com/app/1604030/discussions/0/3272440173689684567/?tscn=1653172869#c3272440173692073685

Confirmed that copying stun_steamnetworking.dll from Battlerite Royale into the two specified V Rising folders works - game now launches and plays with Proton 7.0-2
Could you share the file please?

I don't think this is a good place to share binaries from strangers. You need to download Battlerite Royale from Steam to get that file, and it's free to play.

I have copied the DLL files, but the game is still crashing while attempting to start a solo session.

Copy DLL method works here. Private PvE session works also.

Steps:

1. Download free to play Battlerite Royale

2. Copy from:
   Battlerite Royale/BattleriteRoyale_Data/Plugins/stun_steamnetworking.dll

To both of these locations:

VRising/VRising_Data/Plugins/x86_64/
VRising/VRising_Server/VRisingServer_Data/Plugins/x86_64/

1. To fix intro video, launch game with:
   WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

The last 103 lines of my Proton log are the same except for the timestamp:

467.414:0130:0134:fixme:system:QueryDisplayConfig (00000002 000000000010F740 00000000E0000010 000000000010F8C8 00000000E00000B0 0000000000000000): semi-stub

It's crashing either during Server Starting Up XXX/209, or during Loading.

Replying to https://github.com/ValveSoftware/Proton/issues/5845#issuecomment-1134205419

sadly this doesn't seem to work on the steamdeck nvm I did not use the Royale version

~sadly this doesn't seem to work on the steamdeck~ nvm I did not use the Royale version

Ninja edit'ed before I could say anything.

Yeah to anyone else make sure you're using Battlerite (Royale) and not Battlerite.

Saw this kind of clarification needed on Steam Discussions and in Reddit comments.

Should hopefully be fixed now in Proton Experimental [bleeding edge] branch (without requiring any manual workarounds).

Should hopefully be fixed now in Proton Experimental [bleeding edge] branch (without requiring any manual workarounds).

What branch are you building from? I don't see any recent changes committed

What branch are you building from? I don't see any recent changes committed

https://github.com/ValveSoftware/Proton/commits/experimental-bleeding-edge-7.0-16382-20220523-pad54a5-w198163-d51e56c-v910f15

You can select Proton Experimental properties, choose Beta property page and select [bleeding-edge] branch there, no need to build it.

I confirm current Proton Experimental bleeding-edge let's you get into game (online play also). However, there are two issues:

1. problem with graphics for me
   

2. you still need to kill the game on exit (it's not responding).

BONUS 3) Another interesting fact (not related to our issue) - you don't see any of your existing characters (as played via Bottles workaround) BUT - if you connect to same server, you will be loaded into old character :).

Another interesting fact (not related to our issue) - you don't see any of your existing characters (as played via Bottles workaround)

The game doesn't utilize steam cloud saving for your private saves, so running the game through Bottles and regular Proton don't sync up, they're saved in different locations.

Use something like mlocate to find and copy your saves from Bottles.

$: updatedb
$: locate -i rising | grep -i save

Sorry, I posted my specs above, but here they are again, if anything is missing, let me know, I'll try to fill-in.

Fedora 36
AMD Ryzen 5
AMD 6800 XT
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.0.0-git
RAM 32 GB
Using Wayland

I repeat, via Bottles (wine Steam + wine apparently), game runs PERFECTLY for me (only problem being needing to kill when exiting to OS).

Thanks for adding those to Experimental bleeding edge. Quite the enjoyable game. Looks like all that's left to fix is needing to stop the game from Steam on exit.

Hang on exit should hopefully be fixed too now in the latest Proton Experimental [bleeding-edge].

You are doing an amazing job :)

Can confirm that using the latest Proton Experimental [bleeding-edge] the game launches, is playable and exits cleanly.

I'm having an issue though where if the graphics options in-game are set to "Exclusive Fullscreen", then alt-tabbing out of the game to the desktop, and then attempting to return to the game using alt-tab does not redraw the game window, although the in-game cursor does appear. I then need to alt-tab back to Steam and close the game using the Stop button.

If the game is set to "Fullscreen Window", then alt-tabbing out of the game does not show me my desktop, I just get a non-interactive game screen until I alt-tab back to the game.

Windowed mode behaves as expected, although if I switch from Windowed mode, to Exclusive Fullscreen, the game window is not drawn correctly and I must shut it down.

Anyone seeing similar?

Info for reference:
System:
Host: MintBox Kernel: 5.13.0-44-generic x86_64 bits: 64
Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una
Graphics:
Device-1: AMD driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa tty: N/A
OpenGL: renderer: AMD Radeon RX 6800 (sienna_cichlid LLVM 14.0.1 DRM 3.41
5.13.0-44-generic)
v: 4.6 Mesa 22.1.0 - kisak-mesa PPA

Replying to https://github.com/ValveSoftware/Proton/issues/5845#issuecomment-1135511616

Nice! Exiting game really no longer hangs up the game. I yet still have black screen issue described above, anybody else?

Do you have an ETA for when it will reach proton experimental?

As I've written above, still having black screen with icons ingame, what else can I provide to help pinpoint the problem?

Hi,
I have also observed the same issue as @hatani with black screen if I use exclusive fullscreen and alt tab out of the game.

Running:
Arch
Kernel: 5.17.9-zen1-1-zen
AMD Ryzen 7 5800X
NVIDIA GeForce GTX 1080 Ti (driver version 515.43.04)

Please use the bleeding edge branch of Proton Experimental

Please use the bleeding edge branch of Proton Experimental

I do, and always did (for the scope of this case). But the problem is still there:

EDIT: problem was actually caused by forcing DX11! I've seen that it helped some people play the game, and now after I deleted the command line argument, it works!

Is voice chat working for anyone? It's using Vivox apparently and I saw some fixes in other games ([comment in #5827](https://github.com/ValveSoftware/Proton/issues/5827#issuecomment-1126542829)) with similar issues & Vivox.
In my case (proton experimental, bleeding edge) I can hear people but my audio is never picked up, with or without push to talk enabled.

Voice chat now works!

For about 8 days now (maybe slightly longer), V Rising is crashing pretty consistently, though not always in the same situation. Combat seems to trigger it, although I have crashed without it as well (though less frequently). The Unity Crash Handler is displayed shortly, afterwards the game terminates, and I can rejoin easily.

The last 2 reports on protondb.com suggest other people have similar problems.

I will try to add a proton log with a crash produced as soon as I have time to test more.

Edit 1: Created a log, but it's 91MB, so I've uploaded only the start with the exception, which happened not even 2 minutes into the game. If more is necessary, I can provide more of the log (though creating a gist from it times out).

Edit 2: Unity Crash Handler didn't show up this time, I killed the process myself as it was not shutting down on its own.

Edit 3: Tried yesterday again with the settings described by the latest ProtonDB entry, this time forcing Proton 7.0.4 (didn't have 7.0.3 available) and using the command line mesa_glthread=true gamemoderun %command%, no crashes.

For what it's worth this game doesnt work at all under any proton version for me

Here are the logs for GE, Expiramental, and 7

7 Says "idk how to directx11" and Expiramental and GE bring up the unity crasher app

Glorious_Eggroll.log
Expiramental.log
Proton7.log

https://gist.github.com/praxis88/58c201153d6714b2a5ccef9924e0e54d

@kisak-valve I appended it to the origional post

Reading through I realize libva_driver and vdpau driver were set to radeonsi ( because my real gfx card is on rma, and I've fallen back to an nvidia. I have never run v-rising for either card successfully). After removing the libva_driver and vdpau_driver declarations from /etc/environment, restarting the computer, and retesting, the behavior is the same.

@kisak-valve Thanks, that was the problem

1. To fix intro video, launch game with:
   WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%

Sadly this didn't work for me, are there any other workarounds?

The game works with the latest build of Proton Experimental, however none of the videos will play, including the one in the background of the main menu.

However if you use GE-Proton instead, this fixes the videos.

Got game working on linux with GE. However, the game is too dark to play. Anyone know of a launcher setting to fix this? Using nvidia card

I had this game working up until a few days ago, so it doesn't have anything to do with the 1.0 update as far as I can tell, when it suddenly started to CTD any time a large number of effects occured, ie during most boss fights, it's possible a driver or library update caused something to go sideways, but I have no clue where to start. I've attached logs for Proton 9.0.1, Experimental, and GE-9.4, all of which experience the same crashes, as well as my system info according to Steam's System Information tool.

Gist with Relevant Logs & Steaminfo

@kisak-valve Yep, that's 100% it, downgrading to kernel 6.8.8-arch1-1 for current fixed the issue. Seems like I'll be waiting on that release, then. Thanks for the assist.

I'm seeing an issue with this game and Planet Crafter where the game loads but I can't interact with the game (music plays but I can't click anything inside the game window).

I also run Valheim using proton experiment and that runs quite smoothly so not too sure what the difference is here with V Rising and Planet Crafter.

• System info
• mesa 24.1.0-1
• Using KDE Plasma
• Proton version: Experimental (Forcing the game to use Proton 9.0 had the same results)

The issue I'm having that I haven't seen anyone report yet is most of the models in the game don't seem to render for me. The game runs super smooth without crashing but everything from walls to trees and rocks are just not rendered. :thinking: . Some things, like the tannery, chests, and grass (but not the furnace or workbenches) are rendered. Since I haven't seen anyone else have this issue I am assuming that I'm doing something wrong or weird here.

The only unique thing I can think of is I have all of my steam downloads in a separate drive (/shared, which is owned by root:shared) which is an XFS filesystem.

I have tried systemctl start --user gamemoded and using gamemoderun %command% but that had no effect.

Edit: Looks like this resolved for me after using the radeon vulkan implementation by installing the vulkan-radeon and amd-vulkan-prefixes packages and setting the game's command to vk_radv %command%

Game runs fine for me in PopOS with proton 9, but the proton hotfix and proton 10 beta seem top keyboard input from being recognized by the game

@wtblife could you give some more details? Where exactly are you trying to use keyboard input and it is failing in the game? Could you describe this more precisely?

Also, could you please get a log by adding this as a launch option: PROTON_LOG=+hid,+hidp,+hid_report,+plugplay,+rawinput,+dinput,+xinput,+joystick,+setupapi,+input,+event,+key,+keyboard,+input %command%

And please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.

@tgerpheide I just had another idea -- we just pushed a fix for another keyboard issue in a bump to Proton 10 Beta. When you retest, please make sure you retest Proton 10.0-1d (which just went live ~30 seconds ago) just in case this is already fixed :)

@alasky17 No luck still, but not sure if experimental or 10.0-1 in Steam are the up to date versions (I tried both)

Deleting my other comments cause they were made on the wrong account

Here are the logs etc:
https://gist.github.com/wtblife/3ac4d04441348bcda2f896595df9d32b

I'm having the weird issue that after 40 minutes or so the game's FPS tanks hard. Like 120fps down to 20fps for, what I can tell, no reason. I have to restart to "fix" it for another 40 minutes or so.

I'm running:
arch linux
linux64 6.14.6-arch1-1
mesa 1:25.1.0-1
vulkan-radeon 1:25.1.0-1

proton hotfix and proton experimental same issues. kde on wayland if that matters. intel 14900k and a 7900 xtx.

I'm having the weird issue that after 40 minutes or so the game's FPS tanks hard. Like 120fps down to 20fps for, what I can tell, no reason. I have to restart to "fix" it for another 40 minutes or so.

I'm running: arch linux linux64 6.14.6-arch1-1 mesa 1:25.1.0-1 vulkan-radeon 1:25.1.0-1

proton hotfix and proton experimental same issues. kde on wayland if that matters. intel 14900k and a 7900 xtx.

The lag time bomb is due to https://github.com/ValveSoftware/steam-for-linux/issues/11446
The current workaround is to enable the steam overlay or use LD_PRELOAD=""

Replying to https://github.com/ValveSoftware/Proton/issues/5845#issuecomment-2895016892

Thank you. Enabling overlay and screen recording did fix it. What an odd issue.