Currently the leniency is way too large and needs to be reduced to at least half of what it currently is (70ms to 35ms). Above around 40-50ms is way too large and gives too much time for misfretting and removes the skill of strumming and fretting accurately and correctly. In my opinion, 20-30ms of leniency would be ideal, and gives plenty of leniency for not strumming exactly on time
#strum leniency is way too large
42 messages · Page 1 of 1 (latest)
at first thought, my mind says that might be a little small, for perspective 33 ms is only 2 frames at 60 FPS
but only way to know for sure is to try it
i guess the current of 70 is just a little more than 4 frames lol
I was messing with the strum leniency numbers when i was making my custom timing judgement system, and 35ms felt like a nice middle ground
2 frames sounds like not a lot of time, but it’s actually a decent amount of time
Because if you strum off time from your fretting, it’s usually very close to being on time
I've already made a commit today which does the following:
- Reduce hit window size from 160ms to 150ms
- Change strum leniency from 70ms to 60ms
- Change the strum leniency when no notes are in the window from 35ms to 25ms
Next patch will release with those values and we can see how that feels
If it requires more changes, then we can change
But I don't want to cut it in half immediately
I guess thats fair
The 150ms feels a lot harder than 160
Makes it a lot easier to miss by fretting early on hopos
If you have unity installed you can checkout the rewrite branch and play it for yourself in editor
I still think 60ms is wayyyy too large for strum leniency but ill try out the build and let you know
Bear in mind for more casual players I don't want it to be completely unforgiving
I want the default engine to be approachable for anyone but still provide a decent challenge
Even keeping casuals in mind i think 35 is a really good middle ground
We'll have to see how other people respond to the changes
I'm not sure when we'll be releasing a patch next, but it'll probably be in the next few days if I'd have to guess
just need to fix a few things
tried out the new engine for a bit, still think the leniency is a lot larger than it should be @timid belfry
should fr be like 30-40 ms
its literally as loose as CH strum notes are
it needs to be much smaller
I'll lower it to 50 for the next build
better to go down in smaller increments rather than a large jump
there may be other issues at play but i personally feel like it might be a little tight, there are a number of cases where it feels like i should have hit a strum note but it just misses
though this also happens with multiple strum notes of the same frets in a row on occasion, not sure what's up with that
Agreed with Drumbs, honestly feels pretty tight as is
I super don’t agree i think its too loose in the alpha 3 build
But i mean thats just my opinion
The problem with having the strum leniency similar to CH is that it affects top level gameplay
It takes a lot less precision to hit crazy all strums stuff and therefore makes you have to make the nps really high before things actually become difficult
and it kinda becomes a test of who can strum fast for a long period of time
Instead of actually taking the precision to hit the notes accurately
@noble pulsar @compact timber Hope you don't mind the pings but what do you guys think about the strum leniency right now? Currently in a3 it's 60ms. Do yall think it should be lower (and if so, how much) or its fine where it is?
would there be any way to make settings for different leniencies just for testing?
We could put it in a non-released build just for testing purposes, but we plan to have an engine customiser soon enough anyway. Just needs the UI making for it
i haven't got a chance to really put that skillset through the ringer on yarg yet, but from what I played it felt fair. if anything it could probably be a bit smaller, like 50ms
Will an engine customiser allow for us to change the leniency (or would it fix the following...)? The issue I have is that I prefer to strum on some HOPOs/Taps, however doing that on the new engine means I end up with far too many overstrums, which makes it almost unusable for my skill level. (I'd much prefer to use new over stable as it fixes the issue with some custom songs being way out of sync). I can use all strums on certain songs, but once I play a song with solos, I'm screwed either way.