r/vulkan • • Sep 07 '26

AI disclosure policy for posted content

125 Upvotes

AI use is a heated topic, esp. in developer communities.

To keep our community transparent and conversations on-topic, we require that you clearly disclose if your content was generated by or with the help of artificial intelligence.

This helps people understand the context of the discussion and keeps our community guidelines clear.

Posts that intentionally misrepresent AI-generated content as entirely human-made may be removed.

How to label: Simply add a quick note (e.g., "[Written with AI assistance]") in the title and/or at the top of your posting.


r/vulkan • • Mar 25 '20

This is not a game/application support subreddit

219 Upvotes

Please note that this subreddit is aimed at Vulkan developers. If you have any problems or questions regarding end-user support for a game or application with Vulkan that's not properly working, this is the wrong place to ask for help. Please either ask the game's developer for support or use a subreddit for that game.


r/vulkan • • 18h ago

New video tutorial: Row Major VS Column Major

Thumbnail youtu.be
15 Upvotes

r/vulkan • • 8h ago

Hierarchos-Native v0.2.5 is finally out! P3 WMMA update

1 Upvotes

so, after quite a bit of work since the v0.2.0 release, i've finally managed to get v0.2.5 published!

for anyone who followed the previous release, v0.2.0 was where i first introduced the opt-in RDNA3 WMMA implementation. since then i've been working on improving the Full FP16 path, specifically its numerical accuracy and performance, without having to sacrifice the execution structure that was already working.

the biggest change in this release is something i've been calling P3.

previously, the Full FP16 WMMA kernel merged its eight accumulator-bank partials using multiple intermediate FP16 additions. this meant that the result was rounded to FP16 several times along the way. P3 changes that final merge so all eight partials are summed in FP32, with just one final rounding to FP16.

the actual two-wave workgroup structure, K-slice stream, bank assignment, staging, cooperative multiplication and barriers are all preserved. i wanted to improve the accuracy of the final result without having to redesign the kernel all over again.

some of the results from the new qualification:

  • 37/37 numerical gates passed across all eight qualification seeds.
  • 32/32 preserved K=96 outputs were bit-identical to the previously qualified P3 GPU results.
  • REF64F16 maximum error improved from 0.03035259 to 0.02593803.
  • 31 of 32 cases improved, with zero cases getting worse.
  • The maximum tile16 distance is 0.03125, meeting the existing hard numerical limit.

i also ran another full performance sweep. this time using 24 paired measurement blocks per workload, GPU timestamps, and corrected 95% confidence intervals.

the measured improvements against the preserved Main kernel baseline were:

  • 2048×768×2048 — 1.0243×
  • 512×2048×768 — 1.1246×
  • 512×768×768 — 1.1163×
  • 128×8192×768 — 1.2722×

all four protected workloads passed independently, including the lower bounds of their confidence intervals. the largest measured improvement was around 27%.

just to clarify, these are per-dispatch GPU GEMM measurements, not end-to-end training speedups. i don't want to imply that an entire training run is suddenly 27% faster when that isn't what was measured.

there were some other changes too.

i tightened up the production dispatch admission so the profitability predicate is checked against each actual batch, rather than relying only on the maximum batch size supplied when creating the projection. the existing 16,000,000 MAC profitability floor has not changed.

i also went through the actual portable binaries and verified that they dispatch the P3 kernel when an eligible workload is supplied. the packaged trainer produced 8 cooperative P3 dispatches, and the packaged logits executable produced another 3. disabling WMMA resulted in zero cooperative dispatches, as expected.

the numerical comparison for the packaged logits test covered 262,144 finite elements, with a maximum absolute difference of 0.000738330 and RMS difference of 0.000122237.

the new release is available as a portable Windows x64 package too.

i've included seven executables, and the package was built with a statically linked MSVC runtime. there's no need to install Rust, Cargo, Python, PyTorch, Visual Studio, or the MSVC redistributable just to run it.

you will still need a compatible Vulkan-capable GPU driver and the Vulkan runtime loader. model weights aren't included.

