You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried osu!catch in Lazer and it felt just a little bit off compared to Stable, so I decided to compare them side by side by playing the same map and there are several discrepancies between the two.
Dash trail effect intervals are much larger in Lazer than in Stable. This takes away some sense of speed when dashing.
Hyperdash intervals in Lazer are lower than regular dashes, when in Stable the interval is constant, so when you hyperdash, the distance between trail afterimages is larger in Stable, but in Lazer it's the same.
Albeit minor, I think it should also be mentioned - the fade speed of bounced fruits and droplets are a bit quicker than stable.
I think it's important to be as close as possible to Stable in terms of gameplay visuals so people have a smoother experience switching to Lazer.
Screenshots or videos
Stable vs Lazer dash
Stable vs Lazer hyperdash
Version
2024.718.1
Logs
Not applicable
The text was updated successfully, but these errors were encountered:
Albeit minor, I think it should also be mentioned - the fade speed of bounced fruits and droplets are a bit quicker than stable.
This will require a bit more attention (ie. implementing local gravity rather than using fixed transforms to match stable). Probably best to open a separate issue for it if you consider it important.
Type
Cosmetic
Bug description
I've tried osu!catch in Lazer and it felt just a little bit off compared to Stable, so I decided to compare them side by side by playing the same map and there are several discrepancies between the two.
I think it's important to be as close as possible to Stable in terms of gameplay visuals so people have a smoother experience switching to Lazer.
Screenshots or videos
Stable vs Lazer dash
Stable vs Lazer hyperdash
Version
2024.718.1
Logs
Not applicable
The text was updated successfully, but these errors were encountered: