4 ms·
So, what are the chances of Vulkan drivers from devices makers "follow the tradition" of their OpenGL drivers and only implement half the spec with lots of bugs
by raverbashing 11y ago
So, what are the chances of Vulkan drivers from devices makers "follow the tradition" of their OpenGL drivers and only implement half the spec with lots of bugs and lack of functionality
- DominikD 11y agoHigh if Khronos doesn't provide a comprehensive certification suite. Dunno what's the status for Vulkan, but OGL/OGLES versus D3D (any feature level) is a joke. :S
- _pmf_ 11y ago> So, what are the chances of Vulkan drivers from devices makers "follow the tradition" of their OpenGL drivers and only implement half the spec with lots of bugs and lack of functionality I'd say in the high 99.99999ies
- ska 11y agoHard to say yet, but since one of the design goals of Vulkan is to address this very issue, it seems inept to assume they can't/won't improve things w.r.t drivers before there is evidence.
- Jasper_ 11y agoVulkan is extraordinarily thin. There really isn't the large complex global state machine that OpenGL has -- the potential for complex bugs are a lot less.
- raverbashing 11y agoI agree, that's what I hope, but we never know...
- runeks 11y agoGood point. Vulkan's purpose is for GPU hardware companies to stop having to write graphics software (drivers). GPU producers shouldn't be responsible for writing OpenGL compilers any more than AMD and Intel should be responsible for writing C/C++ compilers and Python VMs. As I understand it, the goal is to move the API closer to the hardware. Hopefully so close that the driver will be very thin. There are plenty of software developers out there who can implement an OpenGL driver in Vulkan as well as the employees of AMD and Nvidia, I would think.
- joshuapants 11y agoBut Intel does make a C/C++ compiler!
- bobajeff 11y agoI hope this is right. Having to rely on companies to update their drivers or open the source code has been a major pain point for a long time. Especially on mobile where there are many custom chips from different companies.
- simoncion 11y agoSure, but: If Vulkan is too low level, perf will could be absolutely terrible. If chip makers expect a third party to -effectively- write an optimizing compiler for their graphics chips, they're probably[0] gonna have to tell people a lot more about those chips than they do already. Worst case, maybe we're looking at another Itanium failure where noone decides that it's worth it to write such software. (Note: I know next-to-nothing about Vulkan and only slightly more about modern graphics programming[1]. It's entirely possible that this worry is wholly unfounded. Also, given that the open-source AMD/ATI driver exists and has decent performance, it's highly unlikely that this will be a repeat of the Itanium failure.) [0] Really, "they" is largely code for "Nvidia". :p [1] I did a fair bit of fixed-function OpenGL software in a former life, tho! Remarkable how poor and ever-changing the support for that was from one NVidia driver revision to the next.
- alexvoica 11y agoDevelopers have been asking for Vulkan for years. Essentially Vulkan and OpenGL ES provide two fundamental choices: going low level for highly tuned, architecture-specific optimizations (i.e. game engines) or high level, respectively, for quick and easy code writing that can run across multiple platforms (i.e. a simple UI or a 2D game).
- simoncion 11y ago> Developers have been asking for Vulkan for years. I would wager that a very large slice of the folks doing graphics programming are largely incapable of writing a new high-performance graphics card driver. Is there demand? Sure. Does anyone want to exert the effort required to meet that demand? I don't know. Once upon a time, the CPU manufacturers were demanding a CPU that was easier for them to design, but just as performant. This lead to the Itanium, which had a simple hardware design but required very complex compilers for optimal performance. Thing is, noone wanted to expend the effort required to make a sufficiently clever compiler in order to get the best perf possible out of the CPU. Anyway, if you can deliver more than platitudes, I'm all ears. I'm pretty ignorant on the topic and would love more information. :)
- makomk 11y agoI suspect the most intractable OpenGL ES issues on mobile have nothing to do with that state machine though. For example, some drivers have oddball hardware limitations on the complexity of shader they'll execute and silently miscompile or drop shaders if they exceed the limits. That's not going to go away with Vulkan.
- Jasper_ 11y agoThe most intractable OpenGL ES issues on mobile have to do with the large amount of state kept, requiring long pipeline flushes, complex application-level batching, driver batching, and other things. Normally, drivers try to batch up a lot of work, but being really subtle about things (calling glGet, for instance), you can accidentally cause a blocking flush of your entire state. Making applications fast involves trying to defer and hack around this state machine as much as possible, while maintaining correct behavior. As such, you end up with tons of subtle, hard-to-find interaction bugs. I've debugged and fixed some of these in a certain mobile OpenGL driver we're deploying on our platform we licensed from the vendor. This is independent from other tricky bits of OpenGL ES, like the shader compiler front-end choking on perfectly valid GLSL, because there's no compliance tests for any of it.
- _joe_ 11y agoGoogle will be porting their Android OpenGL ES conformance test suite to Vulkan and will donate the source to the Khronos group [1]. ---- For Vulkan, we’ll not only develop similar tests for use in the Android CTS, but we’ll also contribute them to Khronos for use in Vulkan’s own open source Conformance Test Suite. ---- [1] http://android-developers.blogspot.co.uk/2015/08/low-overhead-rendering-with-vulkan.html http://android-developers.blogspot.co.uk/2015/08/low-overhea...