Vulkan vs. OpenGL: A Sample Based Introduction
summary
Compares how OpenGL and Vulkan actually draw triangles, showing that OpenGL uses GLSL shaders compiled by drivers while Vulkan requires precompiled SPIR-V binaries (via shaderc or Android Studio’s shader folder). Demonstrates Vulkan image lifecycle with vkCreateImage, find memory type, allocate, bind, and explicit queue/fence synchronization. Notes Vulkan needs NDK/C++ on Android, gives working triangle and texture examples from Google samples/GitHub, and warns mis-specified memory or sync can crash the device.
AI-written summary · about
chapters (6)
- 0:00Introduction and joke
- 2:09OpenGL and the Ogillians
- 5:41Vulcans and their traits
- 9:57Memory management in Vulkan
- 15:59Synchronization and queues
- 17:06Summary and comparison
related talks
26mAndroid game graphics - OpenGL ES vs. Vulkan case study
40mThe Evolution of Android Graphics
18mVulkanized: Mobile Game Optimization Techniques
40mMaking high fidelity Android games possible with Vulkan
59mHigh performance graphics and text rendering on the GPU for...
40mFortnite Behind the Story: Road to Android and Vulkan Collaboration With Galaxy GameDev
07mWhat's new in Android graphics optimization tools
36mThe Evolution of Android Graphics in Android 12/13
