search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.93k stars 1.05k forks source link

Half-Life: Alyx (546560) #3681

Open mathew2214 opened 4 years ago

mathew2214 commented 4 years ago

Compatibility Report

System Information

I confirm:

proton log: https://gist.github.com/mathew2214/a1067ba8bae2d4928c6396b63e14240b

Symptoms

the game does not launch. instead giving the error:

VrOverlay failed initialization with error code VRInitError_Init_InterfaceNotFound: "Interface Not Found (105)"

kisak-valve commented 4 years ago

Looks like err:steamclient:create_win_interface Don't recognize interface name: STEAMTV_INTERFACE_V001 is the line of interest from the log.

TECHNOFAB11 commented 4 years ago

Same Error for me

Edit: my Steam System Info: https://gist.github.com/TECHNOFAB11/8d479c06f7199b0c0ebf23275b531f2f

radriaanse commented 4 years ago

~Not exactly the same error, but also having issues launching the game.~ Proton log says it's the same error. Using Proton 5.0-5 and tried the public, beta & linux_temp SteamVR builds.

Log of SteamVR launch: https://gist.github.com/radriaanse/a13885c86e611e6529507a4500fa163f#file-steamvr_launch

Log of game launch: https://gist.github.com/radriaanse/a13885c86e611e6529507a4500fa163f#file-hla_launch

Proton log: https://gist.github.com/radriaanse/6860478d405853fc19aaf39a48cf1ecd

Error screenshot: image

System info: https://gist.github.com/radriaanse/8e91a8c6b0fd8a20f12d1af97ba03fe3

kivoli commented 4 years ago

For me it worked once I chose Proton 5.0-5 but performance is abysmal — that can’t just be my Vega 56, I have sometimes frame times of 50 ms and above.

mathew2214 commented 4 years ago

For me it worked once I chose Proton 5.0-5 but performance is abysmal — that can’t just be my Vega 56, I have sometimes frame times of 50 ms and above.

system info and proton log please?

zaggynl commented 4 years ago

Starts for me.
PC is struggling with rendering but my god this looks good compared to other VR FPS games I played. Set these launch options: PROTON_LOG=1 RADV_PERFTEST=ACO Performance seems to be better now.

Steam system info: https://gist.githubusercontent.com/zaggynl/19d6a81cd78c88066c7be8f132e63a3e/raw/51cf2ba54ad6cedea97c5648222216beb38ba0c2/gistfile1.txt

