Serious Sam VR: The Last Hope
#2166 System Information
- GPU: RX 580
- Driver/LLVM version: Mesa 19.2.0-devel/LLVM 8.0.0
- Kernel version: 5.2.8
- Link to full system information report as Gist
- Proton version: 4.11-2
Symptoms
The game crashes at the start if Vulkan backend is enabled. Starts with D3D11, but flickering makes it unplayable.
Serious Sam Last Hope won't verify license
Issue transferred from https://github.com/ValveSoftware/SteamVR-for-Linux/issues/481.
@pete777moen posted on 2021-11-19T01:42:13:
I am trying to load Serious Sam Last Hope, but I get the error message that the license verification can't be accessed. I have run many VR games like Saints and Sinners with no problem with my Index system. Here is a list of things that I have tried:
used 8.8.8.8, 8.8.4.4 as dns on computer
tried 8.8.8.8, 8.8.4.4 on router (not allowed)
2001:4860:4860::8888 and/or 2001:4860:4860::8844 IP6 tried
tried +gfxapi OGL launch option
tried proton version 6.3-7
tried various ways to start, desktop icon (unpacked direct x) normal, without VR on, etc.
SamTLH.log can't find
fire wall disabled, thought i could change it, but it was not on
Here is my system information: Computer and Steam Information.
Manufacturer: ASRock
Model: X399 Phantom Gaming 6
Form Factor: Desktop
No Touch Input Detected
SteamVR Version:\t1.21.2 (1636664637)
SteamVR Date:\t2021-11-11
Steam:\tPublic
Steam Branch:\tbeta
Steam AppID:\t250820
Tracking:\tlighthouse
OS:\tLinux version 5.11.0-40-generic (buildd@lgw01-amd64-010) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) [#44](/issue/ValveSoftware/Proton/44)~20.04.2-Ubuntu SMP Tue Oct 26 18:07:44 UTC 2021
OS Version:\t0.0.0.0
Direct Mode Vendor:\tUnknown
Direct Mode Version:\t
Admin:\tYes
AsyncReprojection:\tEnabled
Performance drops:\t20/1 6/2 2/3 2/4 553/614
Display Mode:\tDirect Mode
</Report>
<Displays>
</Displays>
<Devices>
Device 1 - LHR-F65B100F Headset Index Valve
Device Path:\t/devices/lighthouse/LHR-F65B100F
Best Alias:\t/user/head
Firmware: \t1623823641 WMBUILD-W64$@wmbuild-w64 2021-06-15 FPGA 538(2.26/9/2) BL 1555018600
Hardware Revision: \tproduct 34 rev 21.65.9 lot 2000/0/0 0
Hardware Id: \t0x22154109
Watchman Firmware: \t1623823641 / 1623823641 (2021-06-15)
Watchman FPGA: \t538 / 538 (2.26)
VRC Version: \t1623823641 / 0 (2021-06-15)
Camera Firmware: \tVersion not available.
VSync to Photons: \t0.011375
Display Frequency:\t90
User IPD (m):\t0.07
Current Universe ID:\t0
Previous Universe ID:\t0
Dongle Version: \t0ACC1BE8E3-RYB Version: 1553895605 / 1558748372 (2019-03-29) (Update necessary)
Dongle Version: \tC250D258F1-LYM Version: 1553895605 / 1558748372 (2019-03-29) (Update necessary)
<Device1_Additional>
HMD Report:
.version = 2
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen Threadripper 1900X 8-Core Processor
CPU Family: 0x17
CPU Model: 0x1
CPU Stepping: 0x1
CPU Type: 0x0
Speed: 3800 Mhz
16 logical processors
8 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Ubuntu 20.04.3 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 5.11.0-40-generic
X Server Vendor: The X.Org Foundation
X Server Release: 12011000
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20211102.0
Video Card:
Driver: NVIDIA Corporation GeForce RTX 2060/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 460.91.03
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x10de
DeviceID: 0x1e89
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 34.88" x 19.61" (40.00" diag)
88.6cm x 49.8cm (101.6cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 6144 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Realtek ALC1220
Memory:
RAM: 15855 MB
VR Hardware:
Headset: Valve Index (lighthouse)
Base station or sensor: HTC HTC V2-XD/XE (lighthouse)
Base station or sensor: HTC HTC V2-XD/XE (lighthouse)
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 227081 MB
Largest Free Hard Disk Block: 109659 MB
Storage:
Number of SSDs: 0
Number of HDDs: 0
<Unfilled SteamVR issue report template omitted>
@pete777moen I have been having the same Licensing issues for, I think years now. I played this game a lot in VR (linux and windows) back when Proton 2, 3 and 4 were current.
After doing some troubleshooting I also confirmed that my network connectivity is fine, (in general may be borked in Proton) yet the DRM issue remained, in modern versions of proton.
On a hunch I tried proton 4.2, and it works no problem. Also proton 4.11 works no problem. Any newer versions i tested (5,6,7,experimental) and GE newer versions (6,7) all fail to connect to license servers.
Game logs indicate SSL failure, so maybe proton updated with a new ssl/tls library (or is missing a CA for validation or or something). But normal networking checks out as multiplayer works. maybe this is a more complex DRM issue.
Thank you. When I get a chance I will try it.
Peter Moen
On Sun, Mar 6, 2022 at 11:36 AM samualblair @.***>
wrote:
@pete777moen https://github.com/pete777moen I have been having the same
Licensing issues for, I think years now. I use to play this game a lot in
VR (linux and windows) back when Proton 2, 3 and 4 were current.After doing some troubleshooting I also confirmed that my network
connectivity is fine, (in general may be borked in Proton) yet the DRM
issue remained, in modern versions of proton.On a hunch I tried proton 4.2, and it works no problem. Also proton 4.11
works no problem. Any newer versions i tested (5,6,7,experimental) and GE
newer versions (6,7) all fail to connect to license servers.Game logs indicate SSL failure, so maybe proton updated with a new ssl/tls
library (or is missing a CA for validation or or something). But normal
networking checks out as multiplayer works. maybe this is a more complex
DRM issue.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2708#issuecomment-1060025830,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWSGAP5NE4TFRKHOKULOXKDU6UCNVANCNFSM4HN2WNPQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.You are receiving this because you were mentioned.Message ID:
@.***>
Hello @pete777moen, @samualblair, can one of you please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Also, it would be interesting to try running the game with Proton 4.11 once, then switch to Proton 5.0 add see if it keeps working as intended.
proton_4.11-13_steam-465240.log
proton_5.0-10_tempissue_after_container_change_steam-465240.log
proton_5.0-10_worked_after_steam_restart_steam-465240.log
proton_5.13-6_launched_after_steam_restart_but_regression_hit_steam-465240.log
proton_5.13-6_tempissue_after_container_change_2_steam-465240.log
proton_5.13-6_tempissue_after_container_change_steam-465240.log
Logs of working 4.11-13 instance.
Logs of actually working 5.0-10 instance, as noted in a couple logs when I switch proton versions right away the game won't launch, apparently this tricked me earlier into thinking 5.0-10 was broken. After exiting steam, and re-launching it works. My thought is something is hung/pending with the new proton container. Anyway it looks like 5.0-10 is good.
The breakage/regression seems to happen in 5.13-6. Again I attached a (well 2 logs) of the game not launching after proton change, but again after closing and re-opening steam that wasn't a problem. Now the game launches but the "unable to contact licensing server" issue is present.
Logs do show SSL connection failures start on 5.13-6, but SSL connections are good with 5.0 and 4.11
Also just FYI, whenever closing it appears the game engine throws an crash/error page, but that seems to be occurring on any version of proton I've used and from what I can tell is harmless, generally steam kills the window before I look at it or bother. Might just make the end of the logs more messy.
From what I can see in the logs when working (4.11-13 and 5.0-10) we have:
ERR: LVE: 2351
INF: OpenSSL 1.1.0e 16 Feb 2017
And when Failing:
ERR: LVE: 2351
ERR: LVE: 2352 - Failed to initialize SSL! Error: unknown certificate verification error
ERR:
Hopefully there is some more information in there somewhere.
This License Verification problem also happens (although in different ways) in the following Croteam games:
- Serious Sam HD: The Second Encounter: in-game spinning camera DRM triggers far in the game (crack protection)
- Serious Sam 3: BFE: in-game spinning camera DRM triggers far in the game (crack protection)
- Serious Sam Fusion 2017 (beta): requires an "username" and a "password" on launch and nothing works.
Some Steam discussions referring to the issue:
- https://steamcommunity.com/app/564310/discussions/1/569290593938717832/
- https://steamcommunity.com/app/41070/discussions/3/832746196752809574/
- https://steamcommunity.com/app/41010/discussions/0/568164456893401878/
- https://steamcommunity.com/app/41010/discussions/0/657108053777348245/
- https://steamcommunity.com/app/41070/discussions/0/569289127298713917/
Proton versions
proton 4.11x4 2022-03proton 5.0x2 2022-03proton 5.13x1 2022-03proton 4.2x2 2022-03
Launch options
PROTON_LOG=1x1 2022-03
Compatibility Report
System Information
I confirm:
steam-465240.log.tar.gz
Symptoms
Reproduction
Game crashes on boot. Attached wine debug log. Also attempted to boot with the Vulkan API set as a launch option, slightly different symptoms that way but still crashes before booting.