V Rising (1604030)

[kdwinter]

Compatibility Report

• Name of the game with compatibility issues: V Rising
• Steam AppID of the game: 1604030

System Information

• GPU: RX 6700 XT
• Driver/LLVM version: Mesa 22.0.3
• Kernel version: 5.17.1-zen1-1-zen
• Link to full system information report as Gist: https://gist.github.com/kdwinter/7b6fbfe8a3a78ffe8ceb93214d2cfa23
• Proton version: Experimental

I confirm:

• [X] 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.

Symptoms

Crashes on startup. With PROTON_USE_WINED3D=1 the game sometimes reaches the main menu, but then again crashes after the intro video (which isn't visible; only artifacts ), or upon attempting to join a server. With DXVK, it consistently crashes before reaching any menus.

Different Proton versions do not appear to change this behavior, except for 6.3: with Proton 6.3 the game consistently starts, but then stops on a "Steamworks initialization failed" screen.

Reproduction

Launch the game from Steam.

steam-1604030-2.log

steam-1604030.log

[kdwinter]

Steam log: steam-1604030-2.log

[screwylightbulb]

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

[calvinbull]

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

[deverebor]

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".

[hatani]

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

[jimsjoh]

Confirmed, same issue

[Dreameh]

Confirmed, same issues.

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

[screwylightbulb]

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

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

[static-glitch]

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?)

[screwylightbulb]

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.

[1player]

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

[hatani]

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

Same, but after updating bleeding-edge Proton Experimental just now, I can at least stop hung game without it hanging whole Steam.

Also it seems Proton 6.21-GE-2 is the only one letting me see the loading screen with Steamworks initialization error (same as screenshot above from other user).

[xuerivera]

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

[screwylightbulb]

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

steam-1604030.zip

[nenoro]

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

[DeeV55]

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

[screwylightbulb]

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

VRising.zip

[LordJakki]

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

[1player]

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.

[screwylightbulb]

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.

[Melkren]

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.

[WelshPixie]

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?

[Melkren]

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

[WelshPixie]

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)

[LordJakki]

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.

[Wolf-086]

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.

[Wolf-086]

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.

[nenoro]

yeah steam guard doesn't pop up for me too

[1player]

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.

[Wolf-086]

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.

[kisak-valve]

While it's okay to discuss most workarounds here, please keep in mind that this issue tracker is intended for Proton feedback. Issues with Steam for Windows run with wine/bottles is out of scope for this issue tracker and should be discussed elsewhere.

[screwylightbulb]

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

[abique]

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.

[Nicknakin]

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

[WelshPixie]

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

[iMonZ]

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?

[1player]

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.

[fonikz]

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

[GloriousEggroll]

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/

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

[fonikz]

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.

[hrkrx]

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

[GStefanowich]

~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.

[gofman]

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

[luthes]

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

[gofman]

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.

[hatani]

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 :).

[GStefanowich]

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

[hatani]

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).

[Seibz]

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.

[gofman]

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