LunarG creates tools to help simplify Vulkan development. We leveraged the new Vulkan Layer Factory to create the Vulkan Assistant Layer, a layer that helps developers identify Vulkan best practices. The Vulkan Assistant Layer — VK_LAYER_LUNARG_assistant_layer — functions as a Vulkan best practices layer and is intended to highlight potential performance issues, questionable usage patterns, common mistakes, and items that may lead to application problems that are not specifically prohibited by the Vulkan specification. The Vulkan Assistant Layer can be found as part of the LunarG Vulkan SDK.
The Khronos Group will be at GDC & VRDC 2018. Be sure to mark us in your calendar for the Khronos Dev Day on March 19th in Moscone, West Hall, Room 3022. This years sessions are now posted and include WebGL, glTF, OpenXR and Vulkan. Be sure to book mark the Khronos GDC event page and checkout some of our other upcoming events and meet ups.
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.
Intel has announced the availability of a new Graphics driver, namely version 220.127.116.1149, which adds support for Microsoft Windows 10 Fall Creators update features. This update also resolves the intermittent crashes/hangs encountered in DOTA 2 (Vulkan version), enhances memory usage in OpenCL applications.
The Khronos Group has released Vulkan 1.0.65. As well LunarG has released their SDK to match. The following new extensions were added: VK_AMD_shader_image_load_store_lod; VK_AMD_shader_info; VK_EXT_global_priority as well as Updates to loader, layers, and documents.
F1 2017 is coming to Linux and Feral Interactive are porting it. The plan is to release it on November 2nd. More information is available from the Feral mini-site and Gaming on Linux. The game will be powered by the Vulkan API, as confirmed by Feral Interactive in another tweet. This will be their third Linux game to use Vulkan!
The Qt Company, a Khronos member, has recently announce Qt 5.10 Beta. A few new features with Qt 5.10 include initial support for Vulkan and a preview of Qt WebGL Streaming Plugin. ICS has posted a blog to walk you through the new WebGL feature.
PerfDoc 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.
RedGamingTech recently posted Part I of an interview with Neil Trevett - 'CUDA, AI, Self Driving Cars, GameWorks & Deep Learning', President of The Khronos Group. Part II 'Vulkan, Game Development & VR & Graphics Technology' of the interview is now online.