Vulkan tagged news

While current generation Linux games with current Linux GPU drivers using the Vulkan API rather than OpenGL may not be significantly faster with higher-end hardware right, the impact of this newer Khronos graphics API tends to be more profound on lower-end hardware, especially when it comes to lightening the load on the CPU. Following recent Pentium vs. Ryzen 3 Linux gaming tests, Phoronix carried out some fresh benchmarks looking at OpenGL vs. Vulkan on the Ryzen 3 1200 quad-core CPU with NVIDIA and Radeon graphics.

Geeks 3D has a great overview of the new OpenGL and Vulkan features in the AMD Adrenalin 17.12.1 release. AMD has added some OpenGL 4.6 extensions (GL_ARB_gl_spirv) but not all, so Adrenalin 17.12.1 is still an OpenGL 4.5 driver with OpenGL 4.6 features. This driver exposes 319 OpenGL extensions (GL=294 and WGL=25) for a Radeon RX 470 on Windows 10 64-bit. Adrenalin 17.12.1 also exposes Vulkan 1.0.65 which is one of the latest specifications. Vulkan support has been added to Radeon Overlay, Radeon Relive, Enhanced Sync and Frame rate target control.

Neil Trevett, Khronos Group President and Radhakrishna Giduthuri, Software Architecture and Compute Performance Acceleration at AMD, spoke at two Khronos related events this past week. Neils presented was an update on the Khronos Standards for Vision and Machine Learning which covered Khronos Standards OpenVX, NNEF, OpenCL, SYCL and Vulkan. Radhakrishna presented Standards for Neural Networks Acceleration and Deployment covered Khronos Standards OpenVX and NNEF. The slides from both presentations are now online.

Join Patrick Cozzi and his Penn graphics students final project presentations in a live stream December 11th at 5pm EST. There will be 19 4-minute presentations in total. Topics include rendering clouds, terrain, ocean, forests, weather, VR, voxels, ray marching, and more. A complete list of projects can be found online here.

Arm releases PerfDoc v1.0PerfDoc is a Vulkan layer which aims to validate applications against the Mali Application Developer Best Practices Guide. Just like the LunarG validation layers, this layer tracks your application and attempts to find API usage which is discouraged. PerfDoc focuses on checks which can be done up-front, and checks which can portably run on all platforms which support Vulkan. The intended use of PerfDoc is to be used during development to catch potential performance issues early. The layer will run on any Vulkan implementation, so Mali-related optimizations can be found even when doing bringup on desktop platforms. Just like Vulkan validation layers, errors are reported either through VK_EXT_debug_report to the application as callbacks, or via console/logcat if enabled. Dynamic checking (i.e. profiling) of how an application is behaving in run-time is not currently in the scope of PerfDoc. Some heuristics in PerfDoc are based on "arbitrary limits" in case where there is no obvious limit to use. These values can be tweaked later via config files if needed. Some checks which are CPU intensive (index scanning for example), can also be disabled by the config file. Please visit the GitHub repository for PerfDoc.

If you take a look at the conformant vulkan list, you will see entry 220 - Software in the Public Interest, Inc. 2017-10-04 Vulkan_1_0 220. This is radv, and this is the first conformance submission done under the (SPI) membership of the Khronos adopter program. A major milestone has been reached and radv is now a conformant Vulkan driver.

When makers of the ABYSS Engine started working on the Android release of Galaxy on Fire 3 - Manticore, the goal was for everyone to be able to enjoy the same visual fidelity, no matter if playing on Android or iOS. On iOS. They decided to add Vulkan support to their in-house game engine and render 'Galaxy on Fire 3' with Vulkan on Android. Read the entire introduction and fundamentals post on Gamasutra.