r/programming • u/lubosz • Feb 16 '16
KHRONOS just released Vulkan
https://www.khronos.org/vulkan/188
u/sprunth Feb 16 '16
NVidia also put up a C++ API here
-3
u/jimdidr Feb 16 '16
The limited number of cards supported by the Driver(s) is very annoying. I can't use it on my Gaming Laptop (G74sx), its not very new(at all) but it still outperforms all consoles so why can't it do this.
I wonder if its a dick move or if it is actually a hard driver to make.
10
u/ffiarpg Feb 17 '16
I believe the video card in your laptop (Nvidia GTX 560M) was announced over five years ago. The hardware of the card does not support some of the functionality. Replicating it in software would defeat the purpose of the driver.
0
u/jimdidr Feb 17 '16
as with all game code that functionality would be skipped, its about having one target to code toward.
To limit the cards supported by Vulkan is exactly the opposite of the intention(or at least one of the main reasons) of the project, but I guess Nvidia still has their shitty agenda, I'm getting more and more sure I'll make sure my next machine uses anything else. Which is too bad because I like these ASUS machines.
4
u/ffiarpg Feb 17 '16
It isn't like every AMD card support Vulkan either, although probably further back than Nvidia since GCN 1.0 and up has support. Support for linux via AMDGPU will be limited to GCN 1.2 and up so I am going to miss out with my R9 290 unless open source steps in.
1
u/jimdidr Feb 17 '16
Yeah this wouldn't have been my only reason for leaving Nvidia in the dust, its just one more damn reason.
1
u/aaron552 Feb 17 '16
Support for linux via AMDGPU will be limited to GCN 1.2 and up
FWIW, AMDGPU also supports GCN 1.1 cards with a compile-time parameter.
Also, once the Catalyst code dump is trimmed down and merged into the kernel, it wouldn't surprise me if AMD extended AMDGPU to support all their GCN cards (or whatever is on their "supported" list at that time)
6
u/dagmx Feb 16 '16
Probably just a smaller user base to support makes it easier to support at first.
2
u/Izlanzadi Feb 17 '16
I wonder if there is something in the specs, or if both Nvidia and AMD both opted to only support their latest architectures. AMD require GCN architecture (so HD7700 & up) and Nvidia require Kepler/Maxwell (so GTX600 & up) both of these minimum cards are the same generation so the thought crossed my mind that it might be some hard requirement in the spec.
0
Feb 16 '16
[deleted]
82
u/Dworgi Feb 16 '16
C. Most low level APIs are.
3
u/BurstYourBubbles Feb 17 '16
Do you know why such APIs are in C? Why not C++ if performance is similar?
22
u/Dworgi Feb 17 '16
Bunch of reasons:
Not all languages have objects, but all can call into a plain function.
C is lower level. Things are as fundamental as they can be - you're mostly passing around pointers here. Every language is ultimately aware of pointers.
C has a cross-platform binary interface. All standard compilers will produce the same libraries, which means it's easy to just share headers and libraries. C++ is a wild west.
It's easy to wrap C with objects, it's much harder to unwrap objects into functions.
3
u/BurstYourBubbles Feb 17 '16
You reasoning makes sense but how is C lower level than C++? IIRC (please correct me if I'm wrong) C++ still maintains Cs low level features while also including high level abstractions.
13
u/Dworgi Feb 17 '16
Why use the superset if you'd only use the subset?
Plus, ABI compatibility is huge - if you write code that depends only on C standard libraries and compile it on Linux with a standards-compliant compiler, I can link to that code on Windows and use it without problems.
C++ library usage is hampered by the lack of this standardisation, which means you have to share a dozen versions of your code for different compilers and operating systems. Really, you probably need to share your source code in its entirety.
7
Feb 17 '16
Object-oriented programming is inherently higher level than procedural programming, because it abstracts stuff as objects.
5
u/BurstYourBubbles Feb 17 '16
However, C++ isn't strictly object-oriented. You could employ other programming paradigms, such as procedural or functional.
→ More replies (17)1
u/bigjeff5 Feb 19 '16
If you code in C++ but don't use any C++ features, you're just coding in C. You can change that filename from a .cpp to a .c and compile it as straight C.
If you're coding in C, why would you call it C++? It's C.
19
u/u_suck_paterson Feb 17 '16
To allow externing to any non c language through stdcall . Ie c#
→ More replies (2)3
Feb 17 '16
C can code can run marginally faster than C++ in most cases, if the programmer does a lot of hand optimization. Also if it's written it C, it makes it quite easy to write a C++ wrapper (like this one).
1
u/silveryRain Feb 17 '16
I doubt that performance is even relevant here, it's just an API for the GPU as far as I know.
1
u/wrosecrans Feb 18 '16
Compiler ABI's are less stable for C++. If you want to mix a Visual Studio 2012 library with a Visual Studio 2015 project, you are likely to run into linking problems. And that's just a single product from the platform vendor. Making it a C API means you don't need specific versions of the libraries for specific compilers.
Plus, you can use it from languages like C that can't easily call C++ code.
0
u/jeffsterlive Feb 17 '16
I can tell you that on micro controllers we usually use C because the stl causes much larger binary files. Keeping the binary file small when you measure ram in kilobytes sometimes is a big deal.
As for APIs, it's likely to keep the code compact as well. Compile time is important to large projects and templated functions can bog down the compiler on slow machines.
24
37
20
35
u/Jajoo Feb 17 '16
Javascript, obviously
12
9
1
105
Feb 16 '16
[removed] — view removed comment
104
u/quarkman Feb 16 '16 edited Feb 18 '16
Because the API constant shorthands for Vulkan are VK_*. Look at the OpenGL spec. You'll see GL_, NV_, EXT_, GL_EXT_, etc... all over the place.
Why _cpp.h? Because Nvidia naming conventions most likely don't allow for the .hpp extension to keep the whole codebase consistent. It's common for large companies to use a very restricted naming convention.
Edit for formatting.
2
u/Godd2 Feb 18 '16
You can escape asterisks in comments with a backslash so that there isn't intermittent italicization.
\*a\*b\*c\* -> *a*b*c*
whereas
*a*b*c* -> abc
1
86
u/3669d73f6c3ba0229192 Feb 16 '16
Yeah at that point they might as well just have called it
robert.h37
Feb 16 '16
Why the hell didn't they?
148
u/Sydonai Feb 16 '16
Because then Github would have sent them C&D letters for using gendered file names. /s
→ More replies (3)5
-1
32
Feb 16 '16
This is nice.
One nice thing though is that they use stdint.h types.
Looking through the header their supported surfaces are: X11, XCB, Wayland, Mir, Android, and Win32. Most of the header is just constants and structures.
59
u/Nimbal Feb 16 '16
Aww, the SDK downloads end up in a 404.
25
u/Overv Feb 16 '16
Replace "pub" in the link with "v1" and it works. (You do still need to be logged in.)
12
u/badsectoracula Feb 16 '16
Also sadly the "Loader and Validation layer code" stuff seem to reference internal repositories (not to mention that it has a convoluted build process...).
I think i'll wait until things clean up a bit :-p
2
48
u/Tipaa Feb 16 '16
Damn, the site must be getting hammered. 5 minute load times.
Anyway: nVidia's Vulkan page
11
14
Feb 16 '16
So hoping this works out properly. I'm sick of having to completely reboot my computer to switch between a comfortable working environment and good gaming performance.
0
u/Yojihito Feb 17 '16
For that Nvdidia/AMD would need to support their Linux graphic drivers better. I don't see that in the near future because it didn't happen in the last 10 years.
49
u/manvis Feb 16 '16 edited Feb 16 '16
Wanted to download the beta drivers from Nvidia's site and play around with the samples. Unfortunately, the page says that the drivers only support Kepler and Maxwell architectures. Unless I'm mistaken, Fermi was also supposed to have Vulkan support. Anyone knows if it got dropped or if it's a beta only limitation?
EDIT: Yup, only Kepler architecture and up are supported by NVidia http://www.anandtech.com/show/10035/vulkan-10-released
Sucks to be a broke university student with a 5 year old GPU.
14
u/tamyahuNe Feb 16 '16
Those slides referenced in the article say that Vulkan will work on hardware that currently supports OpenGL ES 3.1 or OpenGL 4.X and up.
31
Feb 16 '16
That's nice, but if nvidia doesn't release a driver for it they will never support vulkan.
17
u/mindbleach Feb 16 '16
Open-source drivers are a real possibility, since part of Vulkan's appeal is simplified driver development.
4
u/CalcProgrammer1 Feb 16 '16
Hopefully a Mesa implementation for Nouveau/RadeonSI/r600g comes along soon, AMD isn't supporting TeraScale/VLIW cards even though they are DX11/GL4.x capable either.
1
u/heywire84 Feb 16 '16
There is a beta driver here if I am not mistaken:
8
Feb 16 '16 edited Feb 17 '16
Maybe read the whole thread you are replying to. (We are talking about pre-Kepler gpus, which theoretically have the capabilities but there is no driver or any indication there will be one.)
EDIT: It seems khronos haven't yet defined capability levels, so they might be waiting for that for the older cards. Maybe.
7
Feb 16 '16
It should theoretically, but realistically, Nvidia doesn't seem to want to put in the man power to write the drivers for it
10
u/Berjiz Feb 16 '16
Is Vulcan going to be useful for HPC?
5
u/SantaCruzDad Feb 16 '16
That's what I'd like to know too - it it just for games and 3D graphics etc or can it be leveraged for HPC GPGPU stuff ?
7
4
Feb 17 '16
Vulkan has ways of doing computation and drawing without presenting it to the screen, or even having a display server installed (speaking in linux terms).
3
u/Godspiral Feb 16 '16
It integrates opencl and opengl (replacements) into the same api. I don't know what it does better than just opencl2.0, but from what I understood, you can mix opencl code with it.
2
35
u/GYN-k4H-Q3z-75B Feb 16 '16
Just yesterday I (developing DX12 and OpenGL 4+) came across some post mentioning Vulkan. I was like, hell I am gonna dig up some code samples. But there wasn't anything on the web. Today there is and I am traveling all week on business. There is no god lol
15
1
77
u/Krohnos Feb 16 '16
Thought this was about me for a second
49
u/hinckley Feb 16 '16
I thought it was about a peace deal with the Federation.
6
u/DemonicSquid Feb 16 '16
Thought my watch had stopped...
14
u/NewbornMuse Feb 16 '16
I thought the Titans broke out of the Tartarus and picked up infrastructure programming.
0
8
Feb 16 '16
Is Vulkan another API like OpenGL or DX? Or is it a new language like OpenCL?
7
u/JamiesWhiteShirt Feb 16 '16
It is an API like OpenGL or DirectX, with the main difference being that as a new specification, legacy functionality can be left behind. In addition, Vulkan allows much more granular control of the GPU.
OpenCL is slightly different. It is both an API and a language which is designed for doing non-graphical computations on the GPU.
2
2
u/nosmileface Feb 16 '16
It is another API - yes.
For shading/computing purposes, instead of defining a language it defines a low level binary code, sort of like LLVM IR, it's called SPIR-V. There is a GLSL -> SPIR-V compiler. And I'm sure HLSL -> SPIR-V will be available also. Industry likes HLSL (e.g. UE4 compiles their HLSL shaders to GLSL on opengl platforms).
19
Feb 16 '16 edited Feb 16 '16
[removed] — view removed comment
4
Feb 16 '16
Never worked with Shaders. As someone who works using OpenCL purely for a computation standpoint, 0 graphics related. Does this effect me?
27
u/coffeepot- Feb 16 '16 edited Feb 16 '16
Here are Vulkan bindings for Nim.
14
u/filwit Feb 16 '16
I know what I'm doing today!... working.. I'll be working... BUT LATER TODAY!!
8
6
u/Tipaa Feb 16 '16
Full spec's now loading properly https://www.khronos.org/registry/vulkan/specs/1.0/xhtml/vkspec.html
19
u/mocahante Feb 16 '16
ELI5 What this is and why it's significant?
40
u/Calavar Feb 16 '16 edited Feb 17 '16
Existing graphics APIs like Direct3D and OpenGL are high level. You give a command like "draw this batch of triangles." But are you about to send 100 more batches, or is this the only one? Because the API is so high level, there is no way for the graphics drivers to know. So the drivers use internal heuristics to make a guess. And based on the guess, the drivers will follow different code paths or flip certain switches or settings on the graphics card in order to optimize performance. In other words, these APIs are black boxes.
Unfortunately, these black boxes have given rise to "black magic" on the part of game programmers. In an effort to eke out that last bit of performance, lots of big name software (including most game engines), uses a variety of ugly hacks to try to force the graphics drivers' internal heuristics to go one way or the other. But very few people really understand the internals of the drivers, so these coding acrobatics often have the reverse effect and lead to less performant code.
Vulkan is a lower-level API that exposes more of the internal workings of the graphics card with the goal of eliminating some of this "black magic" code.
You can find an in-depth explanation of the problems with Direct3D and OpenGL in this forum post.
tl;dr: Vulkan is closer to the graphics card than OpenGL or Direct3D, which allows a finer degree of control at the expense of increased complexity.
1
u/flexiverse Feb 16 '16
It's like an open source version of Apples METAL giving you direct access to the GPU. I'm assuming new drivers will appear for OpenGL and directX. I see it as essentially to get rid of direct X so people have direct open control of GPUs at the lowest level.
I guessing most coders will be hidden from these complexities it's only of interest to driver creators and 3D engine designers.
2
u/crusoe Feb 17 '16
This will hopefully bring stability and performance to Linux drivers as well since they can be simpler. Mesa for opengl will set on top of vulkan and others will simply directly use the api.
1
u/flexiverse Feb 17 '16
Certainly a big step towards to cross platform standards. Quite exciting for Linux the one thing it sorely needed was this! Now maybe they'll support vr on Linux ! (Oculus)
0
Feb 16 '16
[deleted]
10
u/TheZahir_NT2 Feb 17 '16
:/
That answer managed to be both condescending and less comprehensible.
1
1
9
u/pali6 Feb 16 '16
If you are interested in Vulkan you might want to subscribe to /r/vulkan subredit.
9
4
Feb 16 '16
Cool i was waiting for it. So will the OpenGL die??
43
u/manvis Feb 16 '16
No, it won't. OpenGL will still be supported and even recommended if the application is not driver limited.
3
Feb 16 '16
Most of the new games will be using Vulkan instead of OpenGL. Wont this affect OpenGL slowly and kill it one day?
43
u/badsectoracula Feb 16 '16
Considering that most of the new games used Direct3D for several years already without OpenGL dying, it doesn't seem like this will change.
Besides OpenGL is used for more than games. Many tools, CAD, etc are built with it and this wont change any time soon.
4
u/zer0t3ch Feb 16 '16
I wonder if programs like CAD and 3d modelers (like Blender) would be a leader to get better performance by switching to Vulkan.
3
u/badsectoracula Feb 17 '16
Vulkan helps developers to do the drivers' work in case the driver is the bottleneck, but if a program isn't bottlenecked on the CPU by its communication with the GPU then it wont benefit much. For cross platform programs like Blender, it might help with performance on AMD GPUs on Linux though because of AMD's slow OpenGL implementation there. But beyond that i don't think those programs are bottlenecked by the driver.
15
7
u/eras Feb 16 '16
Maybe OpenGL drivers of the future will be based on Vulkan as well?
4
Feb 16 '16
Most likely. If something kills OpenGL, it's more likely to be another competitor sitting on top of Vulkan than Vulkan itself.
1
u/CalcProgrammer1 Feb 16 '16
Yeah, with Vulkan being low level it should hopefully be possible to make a cross-platform, cross-driver OpenGL stack (and D3D8/9/10/11 stack) on top of Vulkan.
5
u/way2lazy2care Feb 16 '16
I thought the idea was that you'd use vulkan where it made sense and opengl where it made sense the same way you can use C++ where it makes sense but inline assembly where you need specific performance optimizations.
2
Feb 16 '16
Well iam a linux user and Direct3D doesn't exist for me. :)
1
u/CalcProgrammer1 Feb 16 '16
Gallium-Nine, it's D3D9 implemented on top of Gallium3D for native D3D9 support, which can be used as its own 3D API for Linux native software or through Wine. It works pretty well on Radeon cards!
0
-12
u/ArchiDevil Feb 16 '16
Most of new games will use Direct3D 12, not OpenGL or Vulkan :)
1
Feb 16 '16
[removed] — view removed comment
→ More replies (1)2
u/ironnomi Feb 16 '16
Well the PS4/Nintendo (Yeah right)/Mobile ports won't necessarily use DirectX. There's basically two libraries for N/PS4 - one that's basically OpenGL and one that's low level. Some games use the OpenGL one and they'll likely get OpenGL ports. The others could actually be ported to Vulkan. Mobile ports are mostly OpenGL since they are already using OpenGL.
4
Feb 16 '16
[removed] — view removed comment
1
22
u/Asyx Feb 16 '16
People are still using legacy OpenGL so nope.
I remember there was a talk on the last GDC where they've been playing around with the first specs (like, driver developers. AMD and Valve was there as well) and that typical computer graphics "hello world" where you just render a red triangle or something took them a few 100 lines.
Just like the core profile, the focus is more on performance. It will be very annoying to get something simple going just like it was for the core profile. Writing shaders, using VBOs and stuff like that is overkill for something that takes you 6 lines in legacy OpenGL.
This will be the same. Vulkan goes a lot lower than OpenGL. It basically replaces part of the OpenGL driver because this was a huge issue in the past. Developers were cheesing around with the driver to the point that Nvidia and AMD had to sit there fixing the shit the developers wrote because they thought they were clever (there's a post of gamedev.net or the game dev stackexchange of an intern explaining why gpu drivers are so big).
Vulkan is supposed to fix that. Instead of cheesing with what AMD of Nvidia wrote, the developers now have to write the stuff they used for cheesing themselves.
That also means that you have to do a lot of prep work (like you had to compile shaders and bind buffers in the core profile). So OpenGL will still be the go to option for hobby and independent developers that just can't or don't want to invest a lot of time into dealing with Vulkan.
33
u/Zakman-- Feb 16 '16
(there's a post of gamedev.net or the game dev stackexchange of an intern explaining why gpu drivers are so big).
https://www.gamedev.net/topic/666419-what-are-your-opinions-on-dx12vulkanmantle/#entry5215019
3
u/Kealper Feb 16 '16
That was a really good and insightful read, definitely worth reading it completely instead of skimming it.
1
u/Shurane Feb 16 '16 edited Feb 16 '16
That is frankly, frightening to know.
Definitely wish there were some code samples involved to trigger fast/slow paths of driver code, that would have been the icing on the cake.
4
u/monocasa Feb 16 '16
I remember that if you renamed the old school benchmark/sample "TUNNEL.EXE" to "FUNNEL.EXE" it'd more than halve the framerate.
1
u/hakkzpets Feb 16 '16 edited Feb 16 '16
I don't know that much about coding, but how exactly does it work when GPU drivers solve shitty coding from game devs?
Does the driver patch the game code or how does it fix a problem like this?
D3D9 game never even called BeginFrame/EndFrame
Or does the driver work like it just forces those calls to be made? Wouldn't that quite easily make for some giant bugs depending on how the game devs made their code?
1
Feb 17 '16
Not to use a car analogy but think of it as tuning an engine, but instead of directly manipulating the engine itself you figured out that by shoving a sock in your radiator you get 10 extra horses, so then your car manufacturer decides this is beneficial so they go ok we'll... You know this is a horrible example.
Basically game engines do hacky tricks to push up performance, so eventually the driver writers go "well let's just not make it a hack for this game" and implement specific operations for that game in the driver.
2
2
u/ss4johnny Feb 16 '16
With Firefox, I'm getting messages that the https is configured improperly on their site.
2
1
u/Quicksilver_Johny Feb 17 '16
Odd, it appears fine, and I don't see any errors. What version of Firefox/what errors?
2
u/atomicxblue Feb 16 '16
I haven't been following Vulkan that close, but I wasn't expecting to see it released until at least the summer. I'd be curious to see how many devs switch to this instead of staying with OpenGL or sticking solely with DX.
-9
u/MustafaTaleb Feb 16 '16
This comment is going to be hated but here it goes anyways: I doubt many will switch over to vulkan compared to DirectX12. The reason: from an AAA publisher and a developer perspective there is not much to gain compared to what is there to lose when considering switching to vulkan. Vulkan, as you might've realized is not going to be supported by the second largest desktop OS (OSX), and supporting single digit market shares is a benefit that is outweighed by its cost. The cost is that vulkan is not competing with DirectX, it is competing with Direct3D. Directx includes so many useful libraries to handle sound, input, asset management, as well as the Direct3D API. Finding alternatives to these different APIs is not easy. Especially when the previous version of the game (which the next will probably be based on) probably uses DirectX.
4
u/redsteakraw Feb 16 '16
They gain Android, Nintendo NX, Steam OS and Windows 7/8 support basically for Free. This is worth the time because you can deploy it on more platforms and reach more windows users as well. As far as OSX / Apple they can be dumped if they are not on board, pressuring them to switch would be good no one wants an API per platform nonsense.
3
Feb 16 '16
Engine makers are already onboard with Vulkan and for them I means potentially being able to drop DX in the future in favor of a unified back end across desktop as well as mobile so really it doesn't really matter what else DX has as it's already abstracted such as for consoles.
-1
u/MustafaTaleb Feb 16 '16
That is a great point, but when looking at the benefit of low level api access, doesn't a higher level engine defeat the purpose (besides the fact that the engine itself might perform better)?
1
Feb 16 '16
No because it reduces the engine overhead. The effort for performance still goes down as pretty much every random game uses as modified engine anyway.
Main issue here is speed for effort. Engines amortize that cost.
3
Feb 16 '16 edited Feb 17 '16
Really? DX12's been out for 3/4 of a year now, and the only DX12 games are still to be released. Most of them next month or in the summer. Vulkan's been out for... Hours? And we already have The Talos Principle, and DoTA 2 is expected to be getting a Vulkan update in the coming days. I know, they had time to prepare for Vulkan prior to its release, but I think it was the same for DX12 as well
2
Feb 16 '16
Well I would think that having both vulkan and sdl would solve most of the constraints that directx has while still being smaller and easier to learn.
6
u/ashfixit Feb 16 '16
Looks like khronos has forsaken GCC favor of LLVM.
About time.
6
u/Enamex Feb 16 '16
Why?
I don't know any specifics and am genuinely curious why LLVM in your opinion is a better (recommended?) compiler/target for Khronos to use for something like Vulcan.
6
u/GLneo Feb 16 '16
BSD licence works better with some kinds of proprietary integration that will happen within the drivers.
2
u/ashfixit Feb 17 '16
The llvm/clang suite has amazing qualities aside from the bellyaching about it's licensing. The llvm system decouples compilation from machine specific machine language assembly generation and provides an intermediate representation on which one may attempt any number of brave optimizations or cowardly correctness verifications.
Clang, the compiler, provides excellent and fast feedback about program optimization, syntax and correctness. You can have static analysis too.
Llvm as the back end of this can generate machine code correctly optimised for varied targets including gpu's, vector simd's, polyhedral parallel targets, embedded metal and regular old CPUs.
2
1
u/puppetofuniverse Feb 17 '16
Android Vulkan Page looks really sad https://developer.android.com/ndk/guides/graphics/index.html
1
u/Myzzreal Feb 17 '16
As a newbie to 3D graphics, is this at the stage where I could try to accomplish a "hello world" (triangle on screen)? Probably with the use of some tutorial of sorts? Or is it too early and I should wait?
1
u/snk_kid Feb 17 '16 edited Feb 17 '16
I'll say probably too early for a beginner, not to say that it's impossible but for an API like Vulkan these are going to assume your very familiar with the graphics pipeline, shaders, a bit of knowledge about GPU architectures, and good working knowledge of concurrency because at the very least you will need to deal with all sorts of synchronization with a lower-level API.
I'd say for now stick to learning with modern OpenGL or directx 11 until you get to an intermediate-advance level.
1
u/Exallium Feb 17 '16
So, I have very little graphics programming experience.
In terms of personal development, am I better off learning OpenGL or Vulkan at this point? Given I'm a professional android developer by trade, and a computer engineer by degree.
My primary concern lies in not necessarily knowing all of the fundamentals. Doing my own memory management doesn't scare me, as C was my bread & butter through University, and I've done some CUDA development.
I have to keep in mind as well that if I ever wanted to use this knowledge professionally, I need to be able to go back several API levels with respect to Android in order to support all of the right platforms.
1
Feb 18 '16
Learn some OpenCL first. It'll give you an idea of a configurable pipeline (without all the nice bells and whistles of CUDA).
1
1
u/linuxjava Feb 16 '16
TLDR about vulcan and what it means for i) gamers ii) programmers?
9
u/smiddereens Feb 16 '16
More direct and granular control of the graphics hardware for programmers, which hopefully will translate to more efficient rendering (i.e. higher frame rates on the same hardware) for gamers.
1
u/aaptel Feb 16 '16
lots of low-level boilerplate to write (but infinitely more control) as far as ii) is concerned
4
Feb 16 '16
[removed] — view removed comment
1
u/Shurane Feb 16 '16
If I understand correctly, both ATI and Nvidia will be supporting Vulcan? And Vulcan is a next generation OpenGL that also happens to be more low level and give developers more control over the GPU?
2
u/0pyrophosphate0 Feb 16 '16
Everybody except Apple will be supporting this. Microsoft would rather not, but there isn't much they can do about it.
0
0
u/Dirty_Rapscallion Feb 16 '16
Could I get an ELI5 for wjhat Vulkan is and why it's such a leap forward?
5
Feb 16 '16 edited Feb 16 '16
It's a DirectX 12 equivalent API that's cross platform, instead of being locked to a single system (Win10).
Also it means Valve can finally release new games because they have given DX12 the middle finger.
1
u/EagleDelta1 Feb 17 '16
Both DX12 and Vulkan are "based" on AMD's Mantle. They are both "based" in that AMD helped MS work on DX12 due to their experience working on Mantle and AMD actually donated the Mantle source code to Khronos for Vulkan
1
-18
u/mb862 Feb 16 '16 edited Feb 16 '16
VkSomeFunction
Upper-case, lower-case, upper-case? Who the heck decided this?
13
u/__konrad Feb 16 '16
VK - const, Vk - types, vk - functions... easy to remember (at least for Java devs ;)
6
u/Sean1708 Feb 16 '16
/u/mb862 meet camel case.
0
u/mb862 Feb 16 '16
CamelCase for the namespace abbreviation though? I've only seen all-lowercase (glSomeFunction) and all-uppercase (UISomeFunction).
3
Feb 16 '16
Well, since you mention OpenGL, see glDrawArray (function) vs GLfloat (type)
1
u/mb862 Feb 16 '16
Which is exactly the pattern Vulkan breaks. GL is either all-lower or all-upper with the "GL" text.
1
u/CommandoWizard Feb 16 '16
It appears to be fairly common; one example is Rust (they use it in the standard library).
I prefer it too, I think
XmlHttpRequestis more readable thanXMLHTTPRequest.Edit: I had to re-read the latter a few times, because I thought I had misspelt it -- I guess that can be a testament to why I don't use that style.
1
u/ferrousoxides Feb 16 '16
It's actually
XMLHttpRequest, there's a vaguely practiced rule that acronyms should not be uppercased in names except as the first word. But it's not applied consistently (e.g.toDataURL()).1
u/Sean1708 Feb 17 '16
It's actually
XMLHttpRequestI think his point is that
XmlHttpRequestlooks better, not that it is the correct name.2
u/smiddereens Feb 16 '16
-2
u/mb862 Feb 16 '16
It is trivial, but it's a trivial decision that's going to add up to hours of pain in the ass case considering, especially given how similar lower- and upper-case V and K are.
0
-5
Feb 16 '16
There's got to be five or six other subs you could have posted this in.
5
-3
148
u/MarkyC4A Feb 16 '16 edited Feb 16 '16
I'm not in game dev, but I was really hoping to take a peek at the sample code.
Oh well, at least we can peruse the Loader and Validation layer code and demos.