Ошибка, связанная с библиотекой Vulkan-1.dll, встречается у любителей видеоигр, в частности Doom 4 и Wolfenstein. Данная динамическая библиотека используется для взаимодействия компонентов системы с игрой. На данный момент ошибка отсутствия или повреждения библиотеки очень распространена и имеет несколько простых путей для исправления. Перед тем, как скачать Vulkan-1.dll, требуется знать, в следствии чего он может пропасть из системы или стать неработоспособным. Стоит отметить, что вы сможете скачать Vulkan-1.dll 64 bit для Windows 10 в пару кликов, весь процесс занимает минимум времени.
Возможности Vulkan-1.dll
Не сложно догадаться о том, что рассматриваемая библиотека представляет собой решение проблемы, когда игры в лице Doom 4 и Wolfenstein не могут запуститься.
При повреждении компонента нарушается стабильность работы и теряется способность к функционированию. В результате определённого алгоритма действий всё можно вернуть на свои места. Для этого потребуется лишь следовать тем инструкциям, которые будут перечислены чуть ниже в статье.
Как выполнить скачивание
Для того, чтобы скачать бесплатно Vulkan-1.dll 64 bit для Windows 7, вам нужно реализовать элементарное действие. Просто перейдите по прямой ссылке, её можете найти прямо на нашем сайте.
Установочный процесс
Важный вопрос касается того, куда кидать Vulkan-1.dll и как зарегистрировать его в системе. Какие-то допущенные ошибки могут лишь усугубить ситуацию и повлечь за собой неработоспособность той или иной игры. Следуйте инструкции, которая описана далее:
Загрузите библиотеку на свой компьютер по ссылкам ниже. Как говорилось ранее, вы можете найти их без каких-либо проблем прямо на нашем сайте.
Распакуйте архив и переместите файл DLL в папку, соответствующую разрядности вашей системы.
Рассмотрение практической информации
Важно понимать, что работа с установкой библиотеки не всегда является единственным решением той или иной проблемы. Ниже будет приведена действительно полезная информация по поводу той неприятности, с которой может столкнуться каждый пользователь.
Ошибка Vulkan-1.dll по причине заражения вирусами
Первая причина ошибки в библиотеке Vulkan-1.dll – это вирусное ПО. Зачастую вирусы могут взаимодействовать и изменять файлы исполняемых библиотек для дальнейшего проникновения в систему. Перед тем, как скачать Vulkan-1.dll для Windows, необходимо убедится в том, что система не заражена вирусами.
Чтобы данная проблема была решена максимально качественно, вам потребуется:
Воспользоваться надёжной антивирусной программой, которая имеет высокие рейтинги и признаётся подавляющим количеством пользователей эффективной в борьбе с любыми вредоносными компонентами.
На время проверки закрыть все сторонние программы.
При запуске антивируса нужно указывать полный анализ системы, который позволит выявить абсолютно всё, что только возможно.
В случае обнаружения вредоносных компонентов удалите их и проверьте систему на наличие опасностей ещё раз. Конфликты антивируса и библиотеки.
Вторая причина очень схожа с первой и заключается в принципе работы антивирусов. Любой из современных антивирусов может изолировать заражённый файл библиотеки Vulkan-1.dll, поместить его в карантин или вовсе безвозвратно удалить с компьютера. В таком случае стоит попробовать переустановить игру, если есть такая возможность. Не хотите ждать – можете переходить к загрузке Vulkan-1.dll с нашего сайта.
Стоит отметить, что, чаще всего, антивирусные программы просто добавляют те или иные компоненты в карантин. Вы можете выполнить восстановление файла, после чего работоспособность игр может вернуться.
Ошибка Vulkan-1.dll: как исправить
Вы уже наверняка всё поняли о Vulkan-1.dll, что это и для чего применяется. Отсутствие такой библиотеки препятствует тому, чтобы пользователь имел доступ к комфортному времяпровождению в компании компьютерной игры. Для исправления ошибки «Система не обнаружила vulkan-1.dll» или «Запуск невозможен отсутствует vulkan-1.dll» и других, существует три очень эффективных метода.
Методы исправления ошибки
Преимущества
При работе с ПК могут возникать всевозможные ошибки. Некоторые из них решаются довольно просто. Если рассматривать Vulkan-1.dll, что это за ошибка и как исправить, тут не возникает вопросов. Преимущество установки библиотеки в том, что проблема решается в пару кликов.
Заключение
Рекомендуем загрузить через DS Скачать торрент бесплатно или скачайте по прямым ссылкам ниже
Vulkan-1.dll скачать 64 bit
Vulkan-1.dll 64 bit — библиотека ДЛЛ распространяемая бесплатным образом вместе с пакетом VulkanSDK. У многих пользователей ПК может возникнуть ошибка Vulkan-1.dll, которая не позволит зайти в любимую игру или программу. Библиотека отвечает за взаимодействие компонентов игры с системой, что позволяет корректно отображать картинку и все функции открытого приложения.
Если ошибка застала Вас врасплох, не стоит отчаиваться! Чтобы её решить, рекомендуется выяснить причины возникновения и применить один из описанных методов исправления на нашем сайте. Процесс исправление ошибки займёт не более 10 минут драгоценного времени, главное внимательно прочитать все рекомендации и инструкции.
Некачественное или поддельное программное обеспечение;
Заражение компьютера вирусами;
Случайное удаление библиотеки из системы;
Полное отсутствие пакета VulkanSDK.
Зачастую, проблема возникает из-за скачивания игр из некачественных источников. Использование лицензионных решений и проверенных сборок позволит избежать ошибки. В основном, библиотека автоматически устанавливается в компьютер вместе с файлами игры.
Отсутствует Vulkan-1.dll — как исправить ошибку
Шаги ручной инсталляции Vulkan-1.dll в систему:
Загрузить архив с программой на компьютер и распаковать в удобное место;
Поместить библиотеку в » C:\Windows\System32 » ( для 32-х разрядных систем ) или » C:\Windows\SysWOW64 » ( для 64-х разрядных систем );
Нажать комбинацию клавиш «Win+R» или открыть «Пуск — Выполнить»;
В появившемся окне ввести » regsvr32 vulkan-1.dll «;
Перезапустить Windows.
Обязательно следите за состоянием компьютера и используйте проверенные источники для загрузки игр, во избежание проявления этой или других ошибок. Чуть ниже, можно скачать vulkan-1.dll и прочитать практические рекомендации для поддержания системы в работоспособном состоянии.
Дальнейшие рекомендации для избежания новых ошибок:
Ищите только проверенные игры и сборки программ;
Проверяйте компьютер антивирусными средствами;
Обязательно производите обслуживание и очистку от мусора;
Исправляйте ошибки реестра при помощи CCleaner и другого доверенного ПО.
Надеюсь ошибка Vulkan-1.dll больше Вас не побеспокоит. Если возникли трудности в установке, можете обратиться в комментарии и мы постараемся оперативно решить проблему!
Vulkan
What Is Vulkan?
Vulkan is a new-generation graphics and compute open standard API that provides high-efficiency, cross-platform access to modern GPUs. Created and evolved by the Khronos® Group standards consortium, Vulkan satisfies the needs of software developers in fields as varied as game, mobile and workstation application development. Vulkan’s explicit API design enables efficient implementations on platforms that span a wide range of mobile, console, embedded and desktop hardware using the Windows, Linux and Android operating systems.
Why Vulkan?
Vulkan is an open standard API that the entire industry can cooperatively evolve to provide access to the latest GPU technologies. The API provides a multi-threading-centric design to leverage modern multi-core CPUs, and provide access to GPUs via multiple parallel command queues. Some of the latest Vulkan features include ray tracing, bindless resources and shader programming using GLSL or HLSL. Vulkan is not tied to a specific platform and enables developers to write GPU code that is portable to diverse devices and operating systems.
Vulkan at NVIDIA
NVIDIA provides fully conformant Vulkan 1.2 drivers across our products including Geforce and Quadro on Windows and Linux, Shield Android TV, and the range of Jetson embedded processors using Android or Linux. NVIDIA Nsight™ tools enable developers with cutting-edge Vulkan application debugging, profiling and optimization capabilities.
Vulkan is available across NVIDIA’s products
NVIDIA is deeply engaged at Khronos and the Vulkan Working Group to help drive Vulkan’s evolution through developing vendor extensions to enable developers access the very latest GPU technologies, and encouraging these capabilities to be adopted as cross-vendor Vulkan specifications at the Khronos Working Group.
To help developers get up and running quickly with Vulkan, this page contains information on NVIDIA’s Vulkan drivers, links to the full source code of educational samples and helper libraries, links the downloadable NVIDIA Nsight tools to help you debug and optimise your Vulkan code, and articles and presentations to help you learn more about what Vulkan can do for you!
NVIDIA will be regularly adding new materials on this page — so keep an eye open for the latest updates!
Vulkan Certified Driver Information
When running on Turing or Ampere hardware these drivers include the
Samples
NVIDIA provides a growing collection of Vulkan and OpenGL samples and tutorials with full source code available on GitHub. Developers can download the samples that interest them, from educational introductions to basic Vulkan workflows and extensions, through examples of how to render scenes with high geometric complexity and ray tracing,and on to professional application use-cases. The repository also contains utility code that can speed up Vulkan development.
Vulkan Developer Tools
Nsight Aftermath
The NVIDIA Nsight Aftermath SDK is a simple library that can be integrated into a game’s crash reporter to generate GPU «mini-dumps» when a GPU hang or exception occurs.
Nsight Systems
NVIDIA Nsight Systems is a system-wide analysis tool for visualizing CPU / GPU interactions to help eliminate GPU idle, stutter and CPU bottlenecks. It can trace Vulkan on the CPU & GPU, interoperating GPU APIs, and many CPU or OS events.
Nsight Graphics
NVIDIA Nsight Graphics enables developers to debug & profile Vulkan applications. With powerful low-level profiling features such as GPU Trace, it’s easier than ever to identify GPU performance issues and optimize with confidence.
RTX Ray Tracing in Vulkan
In November 2020, Khronos released the final versions of the Vulkan Ray Tracing extensions that seamlessly integrate ray tracing into the existing Vulkan framework. Vulkan is the industry’s first open, cross-vendor, cross-platform standard that can be used to access RTX ray tracing acceleration.
Alongside the release of ray tracing support in the Khronos Vulkan SDK in December 2020, NVIDIA now ships the Vulkan Ray Tracing extensions in our production Vulkan drivers . All RTX GPUs are supported, together with GeForce GTX 1660 with 6GB+ of memory and GeForce GTX 1060+ with 6GB+ of memory.
NVIDIA has also released Quake II RTX version 1.4 that uses Vulkan Ray Tracing to significantly enhance the visual quality of this well-loved classic running with ray-traced lighting, shadows, and reflections — making Quake II RTX the world’s first cross-vendor ray tracing Vulkan application! NVIDIA releases the full source code on GitHub serving as a great example for developers who want to dive into the details of how this remastering was achieved.
Getting Started with Vulkan Ray Tracing
A tutorial on how to use Vulkan Ray Tracing to create a complete mini-path tracer using the final Vulkan Ray Tracing extensions
An updated Vulkan Ray Tracing Tutorial using the final Vulkan Ray Tracing extensions
Read about how the 2020.6 release of the NVIDIA Nsight Graphics tool supports Vulkan Ray Tracing
Vulkan Driver Support
This page provides links to both Vulkan 1.2 general release drivers, and developer beta drivers.
Vulkan 1.2 General Release Driver Downloads
Vulkan 1.2, including support for the Vulkan Ray Tracing extensions, is available for Windows and Linux in our general release drivers here:
NVIDIA SHIELD TV
Vulkan Beta Driver Downloads
Vulkan Beta Driver Release Notes
The latest Vulkan 1.2 specification can be found here: https://www.khronos.org/registry/vulkan/
NVIDIA provides full Vulkan 1.2 support and functionality on NVIDIA GeForce and Quadro graphics card with one of the following Ampere, Turing, Volta, Pascal, Maxwell (first and second generation) and Kepler based GPUs:
For Vulkan Ray Tracing samples and tutorials see https://github.com/nvpro-samples/vk_raytracing_tutorial_KHR. Drivers supporting the new final release version of the Khronos Vulkan Ray Tracing extensions are not compatible with the provisional Khronos Vulkan Ray Tracing extensions released on March 17th, 2020. Support for the provisional extensions can be found in the older Windows 457.33 and Linux 455.46.01 drivers.
For any bugs or issues, please file a bug through the developer website: https://devtalk.nvidia.com/
Vulkan Beta Driver Release Updates
April 13th, 2021 — Windows 458.17, Linux 455.50.12
March 4th, 2021 — Windows 458.06, Linux 455.50.10
Fixes:
Fixed an issue with vkCmdSetViewport when firstViewport is non-zero
Fixed a memory fault when using some smaller dimensions of sparse images
Fixed an issue where vkCreatePipeline would sometimes crash when the shaders contained resources with no set/binding
Fixed corruption that sometimes occured with shadow rendering with image arrays
Fixed a bug with the host-visible device-local memory heap, where if an allocation failed due to space constraints, it could cause the application to crash on future Vulkan function calls
Fixed a potential crash when clearing images with multiple layers
Fixed a bug where using ray tracing extensions on multi-GPU setups could result in application instability if the GPUs did not match [Linux]
Fixed a bug where vkCreateSwapchain could cause the X Server to crash when an invalid imageFormat was provided [Linux]
February 15th, 2021 — Windows 457.96, Linux 455.50.07
New:
VK_KHR_synchronization2
Fixes:
Fixed handling of VK_DESCRIPTOR_BINDING_VARIABLE_DESCRIPTOR_COUNT_BIT for variable size descriptor bindings
Fixed the present tearing that occured in some situations [Windows]
February 2nd, 2021 — Windows 457.91, Linux 455.50.05
Fixes:
Fixed bug with indexed ray payloads
Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime [Linux]
January 27th, 2021 — Windows 457.88, Linux 455.50.04
Fixes:
Fixed a bug in a stencil-buffer optimization that could occasionally result in VK_ERROR_DEVICE_LOST
January 25th, 2021 — Windows 457.84, Linux 455.50.03
January 19th, 2021 — Windows 457.83, Linux 455.50.02
New:
Support for linear images in host-visible video memory
Fixes:
Fixed a crash Vulkan swapchain initialization on older versions of Windows 10 [Windows]
Fixed VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_D3D12_FENCE_BIT semaphore export support [Windows]
Fixed an issue with OpenGL where imported Vulkan buffers would fail with GL_OUT_OF_MEMORY when marked as resident [Linux]
December 16th, 2020 — Windows 457.67, Linux 455.46.04
New:
VK_NV_acquire_winrt_display [Windows]
Fixes:
Fixed a crash from vkCreateGraphicsPipelines when certain blend operations were used with scalar outputs from the fragment shader
Fixed the X driver’s composition pipeline (used, e.g., for X desktop rotation, «ForceCompositionPipeline», and some OpenGL Swap Group configurations) to correctly preserve color precision in depth 30 [Linux]
November 23rd, 2020 — Windows 457.44, Linux 455.46.02
November 11th, 2020 — Windows 457.33, Linux 455.46.01
November 2nd, 2020 — Windows 457.17, Linux 455.34.01
New:
NVIDIA GeForce RTX 3070 support
Fixes:
Fixed an issue with VK_ACCESS_MEMORY__BITs when used as part of a render pass
Fixed an issue where Vulkan applications would fail to initialize if the connected X11 Server did not expose support for GLX [Linux]
October 20th, 2020 — Windows 457.00, Linux 455.26.02
October 9th, 2020 — Windows 456.80, Linux 455.26.01
Fixes:
Reduce host memory consumption for descriptor memory when VkDescriptorSetVariableDescriptorCountAllocateInfo is used
Handle SPIR-V 1.4 non-Input/Ouput entry point variables correctly
Fixed a blending optimization that sometimes produced an incorrect result
Fixed SPIR-V intersection shader compilation issue when multi entry point ray tracing modules are used
September 29th, 2020 — Windows 456.62, Linux 455.22.04
New:
Rebased to r455 driver branch, which adds Ampere GPU family support
VK_EXT_global_priority support for Windows 10 with hardware scheduling enabled
Application needs to have the SeIncreaseBasePriorityPrivilege enabled to get higher priorities
VK_EXT_shader_image_atomic_int64
VK_KHR_copy_commands2
Allow importing external host memory as cached
Fixes:
Fixed a bug in a barrier optimization that allowed some back-to-back copies to run unordered
September 9th, 2020 — Windows 452.28, Linux 450.56.11
Fixes:
Fixed a bug in a SPIR-V optimization that may cause conditional blocks to not execute
Fixed a bug where calls to vkGetRandROutputDisplayEXT with unexpected inputs would generate X11 protocol errors [Linux]
August 7th, 2020 — Windows 451.98, Linux 450.56.06
July 20th, 2020 — Windows 451.79, Linux 450.56.02
July 9th, 2020 — Windows 451.74, Linux 450.56.01
New:
Rebased beta driver to r450 driver release branch
Added support for the VkPhysicalDeviceRayTracingFeaturesKHR.rayTracingIndirectTraceRays ray tracing feature
VK_NV_device_diagnostics_config
Fixes:
Make the pSizes parameters of vkCmdBindVertexBuffers2EXT be relative to the pBuffers+pOffsets
Fixed potential crash in the first vkQueuePresentKHR() call after creating a new VkSwapchainKHR with a non-NULL oldSwapchain
Fixed potential crash in vkCmdBeginRenderPass() when using VK_EXT_sample_locations
June 23rd, 2020 — Windows 443.41, Linux 440.66.17
May 26th, 2020 — Windows 443.24, Linux 440.66.15
Fixes:
Fixed 16-bit SMin/SMax
CPU performance improvements for VkFence creation and usage [Linux]
Fixed a bug where vkUpdateDescriptorSetWithTemplate would ignore the stride parameter for some VkDescriptorType values
Fixed an issue with the Optimus layer selecting the iGPU when there was an application profile with Auto-select as the preferred graphics processor [Windows]
Fixed layout of compute shader shared memory that may have resulted in a compiler crash
Fixed a bug where vkCreateSampler would fail with no borderColor data, even though it wasn’t needed
Fixed a compiler issue processing image operation with extra unused coordinate operand components Fixed writing to dynamically indexed vec2 and vec3 fragment color outputs
May 11th, 2020 — Windows 443.15, Linux 440.66.14
New:
Added support for the VkPhysicalDeviceRayTracingFeaturesKHR.rayTracingPrimitiveCulling ray tracing feature
Fixes:
Fixed the returned pCheckpointDataCount value for vkGetQueueCheckpointDataNV when there are less than the requested values
Process the VkTimelineSemaphoreSubmitInfo structure correctly for vkQueueBindSparse
Fixed vec3 immediate indexing in ray tracing shaders
May the 4th, 2020 — Windows 443.09, Linux 440.66.12
New:
VK_EXT_custom_border_color
VK_EXT_private_data
VK_EXT_robustness2
Fixes:
Fixed a visual glitch with Vulkan applications when falling out of flipping on certain desktops such as GNOME [Linux]
April 24th, 2020 — Linux 440.66.11
Fixes:
Fixed several synchronization bugs that could momentarily lock up the X server when moving/resizing/focusing OpenGL and Vulkan windows when PRIME Sync is enabled [Linux]
Fixed a bug which caused horizontal lines to corrupt full screen Vulkan applications [Linux]
April 18th, 2020 — Windows 442.98, Linux 440.66.09
New:
Added support for more acceleration structure vertex formats
Fixes:
Fixed some VkPhysicalDeviceRayTracingFeaturesKHR to be advertised correctly for the current GPU
Fixed potential crash when pipeline pInputAssemblyState is NULL for mesh shaders
Fixed memory alignment and type for ray tracing scratch memory
Fixed some issues with ray tracing queries
Fixed an issue with ray tracing pipeline creating with pipeline libraries
Fixed some window state transitions when using HDR [Windows]
April 2nd, 2020 — Windows 442.88, Linux 440.66.08
New:
Added beta support for Ray Queries
VkPhysicalDeviceRayTracingFeaturesKHR.rayQuery is now VK_TRUE
SPIR-V: SPV_KHR_ray_query
GLSL: GLSL_EXT_ray_query
Fixes:
Improve performance of large host-visible VkDeviceMemory allocations
Fixed YCbCr copy of multi-plane images
April 1st, 2020 — Windows 442.86, Linux 440.66.07
New:
Multi thread-capable deferred ray tracing pipeline creation
Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces [Linux]
Fixes:
Added a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory [Linux]
Correctly cap the drawCount for vkCmdDrawIndirectCount and vkCmdDrawIndexedIndirectCount on Turing GPUs
Fixed descriptor indexing with large arrays and large blocks
March 24th, 2020 — Windows 442.81, Linux 440.66.04
Fixes:
Fixed handling of offsets in VkAccelerationStructureBuildOffsetInfoKHR
Fixed a bug which could cause DXVK applications to crash when running on Optimus laptops [Windows]
March 19th, 2020 — Windows 442.77, Linux 440.66.03
March 17th, 2020 — Windows 442.75, Linux 440.66.02
February 19th, 2020 — Linux 440.58.02
Fixed:
Fixed a regression which added syntax errors into the default application profiles configuration file [Linux]
February 15th, 2020 — Windows 442.36, Linux 440.58.01
New:
VK_KHR_shader_non_semantic_info
VK_EXT_tooling_info
Fixed:
Fixed a regression which caused some Vulkan titles to crash on swapchain recreation. This was known to affect the following Vulkan titles [Linux]:
F1 2017
Rise of the Tomb Raider
DiRT 4
Fixed a visual glitch of Vulkan applications when falling out of flipping (such as when doing alt-tab) [Linux]
We are still investigating a glitch that reproduces with the GNOME desktop
January 15th, 2020 — Windows 441.99, Linux 440.48.02
January 8th, 2020 — Windows 441.97, Linux 440.43.02
Fixes:
Fixed a bug that caused DXVK titles to endlessly loop during shader compilation if no OpSource instruction was present
Fixed a build failure «fatal error: drm/drmP.h: No such file or directory» when building for Linux 5.5 release candidates
Other minor fixes
December 11th, 2019 — Windows 441.71, Linux 440.43.01
New:
Rebased Vulkan beta driver to r440 release branch
Fixes:
Fix rendering to 3D depth/stencil image slices
Improvements to Vulkan driver startup time
Fixed various resource leaks
November 25th, 2019 — Windows 436.65, Linux 435.27.08
November 14th, 2019 — Linux 435.27.07
Fixes:
Fixed a bug that caused graphical corruption, reducing visibility in caves, in Steam Play title Assassin’s Creed: Odyssey
Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system
November 13th, 2019 — Windows 436.64, Linux 435.27.06
Fixes:
Fixed memory leak after destroying ray tracing pipeline
Improved responsiveness of X11 driver when ‘NVIDIA: Wait for channel idle timed out’ messages occur
Improved Windows fullscreen exclusive support for non-primary monitors
Improved Windows G-Sync support for borderless windows
Further improvements when system is under low-memory stress on Windows
November 4th, 2019 — Windows 436.61, Linux 435.27.03
New:
VK_KHR_separate_depth_stencil_layouts
Fixes:
Improved behavior in low-memory situations
Fixed graphical corruption in Vulkan game F12017
Various minor performance improvements
Improved Vulkan HDR support for multi-device configurations
October 25th, 2019 — Windows 436.59, Linux 435.27.02
New:
Added HDR10 passthrough presentation format and color space for Windows 10 RS2+
VkFormat — VK_FORMAT_A2B10G10R10_UNORM_PACK32
VkColorSpaceKHR — VK_COLOR_SPACE_HDR10_ST2084_EXT
Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Linux Vulkan applications
Fixes:
Improved bounds checking and stability for some content
Improved unused memory reclamation when running low on system memory for Linux
General performance improvements
October 13th, 2019 — Windows 436.56, Linux 435.27.01
New:
VK_KHR_spirv_1_4
Fixes:
Fix tearing with mailbox present mode on Windows 10 laptops and SLI platforms
October 7th, 2019 — Windows 436.52, Linux 435.27.00
September 18th, 2019 — Windows 436.39, Linux 435.24.02
New:
VK_KHR_shader_subgroup_extended_types
Fixes:
Fixed a regression introduced in 435.19.02 that would cause some applications which use the VK_KHR_display extension to segmentation fault
September 6th, 2019 — Linux 435.19.03
Fixes:
Fixed a bug which caused corruption in the following DXVK titles:
Saints Row IV
Saints Row: The Third
Fall back to system memory when video memory is full for some driver-internal allocations.
This can help fix Xid 13 and Xid 31 cases when video memory is full.
August 29th, 2019 — Windows 436.20, Linux 435.19.02
New:
Rebased Vulkan beta driver features to the latest 436.15 (Windows) and 435.17 (Linux) general release drivers
8-bit integer support added to VK_NV_cooperative_matrix
See here for more info
Fixes:
General performance imporvements from 436.15 and 435.17
August 12th, 2019 — Windows 426.06, Linux 418.52.20
New:
VK_KHR_pipeline_executable_properties
Fixes:
Improved reporting of Xid errors to include the process ID (PID) of the process responsible for the error
July 29th, 2019 — Windows 426.02, Linux 418.52.18
July 17th, 2019 — Linux 418.52.17
Fixes:
Fixed a bug that could cause heapUsage values reported by VK_EXT_memory_budget to not immediately update after vkFreeMemory was called
July 8th, 2019 — Windows 425.94, Linux 418.52.16
July 1st, 2019 — Windows 425.89, Linux 418.52.14
June 1st, 2019 — Windows 425.62, Linux 418.52.10
May 22nd, 2019 — Windows 425.58, Linux 418.52.07
April 19th, 2019 — Windows 425.42, Linux 418.52.05
New:
VK_PRESENT_MODE_IMMEDIATE_KHR present mode is now available for Windows
VK_NV_ray_tracing is now available on the following non-RTX GPUs:
March 30th, 2018 — Windows 389.20, Linux 387.42.06
March 7th, 2018 — Windows 389.10, Linux 387.42.05
January 5th, 2018 — Windows 388.84, Linux 387.42.01
September 28th, 2017 — Windows 383.18, Linux 381.26.20
Full-screen flipping for Linux
Improved performance of fullscreen Vulkan applications using X11 swapchains. This optimization will cause more events that trigger an out-of-date swapchain, such as when entering or leaving fullscreen mode. This is commonly encountered when using the alt-tab key combination, for example. Applications that do not properly respond to the VK_ERROR_OUT_OF_DATE_KHR return code may not function properly when these events occur. See section 30.8 of the Vulkan specification.
Known issue with Quadro and non-composited desktops under some situations. Possible workarounds:
Disable flipping in nvidia-settings (uncheck «Allow Flipping» in the «OpenGL Settings» panel)
Disable UBB (run ‘nvidia-xconfig —no-ubb’)
Use a composited desktop
Bug fixes
NVX_multiview_per_view_attributes and geometry passthrough shaders
Fix handling of SPIR-V SSBO layout qualifiers on members
Fix atomic operations on some 64-bit types
September 15th, 2017 — Windows 383.12, Linux 381.26.17
New Extensions
VK_KHR_maintenance2
VK_KHR_bind_memory2
VK_KHR_image_format_list
VK_KHR_sampler_ycbcr_conversion
VK_EXT_sample_locations
Removed KHX extensions
VK_KHX_external_memory_capabilities
VK_KHX_external_memory
VK_KHX_external_memory_fd
VK_KHX_external_memory_win32
VK_KHX_external_semaphore_capabilities
VK_KHX_external_semaphore
VK_KHX_external_semaphore_fd
VK_KHX_external_semaphore_win32
VK_KHX_win32_keyed_mutex
Updated Vulkan loader to 1.0.61.0
Minor bug fixes
August 16th, 2017 — Windows 382.96, Linux 381.26.13
New Extensions
VK_EXT_shader_viewport_index_layer
Updated Vulkan loader to 1.0.57.0
Fixed potential hang with some semaphore usage patterns
Fixed issue with VK_INDIRECT_COMMANDS_TOKEN_TYPE_PUSH_CONSTANT_NVX and dynamicCount
Other minor bugs fixed
July 31st, 2017 — Windows 382.88, Linux 381.26.11
July 14th, 2017 — Windows 382.83
Fixed issue with unused compute queue
Other minor bug fixes
July 13th, 2017 — Linux 381.26.08, Windows 382.81
June 30th, 2017 — Windows 382.71, Linux 381.26.06
Various performance improvements and bug fixes
June 27th, 2017 — Windows 382.68, Linux 381.10.10
June 9th, 2017 — Windows 382.58, Linux 381.26.03
March 27th, 2017 — Windows 377.14, Linux 375.27.15
SPIR-V compiler bug fixes
Updated Vulkan loader to version 1.0.42.1
March 15th, 2017 — Windows 377.07
March 8th, 2017 — Linux 375.27.14, Windows 377.06
February 28th, 2017 — Linux 375.27.13, Windows 377.01
Fix issue with SteamVR shaders
February 27th, 2017 — Linux 375.27.12, Windows 376.98
Beta support for the following new extensions:
Descriptor Set Extensions
Cross process interop extensions:
Multi-GPU extensions:
Multiview and VR related extensions:
Other extensions:
VK_NV_sample_mask_override_coverage (Maxwell)
VK_EXT_discard_rectangles
Bug fixes to improve compatibility with shaders generated from HLSL
February 9th, 2017 — Linux 375.27.10
February 1st, 2017 — Linux 375.27.08, Windows 376.80
January 23rd, 2017 — Linux 375.27.07, Windows 376.71
January 10th, 2017 — Linux 375.27.03, Windows 376.66
Vulkan beta drivers with experimental API interop features
July 6th, 2016 — Windows 368.69
Public GeForce Game Ready drivers
June 13th, 2016 — Linux 367.27
May 23rd, 2016 — Windows 368.22, Linux 367.18
Public GeForce Game Ready drivers
Bug fixes and performance improvements
May 13th, 2016 — Windows 365.19, Linux 364.19
Public GeForce Game Ready drivers
Bug fixes and performance improvements
April 8th, 2016 — Windows 364.91, Linux 364.16
Updated Vulkan API to 1.0.8
Improve pipeline creation performance and multi-threaded scaling
Increase our maximum bound descriptor sets from 4 to 8
Add support for asynchronous transfer queue
Improve VK_EXT_debug_report messages on incorrect API usage and shader compile failure
Fix VkImageFormatProperties maxMipLevels property
Reduce VkPhysicalDeviceLimits bufferImageGranularity requirement on GM20x GPUs
Improve Vulkan support on Optimus platforms
Fixes for minor driver and SPIR-V compiler bugs
March 28th, 2016 — Windows 364.72
Update Vulkan API to 1.0.5
Various performance improvements
Various bug fixes
March 21st, 2016 — Linux 364.12
March 10th, Windows 364.51
March 2nd, 2016 — Windows 356.45, Linux 355.00.29
Support Vulkan API version v1.0.4
Fix device lost issue with some MSAA resolves
Fix vkGetQueryPoolResults() when queryCount=0
Fix OpImageQuerySample with images
Fix OpVectorExtractDynamic issues with doubles
Fix handling of sparse image miptail when the whole image fits within a page
Improve vkAcquireNextImageKHR() conformance to WSI spec
Improve GL_KHR_vulkan_glsl compatibility when using GLSL directly
Improve GPU texturing performance in some cases
Improve vkAllocateDescriptorSets()/vkFreeDescriptorSets() performance in some cases
Improve vkCmdBindDescriptorSets() performance in some cases
Improve vkCmdCopyImage() performance in some cases
February 23rd, 2016 — Windows 356.43, Linux 355.00.28
Add support for 64-bit vertex attribute formats
Improve performance of vkBindBufferMemory, vkBindImageMemory and vkCreateGraphicsPipelines
No longer enumerate Fermi based GPUs in vkEnumeratePhysicalDevices
Improved compatibility with recent Linux kernels
February 18th, 2016 — Linux 355.00.27
Vulkan on NVIDIA Hardware FAQ
1) How do I start using Vulkan in my code base?
NVIDIA Vulkan developer page https://developer.nvidia.com/Vulkan is a great place to start. You can learn from Vulkan presentations and articles as well as NVIDIA demos and SDK samples.
2) Is NVIDIA going to continue to support OpenGL in the future?
NVIDIA is fully committed to invest in OpenGL that our ISVs rely on and will continue to support and improve it. NVIDIA believes in providing maximum functionality with minimal churn to developers. Hence, NVIDIA fully supports both Vulkan and OpenGL.
3) Is NVIDIA Vulkan driver conformant?
Yes, the beta drivers typically pass the latest version of Vulkan conformance. Current conformance status can be found at https://www.khronos.org/conformance/.
