The developer writes here, https://www.collabora.com/news-and-blog/news-and-events/crac...
> users are still served only by the proprietary driver [...] An open source Vulkan driver on Windows opens up a number of possibilities: a shared codebase across platforms, easier debugging and experimentation, faster turnaround on fixes, and a path for the community (e.g., game developers) to report problems or contribute improvements that benefit everyone regardless of operating system.
To me, the argument against a proprietary driver seems extremely weak if you're running Windows anyway, but I guess they see it more that if more game devs can run the RADV driver, they can get wider testing (or a simpler story for devs to test at least) and backdoor improvements into the Linux side?
I guess I dont understand the "a shared codebase across platforms, easier debugging and experimentation," comment. Shared RADV codebase? Or shared game engine code, at least the specific parts of the engine that target Vulkan x Radeon (how big is that really?). Similarly I guess "debugging" here is tracking down odd ball RADV bugs where you could then run it in windows to see if its a linux thing or a RADV thing?
> To me, the argument against a proprietary driver seems extremely weak if you're running Windows anyway, but I guess they see it more that if more game devs can run the RADV driver, they can get wider testing (or a simpler story for devs to test at least) and backdoor improvements into the Linux side?
Are you using an AMD driver?
Let me share my experience. One day, you wake up and your GPU driver is gone for no reason. I'm not even joking here—the recent driver update broke the driver for many users. Launch Battlefield 6, and your driver is... gone. A new driver update comes out... Launch Battlefield 6, hard freeze. Improvement. I'm still running an older "blessed" driver version for this reason, and I'm scared to update.