one thing i want to make clear is that WMMA is still opt-in globally. the default is still off, and you have to explicitly select full-fp16 to use the P3 path. P3 is simply the default implementation within that mode. the Mixed precision path is separate and hasn't been replaced.

the hardware qualification was performed on my AMD Radeon Graphics adapter, PCI ID 1002:15bf (RDNA3 / Phoenix). i haven't qualified this on every RDNA3 GPU, RDNA3.5, RDNA4, Intel or NVIDIA hardware, so please don't assume universal compatibility.

there are still things i haven't been able to test, including independent clean-machine/second-device acceptance, GUI interaction, Windows 10 acceptance, and code signing. the executables are currently unsigned.

anyway, i'm really happy to finally have this one out. v0.2.0 was the first public release of the WMMA implementation, and v0.2.5 is a pretty substantial improvement to that foundation. a lot of time went into checking that the numerical improvements were real, that the performance was actually measurable, and that the distributed binaries were doing what they were supposed to do.

Release: https://github.com/necat101/Hierarchos-Native/releases/tag/v0.2.5

Source: https://github.com/necat101/Hierarchos-Native

thank you to everyone who's been following the project, testing things, reporting issues, or just keeping an eye on development. it genuinely means a lot! thank you so much everyone!! :3 also, sorry for the AI posts lately, I've been trying to save as much time as possible to work on the project itself due to live events getting tough! this one is completely human written! :3


r/vulkan • • 18h ago

Need Help with my Vulkan Renderer

Thumbnail reddit.com
3 Upvotes

r/vulkan • • 1d ago

Vulkan Dynamic Lighting - Directional, Point, Spot Lights, Tonemapping & glTF Lights

10 Upvotes

Hey, here's the next video in my vulkan series, focusing on dynamic lighting, various light types, gltf lights and tonemapping.

https://youtu.be/oarJboHgFzs


r/vulkan • • 2d ago

Vulkan 1.4.369 spec update

Thumbnail github.com
18 Upvotes

r/vulkan • • 2d ago

Physics Programming Part 5: Spring Physics

Thumbnail youtu.be
0 Upvotes

I explain the mathematics underpinning spring mechanics then implement a solution in C++ using a net as an example. Implementation begins at 10:05. Feedback is welcome.


r/vulkan • • 3d ago

Anyone think it would be cool to create VUDA(CUDA) using vulkan? Its a big task I know but probably will be a proof of concept thing to begin with.

6 Upvotes

I think it would be cool, I mean cuda is the holy grail of GPU programming and we're at a point now where reverse engineering it or whatever could possibly be done. What do y'all think? Am I stupid?


r/vulkan • • 3d ago

vknumpy is my next attempt at something useful. A real drop in NumPy but using gemm and blas from llama.cpp and adding remaining functions over time slowly

Thumbnail github.com
0 Upvotes

If someone wants to help out just read the readme and see if you want to vibe code with me lol..seriously though there is no dataframe package for vulkan so we will build that on top of this https://github.com/billyblackburn/vknumpy/blob/main/docs/ROADMAP.md


r/vulkan • • 3d ago

What are some initial architectural decisions to be made before start building a professional graphics engine ?

Thumbnail reddit.com
0 Upvotes

r/vulkan • • 5d ago

AI content Initial VuPy release: Numpy/CuPy-like GPU array library backed by vulkan

Thumbnail github.com
2 Upvotes

AI was used for this project . gemini 4 hydrogen.


r/vulkan • • 6d ago

cudash - run Cuda and Vulkan compute graphs the easy way

Post image
36 Upvotes

I took my problem - Vulkan compute needs a lot of boilerplate - and ran with it to understand what I need to do to have it run a simple way with capabilities like Cuda and Cuda Graph.

What I did

  • Kernel arguments are plain pointers, with no descriptor sets, using buffer device addresses.
  • Streams map onto the Vulkan queue, with automatic ordering between streams.
  • Graph capture records command buffers.
  • Slang compiles the same source to SPIR-V and PTX to help me check if my Vulkan Compute and Cuda parts are doing the same.

I'm currently very happy with it for my use cases so I'd like to share it and get some feedback: Any Vulkan pitfalls I’ve missed? (What) would you want a layer like this to do your compute?


r/vulkan • • 7d ago

Native Vulkan ar / 3d Viewer for android : Raster and Ray tracing Hybrid

37 Upvotes

Hi..
I am in the process of making an ar viewer in vulkan for android to run natively.

For rendering i am following a hybrid structure mixing Raster IBL approximations and path tracing, the gems are traced with tracing the ray directions and metals with split sum approximations and only traced for inter reflections once the movement stops.

The engine is general purpose focusing on jewellery embedded in an sdk to integrate with 3 lines of kotlin.

The c++ engine takes care of initializing the context based on the hardware capabilities like vulkan 1.1 support, hardware RT cores and compute path fallbacks.I have tested on mali, adreno and xclipse(Exynos) gpus.

Most of the optimization i did are around the memory and cache coherency on mobile gpus, since last couple of years got really obsessed with graphics maths and its implementations but i come from c++ background so pls let me know about the visuals of the same and how can i improve further.

It is closed source for now but happy to share any details to any one interested.

Thanks


r/vulkan • • 6d ago

Mutter Vulkan backend: release 1.2 improves GPU memory management

Thumbnail reddit.com
4 Upvotes

r/vulkan • • 6d ago

vulkan-py easymode. all the boilerplate is in easy.py. vulkan-py fork https://github.com/billyblackburn/vulkan-py-easy/tree/main

0 Upvotes

Example Line-Count Reduction

ExampleBeforeAfterWhat changed
examples/vector_add.py~300+ lines (raw vulkan_py)~57 linesUses get_default_device(), create_buffer_with_data(), create_shader_module(), dispatch()
examples/hello_triangle.py534 lines71 linesUses GraphicsDevice, create_render_pass(), create_graphics_pipeline(), create_framebuffers(), FrameSync
examples/lighting_demo.py1,860 lines815 linesUses GraphicsDevice, create_depth_resources(), create_uniform_descriptor_sets(), create_graphics_pipeline(), begin_render_pass()

r/vulkan • • 7d ago

What's a good benchmark Vulkan PortMaster game?

5 Upvotes

Hello hivemind.

I need 2-3 games or demos for testing with Vulkan on a low-end RK3326 SoC console. Can anyone recommend any good test games for this that are close to the hardware limit and support Vulkan on PortMaster?

Bonus points if they're open source games that I don't need game files for.

Thanks lots!


r/vulkan • • 8d ago

After 7 years my game with a custom Vulkan renderer is finally out

119 Upvotes

I've been posting updates a few times here the last months about the Vulkan renderer I made for my game Satelital. It just launched and is running on actual hardware of people! Which is mindblowing to me.

The demo helped me to find so many weird combinations of GPUs and old drivers I didn't had access to.

I also added other funcionality to the engine, to properly frame limit on screens with very high refresh rates. Which is quite useful in laptops to save some battery.

Here is my changelog:

- Frame pacing was quite trickry, there doesn't seem to be a unique common way of doing this, so you have vendor specific extensions like VK_EXT_present_timing to present_wait2, then present_wait and finally GOOGLE_display_timing. I use time in between frames on Vsync to avoid having tearing.

- HDR on Windows and macOS. I'm using scRGB (RGBA16F + EXTENDED_SRGB_LINEAR) which also works with MoltenVK. On Windows I switch the monitor to HDR when the game starts and restore its previous state on exit.

- I had some issues with AMD switchable graphics and Vulkan layers installed by other software. On some laptops I was picking the discrete GPU when it wasn't actually connected to the display, which resulted in a black screen.

- I added VK_EXT_device_fault along with a lot of logging for recent draw calls and memory usage. Whenever the game crashes or gives some error I can ask the player to send this, and it's been super useful to debu issues.

- I ended up lowering the minimum Vulkan version to 1.1 to support some older hardware.

It was hard to try to fix issues that didn't happened on any of my development machines, which is why I'm interested in hearing from other people who've shipped Vulkan games. What kind of issues did you run into that you never saw during development?

