New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serious Sam VR: The Last Hope (465240) #2708
Comments
#2166 System Information
SymptomsThe 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 ValveSoftware/SteamVR-for-Linux#481. 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: Here is my system information: Computer and Steam Information.
|
@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
<#2708 (comment)>,
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 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. |
Logs of working 4.11-13 instance. 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: And when Failing: Hopefully there is some more information in there somewhere. |
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.
The text was updated successfully, but these errors were encountered: