Latest Directx Now
With , the GPU launches a "Node." That node processes the work. If it needs more work (a second bounce, a third bounce, a particle effect that spawns more particles), it spawns a child node right there on the silicon.
The terror comes from memory. Because the GPU can now generate infinite work (a particle system that explodes into a million more particles), developers can no longer rely on static buffers. Microsoft solved this with —a safety net where excess work spills over into system memory without crashing the driver.
This month, Microsoft’s DirectX team officially changed the menu. With the general release of (via the latest Agility SDK), the GPU finally got a promotion. It is no longer just a brute-force calculator; it now has a scheduler of its own. The "Load Balancing" Nightmare To understand why this is a solid leap forward, you have to look at the old way: the Command List . latest directx
We have reached a point where CPUs aren't getting much faster; they are just getting more cores. Work Graphs finally admit that the GPU is the star of the show. By letting the GPU manage itself, Microsoft has effectively removed the traffic cop from the intersection.
For decades, programming a graphics card has felt like managing a chaotic restaurant kitchen. The CPU (the head chef) had to shout every single instruction: chop the onions, boil the water, plate the steak. If the kitchen fell behind, the chef had to stop everything to micro-manage the cleanup. With , the GPU launches a "Node
The problem? If the GPU finished its work early, it sat idle, twiddling its thumbs while the slow CPU scrambled to feed it the next list of chores. Developers tried to fix this with "ExecuteIndirect," which let the GPU decide how many threads to launch. But that was like giving a line cook a calculator; they could count the onions, but they couldn't decide to make soup instead of salad. Enter Work Graphs: The "Recursive GPU" Work Graphs turn that old linear kitchen into a hive mind.
The GPU finally learned to manage itself. Developers just have to learn to let go. Because the GPU can now generate infinite work
No CPU involvement. No round trip. The GPU becomes recursive. I spoke with a graphics engineer at a major AAA studio (who requested anonymity due to NDA constraints) about the new SDK. His response was blunt: "It’s terrifying, but necessary."
