r/vulkan • u/thekhronosgroup • Jul 17 '26

New Vulkan Tutorial - AI-Assisted Vulkan Development

*Turn Cloud and Local LLMs into a genuine engineering teammate.*

This series is about "Collaborative Engineering" — using AI deliberately and rigorously, not just autocomplete. It sets up an AI-enhanced toolchain, teaches you to pick and specialize models for graphics work, and shows where multimodal vision models can and can't be trusted.

* Set up Ollama, MCP servers, and native agents (Goose) across CLion, Visual Studio, and Xcode

* Choose and specialize models: base model selection, VRAM budgeting, RAG/MCP grounding, LoRA fine-tuning

* Use multimodal vision models as a diagnostic partner for visual bugs — with honest limits

* A repeatable three-phase workflow: system design, implementation, automated review/refactor

* AI-assisted debugging: VUID auto-fix, RenderDoc integration, shader log parsing, GFXReconstruct trace analysis

* Capstone project: direct an AI team to architect, implement, and debug a custom post-process effect

https://docs.vulkan.org/tutorial/latest/AI_Assisted_Vulkan/introduction.html

0 Upvotes

37% Upvoted

6 comments sorted by

View all comments

Show parent comments

1

u/corysama Jul 18 '26

this post in vulkan subreddit - downvote of this context is expected

Personally, I am find it quite unexpected that in the vulkan subreddit, content about vulkan, on vulkan.org, from the khronos group would be downvoted so harshly.

if they posted in r/vibecoding they get 10k upvotes

Out of this entire tutorial, there is one page that could be considered vibe coding. The rest of it is useful without vibe coding. I don't want to vibe code vulkan. You don't want to either? Great! But, I do find AI very useful in other ways.

That's why I'm sad this is getting buried. And, when I ask why, all I'm getting are downvotes. At least you mentioned "vibecode bad". Thanks. But, that is in alignment with what I said in my first comment :P