Experimental renderer feedback thread

[smoogipoo]

Hello circle clickers. The latest release brings some new options to the renderer settings dropdown:

This is a feedback thread where you can share your experience with us.
Here are some topics of particular interest to us, but keep in mind that this is not an exhaustive list and we encourage you to try all options out and share any experiences you've had regardless.

Please keep discussions isolated to one topic/experience.

Windows

I'm using Windows and prefer OpenGL because D3D11 [is laggy]/[causes graphal glitches]/[other].

• Provide a dxdiag report of your system.
• What scenarios are you testing?
• What statistics are you looking at to inform your decision?
• Does the D3D11 (Experimental) option help?

---

I'm using Windows on an Intel Arc or Xe GPU.

• How does the Vulkan (Experimental) compare?

---

I'm using Windows and all options behave poorly for me.

• Provide a dxdiag report of your system.
• What specific issues are you noticing?

---

I'm using Windows and none of the above apply to me.

• Do you notice any substantial difference with the D3D11 (Experimental) option?

macOS

I'm using macOS and regularly see corrupted text.

• Does the Metal (Experimental) option resolve it?
  (You'll likely need to give it some time because it doesn't happen every startup.)

Linux

I'm using Linux and notice red frame spikes in the Ctrl+F11 overlay.

• Does the OpenGL (Experimental) option resolve it?

---

I'm using Linux and the Vulkan (Experimental) option behaves [better][worse] for me.

• What GPU are you using?

General

Vulkan doesn't run for me.

• What operating system are you using?
• What GPU are you using?
  (On windows, you can provide a dxdiag report of your system.)

[Stoppedpuma]

Vulkan doesn't run for me.

Since I've seen multiple people complain about this on Linux, the old solution of linking libdl.so.2 to libdl.so is still required for Vulkan.

(Moved here from my reply below for better visibility.)
ln -s /usr/lib/libdl.so.2 /usr/lib/libdl.so should fix this issue and allow you to use Vulkan.

If you're still unable to initialise the renderer you can find the correct location for libdl.so.2 on your system with this command:
ldconfig -p | grep libdl DO NOT MIX 32 BIT AND 64 BIT LIBRARY LOCATIONS

I'm getting a crash when I use a frame limiter above 2x refresh rate on linux / freeze during entering gameplay and other various locations but input works

If you're running a wayland session try running the game with SDL_VIDEODRIVER=wayland

The freeze / crash but input works thing I'm not sure of any causes yet. I'm mostly seeing this with mobile gpus even on windows?

[earfluffy]

This didn't work for me, fwiw. Not sure where to look for logs.

[Stoppedpuma]

Does your game give you an error saying it failed to initialise the renderer? Or are you getting a crash?

[earfluffy]

Failed to initialise renderer, but it actually did work, I just needed to link /usr/lib64/libdl.so instead, whoops.

[Stoppedpuma]

Forgot different linux distros can't agree on consistent locations, added a command to find where the lib is if it's not in the location of the original command.

[Entropy-10]

After switching to Vulkan, when entering gameplay my osu! lazer would flicker and freeze. It sounded like I could still interact with elements on the screen while frozen, then eventually it would hard crash for me. This behavior was consistent between restarting the game and did not stop until switching renderers.

PC Specs:
Windows Version: Windows 11 23H2
CPU: Ryzen 7 7800X3D
GPU: Nvidia RTX 3070 Super
Ram: 32 GB 6000mhz

Logs:
compressed-logs.zip

Video:
https://github.com/ppy/osu/assets/45132530/bf36b276-ab1a-425a-9cc0-717ded2ab88d

[StalkyBoi43815]

(almost) same except im on arch btw

[copecone]

For Intel Arc GPU, it's working way more smoother and absolutely no problem.

[Stoppedpuma]

I'm getting mostly the same performance on Linux with Vulkan as I did with OpenGL, the main issues I've had related to performance are horrible lag spikes in the main menu when I first open the game (normally ~1k with OpenGL, ~180-200 on Vulkan) but this disappears shortly. I also have the lag spikes occasionally when returning to the main menu. I'm also getting around 50-100 less frames in song select but it returns to normal after around 10 seconds.

I have gotten one hard crash when entering gameplay with Vulkan after around an hour of gameplay, here's the error:

