# DirectX 12, Shader Caches, and the Steam Startup Work

> The graphics feature work and Steam startup fixes advanced useful components. Neither a feature probe nor a running Steam process closed the application journey.

Canonical page: https://pyrosoft.pro/blog/directx-12-shader-caches-and-steam

Live development journal; no publication date.
Work period: 2026-09-04 to 2026-09-06
Updated: 2026-10-20

DirectX 12 support is a good place to be careful about the word working. A particular feature can pass a probe while a game still stops before it reaches that feature. During this period, the project had targeted work on the vkd3d-proton and MoltenVK route, including sparse-resource behavior, pipeline caching, and the feature level exposed by selected test configurations.

Those results are useful because they identify a specific capability or missing mechanism. They aren't enough to label the whole DirectX 12 path complete. A real title has to reach the graphics code, render the expected image, and continue through an interactive session. Some title investigations stopped earlier in the surrounding Windows runtime.

Steam was another large part of the work. Getting the client further into startup involved networking, COM and WMI behavior, process support, and thread-local storage. The records describe concrete blockers being removed and new ones becoming visible. That is progress, even when the final result is still a named failure.

One example involved worker-thread TLS data. Code was trying to copy a template from a runtime module address that wasn't safe to use there. The repair validated and preserved the template in driver-owned memory so the worker could use a stable snapshot. That is the kind of fix that can let a program move past one crash without resolving the rest of its startup.

The boundary I want to preserve is that SteamAPI_Init was still false in the relevant recorded work. A client process starting, loading more libraries, or passing a network initialization step doesn't prove that an owned Steam title reaches its menu through a working client.

The shader-cache results also stay attached to the tests and staged graphics artifacts that produced them. I don't want to turn a specific warm-pipeline improvement into a promise about every game's frame pacing. This phase improved important pieces of the stack, while the complete Steam and DirectX application journeys remained open.