GPU Decompression for Game Loading? DirectStorage Mechanism, NVMe Requirements & Why It May Not Activate

｜ HK GPU Fix

重點摘要

When a game loads slowly, the graphics card may not be the problem. This guide explains how DirectStorage and GPU decompression reorganise game loading, what NVMe and system conditions the full path needs, and why it may not activate even on capable hardware.

The Traditional Loading Path: Why the Processor Becomes the Bottleneck

Game assets are stored on disk in compressed form, and loading them has traditionally followed a path that runs through the processor. The processor decompresses the assets and then sends them onward to the graphics card, handling a large number of small requests one after another. When a game world is large and its assets are many and fragmented, that processor-side handling becomes the bottleneck: loading takes longer, and in an open world, textures can arrive late while the player is already moving, producing the visible pop-in where detail appears after the scene it belongs to.

The important point is that this bottleneck is structural, not a sign that any single component is faulty. The processor is doing work it was not best shaped for, namely a very large number of small decompression tasks handled in sequence, while the graphics card waits for data it is well shaped to consume. DirectStorage exists to reorganise that path, not to replace any component, and understanding the old path first is what makes the new path intelligible. Any guide that presents slow loading as proof of a weak graphics card, without first describing this path, will misdirect its reader.

A further point must be stated before any new mechanism is introduced: slow loading has many possible causes, and the loading path is only one of them. Shader compilation pauses, game interface choices, processor bottlenecks, a disk close to full, and background programs competing for resources can all make loading slow. DirectStorage not running is not the only explanation for slow loading, and this guide returns to that exclusion step at the end of its diagnostic order. The temptation to blame every loading problem on one mechanism must be resisted from the start.

DirectStorage: An Interface That Reorganises the Path

DirectStorage is an application programming interface provided by Microsoft, originating in the fast-loading design of the Xbox platform. Its purpose is to reshape the loading path so that data from an NVMe disk reaches the graphics card in larger batches and with less processor involvement along the way. It is not a program the owner installs, not a driver with its own switch, and not a setting hidden in a game menu. It is an interface that a game developer calls upon inside the game itself, and that distinction governs everything that follows.

The version history matters because the two stages are often confused. The first stage mainly addressed the transfer path, letting disk data move toward the graphics card more directly and in batches. The later stage, from version 1.1 onward, added GPU decompression, moving the decompression work itself from the processor to the graphics card. Those two stages must not be blended into a single claim, because a game or system described as supporting the interface in general may not carry the decompression stage in particular. The decompression stage is the part this guide examines in detail, and its conditions are stricter than the transfer stage alone.

GPU decompression pairs with a compression format designed for parallel graphics work, known as GDeflate. The graphics card is well shaped for handling many small tasks at once, which is exactly the shape of asset decompression work, so moving that work to the graphics card fits the hardware to the task. That fit is the mechanism's logic, and it should be stated as a design fit rather than as a promise about any particular game. Whether a given game benefits, and by how much in the owner's experience, depends on the game's assets, its implementation, and the rest of the system, and this guide makes no quantified claim about any of them.

The Decisive Condition: The Game Itself Must Implement It

The single most important condition is also the most often missed: the game itself must implement DirectStorage. Because the interface is called upon by the game developer inside the game, no combination of system conditions can activate it in a game that does not implement it. A system can meet every hardware and software condition, and a game without implementation will still load by the traditional path. That is normal behaviour, not a fault, and it is the first thing to establish before any hardware or driver check is attempted.

It follows that the absence of a DirectStorage switch in a game menu is itself normal. There is no user-facing switch to turn the interface on, because there is nothing for the owner to switch: the game either calls the interface or it does not. An owner searching menus for a toggle that does not exist will conclude wrongly that something is disabled or broken, when the correct check is the game's own official information about whether it implements the interface. Where that official information is silent, the honest position is that implementation is unconfirmed, not that the system is at fault.

This also settles the language that must not be used. There is no separate DirectStorage driver to install, and the phrase installing a DirectStorage driver misdescribes the mechanism. Capability comes jointly from the game's implementation, the system, the drivers, and the hardware together, and no single installation step can supply it alone. Guides that promise activation through a download misunderstand the interface, and owners who follow them will change drivers and settings without ever reaching the real condition.

The Four Conditions of the Full Path

