Fortnite Behind the Story: Road to Android and Vulkan Collaboration With Galaxy GameDev
summary
Samsung and Epic optimize Fortnite for Galaxy by switching to Vulkan and engine changes that yield concrete wins: a captured scene moves from ~28 FPS on GL to ~43 FPS on Vulkan (Vulkan 50% boost); merging frequent render-pass transitions drops frame time by ~30 ms in heavy scenes (render-pass merging cuts ~30ms per frame); a just-in-time LRU shader cache reduces driver memory from ~250–400 MB down to ~10 MB of on-disk binaries and saves ~200 MB on an S8 (LRU shader cache saves ~200MB). They also offload draw-call work to an RHI thread, target 60 FPS for open-world runs to leave headroom, and fix hash-related cache leaks that free ~500 MB.
AI-written summary · about
chapters (12)
- 0:00Introduction to mobile port
- 1:16Scalability and hardware
- 4:07Optimizing render settings
- 10:56Performance testing strategies
- 13:23Thread management
- 15:34Managing memory on Android
- 19:32Shader and cache optimization
- 23:35Collaborating for engine improvements
- 25:05Vulkan render pass optimization
- 29:22Buffer and query management
- 31:23Fixing pipeline memory leaks
- 37:24Conclusion and Q&A
related talks
43mGalaxy GameDev: Bringing Maximum Boost to Mobile Games II
40mMaking high fidelity Android games possible with Vulkan
26mAndroid game graphics - OpenGL ES vs. Vulkan case study
12mOptimize your graphics with Android GPU Inspector frame profiler
32mOptimizing Android games performance
07mWhat's new in Android graphics optimization tools
37mThe state of Unity on Android
38mGPU. The journey from code to pixel