The situation
The studio's iteration velocity dropped 60 percent under the baked-lightmap workflow — restoring real-time GI is an existential workflow win for the team.
Your task
Implement a real-time global illumination technique in an indie engine, hit 16ms/frame on RTX 3060-class hardware, and ship 3 demo scenes.
The brief
What you do
- Survey 3 candidate GI techniques: voxel cone tracing (VXGI-style), screen-space GI (SSGI), and irradiance probe volumes.
- Pick one and justify based on quality/perf trade-offs for the target scenes.
- Implement it in the existing renderer (Vulkan-based, source available).
- Demo on 3 scenes: a small bedroom, a corridor, and a multi-room temple.
- Hit 16ms/frame on RTX 3060-class GPU.
You deliver
Implementation, the 3 demo scenes, a performance + quality comparison vs. the baked baseline, and a 12-page technique-decision document.
What you will practice
- Survey and compare real-time GI techniques against a scene-specific budget
- Implement a non-trivial GI technique in a real engine
- Compose multi-pass rendering with GI as a deferred contribution
- Communicate technique trade-offs for studio-leadership review
A suggested way in
- SSGI is the cheapest to implement and the most limited — start there only if quality is acceptable for the 3 scenes
- Probe-based GI scales well to large scenes but the relighting math is more involved than it looks
- Always profile per-pass on RenderDoc — GI passes often regress when integrated with the rest of the renderer
Skills you will practice
Physically based rendering, Global illumination, Gpu pipeline, Shading and lighting, Vulkan, Shader programming
How it is assessed
- Visual quality30%
GI improves quality demonstrably vs. unlit baseline; matches baked closely where possible.
- Performance30%
16ms/frame met on RTX 3060 across all 3 scenes.
- Engine integration20%
GI passes integrate cleanly with existing render-pass architecture.
- Technique-decision document20%
Document defends the chosen technique against the two alternatives.
Resources
- VulkanTool
Engine's existing graphics API.
- C++Tool
Engine implementation language.
- GLSLTool
Shader language for the GI sampling passes.
- RenderDocTool
Frame capture and shader debugging.
- GitTool
Version the engine integration.
- NotionTool
Author the technique-decision document.
- FigmaTool
Diagram the GI pipeline passes for the document.
Finish it. Earn this.
A verified certificate with your name. Anyone can check it.
Time to practice.
Solve this challengeMore like this.
- Software EngineerBuild a Multi-Level Feedback Queue Scheduler in xv6
- Software EngineerReverse-Engineer a Stripped Binary to Restore Linking Symbols
- Software EngineerImplement a Distance-Vector Routing Algorithm
- AI EngineerEnd-to-End Lane Following on a Donkeycar Platform
-
Build a Multi-Level Feedback Queue Scheduler in xv6 Software Engineer Fork the xv6-riscv repository and implement MLFQ in proc.c with 3 priority queues, per-queue time slices (10ms / 20ms / 40ms), priority demotion on sl operating systemsschedulingc programming Open challenge → -
Reverse-Engineer a Stripped Binary to Restore Linking Symbols Software Engineer Receive the stripped shared object (Linux ELF, x86-64, ~280KB), a crash dump with 12 frames of indecipherable addresses, and 4 years of partial git hi reverse engineeringlinking and loadingmachine code Open challenge → -
Implement a Distance-Vector Routing Algorithm Software Engineer Implement distance-vector routing in Python: each simulated router maintains a distance vector, exchanges vectors with neighbors every 1 second of sim routingdistance vectornetwork simulation Open challenge → -
End-to-End Lane Following on a Donkeycar Platform AI Engineer Use the public Donkeycar Tub dataset (or collect about 30 minutes of driving on the simulator). Train a CNN-policy baseline (the Donkeycar default arc end to end learningimitation learningpytorch Open challenge →