3 ms·
What is the "hell" here? Just the fact that extensions exist? From where I'm standing the only real problem with extensions in OpenGL is that they are all enab
by account42 6y ago
What is the "hell" here? Just the fact that extensions exist?
From where I'm standing the only real problem with extensions in OpenGL is that they are all enabled by default so it's easy to accidentally rely on one that happens to be supported by the hardware/driver you are testing on. This is not the case with Vulkan where you explicitly need to ask for the extensions you want.
- pjmlp 6y agoThe fact that the code ends up with so many execution paths, that it is hardly any better than having plugin abstraction rendering layer using the native 3D API for each target platform. And everyone ends up writing their own extension loading framework anyway, because feature X differs on extensions across GPUs and the same high level call should be orthogonal to the loaded extension.
- Jasper_ 6y agoTo be clear, pjmlp, I don't think you've ever written a Vulkan app, ever. You don't need an "extension loading framework" on Vulkan (you might be confusing something like volk with that), since the loader is standardized, and a lot of the extensions are for very minor things or IHV moon-shot ideas, or are rolled into the maintenance extension. Vulkan has a lot of faults, but this is such a weird complaint.
- pjmlp 6y agoSince we are pulling credentials here, I have written enough of Metal, OpenGL, OpenGL ES, DirectX (5 - 12), WebGL, XNA, Unit, Java3D, M3G, PHIGS, Glide, Amiga and PC demoscene low level coding, to be able to evaluate Vulkan when going through books like Vulkan Cookbook and NVidia GTC sessions, but yeah, maybe I just don't get it.
- flohofwoe 6y agoThe problem is that there are dozens (hundreds?) of extensions adding very tiny vendor-specific features all over the place, so your code feathers out into vendor-, GPU- and driver-version specific code paths, the "hell" there is maintaining and testing such code. So instead of one "Vulkan API" you have a mess of sub-APIs which offer different features on each device, that's the opposite of a "cross-platform API" that Vulkan apparently wants to be. Other APIs group capabilities into a very small matrix of API versions and feature levels which keeps the amount of optional code paths very small or in many cases eliminates the need for them completely.
- Firadeoclus 6y agoWith Vulkan you can choose to have a small matrix of feature levels and thus few optional code paths. Or you can have many. That choice is up to you. Whereas if the API defines feature levels, it isn't.
- account42 6y agoVulkan does have versions too that provide bundled feature upgrades - no one is forcing you to use evey extension just because they are available. The same is/was true for OpenGL except for the large time window between 2.1 and 3.0 - you can write perfectly functual code without using any vendor extensions. Think of extensions more as a) a testing ground for bleeding edge features and b) a way to expose functionality that is truly specific to some hardware.
- pjmlp 6y agoLatest Vulkan version is 1.2, if you want to target Android since version 7, then good luck. https://developer.android.com/about/dashboards#Vulkan https://developer.android.com/about/dashboards#Vulkan https://vulkan.gpuinfo.org/listdevices.php?platform=android https://vulkan.gpuinfo.org/listdevices.php?platform=android
- account42 6y agoSo now you want to blame Vulkan for mobile hardware variety and lack of Android updates? You can still use the lowest common denominator that is supported for all your targets. If you want to have code paths to enable more features on some devices then do that. Complaining that Vulkan gives you the freedom to choose where to make the cutoff for feature levels is pointless.
- pjmlp 6y agoNaturally, because contrary to proprietary API, and just like OpenGL, it gives free reign to do whatever OEMS feel like supporting.