Raft (648800)

[autra]

Compatibility Report

• Name of the game with compatibility issues: raft
• Steam AppID of the game: 648800

System Information

• GPU: HD Graphics 520 (Skylake GT2)
• Driver/LLVM version: 3.0 Mesa 18.2.8
• Kernel version: 4.18.0-25-generic
• Full system information
• Proton version: 4.2-9

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.

steam-648800.log

Symptoms

The game does not launch. I can see a splash screen with a progress bar during 1-2 sec, then it disappears and nothing happens. ps -ef | grep -i raft shows nothing after that.

Reproduction

Launching the game is enough. I reproduce with other proton version too (3.16-4, 3.7-8).

Thanks in advance for your help!

[autra]

The only way I can get the game to start (sometimes) is by using PROTON_USE_WINED3D=1. It is very slow water is not rendered at all though.

[theslimshaney]

The game plays great with proton 4.11-13 and 5.0-3. But after some time I get a random crash. Attaching log (Proton: 1582148269 proton-5.0-3) steam-648800 (copy).log

[szydell]

To start, had to add "PROTON_USE_WINED3D=1". Works with very poor performance. Proton 5.0-3 i7-3687U, Intel GPU (DELL Latitude 6430u), 16GB RAM, SSD.

[Torstein-Eide]

The game is NTFS sensitive:
https://www.protondb.com/help/troubleshooting-faq#games-stored-on-my-windows-partition-ntfs-wont-start

The game have problems rendering the raft:

System information from Steam

[kisak-valve]

Hello @Eideen, 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.

[Torstein-Eide]

https://gist.github.com/Eideen/72574857df843c9e81b1664137ac2ab1#file-info-txt

[mDuo13]

This game runs well on my system (Nvidia) with the following exceptions:

1. If I add the PROTON_USE_WINED3D=1 launch option, I get the plain white textures problem matching Eideen's screenshot. (This launch option is not necessary to launch the game and, in fact, the game runs fine without it.)
2. When joining someone else's multiplayer game, framerate drops to about 5 FPS and no adjustments to the graphics settings seem to improve it. When I am the host, the game runs well on max settings (both multiplayer and singleplayer).

The multiplayer framerate problem seems to have started with the recent 1.0 update to the game. Previously (almost a year ago) the game ran fine even in multiplayer when joining other people's games.

I tried several different Proton versions including 5.x, 6.x, and 7.x/experimental. Most (not all) were able to launch the game, but none of them fixed the multiplayer framerate issue.

[gibarel1]

Replying to https://github.com/ValveSoftware/Proton/issues/2851#issuecomment-1168527464

I've managed to get decent framerates after thinkering with the settings (i was getting anywhere from 5 to 15 before), had to turn off real time reflections, shadow cascades and shadow quality, that gave me 100 fps, disabling ambient oclusion gave me another 30 fps. I'm running latest nvidia drivers on arch and proton experimental.

[ExpandingMan]

I get around 20 f/s in game but more like 120 f/s in the main menu (which includes an in-engine rendered background). On latest experimental as of today on an RTX 2080 super with latest drivers (in X11).

I'd count this as one of the strangest failure modes I've seen after testing hundreds of games on proton, that the main menu background runs fine seems to suggest something is very much amiss.

[vinivosh]

Can confirm this strange issue. I get around 75 fps in main menu, while only 30 fps in a singleplayer game or a multiplayer game that I host.

Multiplayer games that I join annihilate my FPS and makes it unplayable. I get like 0–2 fps. How bizarre. Unfortunately gonna have to refund the game if I can't fix this.

[Cheaterman]

I am entirely unable to start the game on my optimus laptop, no matter what I do - including trying various versions of proton, including GE.

It works perfectly on integrated graphics but obviously wouldn't be playable as such.

EDIT: I eventually managed after hours of fiddling and the cause/solution is extremely puzzling: all I had to do here was remove __NV_PRIME_RENDER_OFFLOAD=1 from my prime-run script... __GLX_VENDOR_LIBRARY_NAME=nvidia seems to cover GLX just fine, and Vulkan uses my Nvidia card by default (otherwise VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.json:$VK_DRIVER_FILES seems to work just fine as well). Hope this is helpful to anyone else...