Paralysekid Mar 1 @ 3:11pm
For people who have trouble hitting the buttons
Have you tried this:
Originally posted by Epsi:
From my experience, most people complaining about hitbox accuracy are actually suffering from low frame rate due to the GPU not being strong enough. My plan for a future patch is to warn players if unstable framerate is detected and suggest to turn off post-processing to aleviate the issue.

Because before that I couldn't hit anything, it didn't react in time and I had to hit teh right button like 5 meters before the actual arrow/bubble, but now it runs perfectly, maybe this will help some of you too
Showing 1-15 of 35 comments
< >
How2 Mar 1 @ 6:14pm 
Yes i had a similar issue with my laptop having both an integrated and dedicaded graphic card, it would not realise that it needed to switch to my dedicaded card and had to be manually changed in the Nvidia settings to run on the dedicaded card.
himmatsj Mar 1 @ 7:26pm 
Not true. I always was hitting 60fps, and even upgraded to a GTX 750 and the hit detection is not as forgiving as other games. Very often I get an "error" even though I am certain I hit on beat.
zertap Mar 3 @ 6:06am 
Funny, I just tried disabling the vsync (which is actually just a 60fps framelimit in windowed mode, which I'm playing in). I got about 2000 fps with my gtx 770.

Suddenly I couldn't hit almost anything, as if there would be massive input lag or the game would be judging way harsher. So, in another words: "the low fps issue" but in my case "too much fps issue"
Paralysekid Mar 3 @ 6:07am 
Haha wow, this game does crazy things
zertap Mar 3 @ 6:10am 
Originally posted by Epsi:
From my experience, most people complaining about hitbox accuracy are actually suffering from low frame rate due to the GPU not being strong enough. My plan for a future patch is to warn players if unstable framerate is detected and suggest to turn off post-processing to aleviate the issue.
I guess it is kinda unstable if it is going around 2000 with a margin of a hundred or two fps.
Last edited by zertap; Mar 3 @ 6:11am
Loïc  [developer] Mar 3 @ 6:14am 
Could you please press F1 and see if you press at the right moment? (the red bar should be above the colored flatline on the ground, representing the hitbox).
Also does the game work correctly in AUTOPLAY at 2000FPS?
zertap Mar 3 @ 6:39am 
Seems like it is a little less than a thousand while playing(menus are 2000-3000fps). Autoplay works fine.

I'm pretty sure I'm hitting on the right time. Since I don't trust myself 100% on this, I asked my friend to test that too. Seems like he was able to play fine with 600~FPS. I don't know, there may be other factors affecting this too. Like the fps doing something to the visuals etc. I can't say for sure myself so I'd need some more ppl to try this.
Last edited by zertap; Mar 3 @ 6:39am
zertap Mar 3 @ 6:49am 
Difference in performance(2 plays right after each another), I'd say something is breaking it for me :/ :

http://steamcommunity.com/id/zertap/screenshot/595903887456622683
http://steamcommunity.com/id/zertap/screenshot/595903887456627728
Loïc  [developer] Mar 3 @ 6:51am 
Can you try to press F1 while in game to activate beat debug draw mode?
That should give you an indication if you're above the beat hitbox. If you press the button while above the hitbox and it doesn't register it, let me know please.
MDuh Mar 3 @ 7:04am 
told ya epsi, something is weird on unlocked fps. :P
zertap Mar 3 @ 7:27am 
Originally posted by Epsi:
Can you try to press F1 while in game to activate beat debug draw mode?
That should give you an indication if you're above the beat hitbox. If you press the button while above the hitbox and it doesn't register it, let me know please.
I tried earlier, but reading the game was so hard that I couldn't be sure.. Let me try again
*goes ingame*
http://youtu.be/wuAolrJ1CwI
(can't read holds with the debug interface)
Even when I press the correct button on correct time (I think?) it just "error"s at me >:(
Loïc  [developer] Mar 3 @ 7:33am 
Thank you! I will investigate the issue.
I've found that if you press very early at the very first part of the hitbox, it seems to be ignored (22ms long), so that might be it.

Nothing related to the FPS unlock though, except now it's easier to land there if you press too early since they are more possible cycles to do it.

zertap Mar 3 @ 7:38am 
Mm, figured I should just take a video since that is your interface after all. I'm not used to it + it is really hard to monitor it while playing. Glad to be helpful :)
Loïc  [developer] Mar 3 @ 7:40am 
Yeah a video is a huge help.
ou're hitting them too early, could you please try again while making a conscious effort to wait for the small orb to touch Melody's belly, and tell me if you still feel that you get unfair errors?

(There is still a bug with the early part hitbox that I need to fix, good thing you reported the bug :) )
zertap Mar 3 @ 7:47am 
http://i.fluffytail.me/UY.png
Yeah, seems to do the trick (more "OK" = the treshold of that getting smaller too? Or maybe it was just me hitting too late since I was trying to hit exactly on time?)
Showing 1-15 of 35 comments
< >
Per page: 15 30 50