summary: ubuntu 20.04 (upgraded for doom eternal, didn't help) oibaf ppa for mesa-git (not sure if needed?)

streamvr beta screenshot: https://imgur.com/2hVVLfb.png

Proton log: pending

VurtualRuler98 commented 4 years ago

I manually chose Proton 5.0-5 and the game ran fairly well, however it always crashes to a black screen(with the headset ostensibly turning off) when entering the train after getting the pistol, where it seems a level change should occur. In some cases the game will display an error complaining about the steamVR library being out of date(even though steamVR is a newer version than the minimum it requests), in others the game will just freeze and must be manually closed.

System info: https://gist.github.com/VurtualRuler98/25db38bf420800016515507a88b32c38 Proton log: https://gist.github.com/VurtualRuler98/de263199e0d8bd6a836b54c679f8479e vrserver log: https://gist.github.com/VurtualRuler98/a0b8d467f1a8bec8647289d09ce9799d vrcompositor log: https://gist.github.com/VurtualRuler98/e573aec4e564f268e4b6b8e1e580459b

kisak-valve commented 4 years ago

Hello @VurtualRuler98, err:vrclient:create_win_interface Don't recognize interface name: IVRInputInternal_002 looks like a line of interest from the log.

frostworx commented 4 years ago

the game works fine here ( i7-8700K, RTX 2080, up2date arch linux, nvidia-dkms-440.64-5) but it reprodacable crashes when entering the train wagon, probably while loading the next level chapter. In fact SteamVR crashes (including hmd turning off)!

mkalte666 commented 4 years ago

the game works fine here ( i7-8700K, RTX 2080, up2date arch linux, nvidia-dkms-440.64-5) but it reprodacable crashes when entering the train wagon, probably while loading the next level chapter. In fact SteamVR crashes (including hmd turning

Its general level loads as far as i can see. I could progress by saving before the level load, letting it crash (or not). After starting the game again it progresses just fine. A bit annoying, but i save way to often anyway, so this will probably not remove to much progress for me.

Still, would be nice to have this fixed. Ill try to get a log next crash

Okxa commented 4 years ago

Game launches on proton 5.0-5, but like others have said, performance is bad.

I also the game got stuck on the loading screen after the intro chapter, after the 2nd elevator.

Proton log

sys info

lostgoat commented 4 years ago

The SteamVR beta branch has some fixes related to loading screens for HL:A on linux.

mkalte666 commented 4 years ago

The SteamVR beta branch has some fixes related to loading screens for HL:A on linux.

I'm on the beta branch already. Or do you mean linux_temp?

radriaanse commented 4 years ago

I'm probably missing something, but I'm still unable to launch even with the earlier mentioned launch options. Still get the same error in both the log and gui.

radriaanse commented 4 years ago

The SteamVR beta branch has some fixes related to loading screens for HL:A on linux.

I'm on the beta branch already. Or do you mean linux_temp?

https://steamdb.info/app/250820/depots/ beta seems to be the most recently updated, although ~17 hours old.

frostworx commented 4 years ago

the game works fine here ( i7-8700K, RTX 2080, up2date arch linux, nvidia-dkms-440.64-5) but it reprodacable crashes when entering the train wagon, probably while loading the next level chapter. In fact SteamVR crashes (including hmd turning

Its general level loads as far as i can see. I could progress by saving before the level load, letting it crash (or not). After starting the game again it progresses just fine. A bit annoying, but i save way to often anyway, so this will probably not remove to much progress for me.

Still, would be nice to have this fixed. Ill try to get a log next crash I can confirm that loading immediately after entering the wagon fixes this glitch. thank you for the workaround! I'm on SteamVR beta branch btw (not linux beta). the game is mostly at playable speed with some hickups here and there. quiet long loading times, but this might be hdd related and no bigger issue (for me)

FredrikHson commented 4 years ago

had to symlink my .local/share/Steam/SteamApps folder to .local/share/Steam/steamapps to get the controllers to work

Okxa commented 4 years ago

After loading the game up again, it works better in the levels that I already had been at. But after going forward in the game (in the courtyard which was featured in the steamvr home previews), the performance tanks again.

At that point I tried saving and loading, but it got stuck on the load screen, while everything was laggy and slow. Even the controllers and view moved in slow motion.

I was using RADV_PERFTEST=ACO on the hl alyx, as well as the beta branch of steamvr.

Zamundaaa commented 4 years ago

I didn't have any launch or even crash problems at all but sometimes HL:A used all of the GPU and had refresh rates and jittering that was horrible. I solved almost all of these by setting the resolution / super sampling of the Index down to 30%. The problem of the loading screen remains: sometimes it uses the GPU to its full extent and takes like 5 minutes to load, while the PC is unresponsive (even the mouse!) and you get 3fps in VR. After that it does recover again though and is completely playable again. I'm using a 5700 XT with aco, on the beta branch of SteamVR.

mkalte666 commented 4 years ago

Found this in my syslog: https://gist.github.com/mkalte666/9eb82820fff62dfc5b9d3e377c042225

lordkitsuna commented 4 years ago

I didn't have any launch or even crash problems at all but sometimes HL:A used all of the GPU and had refresh rates and jittering that was horrible.

I am having this issue as well, however i have determined it is a VRAM issue and possibly a memory leak. I have tried turning res per eye down and in game fidelity as well all the way down. These help but it only extends the time to VRAM starve. System specs as follow OS: Arch Linux x86_64 Kernel: 5.6.0-rc2-1 CPU: 5820K OC to 4.6GHz GPU:/5700 XT Memory: 48182MiB (48GB) Driver: mesa-git 20.0.0_devel.119657.58ba7b696dd-1 SteamVR: Version 1.10.32 (1584924836) HMD: Index

Here is a shot of the desktop view with DXVK HUD showing the overloaded VRAM image

I can trigger this overload even if i just stay in once spot it just takes much longer. Please let me know if there is anything else i can provide to help track this down.

fabiankranewitter commented 4 years ago

For me it also crashes when a new level is loaded, sometimes during a train or when arrested. But also when selecting saves. It's going well but the performance could be better.

System: i7-4770k Nvidia 2060 super (8gb) [440.64] 32 GB Ram HTC Vive

Syslog dmesg: RenderThread[3829]: segfault at 8 ip 000000000058ef9d sp 00007f5ad0faaee0 error 4 in vrcompositor[400000+36b000] [ 737.625405] Code: 01 00 00 00 0f 84 73 02 00 00 8b 80 10 01 00 00 48 8d 44 10 10 48 8b 44 c7 10 48 85 c0 48 89 85 40 ff ff ff 0f 84 6a 02 00 00 <41> 8b 47 08 83 f8 14 0f 87 76 02 00 00 48 8d 15 cf ff 11 00 45 8b

mkalte666 commented 4 years ago

I also just lost some saves to god-knows where (basically all reset to the launch before the one that crashed/newer ones just gone). I think that might be a steam cloud issue, but no idea how i should approach this

Zamundaaa commented 4 years ago

@lordkitsuna well, the problem only appears after two or three loading screens so that sounds like it is the issue. Weirdly though right now I have only 4038MB of 8 gigs used and got the problem.

rnd-ash commented 4 years ago

This happens to me at every level after getting in the train. No matter how quickly a level is completed.

kivoli commented 4 years ago

@mathew2214 Sorry for being a bad reporter earlier:

System Information

I crashed on me now after a nice hour of game play just after successfully loading the next level (just after fighting the head crabs), probably because I set down my HMD during the loading. Unfortunately I did not have PROTON_LOG=1 set yet. :-/

The real bummer though is that there was a hot fix release for SteamVR beta just twenty minutes ago and now SteamVR won’t start — I’ll reboot to check if I did something to break things. I had to kill SteamVR due to the earlier crash after all.

//edit: I don’t know if it’s the hot fix but my frame times are a lot better now. Still not the desirable 11 ms but absolutely bearable 13-15 ms with better reprojection, too, as it seems. No more frasnell effect — but let’s see, maybe it’s just the level. I’ll keep you posted.

//edit2: Added log of latest gameplay which crashed after loading a save — for the second time, due to dying twice …

radriaanse commented 4 years ago

@kivoli Seeing that you are on Arch as well, did you do anything special besides adding that launch option to be able to start? I've been playing around with some settings and other kernels/mesa-git packages but I'm still not able to get past that first error.

kivoli commented 4 years ago

@radriaanse SteamVR Beta (not forcing any Proton-Version) and Proton 5.0-5 for Alyx although the latter was enough for me to get it running in the first place, even with the non-beta SteamVR.

hdmap commented 4 years ago

I'm not as familiar with lsteamclient stuff so I don't know how much of a problem the STEAMTV_INTERFACE_V001 thing is going to be but I can already tell that the game requesting IVRInputInternal_002 is going to be a difficult problem to fix in the vrclient shim. As far as I can tell that's not exposed by openvr and looks like it's internal to SteamVR itself.

@kisak-valve Is it possible you could contact somebody who works on openvr/steamvr and get more information on this, or do you have any info on if the linux native build is coming soon enough that this wouldn't be worth dealing with?

Plagman commented 4 years ago

Proton 5.0.5 has all the support needed for these interfaces already. SteamVR beta and the Steam client Beta with Proton 5.0.5 should be all that's needed to play, at the moment.

edwin-v commented 4 years ago

Well, the game would get past the "press trigger" without the symlink mentioned by FredrikHson. Only mine had to be in a different location because I used an additional library.

And I too get the crash in vrcompositor after getting in the train.

Plagman commented 4 years ago

The crash in the compositor happens after longer play sessions that go through several transitions, it seems to run out of memory. Restarting everything should let you play proceed forward and play the next level when that happens now.

Thanks for the report on old-style library folder casing causing issues.

radriaanse commented 4 years ago

@Plagman Do you have any idea if the

https://github.com/ValveSoftware/Proton/issues/3681#issuecomment-602768786

VRInitError_Init_PathRegistryNotFound: "Installation path could not be located (110)

Is at all related to this issue, as I'm still not able to launch the game. All other (VR) games work just fine, tried reinstalling SteamVR, HL:A, Proton.

hdmap commented 4 years ago

Proton 5.0.5 has all the support needed for these interfaces already. SteamVR beta and the Steam client Beta with Proton 5.0.5 should be all that's needed to play, at the moment.

Thanks. I'm pretty rusty with Proton so I'll probably need to see what changed there in vrclient later.

I can't get a log myself to confirm but looking at the new log from kivoli they have SteamVR beta and Proton 5.0.5 and are still getting messages about those interfaces missing. I'm guessing if they're not causing any of these issues it's not a big problem, though.

edwin-v commented 4 years ago

The crash in the compositor happens after longer play sessions that go through several transitions, it seems to run out of memory.

Loaded in just before capture. Ran through the next bit in 10 minutes and crashed again at the train. That was after a fresh start on a 32GB machine. Error similar to the one posted above, but the segfault address is different each time.

Saved right before the train this time, so I'll check if that gets me beyond that point tomorrow.

TECHNOFAB11 commented 4 years ago

@Plagman I had the linux_temp version of Steam VR activated. Maybe that was the problem, will try with exactly what you said in the morning. Really hoping it works, heard awesome things about HL Alyx and really wanna play it ^^

kivoli commented 4 years ago

I can't get a log myself to confirm but looking at the new log from kivoli they have SteamVR beta and Proton 5.0.5 and are still getting messages about those interfaces missing.

No, sorry for the confusion — I don’t get this message with Proton 5.0-5 anymore and it’s launching/working. My issues are of a different nature:

a) Crashing from time to time, especially during loading b) Rather unsatisfactory performance

TacticalTux commented 4 years ago

+1 for the issue with the crashing with boarding the train. Really disappointing, but hopefully it will be fixed soon.

llamasking commented 4 years ago

I have had consistent crashes when entering the train and really anywhere there is a loading scene, or just loading a save while in game. The workaround for this issue I found was to save immediately before entering where you would crash, restart the game and after loading in, getting to the loading screen as quickly as possible.

I definitely have an issue with not having enough vram, having a 980 (4gb), though the gpu itself isn't all that strained by the game. Looking at nvidia-smi, there's no free vram free when running the game. My cpu and ram are pretty free though, so I don't believe there's any issue with a memory leak. Performance is rather meh. On the lowest settings, I barely manage to sustain 90fps, dropping below that in areas I don't expect, such as when looking at the second upgrade station, though I suspect that's related to the vram issue.

I am running the latest (beta where applicable) Steam, SteamVR, and Proton. I have verified the integrity of Alyx's files.

System Info:

OS: Arch Linux x86_64 Kernel: 5.5.11-zen1-1-zen GPU: GTX 980 running 440.64 SteamVR: Version 1.10.32 (1584924836) HMD: Vive

rstrube commented 4 years ago

This happens to me at every level after getting in the train. No matter how quickly a level is completed.

I'm having the exact same issue. Steam VR crashes after getting on the train. Other people have said that it crashes in general when attempting to load a new level.

yaomtc commented 4 years ago

I've noticed some issues:

I'll have to try again with Mesa 20 tomorrow. Might work better.

OS: Arch Linux Kernel: 5.5.11-arch1-1 CPU: Ryzen 7 1700X GPU: Radeon 5700 XT Driver/LLVM version: DRM 3.36.0, LLVM 9.0.1, Mesa 19.3.4 HMD: Vive Gist: https://gist.github.com/yaomtc/d0364080eb7dca2448ef0d949275b691

EDIT: Tried Mesa 20, perhaps a bit better but still pretty bad. Lot of choppiness when big things happen, and I still often get the temp loading screen.

hdmap commented 4 years ago

I can't get a log myself to confirm but looking at the new log from kivoli they have SteamVR beta and Proton 5.0.5 and are still getting messages about those interfaces missing.

No, sorry for the confusion — I don’t get this message with Proton 5.0-5 anymore and it’s launching/working. My issues are of a different nature:

a) Crashing from time to time, especially during loading b) Rather unsatisfactory performance

