Help, new PC and not starting SmashBox Arena

[dema95]

My problem is when I launch the game, show the loading screen then crashes and throws me back in the Vive home.

I installed steam to my new PC and transferred my data to it. Every game runs fine except Smashbox Arena, which runned fine on my previous computer (I5, GTX1080, 16GB DDR4).

I tried many options to solve this problem with zero result.

Please help me with this.

[Aragorn]

Hi. Same problem here. I also bought a complete new setup and this game does not work anymore. Other VR games run fine however (win 11 last update, DDR5 32Gb, MSI trio RTX 3090, i9 12900 KS).

[Switch_off]

Hi. Same problem here. My problem is when I launch the game, show the loading screen then crashes and throws me back in Steam. Other VR games run fine however

(win 10, ram 24 GB DDR4, 2060 RTX 6gb, i7 12700F)

[full flaps]

Same here. Although I never played the game on my old computer.
Windows 11, DDR5, RTX 3080. i9. Valve Index.

[Sunydaze]

I was running on my old WIN10 system using Oculus Rift until video/power failed.
I went to new system on Win11, now I can't play. It starts, I see spash screen a few seconds, then it goes away like it played and ended.
I am able to play other Steam and Oculus games. For note, I also have one Oculus game that seems to do the same (Dead and Buried, old West shooting). So for me not just Smashbox and Steam...
Win11, Nvidia 1070, Oculus

[N1gh7w1ng [ZS]]

Same Problem.
Win 11, DDR4, RTX 3070, I5-13gen, Meta quest 2

[LeftyLovesHuskies]

I have 600 hours playing, got a new Windows 11 PC and Smashbox is the only game that will not open. Did anyone ever solve this issue?

[Marvin42]

Hey there just found and posted a thread the solution, you can fix it as follows:

apparently there is an issue with an SSL encryption library used for comms, and the solution is to add the following to the steam launch options (right click on Smashbox Arena in your library, go to launch options): cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"

You can add other flags after the %command% and before the " (like =noai).

Hope this helps.

[Marvin42]

Better solution with no hiccup/pauses: take back out the steam command line, instead use the following suggestion. Bring up a command prompt, type "setx OPENSSL_ia32cap :~0x20000000", hit return. This will set a permanent environment variable. You will need to restart your computer for it to take effect. This prevents the priority/lag issues from the command window that pops up from Steam and it works fine for me. Remember to keep any of your game specific flags in place. Source: https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/openssl-sha-crash-bug-requires-application-update.html

[Sunydaze]

Thanks to Marvin42 I got Smashbox to play. In the main discussion forum he has posted an item "getting Smashbox to run on Intel gen 11/12 systems.... I was able to use the reddit link to Smite comments and set an environment variable in Win 11. Then I was able to run Smashbox for the first time in months.