Knockout League

Knockout League

View Stats:
Game keeps crashing minutes after start
Like the title says, it keeps crashing straight to desktop (there's no error code or pop up afterwards if anyone's wondering). I've reduced the graphics, stopped other background processes, but nothing so far has worked. I don't think any of that would matter, though; I started the game and watched it's activity with the task manager (didn't even touch the headset or controllers), and, despite bouncing between 7 - 11% CPU usage, using around 21% GPU and taking up less memory than six Firefox tabs, it still crashed in just a minute or two. So far, I've not been able to make it through the tutorial or even change my saves' names from the default yet.
If anyone has a solution or even just a suggestion, it would be greatly appreciated.
Originally posted by Kildozer:
This is now solved for me after a developer reached out.

The solution is adding a system environment variable.

Name: OPENSSL_ia32cap
Value: :~0x20000000
(yes, the value also contains a colon)

More information about the issue can be found on Intel's website:
https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html
< >
Showing 1-4 of 4 comments
MrLucid72 Jan 17, 2022 @ 2:11am 
Are you crashing where it says 'adjust' ? With 3080, I'm also getting constant crashes around same area. Sometimes I can get the intro scene for a few seconds. It's like a gpu mem leak. Crashes with no err.
Last edited by MrLucid72; Jan 17, 2022 @ 2:11am
Originally posted by MrLucid72:
Are you crashing where it says 'adjust' ? With 3080, I'm also getting constant crashes around same area. Sometimes I can get the intro scene for a few seconds. It's like a gpu mem leak. Crashes with no err.
No, it was always just some minutes after starting it, regardless of whether I was clicking through menus or hadn't even touched my headset yet. I did actually get this problem fixed just yesterday, but if you're hoping for an answer, I unfortunately don't have one.
I saw a post a couple of days before posting the paragraph above about adjusting CPU clock speeds (unreal engine is apparently really sensitive to overclocking, especially in VR) and decided to try fiddling around in the BIOS to see if I could figure anything out yesterday. I ended up not changing anything since my "overclock mode" setting was turned off, yet when I started the game, it just decided to start working.
I have no clue what happened, why or that it'll even stay working forever. Reinstalling didn't work, reducing RAM load didn't work, adjusting the game settings didn't work, but simply glancing through BIOS made a world of difference for some reason. I guess I see now why the unreal engine is unpopular.
I would suggest trying lowering your clock speed through BIOS or asking God if you haven't already. I would say more, but I was never able to find a solution to this problem when I looked.
Good luck finding a solution.
A developer of this app has indicated that this post answers the original topic.
Kildozer May 19, 2023 @ 9:37am 
2
2
2
2
This is now solved for me after a developer reached out.

The solution is adding a system environment variable.

Name: OPENSSL_ia32cap
Value: :~0x20000000
(yes, the value also contains a colon)

More information about the issue can be found on Intel's website:
https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html
Originally posted by Kildozer:
This is now solved for me after a developer reached out.

The solution is adding a system environment variable.

Name: OPENSSL_ia32cap
Value: :~0x20000000
(yes, the value also contains a colon)

More information about the issue can be found on Intel's website:
https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html
Oh, hell yeah! I never expected this question to get an actual answer. I ended up just putting it down for a couple days and when I tried it again, it worked just fine. I have no idea what happened, especially since it didn't get an update during that time.
Thanks for the info, though. Hopefully this helps someone else in need of an answer.
Last edited by HumuHumuNukuNukuApu-A-A; May 19, 2023 @ 9:01pm
< >
Showing 1-4 of 4 comments
Per page: 1530 50