I understand that it's mostly working, but from the log you posted, the messages are still there, ie on line 1121. That's all I meant.

NeoTheFox commented 4 years ago

Running Arch Linux, Mesa 20.0.2 and Vega 56 I'm getting severe performance degradation whenever heavy lighting is involved. After the part where a hijacked scanner gets destroyed and you go into a room with a TV just looking at the TV tanks the FPS. ACO really helps with shader compilation, but it doesn't help there sadly. Can pretty much confirm this comment.

jrtberlin commented 4 years ago

With switching between the beta branch and the stable branch of SteamVR I can get through loading screens. (Which is weird because both are version 1.10.32) This "fix" doesn't work for the loading screen when you enter:

Spoiler warning The Northern Star

EDIT: The workaround mentioned in ValveSoftware/SteamVR-for-Linux#318 does work to get further.

The linux_temp branch doesn't work at all for me. I should also mention that I have Ferals gamemode on.

OS: KDE neon 5.18 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.5.11-050511-generic Kernel: 5.5.11-zen1-1-zen GPU: GTX 970 running 440.64 (below minimum spec but the game did run pretty good) SteamVR: Version 1.10.32 HMD: Valve Index

ghost commented 4 years ago

The game didn't work for me at first but it started working after restarting steam (after the first installation of half life alyx)

mnn commented 4 years ago

I am very disappointed with terrible performance. Severe frequent drops on 2080ti on lowest details? :disappointed: Enabling legacy reprojection seemed to help a bit at opening calm scenes. The crash in a train (after getting weapon) was actually convenient, I was starting to literally get sick from those stutters (freezes for short time). Most likely won't play until Valve will fix it.

Releasing a game unplayable on Linux. If it was any other company, I would have been expecting this, but from Valve, that I didn't expect at all.

Steam: Mar 23 2020, at 22:21:54 SteamVR: 1.10.32 Proton: 5.0-5 HMD: Valve Index

other pc info 
System:    Host: xxx Kernel: 5.5.7-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: i3 4.18 Distro: Manjaro Linux
Machine:   Type: Desktop Mobo: ASRock model: X570 Phantom Gaming X serial:  UEFI: American Megatrends v: P1.80
           date: 08/08/2019
CPU:       Topology: 8-Core model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen L2 cache: 4096 KiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 124848
           Speed: 3559 MHz min/max: 2200/3900 MHz Core speeds (MHz): 1: 3559 2: 4449 3: 1980 4: 1969 5: 2200 6: 2199 7: 2200
           8: 2196 9: 1987 10: 1984 11: 2199 12: 2189 13: 2176 14: 2178 15: 3559 16: 4435
