Beat Saber Crashes to Desktop upon starting

[Ascyndaeon]

Hey guys, I've been trying to figure this out for the past few hours and no amount of advice via others' discussions or "solutions" have helped.
I've tried quite a few times uninstalling/reinstalling beat saber, even deleting the appdata folder and steamapps/common/beat saber. Even have tried reinstalling frickin' steamvr a few times. Nothing. Even so far as doing -vrmode oculus and stuff to skip steamvr altogether.
All I get is splash screen, a couple seconds of an hourglass, then CTD.
In the Appdata/locallow/hyperbolic magnetism/beat saber folder there is no "output_log.txt", there is only Player.log and Player-prev.log so idk how to dump some diagnostics on you to get help, I'm just at the end of my rope and ready to refund...

as for specs... I have
Nvidia GTX 960 w/ 4gb gddr5
AMD Ryzen 3700X
16 gb of ram...
And I guess headset I'm using is Quest 2 through either oculus link or virtual desktop, but idk how that can be the problem. Though for the record I've also reinstalled oculus as well just in case it was and still nothing.

It should work, as I've been able to run other games like vrc, neos, and phasmophobia just fine...though I will note that phasmophobia I'm also having issues of crashing now for some reason when a house level is being loaded so idk what's going on.
All my drivers, software, firmware, etc. are ALL up to date, so there's no possible way that could be an issue.
Please help...I don't know what else to do...

[Angry Russian]

Where your Beat Saber folder is located? What you describe can be related to problems of Unity to read the game data. Could be due to Windows user account rights given to game folder or rights given to steam. Try moving the folder to let's say D:\Beat Saber and run from there. Also try running both steam and the game with admin rights.

Phasmophobia is also built on Unity, so the issues can be related to how your PC handles this engine.

[Ascyndaeon]

Originally posted by Angry Russian:

Where your Beat Saber folder is located? What you describe can be related to problems of Unity to read the game data. Could be due to Windows user account rights given to game folder or rights given to steam. Try moving the folder to let's say D:\Beat Saber and run from there. Also try running both steam and the game with admin rights.

Phasmophobia is also built on Unity, so the issues can be related to how your PC handles this engine.

Hmm okay, that's also something I haven't tried yet, perhaps reinstalling unity stuff would do it. I shall try, thanks.
But as far as where it's installed, I first had it installed on my other drive (in this case E:\) and then figured maybe installing it to C:\ might have done it but still no.
But I can try the admin rights thing too

Either way, I mean...I will say everything seemed to work nearly flawlessly before I installed the new mobo/cpu/ram cuz I used to have an i7 3770k in it, and maybe we're having problems because things were installed with intel drivers in mind and now I need each app to have amd driver support? I'm not sure but I'd have thought simply installing amd drivers and uninstalling intel ones would suffice xwx\

[Ascyndaeon]

Originally posted by Angry Russian:

Where your Beat Saber folder is located? What you describe can be related to problems of Unity to read the game data. Could be due to Windows user account rights given to game folder or rights given to steam. Try moving the folder to let's say D:\Beat Saber and run from there. Also try running both steam and the game with admin rights.

Phasmophobia is also built on Unity, so the issues can be related to how your PC handles this engine.

So I reinstalled the game in D:\Games\SteamLibrary\steamapps\common\Beat saber, and tried launching both steam and the game as admin, with and without -vrmode parameters/arguments, still nothing. It goes on a little bit longer, before completely crashing.
I will note that in the hyperbolic appdata folder there's a few more files but still no "output_log". There's "player.log", playerdata.dat, player-prev.log, and settings.cfg, and a couple .bak files of playerdata and settings.
Still doesn't work.
(I also reinstalled unity stuff but idk if there's other unity drivers idk how to uninstall and reinstall, I can't figure that out.)

[Ascyndaeon]

I will note too, now that the settings file is there, I tried to lower the settings to the lowest in GeForce Experience to see if it is the graphics but, still doesn't do it.

[Angry Russian]

Sorry, but I meant move the folder away from steam library, like d:\beat saber and run it from exe. This way you get rid of potential steam vs unity issues.

[Ascyndaeon]