Also if you are interested in the game, Satelital is a puzzle game set in a small alien solar system. Each planet has its own puzzle rules and there's no tutorial explaining how things work. You have to figure them out by observing and experimenting. I made everything myself, including the engine, renderer, art and music.

You can check it here, the game is out and there is a free demo too:
https://store.steampowered.com/app/3256790/Satelital/


r/vulkan • • 8d ago

Slang extension for JetBrains IDEs

Thumbnail reddit.com
11 Upvotes

r/vulkan • • 8d ago

[Written with AI assistance] Cross-compiling Mesa 27.0 Zink to COFF-ARM64EC with native arm64 KosmicKrisp (Vulkan 1.4 -> Metal) for WGL OpenGL 4.6 viewports

0 Upvotes

Test setup running x86_64 Windows WGL OpenGL 4.6 (Compatibility Profile) workstation viewports on Apple M4 without Rosetta 2 or virtualization, pairing a COFF-ARM64EC build of Mesa 27.0.0-devel Zink (libgallium_wgl.dll) with a native arm64 build of KosmicKrisp inside a single arm64 Wine 11.20 + FEX process.

 Architecture notes and patch diffs: muradjabir.com/blog/post-rosetta-opengl-apple-silicon


r/vulkan • • 9d ago

A new physically based SSAO is now open source! CORTAO - Circular Occluder Ray-Traced Ambient Occlusion

318 Upvotes

Hi, everyone!

Today I'm releasing CORTAO, a new physically based SSAO technique invented and developed by me, as open source. Vulkan is supported through first class GLSL support, and the majority of CORTAO's development was done using Vulkan.

https://github.com/theagentd/CORTAO

Circular Occluder Ray-Traced Ambient Occlusion, or CORTAO, is a brand new physically based ambient occlusion technique. Unlike existing horizon-based state-of-the-art techniques, CORTAO is based screen space raytracing with up to 32 rays per pixel, allowing it to avoid the inherent limitations of existing techniques. Through a combination of much better convergence and clever optimizations, CORTAO is able to achieve much better quality for the same performance cost as GTAO.

All this allows CORTAO to just work without any scene-specific tweaking at all regardless of the type of scenes, whether it's a simple indoor room, an open world with heavy foliage and vegetation, or a vast space scene with extreme depth range.

Compared to existing techniques such as GTAO:

  • CORTAO provides a never-before-seen level of physical accuracy rivaling that of brute-force hardware raytracing, while only relying on screen space information.
  • CORTAO handles depth discontinuities in complex scenes in a more conservative way, avoiding the view-dependent occlusion of GTAO and producing less obvious artifacts when screen space information is limited.
  • CORTAO at the same time has greatly improved convergence, producing much higher quality results at lower sample counts even for scenes where GTAO works well, which is especially important for low-end hardware.

What started as a fun little personal project two years ago has now grown into something much bigger than I could've ever imagined, with multiple collaborations and conference applications, most of which I cannot talk about publicly yet. The open source release of CORTAO marks an important milestone where I'm finally sharing my work with the world, but the work is far from finished. There's a long to-do list of improvements and extensions that I will be exploring over the coming months and maybe even years. I'd be honored if you checked it out, and if you have any questions, I'd love to answer them.

AI disclosure: No AI was used in the development of CORTAO.


r/vulkan • • 9d ago

Issue in Vulkan Rendering for 1M objects in C++

8 Upvotes

I have been following the Introduction - Vulkan Tutorial couples of times and this time i was doing something a bit different. I have create this Lonewolf30/CityFoundingSimulator but currently with 1M objects i seem to have an issue in only getting 4 FPS, as far as i can narrow it down i seem to have an issue in the vulkan rendering sequence but i cant seem to profile using VTune as to where the slowdown is, can somebody please point me in the right direction of what i am doing wrong.

If there are any other code suggestions play let me know so i can implement them.

I have been working on this project for a while on and off, no AI was used in the creation of the rendering system, the only part i used AI in was for help with the TerrainChunkRenderer::OptimiseMeshData() algorithm.


r/vulkan • • 8d ago

AI content Building an open-source character posing and rendering tool (C++/Qt6). Looking for architectural feedback and graphics-focused contributors.

Post image
0 Upvotes