RadeonSI OpenGL vs. RADV Vulkan Performance For Mad Max

[andre30correia]

AMD shut down the proprietary driver and put the resourges in open-source driver, it's simply stupid they having two implementions. They need to look at Intel one driver for linux after some years of investiment they have a good driver (only need to mature vulkan and beignet)

[darkbasic]

they have a good driver (only need to mature vulkan and beignet)

The same is true for AMD... (even if anv and beignet are in a better shape than radv and clover, especially for the second one).

[agd5f]

AMD shut down the proprietary driver and put the resourges in open-source driver, it's simply stupid they having two implementions. They need to look at Intel one driver for linux after some years of investiment they have a good driver (only need to mature vulkan and beignet)

I agree that it doesn't make sense to have two implementations. AMD doesn't have two vulkan implementations, we have one. It just hasn't been open sourced yet.

[mitch074]

I agree that it doesn't make sense to have two implementations. AMD doesn't have two vulkan implementations, we have one. It just hasn't been open sourced yet.

Well, maybe AMD doesn't consider RADV worth consideration, but since it's pretty much the only workable Vulkan driver for AMD hardware when gaming, then it means AMD doesn't have ANY Vulkan driver under Linux.

Either that, or please open source your Vulkan driver pronto otherwise it'll be deemed irrelevant and simply rejected from Mesa when you finally do.

[marek]

Well, maybe AMD doesn't consider RADV worth consideration, but since it's pretty much the only workable Vulkan driver for AMD hardware when gaming, then it means AMD doesn't have ANY Vulkan driver under Linux.

Either that, or please open source your Vulkan driver pronto otherwise it'll be deemed irrelevant and simply rejected from Mesa when you finally do.

It won't be part of Mesa. Also, having multiple drivers for the same hardware and API is normal in Mesa. The Mesa community doesn't reject stuff like that. It's more open and welcoming for everybody.

[agd5f]

Well, maybe AMD doesn't consider RADV worth consideration, but since it's pretty much the only workable Vulkan driver for AMD hardware when gaming, then it means AMD doesn't have ANY Vulkan driver under Linux.

We already have a vulkan team and a vulkan driver that supports multiple OSes. If we wanted to support radv, we'd need to hire a bunch of additional developers to support it. That doesn't make much sense.

[mitch074]

We already have a vulkan team and a vulkan driver that supports multiple OSes. If we wanted to support radv, we'd need to hire a bunch of additional developers to support it.

You have a team working on your Vulkan driver, but it's in effect unusable. RADV is usable, and you're not currently paying for its support. That makes even less sense.

@Marek: I don't understand - RADV is currently shipping with Mesa, so it's part of it, right? Or are you talking about AMDGPU-PRO's Vulkan driver? As for Mesa accepting several drivers, it may be so but more often than not only one is built by default. The one that isn't sooner or later ends up like a slice of pizza forgotten at the back of the fridge.

It's like radeonhd/radeon all over again.

[darkbasic]

We already have a vulkan team and a vulkan driver that supports multiple OSes. If we wanted to support radv, we'd need to hire a bunch of additional developers to support it. That doesn't make much sense.

So you finally made your choice on the matter? Because it's the first time I hear such statement, instead I always heard something like "we will evaluate which stack to support when we will have some more time to invest on Vulkan".

[xpander]

Can't understand that. On my R9 380 on OpenGL (Normal settings) I can barely reach 20FPS in the first 10 minutes while in Vulkan-Mode (RadV-git, Manjaro) on "Very High"-setting I'm with 40-60fps. Maybe you should consider to use mid-range hardware more often

whats your CPU? this game is heavily cpu bound in opengl, singlethread perf is the thing that makes difference. Micheal has 7700K @4,5ghz, that will chew through that bottleneck .

[bridgman]

So you finally made your choice on the matter? Because it's the first time I hear such statement, instead I always heard something like "we will evaluate which stack to support when we will have some more time to invest on Vulkan".

With respect, I don't think we have ever said anything like that.

What we have said is that we are continuing to work on open sourcing our Vulkan driver.