The full path requires four conditions together, and the absence of any one of them means the full path does not run. First, a game that supports the interface, as established above. Second, an NVMe solid-state disk connected through the PCIe bus, with the game itself installed on that qualifying disk. It is not enough for the system disk to qualify while the game sits on another older disk; the game must live on the qualifying disk itself. Third, a graphics card that supports the DirectX 12 Ultimate interface level and Shader Model 6.0. Fourth, the Windows 11 system, whose storage optimisation path belongs to the full route.

Windows 10 requires careful wording. The interface itself is supported on Windows 10, so Windows 10 must not be described as having no DirectStorage at all. But its storage stack is older, and its benefit is lower than on Windows 11, because the complete storage optimisation path belongs to Windows 11. An owner on Windows 10 who meets the other conditions is therefore not in an error state, but in a reduced-benefit state, and that distinction matters for honest advice. Likewise, a graphics card below the DirectX 12 Ultimate and Shader Model 6.0 level does not meet the threshold for the full path, and that is a threshold matter, not evidence of driver damage.

The storage optimisation path on Windows 11 is known as BypassIO, and this guide describes it at the concept level only. In concept, it lets qualifying reads bypass part of the traditional file system filtering layer, so that data reaches its destination with less intermediate handling. If the storage driver or an intermediate filtering driver does not support that path, the system falls back to the traditional path, the interface benefit is reduced, and the game itself still runs. That fallback is graceful rather than a failure, and it must be described that way. This guide gives no registry steps, no checking commands, and no third-party tool procedures for this layer, because those belong to advanced system work and are not needed to judge whether the conditions are met.

Drivers and Updates: Exposure, Not Activation

The graphics driver, system updates, and motherboard chipset driver must be kept current, because interface capability is exposed through drivers. An outdated driver may fail to expose capability that the hardware otherwise carries, so the system check described below may show an unoptimised state for a driver reason rather than a hardware reason. Updating is therefore a genuine diagnostic step, and it belongs in the checking order.

But updating must not be confused with activation. Updating a driver only lets qualifying hardware be recognised; it does not create implementation in a game that lacks it, and it does not switch the interface on. An owner who updates everything and still sees no change in a game without implementation has not failed at updating, and has not encountered a fault. The update step and the implementation step answer different questions, and the checking order below keeps them separate for exactly that reason.

The user-level check for system recognition is the gaming features page of the Xbox Game Bar, which shows whether the graphics card and the disk are recognised as optimised for the interface. That page confirms recognition at the system level, and its limits must be stated plainly: it is not a guarantee about any particular game. A Game Bar page showing optimised status does not mean a specific game is using the interface, because the game's own implementation remains a separate condition. The Game Bar result and the game implementation result are two different answers, and only together do they describe the full picture.

Checking in Order: Game Layer First, Hardware Blame Last

Step one is game implementation. Confirm from the game's official information whether that game implements the interface. If it does not, the remaining checks are unnecessary, and loading behaviour in that game has nothing to do with the interface. Stopping here is not laziness; it is the correct end of the investigation for that game, and it prevents a long chain of driver and hardware changes that could never have helped.

Step two is install location. Confirm that the game is installed on the qualifying NVMe disk itself, not merely that some disk in the machine qualifies. Step three is system recognition: use the Game Bar gaming features page to confirm whether the graphics card and the disk show as optimised, and where they do not, work through the conditions one by one, system version, driver state, and disk type, rather than changing several at once. Step four is system and driver updates, applied one layer at a time, with the Game Bar state rechecked after each layer, so that any change can be attributed to the layer that produced it.

Step five is the storage path layer. If the Game Bar page shows the disk as unsupported, the cause may sit in the storage driver or filtering driver layer, and the direction is to update the relevant drivers or firmware and to consult the disk maker's support channel. This guide deliberately stops at that direction and gives no registry, command, or third-party tool procedure. Step six is the exclusion of other loading causes: shader compilation, game interface choice, processor bottleneck, a disk close to full, and background programs competing for resources. Shader compilation pauses are article 161, game interface choice effects are article 213, and video hardware decoding, which is a different layer from game asset decompression, is article 173, each pointed to here in a single sentence. Only after those exclusions can loading behaviour be discussed fairly, and even then the discussion must stay at the level of which path is running, not at the level of promised gains.

Boundary Cases and Honest Limits

A game on a SATA solid-state disk or a traditional hard disk still runs; it simply does not run the complete interface path. That must never be written as being unable to play, because the traditional loading path remains fully available. A graphics card below the DirectX 12 Ultimate and Shader Model 6.0 threshold is in the same position: no complete path, but no error state either. Windows 10, as already stated, supports the interface with an older storage stack and a lower benefit, and must not be written off entirely.

