K.Wagrez Posted December 12, 2025 Posted December 12, 2025 (edited) Hello everyone, We have migrated some projects to Unigine 2.19.1 and, while it works on our machines, we discovered on some of our build machines a crash durign the use of the build tool with this message: Quote 08:08:09 ERROR: VkWrapper::init(): can't initialized volk It seems related to the Vulkan API wrapper I suppose. Was there some added dependencies we might need ? (it could be our computer's drivers, but I'm surprised that launching the build too with Dx 12 would generate a Vulkan-related error) Edited December 12, 2025 by K.Wagrez
silent Posted December 15, 2025 Posted December 15, 2025 Hi Kevin, This error may occur when GPU is not found or Vulkan runtime is missing. You can either update GPU drivers to the latest version or install Vulkan Runtime manually. Thanks! 1 How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
K.Wagrez Posted December 17, 2025 Author Posted December 17, 2025 To give more details to @silent's answer, Unigine actually changed the internal API used to query GPU information, from DX11 to Vulkan, during the 2.18 to 2.19 transition. So our virtual machines without access to GPUs and with no drivers didn't have the necessary Vulkan dependencies to function. Some of our other technologies actually ship Vulkan dependencies and SwiftShader, which is a CPU implementation for Vulkan. We will ponder if we use these. For now we solved this by setting the build tool to not target any api (vapi to null in the configuration). This way Vulkan won't be used by the build tool to query information.
Alexander.Komarov Posted January 20 Posted January 20 Hello, I decided to test WPF integration in 2.20 and created a simple WPF project (net8.0), imported DLLs from SDK and followed WPF integration guide. Yet the engine refuses to run:
Recommended Posts