Unhandled exception. System.IndexOutOfRangeException: Index was outside the bounds of the array. at Veldrid.Vk.VkSwapchain.CreateSwapchain(UInt32 width, UInt32 height) at Veldrid.Vk.VkGraphicsDevice.SwapBuffersCore(Swapchain swapchain) at osu.Framework.Platform.GameHost.Swap() at osu.Framework.Platform.GameHost.DrawFrame() at osu.Framework.Threading.GameThread.processFrame() --- End of stack trace from previous location --- at osu.Framework.Platform.GameHost.<>c__DisplayClass141_0.<abortExecutionFromException>b__0() at osu.Framework.Threading.ScheduledDelegate.RunTaskInternal() at osu.Framework.Threading.Scheduler.Update() at osu.Framework.Threading.GameThread.processFrame() at osu.Framework.Platform.ThreadRunner.RunMainLoop() at osu.Framework.Platform.SDL2Window.RunMainLoop() at osu.Framework.Platform.SDL2Window.Run() at osu.Framework.Platform.GameHost.Run(Game game) at osu.Desktop.Program.Main(String[] args) in /home/runner/work/osu-auth-client/osu-auth-client/osu/osu.Desktop/Program.cs:line 146

I've only gotten this error once

[nick1324354]

Vulkan doesn't run for me.

I simply get my renderer set back to Automatic upon restarting osu!.

PC Specs (Laptop):
Linux Distro: EndeavourOS
CPU: Intel i7-11800H
GPU: NVIDIA RTX 3060 Mobile
RAM: 16GB 3200MHz

[Skaldebane]

Hi @Stoppedpuma, this doesn't work for the Flatpak version of osu!.

From the logs, it seems to be looking for libdl.so in /app/bin/, which is part of the Flatpak sandbox.