Wait, you can do that? I would have thought doing something like that in and of itself would cause problems :thinking:
Okay, I can try that too though

[Ascyndaeon]

Regardless, I just tried with fresh install, put in where you suggested, still CTD :(

[Angry Russian]

RIP

Can you post here your settings.cfg?

[Ascyndaeon]

Alright, I can do that sure. But I'll also note I didn't change it again to lowest settings after reinstalling the game again so it's the default settings
So here, settings.cfg:

{"version":"1.6.1","windowResolutionWidth":1280,"windowResolutionHeight":720,"windowMode":1,"vrResolutionScale":1.0,"menuVRResolutionScaleMultiplier":1.0,"useFixedFoveatedRenderingDuringGameplay":false,"antiAliasingLevel":2,"mirrorGraphicsSettings":2,"mainEffectGraphicsSettings":1,"bloomGraphicsSettings":0,"smokeGraphicsSettings":1,"burnMarkTrailsEnabled":true,"screenDisplacementEffectsEnabled":true,"roomCenterX":0.0,"roomCenterY":0.0,"roomCenterZ":0.0,"roomRotation":0.0,"controllerPositionX":0.0,"controllerPositionY":0.0,"controllerPositionZ":0.0,"controllerRotationX":0.0,"controllerRotationY":0.0,"controllerRotationZ":0.0,"smoothCameraEnabled":0,"smoothCameraFieldOfView":70.0,"smoothCameraThirdPersonPositionX":0.0,"smoothCameraThirdPersonPositionY":1.5,"smoothCameraThirdPersonPositionZ":-1.5,"smoothCameraThirdPersonEulerAnglesX":0.0,"smoothCameraThirdPersonEulerAnglesY":0.0,"smoothCameraThirdPersonEulerAnglesZ":0.0,"smoothCameraThirdPersonEnabled":0,"smoothCameraRotationSmooth":4.0,"smoothCameraPositionSmooth":4.0,"useCustomServerEnvironment":false,"customServerHostName":"","volume":1.0,"ambientVolumeScale":0.800000011920929,"controllersRumbleEnabled":true,"enableAlphaFeatures":0,"pauseButtonPressDurationLevel":0,"maxShockwaveParticles":1,"overrideAudioLatency":false,"audioLatency":0.0,"maxNumberOfCutSoundEffects":24,"onlineServicesEnabled":false,"oculusMRCEnabled":false,"openVrThreadedHaptics":false,"languageSettings":0}

[Angry Russian]

Technically GTX 960 is unsupported, but it seems you make it work somehow with other apps.. Did you try to lower the settings of link in Oculus Debug Tool?

Try maybe setting "vrResolutionScale":0.5 just to run it. Also disable antialiasing, smoke etc.

[Angry Russian]

So try this:
{"version":"1.6.1","windowResolutionWidth":1280,"windowResolutionHeight":720,"windowMode":1,"vrResolutionScale":0.5,"menuVRResolutionScaleMultiplier":1.0,"useFixedFoveatedRenderingDuringGameplay":false,"antiAliasingLevel":0,"mirrorGraphicsSettings":0,"mainEffectGraphicsSettings":1,"bloomGraphicsSettings":0,"smokeGraphicsSettings":0,"burnMarkTrailsEnabled":false,"screenDisplacementEffectsEnabled":false,"roomCenterX":0.0,"roomCenterY":0.0,"roomCenterZ":0.0,"roomRotation":0.0,"controllerPositionX":0.0,"controllerPositionY":0.0,"controllerPositionZ":0.0,"controllerRotationX":0.0,"controllerRotationY":0.0,"controllerRotationZ":0.0,"smoothCameraEnabled":0,"smoothCameraFieldOfView":70.0,"smoothCameraThirdPersonPositionX":0.0,"smoothCameraThirdPersonPositionY":1.5,"smoothCameraThirdPersonPositionZ":-1.5,"smoothCameraThirdPersonEulerAnglesX":0.0,"smoothCameraThirdPersonEulerAnglesY":0.0,"smoothCameraThirdPersonEulerAnglesZ":0.0,"smoothCameraThirdPersonEnabled":0,"smoothCameraRotationSmooth":4.0,"smoothCameraPositionSmooth":4.0,"useCustomServerEnvironment":false,"customServerHostName":"","volume":1.0,"ambientVolumeScale":0.800000011920929,"controllersRumbleEnabled":true,"enableAlphaFeatures":0,"pauseButtonPressDurationLevel":0,"maxShockwaveParticles":1,"overrideAudioLatency":false,"audioLatency":0.0,"maxNumberOfCutSoundEffects":24,"onlineServicesEnabled":false,"oculusMRCEnabled":false,"openVrThreadedHaptics":false,"languageSettings":0}

In link settings of ODT set bitrate to 100 and encode resolution width to 2016. For more comfort I'd suggest using Oculus Tray tool software so settings don't get reset all the time.

[Ascyndaeon]

Okay so, I tried all that, even reinstalled the Nvidia drivers to see if it could be that because a friend suggested it after Hunt showdown crashed for me a couple times when we were playing. Even with all that, the lower settings and all you suggested, still CTDs. The only difference being the config and I guess the bitrate being at 100 (before I had it set to 400 after watching a video about setting it etc, already had the width at 2016 because of it)

I also took longer to reply because I wanted to know I wasn't crazy, and decided to try a few more VR apps worked. Chillout VR worked, Job Simulator worked, Detached worked...I know technically according to oculus/nvidia/etc the recommended is indeed 970 and above, and yet Beat Saber's store page suggests you can run it at minimum on the 960 apparently. And there's even a video of someone on youtube playing Beat Saber on a 960 with seemingly normal settings so...I would think it ought to work? especially with such gimped settings (heck nvidia suggests higher anti-aliasing compared to the default settings of BS; x4 as opposed to x2)
Just why won't this work, I don't understand :c

[Angry Russian]

Originally posted by Ascyndaeon:

Okay so, I tried all that, even reinstalled the Nvidia drivers to see if it could be that because a friend suggested it after Hunt showdown crashed for me a couple times when we were playing. Even with all that, the lower settings and all you suggested, still CTDs. The only difference being the config and I guess the bitrate being at 100 (before I had it set to 400 after watching a video about setting it etc, already had the width at 2016 because of it)

I also took longer to reply because I wanted to know I wasn't crazy, and decided to try a few more VR apps worked. Chillout VR worked, Job Simulator worked, Detached worked...I know technically according to oculus/nvidia/etc the recommended is indeed 970 and above, and yet Beat Saber's store page suggests you can run it at minimum on the 960 apparently. And there's even a video of someone on youtube playing Beat Saber on a 960 with seemingly normal settings so...I would think it ought to work? especially with such gimped settings (heck nvidia suggests higher anti-aliasing compared to the default settings of BS; x4 as opposed to x2)
Just why won't this work, I don't understand :c

Yeah mate don't know what else to suggest. Something could be borked with you windows after upgrade, but don't want to be the a$$ to suggest you windows reinstall for this..

Does the game start at all at desktop mode? Try FPFC mode (add fpfc to launch parameters).

[Ascyndaeon]

Originally posted by Angry Russian:

Does the game start at all at desktop mode? Try FPFC mode (add fpfc to launch parameters).

I appreciate you at least trying to help with anything short of reinstalling windows, but I wonder if that's what I'm going to have to do at this point... why windows do you suck with cpu upgrades

Hmm, I just tried that and yeah I guess not. Even in FPFC/desktop-only mode it still CTDs :c

[Angry Russian]

Originally posted by Ascyndaeon:

Originally posted by Angry Russian:

Does the game start at all at desktop mode? Try FPFC mode (add fpfc to launch parameters).

I appreciate you at least trying to help with anything short of reinstalling windows, but I wonder if that's what I'm going to have to do at this point... why windows do you suck with cpu upgrades :fsad:

Hmm, I just tried that and yeah I guess not. Even in FPFC/desktop-only mode it still CTDs :c

So then I bet it's not related to VR at all, just to your PC vs Unity stuff, something is really broken here. Maybe reinstalling some VC redists and DirectX will help, but I doubt it honestly.