Graphics:  Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: ASUSTeK driver: nvidia v: 440.59 bus ID: 10:00.0
           Display: x11 server: X.Org 1.20.7 driver: nvidia resolution: 1920x1080~60Hz, 3840x2160~60Hz, 1920x1080~60Hz
           OpenGL: renderer: GeForce RTX 2080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.59 direct render: Yes
Audio:     Device-1: NVIDIA TU102 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 10:00.1
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel v: kernel
           bus ID: 12:00.4
           Device-3: Valve type: USB driver: cdc_acm,hid-generic,usbhid bus ID: 3-4.3.3:9
           Device-4: Valve type: USB driver: hid-generic,snd-usb-audio,usbhid
           Sound Server: ALSA v: k5.5.7-1-MANJARO
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 08:00.0
           IF: wlp8s0 state: down mac: 
           Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: 5.6.0-k port: e000 bus ID: 0a:00.0
           IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: 
           Device-3: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel port: d000 bus ID: 0c:00.0
           IF: enp12s0 state: down mac: 
Drives:    Local Storage: total: 2.05 TiB used: 1.79 TiB (87.6%)
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB
           ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB
           ID-4: /dev/sda vendor: Western Digital model: WD20EZRZ-00Z5HB0 size: 1.82 TiB
Partition: ID-1: / size: 219.27 GiB used: 186.32 GiB (85.0%) fs: ext4 dev: /dev/dm-0
           ID-2: swap-1 size: 8.80 GiB used: 12.0 MiB (0.1%) fs: swap dev: /dev/dm-1
Sensors:   System Temperatures: cpu: 61.9 C mobo: 48.5 C gpu: nvidia temp: 47 C
           Fan Speeds (RPM): fan-1: 0 fan-2: 1111 fan-3: 0 fan-4: 860 fan-5: 864 fan-6: 2657 fan-7: 1037 gpu: nvidia fan: 42%
Info:      Processes: 395 Uptime: 9h 10m Memory: 31.29 GiB used: 4.36 GiB (13.9%) Init: systemd Compilers: gcc: 9.2.1
           Shell: zsh v: 5.8 inxi: 3.0.37
Zamundaaa commented 4 years ago

Hmm, most loading screens now seem to lag SteamVR extremely (the video even has a 2 second delay from my actions, not just low frame rate) until it eventually crashes SteamVR without filling the VRAM. The VRAM wasn't even at 3 gigs yet.

rstrube commented 4 years ago

