News for hackers. Stuff that matters.
Re:Vulkan1.3 on the M1 in 1 Month by pcwalton on Wednesday June 05, 2024 @04:14PM (#40589984)
> You then say that if they used Vulkan, it would mean they wouldn't have to debug on a Mac. This is overly optimistic.

Sure, but supporting two variants of Vulkan is less work than having to support two incompatible APIs. It's not a binary thing.

Re:Vulkan1.3 on the M1 in 1 Month by pjmlp on Thursday June 06, 2024 @03:34AM (#40594584)
The problem is that there isn't two variants, there is an extension soup of Vulkan variants.
Re:Vulkan1.3 on the M1 in 1 Month by exDM69 on Thursday June 06, 2024 @05:42AM (#40595442)
I get by just fine with "one variant" using all the Vulkan 1.3 features that are ubiquitously available on desktop (= almost all of them) platforms with up to date drivers.

The fact that there's n+1 extensions does not mean you have to support 2^(n+1) combinations. I can't recall a single situation where I would've needed even two code paths to get something done in the past few years.

Situations where you need two or more code paths only arise if you use new hardware features like mesh shaders or ray tracing. For "software" features like dynamic rendering or dynamic states (both of which simplify things a lot), there's no need for a fallback on desktop, just require a recent driver version and you're good.

That said, the mobile driver support situation and lack of long term updates is an issue if mobile support is required.

Re:Vulkan1.3 on the M1 in 1 Month by pjmlp on Thursday June 06, 2024 @05:52AM (#40595533)
> just require a recent driver version and you're good.

Easier said than done, as everyone that has experience with Khronos ecosystem knows.

It is no accident that OpenGL 3.3 is still quite common target.

Using middleware is much saner that relying on whatever Khronos does.

Re:Vulkan1.3 on the M1 in 1 Month by exDM69 on Thursday June 06, 2024 @06:07AM (#40595639)
How is it easier said than done? All three major GPU vendors (Intel, nvidia, AMD) have drivers have a very good support on all three major desktop platforms (Windows, Linux and Macos), and it goes back to quite old hardware (Intel Skylake 2015, Nvidia Maxwell 2014, not sure about AMD).

If you know exactly which driver version(s) you require, you can explicitly check it at init time, or you can just check for the feature flags and require them at init (you need to do this explicitly anyways).

OpenGL 3.3 is a popular choice only because Apple dropped OpenGL support and HW features (tessellation, etc) were required for 4.x. You don't have a situation like that with Vulkan. You get all the latest SW features even on old HW.

Vulkan's explicit extensions/features setup is much much better than OpenGL ever was, and there are no "half assed" implementations out there like there were in OpenGL days. You don't end up using a feature by accident, and then have your app not work on a platform you didn't test on. The conformance test suite is very strict, so if a feature is supported it's very likely to work as advertised, much less driver bugs than in the OpenGL days.