I tried entering the sandbox and symlinking to it while inside of the sandbox (flatpak enter <osu's instance> bash), but these are read-only filesystems (as the sandbox is naturally immutable).

Any solutions here?

[Stoppedpuma]

@Skaldebane I could probably figure this out within the next hour or so on my end so I'll get back to you in a bit with either a solution or what I tried.

/usr seems to be blacklisted for modifications from the flatpak sandbox level, I don't know flatpak very well at all so I'd recommend looking around for other users having a similar request of wanting to use system libraries and see if they found a solution. The closest I've found to a solution is /run/host seems to be writeable to, I don't know / think this would work? I'm afraid for flatpak I can't help very much if at all as if I ever use a flatpak it's mostly just set and forget with some basic permissions.

Is there a specific reason you're using flatpak instead of the appimage / aur / whatever else?

[Skaldebane]

@Stoppedpuma Thanks, I'll look into it.

I just use Flatpak for everything so I installed osu! as a Flatpak (in fact, I discovered osu! for the first time in Flathub!), which makes updates conveniently managed by the system as well as .desktop files. But I'll probably switch to the osu AppImage (and use some AppImage manager that creates .desktop files etc...)

(I use Fedora so no aur for me 😅 )

[Stoppedpuma]

Makes sense, if you want auto updates the linux build doesn't have them but it will automatically check. You can use the appimage.zsync for auto updates though.

If you're concerned or just generally want to lock down osu! in a sandbox or other something similar I recommend making an SELinux or Apparmor profile as an alternative.

[smoogipoo]

This one will be fixed by a series of PRs stemming from ppy/vk#1

[pockysam]

Swtiching to the Metal (Experimental) renderer causes several HUD elements to disappear and causes the game to flicker constantly. I restarted my MacBook and reinstalled lazer a few times by now but the problem still remains, the game still runs normally when I switch back to Metal.

This might not be relevant but I'll list this here just for more information, this is running on a MacBook Pro (2020):

• Processor: 1.4 GHz Quad-Core Intel Core i5
• Graphics: Intel Iris Plus Graphics 645 1536 MB
• Memory: 8 GB 2133 MHz LPDDR3

Screenshot:

Video (sorry for the bad quality):

example.mp4

[huyenden]

Clip:
https://streamable.com/r0fdj5 or https://www.veed.io/view/4702b7eb-cdc6-4d27-84ee-34a8ad121223?panel=share

In my opinion, the two new renderers, Vulkan Ex and Direct 3D11 Ex, are still not as good as the best one, OpenGL.

Since the mod I'm playing is the mod that consumes the most graphics, I'm pretty sure my test is correct.

[Sinamer]

D3D11 vs D3D11 (Experimental)

D3D11 (Experimental) feels more stable, and according to captures it is slightly better in low% metrics on my machine

Vulkan (Experimental)

It runs, although not very successfully.

First, Vulkan (Experimental) doesn't seem to respect the GPU choice in Nvidia Optimus (hybrid graphics) systems:

Second, it crashes in a lot of cases, like opening the Playing Now overlay, switching to song select (occasionally), and gameplay start:

crash.mp4

Logs

Logs cut off without any relevant information

compressed-logs.zip

Event Viewer Errors

Application error

Faulting application name: osu!.exe, version: 0.0.0.0, time stamp: 0x65f90000
Faulting module name: coreclr.dll, version: 8.0.424.16909, time stamp: 0x65f9e938
Exception code: 0xc0000005
Fault offset: 0x00000000001cc9e2
Faulting process id: 0x420
Faulting application start time: 0x01da8d6e9b17f835
Faulting application path: C:\Users\Sin\AppData\Local\osulazer\app-2024.412.0\osu!.exe
Faulting module path: C:\Users\Sin\AppData\Local\osulazer\app-2024.412.0\coreclr.dll
Report Id: 55ce0c34-e56d-4dbe-874a-bf3eafedafde
Faulting package full name: 
Faulting package-relative application ID: 

.NET Runtime

Application: osu!.exe
CoreCLR Version: 8.0.424.16909
.NET Version: 8.0.4
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
   at Vulkan.VulkanNative.vkMapMemory(Vulkan.VkDevice, Vulkan.VkDeviceMemory, UInt64, UInt64, UInt32, Void**)
   at Veldrid.Vk.VkDeviceMemoryManager+ChunkAllocator..ctor(Vulkan.VkDevice, UInt32, Boolean)
   at Veldrid.Vk.VkDeviceMemoryManager+ChunkAllocatorSet.Allocate(UInt64, UInt64, Veldrid.Vk.VkMemoryBlock ByRef)
   at Veldrid.Vk.VkDeviceMemoryManager.Allocate(Vulkan.VkPhysicalDeviceMemoryProperties, UInt32, Vulkan.VkMemoryPropertyFlags, Boolean, UInt64, UInt64, Boolean, Vulkan.VkImage, Vulkan.VkBuffer)
   at Veldrid.Vk.VkBuffer..ctor(Veldrid.Vk.VkGraphicsDevice, UInt32, Veldrid.BufferUsage, System.String)
   at Veldrid.Vk.VkResourceFactory.CreateBufferCore(Veldrid.BufferDescription ByRef)
   at Veldrid.ResourceFactory.CreateBuffer(Veldrid.BufferDescription ByRef)
   at Veldrid.ResourceFactory.CreateBuffer(Veldrid.BufferDescription)
   at osu.Framework.Graphics.Rendering.Deferred.Allocation.DeviceBufferPool+PooledDeviceBuffer..ctor(osu.Framework.Graphics.Veldrid.Pipelines.GraphicsPipeline, UInt32, Veldrid.BufferUsage)
   at osu.Framework.Graphics.Rendering.Deferred.Allocation.DeviceBufferPool.Get()
   at osu.Framework.Graphics.Rendering.Deferred.Allocation.UniformBufferManager.Write(osu.Framework.Graphics.Rendering.Deferred.Allocation.MemoryReference ByRef)
   at osu.Framework.Graphics.Rendering.Deferred.DeferredUniformBuffer`1[[osu.Framework.Graphics.Rendering.GlobalUniformData, osu.Framework, Version=2024.329.0.0, Culture=neutral, PublicKeyToken=null]].Write(osu.Framework.Graphics.Rendering.Deferred.Allocation.MemoryReference ByRef)
   at osu.Framework.Graphics.Rendering.Deferred.DeferredUniformBuffer`1[[osu.Framework.Graphics.Rendering.GlobalUniformData, osu.Framework, Version=2024.329.0.0, Culture=neutral, PublicKeyToken=null]].osu.Framework.Graphics.Rendering.Deferred.IDeferredUniformBuffer.Write(osu.Framework.Graphics.Rendering.Deferred.Allocation.MemoryReference ByRef)
   at osu.Framework.Graphics.Rendering.Deferred.EventProcessor.processUploads()
   at osu.Framework.Graphics.Rendering.Deferred.EventProcessor.ProcessEvents()
   at osu.Framework.Graphics.Rendering.Deferred.DeferredRenderer.FinishFrame()
   at osu.Framework.Graphics.Rendering.Renderer.osu.Framework.Graphics.Rendering.IRenderer.FinishFrame()
   at osu.Framework.Platform.GameHost.DrawFrame()
   at osu.Framework.Threading.GameThread.processFrame()
   at osu.Framework.Threading.GameThread.<createThread>g__runWork|66_0()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

System Info

Edition	Windows 10 Pro
Version	22H2
Installed on	‎2024-‎01-‎05
OS build	19045.3803
Experience	Windows Feature Experience Pack 1000.19053.1000.0

Drivers

Recently updated for both my Intel iGPU and the Nvidia dGPU
DxDiag.txt

[Stoppedpuma]

@akai-hana are you using a compositor / compositor disabling script on x11?

[catuhana]

Same thing happens on me, but without that much flickering. And I personally noticed this mostly happen when exiting a map, but it seems like it's not just specific to that, since just trying to download a map triggered that too. It doesn't happen always or frequently for me though, just in rare cases.

Edit 1: As mentioned above, after crash, there's a chance that we lose all the maps. Doesn't happen all the time.

I'm going to upload a whole 2-minute video, since I was experimenting with renderers window modes (to reproduce the bug), and it might somehow be related to that. The crash happens at around 1:45 (with Vulkan renderer).
https://github.com/ppy/osu/assets/108196023/58973881-a25a-42dd-9c07-f164cae371ca

Game Logs

1713355514-logs.zip

Event Viewer Logs

.NET Runtime Crash Event Log

Application: osu!.exe
CoreCLR Version: 8.0.424.16909
.NET Version: 8.0.4
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
   at osu.Framework.Graphics.Veldrid.Pipelines.BasicPipeline.updatePendingExecutions()
   at osu.Framework.Graphics.Rendering.Deferred.DeferredRenderer.BeginFrame(osuTK.Vector2)
   at osu.Framework.Platform.GameHost.DrawFrame()
   at osu.Framework.Threading.GameThread.processFrame()
   at osu.Framework.Threading.GameThread.<createThread>g__runWork|66_0()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

Application Error Crash Log

Faulting application name: osu!.exe, version: 0.0.0.0, time stamp: 0x65f90000
Faulting module name: coreclr.dll, version: 8.0.424.16909, time stamp: 0x65f9e938
Exception code: 0xc0000005
Fault offset: 0x00000000001cc9e2
Faulting process ID: 0x0x33F4
Faulting application start time: 0x0x1DA90BF812FCEC8
Faulting application path: C:\Users\Tuhana\AppData\Local\osulazer\app-2024.412.1\osu!.exe
Faulting module path: C:\Users\Tuhana\AppData\Local\osulazer\app-2024.412.1\coreclr.dll
Report ID: becec298-4bbb-4276-be51-f8cf9eb66066
Faulting package full name: 
Faulting package-relative application ID:

dxdiag Information

DxDiag.txt

[ricterG]

I am getting the same AccessViolationException as others using Vulkan, it runs fine at first then visual glitches start occurring and eventually crash. For me, takes 10+ mins or so to start seeing the issues I'm guessing because running a beefy card

DxDiag.txt

Also here is a crash dump if it would help

osu!.exe.43044.dmp

[akai-hana]

@Stoppedpuma i dont do any compositing. I run awesomewm compositorless.

Sorry for really late reply, i dont check notifs often.

[Stoppedpuma]

No worries, I think I'm able to reproduce the lower framerate visual and input lag very slightly as well. I wasn't able to notice this on Sway with max_render_time but I am able to notice this on Hyprland with tearing enabled.

[cihe13375]

win10, surface pro 6 (i5-8250u + uhd620), autoplay this map https://osu.ppy.sh/beatmapsets/513731#osu/1094998 with storyboard enabled. FPS observed from the counter at bottom-right:
Vulkan (experimental): 35-45fps
OpenGL: 40-50fps
D3D11: 25-35fps
D3D11 (experimental): 15-30fps

stable (stable has no argon skin so tested with stable default skin): 45-60fps

DxDiag.txt

[JacksonChen666]

The cursor trail while paused doesn't fade out, making it look weird. Only with the experimental metal renderer.

compressed-logs.zip

(I've unsubscribed from this thread. Ping me explicitly or I might not notice your comment)

[Rudasy]

I'm on Linux with an Nvidia GPU(GTX 1650 SUPER), 16Gb RAM and an Intel if-10400F CPU.

The Vulkan option feels almost the same as OpenGL but the screen sometimes freezes completely but moving the cursor and pressing key binds still interacts with the elements and the audio still works. Closing the game in this "frozen" state freezes my entire computer for a few seconds. The "frozen" state happens randomly for me.

EDIT: Deferred OpenGL behaves worse for me than regular. I can see Vulkan performs better than OpenGL after using it more.

compressed-logs.zip

[bytenekos]

I'm on the latest windows 11 release with an rtx 3080. Vulkan is very hit or miss, most of the time showing a garbled mess/flickering when launching a beatmap, seemingly at random times. So for example sometimes it loads the beatmap and I can move the cursor for a few frames, after which it starts flickering. I've also had some times when it would start flickering right when the fade out happens (so when the game goes from the loading screen to the actual map ui).

Dxdiag:
DxDiag.txt

Video showcase:

Osu.2024.04.13.-.15.45.30.15.mp4

Logs:
compressed-logs.zip

[adryzz]

I'm using Linux and the Vulkan (Experimental) option behaves just like OpenGL for me (which is great).
Using an AMD Radeon rx 580 (4GB), latency is low, and Vulkan (Experimental) is able to run at 1000Hz if left uncapped, and at 2x refresh rate, it floats around 0.6-0.9ms of latency, with a nice and clean graph.

[nyaruku]

i tried vulkan on windows, worked fine with default argon skin, after switching to my usual gameplay skin, my entire OS (Windows) Froze, no BSOD, just everything was frozen so that it required a hard reset

[EdmundDong]

dxdiag report: DxDiag.txt

What scenarios are you testing?

I tested the different renderers on a single beatmap diff across all the renderer options.

What statistics are you looking at to inform your decision?

I ran performance logging in GeForce Experience and took a screenshot during a break in the map to get a sample frame time and FPS from in-game.

GeForce Experience logging (199 samples, ~100 seconds) - Mean values with 95% CI (Data)

Renderer	Frame Time	FPS	99% FPS
D3D11	10.3-10.6	236-239	150-158
OpenGL	2.3-2.5	569-582	233-246
Vulkan (Experimental)	1.6-1.7	722-737	367-388
D3D11 (Experimental)	9.3-9.9	231-234	130-137

In-game data (1 sample)

Renderer	Frame Time	FPS
D3D11	1.1	341
OpenGL	1.1	653
Vulkan (Experimental)	1.1	988
D3D11 (Experimental)	1.1	215

Does the D3D11 (Experimental) option help?

The D3D11 experimental renderer did not feel very different for me from the current D3D11 renderer.
The Vulkan renderer felt very snappy, but I did crash once after restarting a beatmap.

EDIT: In-game data and GFE samples were taken from separate runs.

[EdmundDong]

Seems a lot of people are mentioning the Vulkan crashing. I'll throw in a screen recording and a set of logs in case it's useful.

2024-04-28.00-00-07-cut.mp4

compressed-logs.zip

[Neon095]

I have a problem with Vulkan, and it is that from using it for a while without closing the game, when I retry a beatmap it resoult on a bad framerate (from 660 fps (limited) to 240) and idk why. This is the logs from the latest time it happened:
compressed-logs.zip
Arch Linux, 6.8.9-x64v3-xanmod1, KWin (Wayland), AMD Ryzen 5 2600x, AMD Radeon RX 6500 XT, 8gb ram 2666

[MTGPROD]

My experience with Vulkan is quite bizarre, I first tested it on linux (PopOS, ubuntu-based) but it failed to initialize. On windows it initialze and the UI works. But when in game nothing displays and a lot of random visual noise appears and the game is visually broken. So I had to revert to Direct3D11 (experimental variant seems a lot more responsive, with micro-stutter when loading things but definitively less 100) which has a poor latency. Like I got random 100 with this renderer. OpenGL seems the more viable option for now.

I have a GTX 1050 Max-Q (Laptop) paired with a i5-9300H and 16go of RAM.

[Neon095]

Actually, I reinstalled arch and it now works fine

[huuishuu]

I made an issue about this in osu-framework (ppy/osu-framework#6285) but I guess I'll repost my findings here. I am noticing a lot of people reporting similar things, either by making new issues or just posting here. I have some slightly more useful information than what I've seen posted here but other issues have provided similar information to mine, such as #28039 and this comment here: #27659 (comment)

PC Specs:

CPU: AMD Ryzen 5 5600X
RAM: 32GB DDR4 3200mhz
GPU: Nvidia GeForce RTX 3060 (driver version 552.44)
OS: Windows 11 Pro 23H2 (OS Build 22631.3447)

Game client version:

2024.412.1-lazer

Description:

@shavitush helped me debug this locally using x64dbg and dnSpy.

I've started encountering an issue where my osu!lazer would just crash every time, without fail, when either:

• Entering the results screen after a map
• Starting a new map after exiting out of one

What tends to happen usually is that my game would completely freeze over, begin flickering, while the audio in the background would continue. Sometimes I'm able to interact with UI elements while the game is frozen but this isn't consistent. The game crashes silently without an error message. This is only an issue when the game is in full screen mode, Windowed & Borderless don't seem to be affected.

While debugging, we encountered anomalies where the game silently crashed without an error when entering song select. We did, however, manage to catch the crash regarding the results screen once but couldn't replicate it again. We forgot to take a screenshot of it but the top of the call stack threw an exception saying that memory is trying to be written to a non-accessible page and the module was ppy.Veldrid or something among those lines, with function calls starting with vk, indicating Vulkan APIs are triggering it.

Under Direct3D11, it works fine.

I recorded what I could regarding this with OBS here:
https://www.youtube.com/watch?v=FWUt_4L-jy4

[LittleLilyBun]

After the recent update (2024.519.1), switching renderer to Vulkan while using Wayland results in the game refusing the open, I was able to get the game working again by editing framework.ini and setting the renderer back to OpenGL, and Vulkan seems to work fine on X11, if it helps, I'm using KDE Plasma 6.0.4, and had __SDL_VIDEODRIVER=wayland set (but it still crashed without that argument), and I run osu! with AMD Integrated Graphics (my cpu is an AMD Ryzen 5 6600HS).

[elsandosgrande]

What's your frame rate set to? osu! doesn't open with Vulkan for me either, but only when the frame rate is set to VSync when the game is starting up. I'm on Plasma 6.1, have SDL_VIDEODRIVER=wayland set, and play on a 10th generation Intel APU.

[DeroXP]

Type

Crash to desktop

Bug description

Sometimes while using the experimental vulkan and i go into my beat maps its glitches really bad and the UI just stays stuck or when i try to play a song. I don't know if it's my hardware, it shouldn't be because I do have good specs, but it just freezes. (May be because I play on win?)

Screenshots or videos

like here for example it's playing the song but the UI just froze.

Version

2024.412.1

Logs

1714674827.runtime.log

[BlockHead007]

It's been reported many times above that VK is unstable for most people, so it's not just your hardware. We should wait for a fix.

[iwa]

just for info, I was running an AMD Ryzen 7 7700X with a Radeon RX 7800 XT, and using Direct3D 11 (Experimental) did indeed stabilize my fps

due to some external issues with the card I've returned it and replace it with an Nvidia one so I don't have any tracing/logs, but from what I recall:

• I was averaging 950fps with the RX 7800 XT on normal Direct3D, with drops to 750/800fps
• I was averaging 999fps with the RX 7800 XT on experimental Direct3D, with no drops at all (maybe tiny drops of like 20fps but nothing i could easily read during my gameplay)

[BlackDiamond31]

Where do I even begin with this....
Direct3D 11 and Direct3D 11 (Experimental) messed up all my colors.
Messed up HP
Messed up top right
In those images it is shown how it looks when I have ether of them enabled.
Fine top right
Fine hp
These images show how it is supposed to look like.
It also boosts the bloom/brightness by like 3x in any gui I go to (map select, editors, everything) It is like this for every skin as-well.
I know that it is not the display because no other game does that and when I run osu on my other monitor, the result is the same. If any extra information is needed then let me know.
System specs:
CPU:3900x
GPU: EVGA FTW3 RTX 3090
RAM: 32GB cl 16 3200mhz
Windows 11 leatest version

[StalkyBoi43815]

help a brotha out and drop the skin🙏

[ggtylerr]

Vulkan doesn't run for me.

OS is Nobara Linux 39 (a Fedora based) and GPU is an RTX 3050 Ti. It seems the main problem for me is that it's looking for the libraries in the AppImage's mount directory and not my actual system libraries:

2024-06-16 05:38:21 [verbose]: 🖼️ Renderer initialisation failed with:
2024-06-16 05:38:21 [verbose]: System.TypeInitializationException: The type initializer for 'Vulkan.VulkanNative' threw an exception.
2024-06-16 05:38:21 [verbose]: ---> System.DllNotFoundException: Unable to load shared library 'libdl' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:
2024-06-16 05:38:21 [verbose]: /tmp/.mount_osu.ApNqIqQZ/usr/bin/libdl.so: cannot open shared object file: No such file or directory
2024-06-16 05:38:21 [verbose]: /tmp/.mount_osu.ApNqIqQZ/usr/bin/liblibdl.so: cannot open shared object file: No such file or directory
2024-06-16 05:38:21 [verbose]: /tmp/.mount_osu.ApNqIqQZ/usr/bin/libdl: cannot open shared object file: No such file or directory
2024-06-16 05:38:21 [verbose]: /tmp/.mount_osu.ApNqIqQZ/usr/bin/liblibdl: cannot open shared object file: No such file or directory

Unfortunately the regular OpenGL renderer seems to be very choppy, maxing out at 45 FPS. If I set the frame limiter to anything higher than VSync (note, my monitor is 144Hz) it says it's rendering at 240+ FPS, but the actual input and display is incredibly choppy, somewhere between 15-30 FPS.

Full runtime log in case it's needed.

[Glebsin]

I can say that on the latest version of nvidia drivers (556.12) vulkan stopped working when going to gameplay from song select, but working in gameplay of skin editor.
537.58 version of nvidia drivers works perfectly for me, but can sometimes crash in rare cases
OS: Windows 10 22H2
GPU: GTX 1660 Super

[mangkoran]

Hi thank you for your comment. I also would like to add here that 537.58 performs more stable and way less stutter compared to newer drivers. I tested with DX11, DX11 (exp), Vulkan (exp) (all SDL2). I also tested using SDL3 and it seems help the stability a bit too.

OS: Windows 10 LTSC 21H2
CPU: AMD 4800H
GPU: 2060 Laptop

[tl27863]

Been using Vulkan, pretty good experience so far 0 stutters while in gameplay

Though experienced a bug where using a 144hz screen with frame limiter set as 2x resulted in 576fps max on single thread
while its 288fps as expected on multithreaded

Logs
compressed-logs.zip

Lazer 2024.725.0

CPU: Ryzen 7 6800H
RAM: 16GB DDR5 4800MHZ
GPU: Nvidia RTX 3050 4GB(555.58)
OS: Fedora Workstation 40 (Kernel 6.9.9)
DE: Hyprland

[DaVince]

Just for completeness sake, I'll include a reference to my report on #29267. Works fantastic on Steam Deck until you invoke the compositor in desktop mode somehow. Other than that, the Vulkan renderer has provided me with zero lag spikes and very low latency (aside from some brief moments while menu-ing).

[copecone]

For Intel Arc GPU, Vulkan renderer is working way more smoother than other renderer and absolutely has no problem.

[ZenoG2]

[Vulkan] Weird, artifact-like issues when switching resolution.

Bug description

When switching resolution, the game causes weird artifact-like bars to pop up. This is not a hardware issue and is only present in the Vulkan renderer.

Screenshots or videos

Unfortunetly, this bug (somehow) does not appear on OBS, so I had to record it manually with a camera...
https://youtu.be/NjqY3smA7nA

Version

2024.906.1

Hardware

OS: Windows 11
CPU: Intel core i7 7700K
GPU: AMD RX 6600

Logs

compressed-logs.zip

[kichirouhoshino]

Vulkan runs better for me than OpenGL in Linux. The only issue is that there is no screen tearing even when selecting non-vsync framerate options. This is probably why the others said that the mouse felt laggy or delayed even if the FPS is 240+.
I can work around this by using something like libstrangle, which forces osu! to disable vsync.

Vulkan apps on Wayland now supports screen tearing (both native and xwayland). I've seen other games using SDL that could do screen tearing.

OS: Fedora Kinoite 41
DE: KDE Plasma 6.2.2
CPU: Ryzen 5 5500U
GPU: AMD Integrated Graphics (RADV)