Dan Balasescu
d4a4acd3f4
Fixes https://github.com/ppy/osu/issues/29223 This fixes several issues around hold note dimming. Notice in the following video: - The tail piece of the first note not getting dimmed. - The body of the second note not responding to dimming at all. https://github.com/user-attachments/assets/8e51053d-8d88-4e48-909b-79218d65917b Then, notice in the following video: - The body piece of the second note is dimmed from the very beginning. https://github.com/user-attachments/assets/a514c630-5c72-4ba5-96d5-472bae1058b3 This requires a specific setup whereby the hold note and its components must be reused from the pool. In particular: 1. The hold note must be long. So long that by the time the tail becomes on screen, the body will already have dimmed. 2. The hold note must be re-used from the pool. We can induce this by setting the pool sizes to 1 in [`Column.cs`](https://github.com/ppy/osu/blob/780ce2666099c22d1e0673cafab544418b5d14b0/osu.Game.Rulesets.Mania/UI/Column.cs#L121-L123). 3. The second hold note should be placed far enough in the timeline that the first hold note dies by the time it becomes visible. 4. Scroll speed should be adjusted to fit the above constraints. I haven't done a full deep dive into exactly _why_ this is happening, so the fix here is hand-wavy. That said, just by looking at the old code in `LegacyBodyPiece` you'll get a feeling that something's bound to go wrong; - It never resets the `missingFadeTime` state. - It never resets the colours back to `Color4.White`. - It applies transforms onto external components. - It jumps through hoops to figure out how to set `missingFadeTime`. My hope is that these changes first bring some sanity in the process, and if it breaks again I'll consider doing a more proper root cause (I've had this issue in the back of my mind for about 1 year). With this PR, they now behave as expected: https://github.com/user-attachments/assets/140b37c5-cf84-44ba-b797-86ac6d8130c8 https://github.com/user-attachments/assets/6f2342a4-6a9a-4941-a55a-24a357f27c25
osu!
A free-to-win rhythm game. Rhythm is just a click away!
This is the future – and final – iteration of the osu! game client which marks the beginning of an open era! Currently known by and released under the release codename "lazer". As in sharper than cutting-edge.
Status
This project is under constant development, but we do our best to keep things in a stable state. Players are encouraged to install from a release alongside their stable osu! client. This project will continue to evolve until we eventually reach the point where most users prefer it over the previous "osu!stable" release.
A few resources are available as starting points to getting involved and understanding the project:
- Detailed release changelogs are available on the official osu! site.
- You can learn more about our approach to project management.
- Track our current efforts towards improving the game.
Running osu!
If you are just looking to give the game a whirl, you can grab the latest release for your platform:
Latest release:
| Windows 10+ (x64) | macOS 12+ (Intel, Apple Silicon) | Linux (x64) | iOS 13.4+ | Android 5+ |
|---|
You can also generally download a version for your current device from the osu! site.
If your platform is unsupported or not listed above, there is still a chance you can run the release or manually build it by following the instructions below.
For iOS/iPadOS users: The iOS testflight link fills up very fast (Apple has a hard limit of 10,000 users). We reset it occasionally. Please do not ask about this. Check back regularly for link resets or follow peppy on twitter for announcements. Our goal is to get the game on mobile app stores very soon so we don't have to live with this limitation.
Developing a custom ruleset
osu! is designed to allow user-created gameplay variations, called "rulesets". Building one of these allows a developer to harness the power of the osu! beatmap library, game engine, and general UX for a new style of gameplay. To get started working on a ruleset, we have some templates available here.
You can see some examples of custom rulesets by visiting the custom ruleset directory.
Developing osu!
Prerequisites
Please make sure you have the following prerequisites:
- A desktop platform with the .NET 8.0 SDK installed.
When working with the codebase, we recommend using an IDE with intelligent code completion and syntax highlighting, such as the latest version of Visual Studio, JetBrains Rider, or Visual Studio Code with the EditorConfig and C# Dev Kit plugin installed.
Downloading the source code
Clone the repository:
git clone https://github.com/ppy/osu
cd osu
To update the source code to the latest commit, run the following command inside the osu directory:
git pull
Building
From an IDE
You should load the solution via one of the platform-specific .slnf files, rather than the main .sln. This will reduce dependencies and hide platforms that you don't care about. Valid .slnf files are:
osu.Desktop.slnf(most common)osu.Android.slnfosu.iOS.slnf
Run configurations for the recommended IDEs (listed above) are included. You should use the provided Build/Run functionality of your IDE to get things going. When testing or building new components, it's highly encouraged you use the osu! (Tests) project/configuration. More information on this is provided below.
To build for mobile platforms, you will likely need to run sudo dotnet workload restore if you haven't done so previously. This will install Android/iOS tooling required to complete the build.
From CLI
You can also build and run osu! from the command-line with a single command:
dotnet run --project osu.Desktop
When running locally to do any kind of performance testing, make sure to add -c Release to the build command, as the overhead of running with the default Debug configuration can be large (especially when testing with local framework modifications as below).
If the build fails, try to restore NuGet packages with dotnet restore.
Testing with resource/framework modifications
Sometimes it may be necessary to cross-test changes in osu-resources or osu-framework. This can be quickly achieved using included commands:
Windows:
UseLocalFramework.ps1
UseLocalResources.ps1
macOS / Linux:
UseLocalFramework.sh
UseLocalResources.sh
Note that these commands assume you have the relevant project(s) checked out in adjacent directories:
|- osu // this repository
|- osu-framework
|- osu-resources
Code analysis
Before committing your code, please run a code formatter. This can be achieved by running dotnet format in the command line, or using the Format code command in your IDE.
We have adopted some cross-platform, compiler integrated analyzers. They can provide warnings when you are editing, building inside IDE or from command line, as-if they are provided by the compiler itself.
JetBrains ReSharper InspectCode is also used for wider rule sets. You can run it from PowerShell with .\InspectCode.ps1. Alternatively, you can install ReSharper or use Rider to get inline support in your IDE of choice.
Contributing
When it comes to contributing to the project, the two main things you can do to help out are reporting issues and submitting pull requests. Please refer to the contributing guidelines to understand how to help in the most effective way possible.
If you wish to help with localisation efforts, head over to crowdin.
We love to reward quality contributions. If you have made a large contribution, or are a regular contributor, you are welcome to submit an expense via opencollective. If you have any questions, feel free to reach out to peppy before doing so.
Licence
osu!'s code and framework are licensed under the MIT licence. Please see the licence file for more information. tl;dr you can do whatever you want as long as you include the original copyright and license notice in any copy of the software/source.
Please note that this does not cover the usage of the "osu!" or "ppy" branding in any software, resources, advertising or promotion, as this is protected by trademark law.
Please also note that game resources are covered by a separate licence. Please see the ppy/osu-resources repository for clarifications.