Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Very true in 100% cases until now. Everyone complaining that it's not the case for some reason can't show proof, although recording is indeed very easy. One comment here though, don't rely on replay feature of scoresaber, it creates false misses sometimes in the recording, so you need to record actual gameplay.
one thing I've been noticing that was particularly bad today is that my blade will randomly turn off. reading up on it, it sounds like the battery can sometimes come loose. supposedly you can use a rubberband to fix that
I swung at a red today and missed, but then when I brought up my left hand, the sword wasn't there, I had to shake the controller to get my sword to turn back on. battery power reads fine for both controllers, but I've had both disappear on me today.
sometimes I swing too early on blocks far to the side because I rely on my peripheral vision, but I can see the block just out of reach of my blade.
For timing issues I highly recommend trying njsfixer mod, this way you can optimize note spawn distance (what devs call offset) based on map note jump speed. You will find the values which will feel natural to you. I'd suggest starting with NSD=NJS and go from there. Overall I feel like the lower NSD the easier is to follow the rythm, but more difficult to read patterns.
Also you can try smaller notes (start with 80%, then after a month try 60-70% sized), they help to read patterns and hit more accurately, and this at the end will also help with timing. Hitboxes remain the same, so they'll change only visually. I think Duhhello still have such notes in his discord as he is using them a lot, but if you can't find them just let me know and I'll post them somewhere.
HOWEVER
There is some evidence that there actually is some sort of issue with the game or maybe the hardware. Like, there are times where I swear I see the saber actually go through a block but it doesn't register. These are almost always in my peripheral vision so I can't exactly be sure, but there have been times where I'll swing at a line of blocks all in the same direction (so three red "^" blocks, for instance) and will somehow miss the first one but hit the other two? Seems pretty suspicious to me, could maybe be lag since I'm pretty sure my timing is fine...I have yet to actually record any gameplay to confirm, but if it IS lag wouldn't it just be recorded as swinging too late and missing...?
Anyway, following to see if any solutions pop up.
What you describe can happen in bad tracking cases. What headset do you use? When you will record your plays you will see what exactly is happening. It indeed could be a false rotation or saber just teleporting somewhere. Beat Saber is the ultimate tracking test actually.
I use a Quest 2, and it could easily be a tracking issue, as I have definitely noticed the controller "cursers" just kind of teleporting above my head sometimes if they're held off to the side, so it's certainly possible that they're just out of view of the sensors or something.
Is there a fix for that? I seem to remember there were, like, boxes you could buy and set up around the play area that aid in tracking, though I haven't looked into that at all yet =S
https://steamcommunity.com/sharedfiles/filedetails/?id=2385116062
This is how I hold the controller, this allows me to swing up and down by moving palm up and down and not sideways like with normal grip, so you don't need to swing arms too much thus loose the tracking. Also this moves center of mass inside my hand, making swinging easier for my wrist joints. Strap over thumb helps to pull controller inside my hand in case I relax my pinky and ring fingers.
Obviously this requires controller settings adjustment to make the saber point in the right direction, but that is another big topic. You can also check out claw grip or palm grip, there are plenty of images for Quest 1, and they are the same for Quest 2.
I've had blocks go through me, blocks on the right side seem to have the most issues, including blocks higher up. I've had issues where it's 3 blocks together and I miss the middle one but hit the first and third... I've not played as much anymore as it got so frustrating.
But what's the point of recording it as we can't really send it to the developers who can actually do something about it?
When you were recording you are sure that ASW or something like that were not building fake frames for you? It's easy to check when you record with performance overlay on or fps counter plugin. Was that an actual gameplay recording or you were watching/recording a scoresaber replay?
I'm just saying that noone till now was able to show this on a valid replay, don't you find this strange?