Open kdwinter opened 2 years ago
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) 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 _mesaglthread=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
Hello @praxis88, please copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
@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.
Thanks, we've seen AMDVLK break other Vulkan drivers before, and it's installed on your system causing the same to happen to you. ( https://gist.github.com/praxis88/58c201153d6714b2a5ccef9924e0e54d#file-gistfile1-txt-L300-L313 / https://gist.github.com/praxis88/58c201153d6714b2a5ccef9924e0e54d#file-gistfile1-txt-L565-L578 )
@kisak-valve Thanks, that was the problem
- 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.
Hello @rtngtom, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot to an older kernel and see how the game behaves.
@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.
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%
Compatibility Report
System Information
I confirm:
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