Had issues with hits not registering. Turned out Beat Saber now lags after v1.0 update (clean install).

[s810]

This may not fix it for everyone, but I've noticed since the v1.0 update many hit blocks wouldn't register.

I turned down my pixel density from 1.8 to 1.0 and the game runs fine now- seems to register everything as before. (I've had it on 1.8 for almost all 60 hours of playtime previously). Keep in mind, it doesn't really LOOK/feel like it's lagging until you really look for it.

In short, the game now lags where it otherwise didn't.

Hope the developer sees this, and they optimize a few things.

And hope this helps some of you.

This was the case with a Rift S, and a Rift CV1. I have three identical computers I've tested with. Took me a while to figure out if it was an S issue or me losing my mind- now it's clear it's a BeatSaber issue, and only after this update.

[Silver Dragon]

My son sees this problem too. He calls is stutter where he can see the blocks no moving smoothly.

[empireboy2000]

Check if you accidentally set the program specific super sampling too high in steamvr settings. Also check the super sampling settings in Beatsaber too.

[s810]

Originally posted by empireboy2000:

Check if you accidentally set the program specific super sampling too high in steamvr settings. Also check the super sampling settings in Beatsaber too.

I appreciate the response, but they're still defaults (AA in BS is actually lowered than before lol)

[empireboy2000]

Originally posted by SKURKVonn64 (Sometimes):

Originally posted by empireboy2000:

Check if you accidentally set the program specific super sampling too high in steamvr settings. Also check the super sampling settings in Beatsaber too.

I appreciate the response, but they're still defaults (AA in BS is actually lowered than before lol)

Can u ask your question in the support channel here https://discord.gg/beatsabermods

[s810]

Originally posted by empireboy2000:

Originally posted by SKURKVonn64 (Sometimes):

I appreciate the response, but they're still defaults (AA in BS is actually lowered than before lol)

Can u ask your question in the support channel here https://discord.gg/beatsabermods

Not a question, and this has nothing to do with any mods.. I'm just saying that the stock v1.0 release lags more than the versions before it, and that "lag" (while virtually impossible to perceive) affects note/block hits in a negative way (missed blocks).

[BulletApe]

I've had hits not registering from V1.0 on the Oculus version. Haven't been able to pin blame to beat saber yet but usually one or more missed notes per song. It's now rare I can get thru a song without a ghost hit before the end.

The misses are too inconsistent to be tracking errors. They can happen on either controller, left or right. They don't seem to be linked to only particularly fast strikes or from just a certain area. You randomly just ghost thru a cube during a song, sometimes a couple. Makes it all a bit crappy.

I'd like to be able to retry on previous version but can't do that on Oculus store. Doesn't seem to be a problem loads of folk are complaining about either. So I still cant rule out a controller issue that just happened to occur about the same time 1.0 happened.

[krylke]

This is still happening for me. It's so bad I can't even play the game anymore :-(

Edit:
1. Deleted Beat saber completely including all mods.
2. Reinstalled Beat saber and my usual mods and now it seems to work again.

My guess is that some old outdated mod was messing with the game.

[⎛⎝ casedistorted™ ⎠⎞]

I am having this issue where my saber goes straight through the middle of a block that is very easy to hit. This only started happening AFTER the latest Skrillex patch, I never had it happen beforehand. I have uninstalled any mods and reinstalled the game completely, redid my sensor tracking, replaced the batteries in my touch controllers, anything I can think of and it hasn't fixed the issue.

[Angry Russian]

Originally posted by ≈✨TheFamousChrisA™✨💖:

I am having this issue where my saber goes straight through the middle of a block that is very easy to hit. This only started happening AFTER the latest Skrillex patch, I never had it happen beforehand. I have uninstalled any mods and reinstalled the game completely, redid my sensor tracking, replaced the batteries in my touch controllers, anything I can think of and it hasn't fixed the issue.

Replying in 2019 thread, right? ;)

Anyway, this thing could be related to:
1) Mods leftovers. Yeah, I can read that you've tried that, but just to be sure start with completely empty game folder, not just uninstalling and reinstalling through steam. Typically this happens with mods like Slice visualizer, Custom Sabers, HSV or anything else what touches scoring functions. Maybe also backup and clean up your \AppData\LocalLow\Hyperbolic Magnetism\Beat Saber
2) Try using FPS counter mod and see whether you have frame drops at the moments you miss. You can also use some monitoring software like MSI Afterburner which can write the logs of FPS and GPU/CPU load.
3) Search for a garbage collection fix, it's literally one line in game's boot.config. I have a beast of a PC and only with this fix I get completely smooth experience.
4) On CV1 you must play with -vrmode oculus launch parameter, otherwise you'll really lose on tracking a lot. Generally never use steamvr with Oculus unless it's completely unavoidable..