A game that implements the interface but feels no faster to its owner is not necessarily failing. Loading behaviour still depends on asset scale, the relative capability of processor and graphics card, and disk state, and the interface shortens the loading and streaming stages, not the frame rate. Frame rate must never be used to judge whether the interface is active, because the interface affects loading and asset streaming, not frame rate, and a frame rate comparison will mislead in both directions. A game that feels unchanged may still be using the interface, and a game that feels smoother for other reasons may not be using it at all.

GPU decompression and processor decompression can also be chosen between by the game and its configuration, so GPU decompression is not necessarily faster in every configuration. The game may select whichever side fits its configuration better, and this guide makes no absolute faster-or-slower conclusion. That restraint is not evasiveness; it is the accurate statement, because the benefit depends on the balance of the whole system rather than on one mechanism in isolation. Official example figures for the mechanism are deliberately not quoted in this guide, because example figures are easily misread as promises about a reader's own machine.

Common Myths, Dismantled

Myth: Slow loading means the graphics card is weak. The traditional path bottlenecks at the processor, and slow loading has many causes, from shader compilation to a disk close to full. The loading path must be described before any component is blamed.

Myth: There is a DirectStorage switch to turn on. There is no user-facing switch, because the interface is called upon by the game itself. Searching menus for a toggle that does not exist will only produce a false fault.

Myth: Installing a DirectStorage driver activates it. There is no separate driver to install. Capability comes jointly from game implementation, system, drivers, and hardware, and no single download supplies it.

Myth: Updating drivers guarantees activation. Updating only exposes capability in qualifying hardware. A game without implementation still will not use the interface, however current its drivers are.

Myth: A Game Bar optimised result means a specific game uses it. The Game Bar page confirms system recognition, not game implementation. Both answers are needed, and one cannot substitute for the other.

Myth: Without the interface, a game cannot be played. Games on SATA disks and traditional hard disks run by the traditional path. The interface path is an optimisation, not a requirement for running.

Myth: The interface raises frame rate. It affects loading and asset streaming, not frame rate. Frame rate must never be used to judge whether it is active.

Myth: GPU decompression is always faster. The game and its configuration may select either side, and the benefit depends on the balance of the whole system. No absolute faster-or-slower conclusion is valid.

Frequently Asked Questions (FAQ)

Why is there no DirectStorage switch in my game menu? Because there is none to find. The interface is called upon by the game developer inside the game, not switched on by the owner. The correct check is the game's official information about whether it implements the interface, not a menu search.

My system meets every condition, but loading feels unchanged. Is something broken? Not necessarily. Loading behaviour still depends on asset scale, processor and graphics capability balance, and disk state, and the interface shortens loading and streaming, not frame rate. A game that implements the interface may still feel similar, and feeling alone cannot judge whether it is active.

The Game Bar page says my system is optimised, but does that mean my game uses it? No. The Game Bar page confirms system recognition for the graphics card and disk. Whether a particular game uses the interface depends separately on that game's implementation, and both answers are needed.

I installed the game on a different disk from my system disk. Does that matter? Yes, it can. The game itself must sit on the qualifying NVMe disk. A qualifying system disk does not compensate for a game installed on another older disk.

I use Windows 10. Do I have no DirectStorage at all? No. The interface is supported on Windows 10, but its storage stack is older and its benefit is lower than on Windows 11, where the complete storage optimisation path belongs. You are in a reduced-benefit state, not an error state.

Can I play games on a SATA disk or a traditional hard disk? Yes. Those disks run games by the traditional loading path. They simply do not run the complete interface path, and that is a path difference, not an inability to play.

I updated my graphics driver and nothing changed. Did the update fail? Not necessarily. Updating exposes capability in qualifying hardware; it does not create implementation in a game that lacks it. If the game does not implement the interface, no driver update can activate it there.

When to Seek Professional Help

If the game is confirmed to implement the interface, the game sits on a qualifying disk, system recognition shows optimised status, and loading problems persist alongside other symptoms such as repeated storage errors or display faults, a professional inspection can separate a storage or graphics problem from a game implementation matter before parts are replaced unnecessarily.

HK GPU Fix is located at Dali Plaza, Room 1209, Shek Mun. For graphics or display-related inspection, call 2186 8010 or reach us on WhatsApp at 6558 6806.