Vulkan 1.2

#1

Post by c89X » Thu, Jan 16, 2020, 9:41 AM UTC

Re: Vulkan 1.2

#2

Post by roenxi » Thu, Jan 16, 2020, 1:03 PM UTC

In case anyone isn't keeping up this is basically the next generation of OpenGl, but they've made enough changes to justify a new name.

Good idea too. Make it clear that they are doing things differently.

Re: Vulkan 1.2

#3

Post by rustybolt » Thu, Jan 16, 2020, 1:04 PM UTC

roenxi wrote: post #2

In case anyone isn't keeping up this is basically the next generation of OpenGl, but they've made enough changes to justify a new name. Good idea too. Make it clear that they are doing things differently.

I don't think that is a suitable way to refer to Vulkan. It's much more low-level than OpenGL.

Re: Vulkan 1.2

#4

Post by davedx » Thu, Jan 16, 2020, 1:06 PM UTC

This blog series on Vulkan is apparently pretty good (written by an id software engineer): https://www.fasterthan.life/blog/2017/7/11/i-am-graphics-and...

Talk by the same guy at GDC about porting Doom 3 to Vulkan and Stadia: https://stadia.dev/intl/en/blog/gdc-2019-session:first-light...

Re: Vulkan 1.2

#5

Post by boutad » Thu, Jan 16, 2020, 1:08 PM UTC

Does Vulkan have an answer to DirectX Raytracing?

Re: Vulkan 1.2

#6

Post by flohofwoe » Thu, Jan 16, 2020, 1:10 PM UTC

roenxi wrote: post #2

In case anyone isn't keeping up this is basically the next generation of OpenGl, but they've made enough changes to justify a new name. Good idea too. Make it clear that they are doing things differently.

Unfortunately the API update model hasn't changed much from OpenGL it seems ;)

...not talking about the idea to first test out new ideas in vendor-specific extensions, and then elevate them to the core, this is definitely a good idea - but about stacking new stuff on the previous API version, this approach is what turned OpenGL into the heap of accumulated cruft it is today.

Direct3D instead was a new API with each new major version, which in the beginning sounded insane, but turned out the better decision in the end because that made it possible to discard the cruft (the crucial part is that old API versions are frozen but still supported).

Re: Vulkan 1.2

#7

Post by flohofwoe » Thu, Jan 16, 2020, 1:14 PM UTC

boutad wrote: post #5

Does Vulkan have an answer to DirectX Raytracing?

NVIDIA offers a vendor-specific extension:

https://www.khronos.org/registry/vulkan/specs/1.2-extensions...

I guess this will first be elevated to a vendor-neutral extension and (I guess) eventually will move into the core API.

Re: Vulkan 1.2

#8

Post by boyadjian » Thu, Jan 16, 2020, 1:15 PM UTC

Im am eager to have a usable implementation of OpenGL over Vulkan, like Zink. At last, no more different implementations of OpenGL from one vendor to another.

Re: Vulkan 1.2

#9

Post by bullen » Thu, Jan 16, 2020, 1:23 PM UTC

I'm sticking with OpenGL (ES) 3 that brought VAO for life.

The returns will diminish to the point that porting or developing on new APIs does not pay for itself.

I know both Jonathan Blow and Godot are clear signs that I'm wrong, but I guess we'll just have to wait and see.

Until then I have my engine running on Win/x86 and the Pi 4 at good performance with minimal effort.

Which is good; simple software will live forever.

Re: Vulkan 1.2

#10

Post by theandrewbailey » Thu, Jan 16, 2020, 1:23 PM UTC

rustybolt wrote: post #3

roenxi wrote: post #2

In case anyone isn't keeping up this is basically the next generation of OpenGl, but they've made enough changes to justify a new name. Good idea too. Make it clear that they are doing things differently.

I don't think that is a suitable way to refer to Vulkan. It's much more low-level than OpenGL.

In addition, it has a completely different lineage than an 'updated' OpenGL. It started off as AMD's Mantle API.