If this doesn't help try recording through OBS or something with FPS counter and show it, it will help to investigate further.

[Neawoulf]

About that launch parameter for Oculus headsets: Maybe it's just me, but with "-vrmode oculus" this game is completely unplayable (extremely laggy!), and i'm using a Rift S.

SteamVR runs a lot better, but with the occasional hits not registering.

[Angry Russian]

Originally posted by Neawoulf:

About that launch parameter for Oculus headsets: Maybe it's just me, but with "-vrmode oculus" this game is completely unplayable (extremely laggy!), and i'm using a Rift S.

SteamVR runs a lot better, but with the occasional hits not registering.

That should not be the case, in fact it should be the opposite. I'm just guessing that you might have something messed up in super sampling settings in oculus debug tool. Basically when you run through steam it applies it's own pixel density/super sampling multiplier on top of the Oculus one, so maybe that's your case? Just check oculus debug tool and make sure pixel density is set to 0 or 1.0, AND when you run the game with -vrmode oculus you have pixel density set to 1.0 in the game settings.

If that's not the case can you elaborate on what exactly is going on, like does the game occasionally stutter or just constantly on low fps, and what fps exactly we are talking here about?

[Neawoulf]

Originally posted by Angry Russian:

Originally posted by Neawoulf:

About that launch parameter for Oculus headsets: Maybe it's just me, but with "-vrmode oculus" this game is completely unplayable (extremely laggy!), and i'm using a Rift S.

SteamVR runs a lot better, but with the occasional hits not registering.

That should not be the case, in fact it should be the opposite. I'm just guessing that you might have something messed up in super sampling settings in oculus debug tool. Basically when you run through steam it applies it's own pixel density/super sampling multiplier on top of the Oculus one, so maybe that's your case? Just check oculus debug tool and make sure pixel density is set to 0 or 1.0, AND when you run the game with -vrmode oculus you have pixel density set to 1.0 in the game settings.

If that's not the case can you elaborate on what exactly is going on, like does the game occasionally stutter or just constantly on low fps, and what fps exactly we are talking here about?

In my case it's not a framerate issue. It's physics, tracking, laggy force feedback etc. It just all feels very off and laggy, but not graphically.

[Angry Russian]

Originally posted by Neawoulf:

Originally posted by Angry Russian:

That should not be the case, in fact it should be the opposite. I'm just guessing that you might have something messed up in super sampling settings in oculus debug tool. Basically when you run through steam it applies it's own pixel density/super sampling multiplier on top of the Oculus one, so maybe that's your case? Just check oculus debug tool and make sure pixel density is set to 0 or 1.0, AND when you run the game with -vrmode oculus you have pixel density set to 1.0 in the game settings.

If that's not the case can you elaborate on what exactly is going on, like does the game occasionally stutter or just constantly on low fps, and what fps exactly we are talking here about?

In my case it's not a framerate issue. It's physics, tracking, laggy force feedback etc. It just all feels very off and laggy, but not graphically.

How do you monitor the FPS exactly? Because what you have is possible to observe with ASW on too.. it may seem smooth but everything is quite wrong when you are locked on half of refresh rate and the headset is just in motion smoothing mode.