Vulkan
Vulkan-Docs
Our great sponsors
Vulkan | Vulkan-Docs | |
---|---|---|
70 | 161 | |
9,693 | 2,660 | |
- | 0.9% | |
9.3 | 8.5 | |
6 days ago | 23 days ago | |
GLSL | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Vulkan
-
Usages for vkCreateHeadlessSurfaceEXT
Samples in https://github.com/SaschaWillems/Vulkan have shown how to use vkCreateHeadlessSurfaceEXT. But these headless samples crash at acquireNextImage from the swapchain. Now I guess the problem lies in the vulkan-wsi-layer.
-
offscreen rendering vs render to texture
This is the reference I used. https://github.com/SaschaWillems/Vulkan/blob/master/examples/hdr/hdr.cpp
-
Question about descriptor buffers.
Hi, I'm messing with descriptor buffers but I've came across certain issues I can't seem to solve. I'm using this tutorial as reference. I've tried UBOs and SSBOs, it works perfectly and there is no need to change the buffers offsets when recording a command buffer because I can access them by index like this:
-
Need help learning descriptor sets
Hi I am trying to learn Vulkan for an upcoming project and I have so far found everything to be straight forward if very verbose. I have now come to descriptor sets, layout bindings and the so forth and it's got more confusing than I can work out. I have been following this github repo for a headless compute example and it works fine as it is. But when I tried to add an additional storage buffer to the test shader than it comes with I am unable to copy the data over instead just getting a whole collection of 0's.
- Sascha Willems bloom example dependency management
-
Vulkan ray tracer with fog and stuff
P.S. do you know of Sascha Willems’ code? https://github.com/SaschaWillems/Vulkan
-
Proper way to access a read-only texture that has no sampler from an hlsl compute shader?
BTW, this problem can be reproduced as described below: - clone https://github.com/SaschaWillems/Vulkan.git - build the project and run it with arguments : -v - s hlsl to enable the validation layer and to use hlsl code - run ComputeShader project. The following validation error "Type mismatch on descriptor slot ..." will be shown in the console. - to fix it, as suggested above, you can replace the 3rd line of emboss.comp, sharpen.comp, and edgedetect.comp from: Texture2D inputImage : register(t0); //Creates validation errors to RWTexture2D inputImage : register(u0); //no validation errors (you'll then need to recompile the shaders to spv with a proper hlsl compiler such as Microsoft dxc)
-
Recommendations on how to start a small Vulkan project
Another way I saw some projects start was by using example base classes (either Sascha Willems' implementations or the framework used by Khronos Samples).
-
I've been working on a real-time ray tracing renderer
It's not a tutorial but I'd recommend Sascha Willems examples. A good next step could be adding models and shadows (see https://github.com/SaschaWillems/Vulkan/tree/master/examples/raytracingshadows). It's a single file but you can easily understand what each function does.
-
Add a second texture to Sascha Willems glftLoading app
Exactly as u/aerorang said. I recommend comparing your linked example with Sascha's gtTF Scene rendering example where he adds a normal map along with the base albedo texture. He also marked important parts of the code with the POI keyword, so you can search for them in the code.
Vulkan-Docs
-
GPU synchronization in Godot 4.3 is getting a major upgrade
Pipelines (or in general terms PSOs) are the most problematic aspect of Vulkan / DX12 - much more than synchronization! Large parts of the gamedev industry seems to recognize all the performance issues with pipelines and therefore companies are experimenting with newer models like the VK_EXT_shader_object extension ("Vulkan without Pipelines": https://www.khronos.org/blog/you-can-use-vulkan-without-pipe...).
I've written a detailed comment about this before here (https://news.ycombinator.com/item?id=37843946#37845431) but for a much more comprehensive explanation by an engineer from Nintendo read the initial proposal for the VK_EXT_shader_object extension: https://github.com/KhronosGroup/Vulkan-Docs/blob/main/propos...).
There's also Casey Muratori's mail to the Vulkan advisory on 2015 that basically predicts this whole clusterfuck would happen: https://github.com/cmuratori/misc/blob/main/vulkan_dynamic_s...
- Vulkan 1.3.273 spec update
- [Roadmap Feedback] Function Pointers with some limitations
-
New Vulkan Documentation Website
Apple -> MoltenVK is an emulation layer and doesn't give you as much control as using Metal directly.
Nintendo and Sony prefer their own APIs, NVN and LibGNM, and AIUI Vulkan is a second-class API on those platforms which does not offer as much power, it is widely understood studios use NVN and LibGNM to get access to the real hardware on those platforms.
Windows/AMD/NVidia/Intel -> HW manufacturers tend to prototype and release new features with D3D first and then 'backport' them to Vulkan after a while. DirectX 12 for example had mesh shaders for over 2 years before Vulkan got a vendor neutral extension for them[0]
Android and Linux are the only platform where Vulkan is a first-class citizen.
You could maybe argue Nvidia treats Vulkan as a first-class citizen because they tend to have vendor-specific Vulkan extensions for the latest features available before anyone else. But otherwise, no, Vulkan is not a first-class API anywhere except Linux and Android.
Graphics API wars are alive and well.
- Vulkan 1.3.267 spec update
- Vulkan 1.3.266 spec update
- Vulkan 1.3.262 spec update
- Vulkan 1.3.260 spec update
- Vulkan 1.3.257 spec update
- Vulkan 1.3.256 spec update
What are some alternatives?
vulkano - Safe and rich Rust wrapper around the Vulkan API
wgsl-cheat-sheet - Cheat sheet for WGSL syntax for developers coming from GLSL.
vulkan-guide - Introductory guide to vulkan.
vkd3d-proton - Fork of VKD3D. Development branches for Proton's Direct3D 12 implementation.
vk-bootstrap - Vulkan Bootstrapping Iibrary
webgpu-wgsl-hello-triangle - An example of how to render a triangle with WebGPU using WebGPU Shading Language - the "Hello world!" of computer graphics.
msdf-atlas-gen - MSDF font atlas generator
Vulkan-Headers - Vulkan header files and API registry
tinyrenderer - A brief computer graphics / rendering course
WASI - WebAssembly System Interface
Vulkan-Samples - One stop solution for all Vulkan samples
vulkan-gp