Hitbox Issue - Saber goes through Blocks (with Video) - What can I do?

[HitrapperAndArtistDaBaby]

Hello!

Since I got my new PC with a new VR-Headset, I have the issue that the Saber goes through Blocks even though I hit the Blocks.

In the Video you can see that sometimes the blue Saber goes through Blocks even I don't move the Saber.
When I normaly play this happens with the left Saber too (I used the right Saber only for this Video to see exactly what happens).

Sometimes the Saber goes through the Block and sometimes it cuts it even the Saber is on the SAME Position.

I googled a bit and found this: https://bsmg.wiki/grips-and-tricks.html#ranking-up-mega-tutorial
The Hitboxes are much bigger than the Blocks, is this so? So why goes the Saber sometimes through the Blocks?

Video: https://youtu.be/vVLPe6hZeIU (i made this Video a few days ago but nothing changed with the new Patch)

My PC:
i7 10700k (non-oc)
32GB 3200Mhz RAM
GTX 1080 Ti
The Game an Steam are installed on a SSD
Valve Index with Base Station 2.0 and Knuckle Controllers

I have the PC one and a half week now

What I tried:

-Clean-Installed Windows 10 and the newest Drivers (MB, Graphicscard, etc) two times
-Re-Installed Beat Saber and SteamVR
-Re-Installed Valve Index
-Tried Beat Saber without Mods (I only use the Standard Mods for Custom Songs from Mod Assistant)
-Tried several USB Ports (USB 3.0 and USB 3.1 Gen2)
-Deactivate "Allow the computer to turn off this device to save power" for every USB-Hub
-Deactivate in the Power Management Options the "USB selective suspend" feature
-Turn off "Smooth Motion" in Steam VR
-Turn on "Smooth Motion" in SteamVR
-Set the SS in SteamVR to 1.0
-Set the Resolution in SteamVR to Automatic
-Set the Hz to 80/90/120/144

fpsVR shows me ingame 2-3 ms all the time (80Hz). There are no Frametimepeaks. The Game run smooth all the time even when the Saber goes through the Blocks. No Frametimepeaks befor or after that.
Temps from CPU and Graphicscard are Ok
CPU-Usage is Ok
RAM-Usage is Ok

Nothing in the Room reflects the Lasers from the Base Stations. The tracking works without any issues in every game, even in Beat Saber. No Jiggling or something like that. Both Sabers works perfect and smooth.
Only the Hitboxes in the Game (Sabers AND Blocks) don't work as they should....

With my old PC and VR-Headset (i7 4790, 16GB RAM, GTX 1080 Ti, Rift-S) I didn't had this Issue or I didn't notice it...

This bothers me so much that I'm losing the interest to play this Game =/

What else can I do to solve this Issue?

Thank you for your Support.
Best regards

[HitrapperAndArtistDaBaby]

Push

This Problem was Pre-Multiplayerpatch and it's still happen.

Can a Developer explain this strange issue to me? Why does the Saber sometimes go through Blocks without cutting them even the Saber isn't moving?

[Neawoulf]

Can confirm things like that happens "a lot" to me (about 0.5 to 1% of all strikes):

- When i'm sometimes hitting two blocks parallel i can clearly see both sabers are hitting their block. One hit counts and gives rumble, the other doesn't.
- From time to time i hit a block but i don't get any rumble in the controller. A second later (when the block is already gone) i get the rumble and the hit counts.
- Rarely i'm 100% sure i missed a block but it still counts as a hit a second later.
- Sometimes i clearly miss a block and i still get a hit sound and rumble, but the hit doesn't count.

There's definitely something weird going on with the hit detection. Hope this will get fixed soon. Right now Beat Saber is a great game for workout, but hunting for points is not really worth it and can be quite frustrating.

Oculus ASW is always disabled, tried both SteamVR and Oculus. For testing purposes i reduced the graphics quality to minimum, but it doesn't make a change. Also it feels like the longer i play the worse the issue gets. First one or two rounds feel okay, then the weird events start to happen.

And i don't think it's a tracking error because this happens a lot while i see the sabers move the way i move my hands without any visual stutters, tracking gitches etc.

My system: Windows 10, Ryzen 3600X, 32 GB Ram, RTX 2080, Oculus Rift S

[HitrapperAndArtistDaBaby]

Yeah, it's definitely not a tracking Problem or a laggy Game. You can see in my Video that the Saber is not jittering or lagging or something like that. I have no Frametimepeaks or dropped Frames. A friend of mine has the same Problem.

[shauniedarko]

This has been a problem for quite some time. The devs simply don't care. They've got Facebook money now. If you can even get the devs to reply, they gaslight players telling them it has to be lag or tracking or the player's computer, but the simple fact is that there's a problem with the game that they refuse to acknowledge. It's at the point where I just play with the HUD off so I can't see the misses, and put the game on No Fail so that it's not really keeping score because it's just too frustrating otherwise.

[m1x]

Yes, there is definitely a problem. Not often, but you can see how the saber either just passes through the block and does not count at all (miss), or the blow passes with a significant visual delay and a small number of points. Although the blow is executed perfectly. On the non-multiplayer version, everything is fine both before and now.

My configuration: Windows 10, i9 9900k, 32GB RAM, RTX 2070S, WMR, Steam app

[HitrapperAndArtistDaBaby]

I had the Problem even before the Multiplayerpatch. The video I made is 1 week before the Multiplayerpatch was released.

But yeah. In some Threads from the past about this problem the devs only said that they couldn't reproduce the issues...

[Manicka111]

The video does not tell anything. The combo counter stays 0 because you hit nothing. Debris is sseparated from hit detection, same with hit sounds, these are buffered so might play even when you miss.

[HitrapperAndArtistDaBaby]

What do you mean? The Saber stands still and sometimes the Blocks will be cut if it the Saber touch it and sometimes not. Explain this to me please.

You can clearly see that the right Saber sometimes go DIRECTLY THROUGH Blocks (in the Slow Motion Parts).

[Marcyan]

This happens to me a lot, so I am often not even able to get close to my own highscores. It was not a problem before the time they changed the menu-graphics and stuff. How can it be that it cannot even be reproduced by the developers?

[Evilplay]

I have the issue often, i actually quit playing & mapping beat saber for the fact is i can no longer hit boxes properly anymore. It's got more worse the more updates been added. I'm only able to do some expert maps at best & wanted to get better though what chance do i or anyone else have with things like this going on. I just tried mapping again in editor & tested hitting single blocks slow & i hit them, block breaks though it says i missed.... i consider beat saber a unplayable broken game until this issue sorted and like many have said... the devs don't care.

[Lonegnr]

This deserves so much more attention. Have you posted this anywhere else?

[Neawoulf]

Hope the devs see this. I've just played a bit, started a new song on expert (but blocks weren't moving too fast) and almost all the hits in the first 20 seconds were misses, even though i'm sure i've hit most of them. I restarted the song and suddenly it worked as intended and all the misses from before were hits.

There's definitely something weird with the hit detection going on. Maybe the framerate of the graphics and the physics are sometimes slightly out off sync?

[HitrapperAndArtistDaBaby]

No, I posted this only in the Steam Forum.

[Any time other than Friday]

i have started seeing this exclusively since the new multiplayer update, use to be able to do like custom songs on expert pluss, not i am failing the pre installed ones on hard i have a feeling its to do with new colision rules or something like they might have changed it so that you need to go though at a different speed than befor or something idk.

[Angry Russian]

Something maybe wrong with cut plane calculation here, especially when saber is standing still or moving in a strange way (like piercing instead of swinging).Try to record all your actual plays with OBS (there is a mod which automatically starts recording of each song) and camera+ mod and see what exactly is happening, hope you catch it. Till now nobody was able to present such evidence, unfortunately.

Personally I can't say I've experienced anything like this as all my misses were my fault or tracking which I confirmed by OBS, but lots of people indeed complaining about this, so this could very well be true.