PowerVR Show Off Vulkan On Android, Impressive

Yes but... OpenGL ES 3.0 (2012) versus Vuklan (2015). OpenGL ES 3.2 (2015) is large better than OpenGL ES 3.0, but yeah, it's amazing !

Quoting: MohandevirIn this exemple, you can really see the load balancing between cpu cores and it's great but there's nothing about switchable gpus. They can balance the load in this aspect too, so I read, on pcgaming. They are able to give some tasks to the Intel onboard gpu while the NVidia or AMD graphic card keep its ressources to deal with the most serious tasks.

Yeah, idea is that both DirectX12 and Vulkan will remove need for artificial hardware level constructs like SLI. Graphics engines will be able to be run multithreaded, utilizing memory as they see fit. That's why all high level stuff was removed, because OpenGL was basically an engine - from times when there was no one else to draw that box on screen. Now, while I still see OpenGL being beneficial for many devs, Vulkan plus good engine will make wonders - including scenarios where it will be able spread graphics work to multiple completely unrelated graphics cards and all your CPUs.

Question: Is the word "pipeline" now obsolete?
If so, then how should we describe how a triangle
gets rendered within a Vulkan inplementation?

Quoting: Guest

Quoting: linuxgamerIndeed very impressive. Now we need some Nvidia Vulkan drivers, or at least Intel ones (Valve?).

Not until the end of the year, and it can likely be expected for nvidia, amd, intel, and on mobile platforms. Ideally, for Linux, the best place to have it is with all appropriate drivers through Gallium3D.

Not sure if Gallium3D is fitting for it. There is duplication of functionality between Gallium and SPIR-V / Vulkan. I think Vulkan drivers will be independent of Gallium3D, since there is no need for redundant abstractions.


Last edited by Shmerl on 10 August 2015 at 10:27 pm UTC

why the left side only use two core that is opengl and vulkan use four core?

Because Vulkan is having a multithreading support, which was missing in OpenGL. This is one of the reasons they made Vulkan. Is that so hard to understand?

Quoting: GuestI'm posting too much in here, but please to read the linked blog post. There isn't as much of a difference as you are expecting - they've shown essentially the worst way to do things with OpenGL ES vs the most optimal way for Vulkan. Expect possibly some middle ground - and only if the scene is CPU bound.

I created the demo. Yep you should take the performance with a pinch of salt. Not all games are going to get an instant speed boost. It will take time for game engines to support Vulkan and games that do not use engines will have to pick up the new API first.

I do think that mobile games will benefit from performance more than desktop games.

Quoting: Mohandevirbut there's nothing about switchable gpus.

I'm not sure I'm allowed to say much on this yet, but check this post: http://www.gamedev.net/topic/666419-what-are-your-opinions-on-dx12vulkanmantle/#entry5215019 for multi-gpu. :)


Last edited by ashleysmithgpu on 11 August 2015 at 8:46 am UTC

Please tell me that the garden gnomes are meant to hint at snappier performance on the GNOME desktop, when its compositor makes use of Vulkan?

(And no longer heats up one's GPU, doing nothing but showing a bunch of windows, as high as an hour-long session of SoM, or Metro?)


Last edited by wvstolzing on 11 August 2015 at 10:13 am UTC

Quoting: wvstolzingPlease tell me that the garden gnomes are meant to hint at snappier performance on the GNOME desktop, when its compositor makes use of Vulkan?

(And no longer heats up one's GPU, doing nothing but showing a bunch of windows, as high as an hour-long session of SoM, or Metro?)

It has nothing to do with it, this is an Android demo.

Holy crap, that's a HUGE difference. I did expect pretty much by Vulkan, but certainly no that much.