I cannot get the game to run

[zippyandgeorge]

I have a new PC with a clean install of Windows 10 (October 2020 release). On my old PC the game was running great. On my new PC if I choose to run either the 2D or VR version nothing happens. This is the only game I having a problem with. I am using a RTX 3080 graphics card.

[zippyandgeorge]

I have just read somebody else is having problems with the game and they are also using a RTX 3080.

[ThreeSon]

Same here and also with a 3080 FE. Game won't start no matter what.

[ThreeSon]

I don't know what this fix[web.archive.org] is doing, but it worked. Suggested by another user here in the forum.


EDIT: There is probably a better solution available that is more secure than this one, courtesy of PurSpyk!!:

1. Right-click Trover in your Steam library page and select "Properties"

2. In the "Launch Options" box in the General tab, copy and paste this string:

cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"

3. Close the Properties window and launch the game

I have not tested the above solution but if it works then it's almost certainly a better option versus modifying the Windows environment, in addition to being easier to implement.

[Thorsen]

i have the same problem and i have the 3060. @ThreeSon the link you sendt wont load up for me.

EDIT: i got youre link to load and did what it told me to do and now it works :D

[trevnologies]

I have a 1660 super and was having the same issue. I tried the Environmental Variable on my machine and that fixed the launching for me too.

[ThreeSon]

Maybe it is related specifically to 10th and 11th gen Intel processors, instead of GPUs. I am using a 11700K at stock speed.

[trevnologies]

Definitely possible. I am also running an 11700k.

[zippyandgeorge]

Originally posted by ThreeSon:

I don't know what this fix[web.archive.org] is doing, but it worked. Suggested by another user here in the forum.

Thanks this worked for me.

[Healed to Death]

My game also refuses to play. The above hack did not work for me

intel i7- 11800H
32GB RAM
3080 maxq

[Longduzboub]

same here nothing work

[MrSkinny]

The web archive link and original is down. Anyone have the actual instruction... it's just a Windows env var from what I remember?

[ThreeSon]

Originally posted by MrSkinny:

The web archive link and original is down. Anyone have the actual instruction... it's just a Windows env var from what I remember?

link[web.archive.org] is working again but here are the instructions just in case:

1. Open “File Explorer” (Win+E), right-click on “This PC”, and select “Properties”

2. Select “Advanced System Settings”

3. Select “Environment Variables” in the “Advanced” tab

4. Select “New…” under “System variables”

5. Input the text below and select “OK”
Variable name: OPENSSL_ia32cap
Variable value: ~0x200000200000000

6. Confirm that the variable has been added successfully, then select “OK”


EDIT: There is probably a better solution available that is more secure than this one, courtesy of PurSpyk!!:

1. Right-click Trover in your Steam library page and select "Properties"

2. In the "Launch Options" box in the General tab, copy and paste this string:

cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"

3. Close the Properties window and launch the game

I have not tested the above solution but if it works then it's almost certainly a better option versus modifying the Windows environment, in addition to being easier to implement.

[MrSkinny]

Thanks very much. Would be nice to know if this is "safe" to leave running in env when not playing the game. Since this is a basic Unity engine game, I can't believe Trover and Rick & Morty are the only games affected by the later Intel processors. Googling the env var[www.openssl.org], I can't parse what the bit value is actually doing to OpenSSL handling.

[ThreeSon]

Originally posted by MrSkinny:

Thanks very much. Would be nice to know if this is "safe" to leave running in env when not playing the game. Since this is a basic Unity engine game, I can't believe Trover and Rick & Morty are the only games affected by the later Intel processors. Googling the env var[www.openssl.org], I can't parse what the bit value is actually doing to OpenSSL handling.

I am ignorant as far as the implications go. All I could say is that since implementing this fix back in July, I haven't had any odd graphical or other problems that weren't there before, or that I was unable to explain.

[MrSkinny]

Good to know! Also, I've found other threads indicating this was impacting PUBG Battlegrounds and Pavlov VR, so it's clearly not isolated, but both of those games were patched to fix the issue. Unfortunately, not all games are budgeted for ongoing updates.