Hello fellow hackers!
We are happy to announce the first release of our Vulkan API renderer tech demo. The release can be found here: https://github.com/inexorgame/vulkan-renderer/releases Please download the release and try it. Make sure to update your graphics drivers before testing!
Currently, we have a build for Windows only. We are working on a Linux build with high priority: https://travis-ci.org/github/inexorgame/vulkan-renderer/builds/674142137 There is no Mac OS build available currently. We might support Android in the future, we will see.
If you start the program, you should see something like this:
We need your feedback! Send logfiles to firstname.lastname@example.org!
We need testers! Download this alpha and try it out. You should see something like this:
- You can start
inexor-vulkan-renderer.exedirectly or you can use
- When starting with
start_inexor.bat, a logfile is generated.
- It would be nice if you could send us this logfile by mail:
- The logfile does not containt any personal information about the system.
New discord server
Join our discord! https://discord.gg/acUW8k7
What is Vulkan?
Vulkan is a new, low level API (application programming interface) for high-performance graphics programming and computing. It is seen by some as the successor to OpenGL, although it is important to state that is is very different from it. Vulkan is not just a new version of OpenGL or an extension of it. Both Vulkan and OpenGL are being developed by the Khronos Group. Like DirectX 12 or Apple's Metal, Vulkan is a low level API which allows for much deeper control over the graphics card and the driver. This offers better performance (higher FPS) due to reduction of overhead and driver guesswork during runtime. In general, Vulkan does a lot of work during the initialisation of the application but therefore reduces work during rendering. Since Vulkan is much more explicit, it is neccesary to write more code and to think about how to abstract it. Rendering a first triangle for example will take much more work than you are used to from OpenGL. The benefits of this low level design outweigh the additional effort though!
Why use Vulkan?
- Unlike OpenGL, Vulkan fits the design of modern GPUs as it is not just one single state machine.
- Vulkan is a low-level API which gives much more control over GPU behaviour. This reduces driver guesswork und avoids undefined behaviour of graphics drivers.
- The API is asynchronous and encourages multithreaded rendering. This is a major advantage over OpenGL! Vulkan also wants you to use the GPU asynchronously.
- Lower and more predictable CPU load which results in better performance and a reduction of driver guesswork.
- The reduction of CPU workload and it's improved predictability can enforce the GPU to be the limiting factor (as it should be), instead of the CPU.
- Vulkan implies memory-management to be done by the application (by you) rather than the driver.
- Vulkan is a fresh start, whereas OpenGL contains a myriad of hacks to support very rare use cases.
- Available on a variety of platforms: Windows, Linux, mobile devices and much more!
- Validation layers and diagnostics can be independently activated during development, allowing better error handling and debugging compared with OpenGL or DirectX. Upon release builds, the validation layers can be deactivated easily.
- Vulkan pre-compiles shaders to a standardised bytecode format. This again reduces driver guesswork during runtime.
- Vulkan API and most of the drivers are open source! (unlike DirectX 12 for example)
- Vulkan has layers and extensions as part of its design. For example it's easy to put steam overlay into a game simply by enabling Valve's steam overlay layer.
- Vulkan is being developed through an unprecedented collaboration of major industry-leading companies. It is not being developed by one company only (like DirectX by Microsoft). As Vulkan's motto states, it really is
- The ending of the OpenGL era has begun.
Getting into Vulkan
You really should watch these expert talks on YouTube:
GDC 2018 - Getting explicit: How Hard is Vulkan really? Dustin Land, Software engineer, id-Software.
DevU 2017: Getting Started with Vulkan Developers from Imagination, Google and LunarG.
Porting your engine to Vulkan or DX12 Adam Sawicki, Developer Software Engineer, AMD.
Vulkan Best Practices Roundtable discussion NVidia, Imagination, Qualcomm, id-Software, EPIC-games and Google.
Vulkan Memory Management Jordan Logan, Developer technology engineer, AMD.
Vulkan Memory Managenent Steven Tovey, Developer technology engineer, AMD.
Vulkan: State of the Union 2019 Developers from ARM, LunarG, NVidia.
The next tech demo will be released on April 26th, 2020.
Thanks you all, Hanni