Outerra Engine > Technology

Vulkan is already among us!

(1/2) > >>

zombie00:
So Vulkan is finally out, took them sometime, but if it delivers what it was promised, it should be more than worth the wait.
https://www.khronos.org/news/press/khronos-releases-vulkan-1-0-specification

I was wondering if you guys (the dev team of Outerra) was going to implement it into the engine. If I'm not wrong, Vulkan was built around Mantle, so implementing Vulkan could come around with an improvement on the performance with AMD drivers (that perform sort of poorly with OpenGL).

HiFlyer:

--- Quote from: zombie00 on February 16, 2016, 04:27:23 pm ---So Vulkan is finally out, took them sometime, but if it delivers what it was promised, it should be more than worth the wait.
https://www.khronos.org/news/press/khronos-releases-vulkan-1-0-specification

I was wondering if you guys (the dev team of Outerra) was going to implement it into the engine. If I'm not wrong, Vulkan was built around Mantle, so implementing Vulkan could come around with an improvement on the performance with AMD drivers (that perform sort of poorly with OpenGL).

--- End quote ---

I will be curious as to how this affects their ongoing performance testing.

cameni:
We don't expect big performance gains from switching OT to Vulkan (not CPU bound), and even if we very much liked to switch to a clean modern API, it's hard to justify the switch that would take us several months. For us it's mainly the question if Vulkan can really bring in better quality drivers, so we'll follow it closely and evaluate it.


--- Quote from: HiFlyer on February 16, 2016, 05:28:44 pm ---I will be curious as to how this affects their ongoing performance testing.

--- End quote ---

Our perf tests aren't struggling on the CPU side at all, it all seems to be on the GPU side. Similarly whole OT is rather GPU bound, and the agreement is that Vulkan won't help much here. However, since it's a simpler and more explicit model, the drivers *might* be better optimized. On the other hand, explicit model is more complex, and if coders start to emit bad code, vendors will likely try to optimize it in their drivers to gain over their competition ... that would be bad.

HiFlyer:
Interesting.

ddenn:
There's a very interesting post about Vukan from Ben Supnik, Laminar Research lead developer (X-plane).

Navigation

[0] Message Index

[#] Next page