Notice: We are still figuring out game balance and mechanics. For now, scores set on lazer should not be considered permanent.
osu!(lazer) is the next major update to the game. It is the culmination of several years of work behind the scenes to painstakingly reimplement the game.
The eventual goal is that this version will be released as an update which will completely supersede the existing stable version of the game, but there's still some work to be done before that is feasible. At the end of the day, the players will dictate when this happens and we will continue to support the previous release until users have migrated across.
"lazer" is a codename and will eventually be dropped as it becomes the primary release of the game. The rest of this document will refer to osu!(lazer) as "lazer" and osu!(stable) as "stable" for simplicity.
The following is a comprehensive list of the current state of lazer in comparison to stable. Note that this is a moving target — the end goal is to implement all the features that players care about over time.
|Windows 8.0 and lower|
|macOS / Linux||1|
|DirectX / Vulkan||2||3|
|Custom rulesets (game modes)||4|
|De-duped file store||5|
|Tablet area adjustment|
|Song select grouping modes|
|In-game skin / UI layout editing|
|Accurate performance point display||7|
|Difficulty adjust mod||8|
|New "fun" mods|
|Combo colour normalisation9|
|Hold for HUD||10|
|osu! sliders "snake" while dragging||13|
|osu! player-friendly "note lock"||14|
|osu!mania timing-based note colouring|
|Wiki / News / Changelog / Rankings||18|
|Unlimited multiplayer room size||20|
|Playlists (user-curated leaderboards)|
|Updating beatmaps with online changes||24||25|
|Open difficulty as reference|
|Per-object SV / volume|
So you've decided you want to give lazer a shot? Great!
You can find it for download here. In the near future, you will be able to switch to lazer from stable (from the
Release stream setting) and find the download link on the osu! website.
Stable will continue to be maintained as long as users are using it. At very least, it will be maintained for several years.
Currently, beatmaps, skins, scores, replays and collections can be imported into lazer. Of note, settings are not yet imported so you will need to set them up from scratch.
If you have both lazer and stable on the same drive, hard links are used to avoid using extra disk space.
In all other cases, importing beatmaps will use double the disk space.
Yes, lazer always installs alongside stable. Unless you choose to delete one or the other, both will be accessible.
No. This will not be supported.
That said, individual scores and beatmaps can be exported from lazer and manually imported into stable for now.
Scores will show under "recently played" but not in "best performance" yet.
Scores will already have performance points calculated (you can see this in the "recently played" section of your profile), but it will not contribute to the total value yet.
Lazer currently uses a new experimental score implementation which is similar to ScoreV2 but not the same. This is still in development and we are looking for more feedback on how it feels in various contexts (solo play, leaderboards, tournaments etc.)
You can actually change the
Score display mode setting to
Classic to get back the explosive style of scoring game-wide! It won't be a perfect match, but will give you the same feel of classic scoring and be applied everywhere you'd expect it to be.
While we will try to preserve as many scores as possible, we offer no guarantee that scores will remain indefinitely. At any point we may choose to wipe a subset or all scores in order to preserve game balance.
Yes. Once we finish balancing the combination of lazer and stable scores, both will be visible.
For now, scores of all mod combinations appear on leaderboards. Whether scores will give performance points with all mods (and if they do, whether there will be a bonus or penalty applied) is still in discussion.
Please try applying the "classic" mod, which will restore much of the old behaviour that you are used to. Also make sure to check the settings offered by classic mod, as it will let you further customise your experience and also understand what changes are being applied (as they are all listed there).
Please run the setup wizard at the top of settings and go through the settings on the
Behaviour screen. A lot of the common settings which have defaults changed are listed here. There's also a single button you can press to apply the old behaviours as a starting point for your lazer journey.
We'll do our best to bring back as much of this as we can without blocking new functionality. This will come later on.
We will likely bring back support for this in the future due to popular demand.
Above a certain threshold there is no reason to run at higher frame rates. Lazer employs various new technologies to ensure the lowest latency is achievable without requiring high frame rates. This will continue to improve going forward as we still have a few improvements left to implement.
Lazer polls for input at 1,000 Hz regardless of FPS limiter, which is why the maximum limiter setting will also limit to 1,000 FPS.
If you are curious about how this affects input latency and test your own perception, please run the built-in "latency certifier" at the bottom of settings.
You can also read this technical document explaining the path we are taking along with rationale behind it.
The operating system will still poll at the higher rate, although benefits are proven to be negligible. Polling at such high rates can have unforeseen overheads, and we recommend limiting devices to 1,000 Hz for system stability.
While on most modern hardware we see lazer outperform stable, there are always edge cases when each user has a different hardware configuration. In our short-term roadmap, we are looking to support DirectX (aka "compatibility mode" on stable) and Vulkan, which both have better driver support than OpenGL across all hardware. Once this is implemented, performance on hardware like Intel integrated chipsets will improve greatly.
There's a very high chance we are already aware of this and tracking it for future implementation! Please search the issue tracker and discussions page. If you can't find any matching threads, feel free to open a discussion.
Do note that we are already tracking over 1,000 issues of varying priorities, and it may take us some time to fix issues that only affect a small number of users.
What is sharper than cutting–edge?
While osu! may seem like a simple game, there are hundreds on hundreds of features and systems that users have come to rely on. Depending on who you ask, lazer may have been in a fully playable state for years now, or it may be missing countless features.
Another area which has taken a huge amount of effort is historical preservation — making sure that beatmaps behave exactly as they should, including edge cases that weren't originally planned for. osu! is a vibrant ecosystem and users have taken liberty to extend the game far beyond its planned extents, and we are trying our best to embrace and support this going forward.
Finally, unlike the last iteration, we are putting in the time and diligence to ensure the code base will serve us well into the future. We have done the groundwork to allow new features to come online at blazing speed going forward. This will include new UI components, new ways to skin the game, new multiplayer systems and let's not forget the ability to load and play all your existing beatmaps on completely new game modes (a.k.a. rulesets)!
We have a huge backlog of user-requested features and improvements that we will continue to push out at the speed of light. For those that have joined us recently and haven't experienced the momentum of osu! development, prepare to be in for a surprise.
There is no songs folder in lazer! This allows us to do cool things like not require pressing
F5 at song select to refresh beatmaps (because beatmaps are always in a good state) and reduce the disk space used by beatmaps by 20–40%. You can read more about the way lazer stores files.
If you need to make changes to a beatmap, please use the editor. Going forward we will introduce a mode in the editor which makes a beatmap's folder temporarily accessible for external editing. This will allow you to use external tools on a beatmap during the creation process.
Some filters in the beatmap listing are still supporter-only.
There are also some additional benefits already:
We do intend to look into new benefits in the future, but our focus is currently on feature parity with stable so please use your supporter tag purchase as a way to... support the game's development!
The same way you usually would.
You're likely thinking of another game.
Using wine. ↑
DirectX via compatibility mode. ↑
Coming soon. ↑
.dll files. ↑
Gameplay only. ↑
Via online retrieval. ↑
Change CS/AR/OD/HP of a beatmap directly from song select. ↑
This brings beatmap custom combo colours to the same brightness level. ↑
Ctrl to view the HUD momentarily while it's hidden. ↑
Adjustable manually via key bindings. ↑
When retrying a beatmap, you can calibrate the offset based on your last play. ↑
Can be disabled. ↑
Still exists, but should not interfere. ↑
Scores will be reset to ensure balance. ↑
Scores will be reset, currently isolated from stable scores. ↑ ↑
Messages can take up to 15 seconds to arrive. ↑
Native access to most online content. ↑
osu!direct, osu!supporter-only. ↑
16 players max. ↑
Set a countdown using a command, no automatic start. ↑
Set a countdown from the game UI to automatically start the match. ↑
Turn on to allow anyone in a lobby to queue new beatmaps, a.k.a. "host rotate". ↑
Map only. ↑
All files. ↑
Missing precise angle rotation. ↑
Some editor features will cause beatmaps to play incorrectly in stable — will be fixed soon. ↑