Index » Other » Client Modding » b20130303 Digital Client++

I think osu!lazer actually has the sliders wiggle on notelock so it's definitely worth fixing/leaving as a separate option. TBH, I'm not sure why the decision was made to have sliders not wiggle in the first place.

jvyden wrote:

I think osu!lazer actually has the sliders wiggle on notelock so it's definitely worth fixing/leaving as a separate option. TBH, I'm not sure why the decision was made to have sliders not wiggle in the first place.

interesting, thats good to know. the way that my client is currently doing notelock on snaking out sliders is definitely a bit cursed though, I would need a better animation xd

If you encounter any issues with Digital Client 5.0.20 on Windows versions older than Windows 10 (errors on beatmap star calculations, errors with pp counter), I made a pack of fixed dll files that prevent that issue. These files will be built into the next Digital Client release. I'm posting these here for now until the next patch releases, and won't be needed in the future.

YOU DO NOT NEED TO USE THESE IF YOU ARE USING WINDOWS 10 OR LATER OR WINE!!!!!

Instructions:
- Rename the appropiate rosu-pp dll (rosu_pp_32.dll for 32-bit, rosu_pp_64.dll for 64-bit) to rosu_pp.dll
- Replace the file in your Digital Client 5.0.20 install.

Download link: https://www.mediafire.com/file/frbjsznu8zb9ux6/rosu_pp_fixed.zip/file

There is a small issue: slider elements on timeline cannot be clicked with cs 10, making some maps harder to hitsound. Proper explanation is here (it's both clients issue). Hoping you will fix it

This is an amazing client, thanks to the author! However, there is one small caveat.
When raw input is enabled, the in-game cursor does not respond to tablet stylus input.
Without raw input, input latency can be noticeably higher. Is there a way to fix this?

Hinu wrote:

This is an amazing client, thanks to the author! However, there is one small caveat.
When raw input is enabled, the in-game cursor does not respond to tablet stylus input.
Without raw input, input latency can be noticeably higher. Is there a way to fix this?

Not currently. This is raw input matching b20140323, which unfortunately just works this way. January 2015 brought a massive rewrite to input handling that fixed it, but so far I haven’t been successful in backporting that. Possible? Yes. Have a been able to do it yet? Nope xD.