F2 Enjoyer

osu!lazer Enjoyer

check your universal offset kids

cool labs:
mahisuru and Zheant: IMG

SPECS

- Wacom PTH-851 (previously Wacom GD-0608)
-- Driver: OpenTabletDriver
- Razer Huntsman TE (Razer linears)
- 280hz 16:9 1080p monitor (game fullscreen)
- Onyx Artist 1-2
- Linux (Sway WM, Wayland)
-- Measured end-to-end audio latency (click to sound, ThePooN method)
--- osu!stable: 6ms
--- osu!lazer: 5ms or below (difficult to measure)

History

2019:
Oct 27th: Started, using 125hz keyboard, 72hz monitor, and Logitech G303 at 800 DPI - later ~1600 DPI.

Nov 9th: First 100pp, +HR beatmapsets/1010865#osu/2118197
Nov 25th: Tablet GET (XP-PEN Star G640)
Nov 27th: First 100pp tablet play, nomod beatmapsets/230989#osu/537377

2020:
Jan 4th: 5 digits
Jan 19th: First 200pp, nomod beatmapsets/517055#osu/2157548

Feb 9th: Rank 50k

April 16th: 10k Playcount

May 24th: Rank 40k

July 4th: First 300pp, nomod beatmapsets/886368#osu/1854022
July 7th: Rank 30k

Oct 28th: Rank 20k

Dec 11th: 20k Playcount

2021:
Jun 29th: New tablet GET (XP-Pen G640 -> Wacom GD-0608)

2022:
Jan: 30k Playcount

2023:
Oct 21th: First 400pp, nomod beatmapsets/440650#osu/1564521

2024:
Feb: First Taiko 200pp, nomod beatmapsets/1904848#taiko/3943884
July: First Taiko 300pp, nomod beatmapsets/1875585#taiko/3859766

osu! Linux config FAQ

1. Which WINE to use for osu!stable?
   wine-staging 7.11 with custom winepulse patch
   
   This reverts major v5.15 winepulse changes, and removes the 10ms audio period floor (similar to ThePooN's)
   If you really want to use something newer (which as of mid-2024, there isn't really a huge reason to do so), I suggest at the minimum using a WINE version that does the 2 above things. marshnello's WINE is doing this last time I checked.
2. Which tablet driver should I use?
   If you need filters (like smoothing or antichatter), use OpenTabletDriver
   Otherwise use either the stock Linux driver (assuming it works out of the box), or OpenTabletDriver. Keep in mind that tablets (such as OpenTabletDriver in artist mode) are always smoothed unless disabled in libinput.
   Stock driver works fine too if you don't need filters. I suggest manually disabling smoothing in libinput though.
3. Which sound card has the best latency?
   Short answer: The one that's already built in to your computer
   Long answer:
   Preferably something that doesn't need to have its audio pushed to it ("batch" sound cards, aka. USB sound cards and extremely few built-in sound cards)
   If you use a batch sound card, manually enabling it to run at static buffer sizes (or flooring the minimum possible period size, once Pipewire is able to do that) can help reduce latency further.
4. Do custom CPU schedulers matter in kernels?
   Probably, but in recent years I've found custom kernels to be more of a headache to keep maintained, since major versions of the kernel tend to have some sort of performance uplift with it, especially for newer computers. So I use the stock kernel provided by my Linux distribution. Custom CPU schedulers tend to be poorly maintained, so they do not always follow the latest major versioning.
   2026 edit: this is less correct now that sched-ext exists

osu!stable Linux personal config

1. Input: OpenTabletDriver - artist mode
2. Sound: WINE -> PipeWire -> Studio-grade USB DAC
3. WINE: My personal wine-staging 7.11 with custom winepulse patch (can be found on ThePooN's discord)

For anything else I can be reached on ThePooN's discord

osu!lazer Linux personal config

1. Input: OpenTabletDriver (out of game driver, already using out of game)
2. Sound: PipeWire's ALSA endpoint
   Using an environment variable (PIPEWIRE_ALSA) to force low periodicity (sound timer resolution)

Tips for noobs

1. its not genetics
2. If your audio latency is garbage, consider playing without hitsounds and adjusting offset to your physical clicks instead (usually in the order of -200 to -50 universal offset). But don't play without hitsounds, osu is made for it.
3. How to set universal offset properly:
   
   1. My preferred method:
      
      1. Set 100% effects volume and 50% music volume or higher
      2. Select any recently ranked map (guaranteed close to correct offset)
      3. Use auto mod (press ctrl+enter on song)
      4. Use local offset keys (default -/+) to adjust auto click with song.
      5. Apply this local offset (on stable, inversely) to your universal offset (on stable; ie. +20ms map offset = subtract 20ms from global)
   2. Easier, but potentially less accurate, method to set universal offset on osu!lazer:
      
      1. Play some maps
      2. Click the auto offset button
      3. Rinse and repeat until it's good enough for you (if it isn't, kicking it 5ms either direction can help the
         auto-offset better find the correct auto for you)
4. Changing drivers, audio hardware or input device(s) may affect offset