I am very disappointed with terrible performance. Severe frequent drops on 2080ti on lowest details? Enabling legacy reprojection seemed to help a bit at opening calm scenes. The crash in a train (after getting weapon) was actually convenient, I was starting to literally get sick from those stutters (freezes for short time). Most likely won't play until Valve will fix it.

Releasing a game unplayable on Linux. If it was any other company, I would have been expecting this, but from Valve, that I didn't expect at all.

Steam: Mar 23 2020, at 22:21:54 SteamVR: 1.10.32 Proton: 5.0-5 HMD: Valve Index

other pc info System: Host: xxx Kernel: 5.5.7-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: i3 4.18 Distro: Manjaro Linux Machine: Type: Desktop Mobo: ASRock model: X570 Phantom Gaming X serial: UEFI: American Megatrends v: P1.80 date: 08/08/2019 CPU: Topology: 8-Core model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 124848 Speed: 3559 MHz min/max: 2200/3900 MHz Core speeds (MHz): 1: 3559 2: 4449 3: 1980 4: 1969 5: 2200 6: 2199 7: 2200 8: 2196 9: 1987 10: 1984 11: 2199 12: 2189 13: 2176 14: 2178 15: 3559 16: 4435 Graphics: Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: ASUSTeK driver: nvidia v: 440.59 bus ID: 10:00.0 Display: x11 server: X.Org 1.20.7 driver: nvidia resolution: 1920x1080~60Hz, 3840x2160~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce RTX 2080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.59 direct render: Yes Audio: Device-1: NVIDIA TU102 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 10:00.1 Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 12:00.4 Device-3: Valve type: USB driver: cdc_acm,hid-generic,usbhid bus ID: 3-4.3.3:9 Device-4: Valve type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server: ALSA v: k5.5.7-1-MANJARO Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 08:00.0 IF: wlp8s0 state: down mac: Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: 5.6.0-k port: e000 bus ID: 0a:00.0 IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: Device-3: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel port: d000 bus ID: 0c:00.0 IF: enp12s0 state: down mac: Drives: Local Storage: total: 2.05 TiB used: 1.79 TiB (87.6%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 970 EVO Plus 250GB size: 232.89 GiB ID-4: /dev/sda vendor: Western Digital model: WD20EZRZ-00Z5HB0 size: 1.82 TiB Partition: ID-1: / size: 219.27 GiB used: 186.32 GiB (85.0%) fs: ext4 dev: /dev/dm-0 ID-2: swap-1 size: 8.80 GiB used: 12.0 MiB (0.1%) fs: swap dev: /dev/dm-1 Sensors: System Temperatures: cpu: 61.9 C mobo: 48.5 C gpu: nvidia temp: 47 C Fan Speeds (RPM): fan-1: 0 fan-2: 1111 fan-3: 0 fan-4: 860 fan-5: 864 fan-6: 2657 fan-7: 1037 gpu: nvidia fan: 42% Info: Processes: 395 Uptime: 9h 10m Memory: 31.29 GiB used: 4.36 GiB (13.9%) Init: systemd Compilers: gcc: 9.2.1 Shell: zsh v: 5.8 inxi: 3.0.37

This is interesting, I'm having great performance on a much lower spec machine. RTX 2070 plus Ryzen 3600.

ZarathustraDK commented 4 years ago

OS: Manjaro Plasma (Linux) Kernel: 5.4.27-1 CPU: AMD Ryzen 3900X GPU: Nvidia 2080TI Memory: 32GB Nvidia driver: 440.64 SteamVR: 1.10.32 (1584924836) Proton: 5.0-5 HMD: Index

Also getting the "Level-transition"-crash when entering the train-wagon and the quarantine-zone (haven't played further). If vRAM was getting filled wouldn't 2080TI-users crash later than any other considering most other cards have significantly less vRAM? Also getting the heavy stutter that seems to reduce significantly after the first playthrough (shader-cache being generated?). For instance, lag/stutter went through the roof in Russel's Lab, it reaaally didn't like that place, probably because of the increased details in everything there (somebody mentioned TV-screens, Russel's Lab has a lot of those). Seems like these are common across all configurations on linux at the moment.

Zamundaaa commented 4 years ago

Well, as I get crashes without the VRAM being filled that is probably not the only issue but very possibly still one of the problems. Now later in the game I also consistently get stutters every time I open the weapon inventory once I'm in the game for like 3-10 minutes. It always crashes on loading screens now, too, unless I load a save that's right before the level transition.