The open-source OS ReactOS merged pull request (PR) #9352 on September 25, 2026, updating its DirectX compatibility layer to align with the Wine 10 implementation. The change spans 498,142 lines added, 119,138 lines removed, and 964 files. However, it would be premature to read these numbers as a direct indicator of the number of newly supported games or the scale of performance improvements. At its core, this update involves re-importing long-diverged Wine code and reconnecting it to fit ReactOS's specific needs, namely legacy Windows compatibility and a limited testing environment.
498,142 Lines Reflects Sync Scope, Not Feature Count
PR #9352 consists of 19 commits. The central commit is titled "Reimport all directx from WINE-10.0," indicating a broad re-import of Wine-derived DirectX compatibility code. This covers DirectDraw and Direct3D, and also includes DirectMusic and DirectShow-related components. While the PR's statistics show 498,142 lines added and 119,138 lines removed, this does not mean 498,142 lines' worth of new functionality was built from scratch. Since the change involves a large-scale re-import and file synchronization, these numbers should be understood as an indicator of the breadth of the change, not its functional depth.
The version labeling also requires clarification. The PR description states the goal as moving "to Wine 10.0," and the main commit explicitly cites a re-import from Wine 10.0. Meanwhile, the PR's title references a specific snapshot of Wine-10.1-dev. Therefore, it would be inaccurate to conclude that the merged ReactOS is now fully equivalent to all of Wine 10.1. It is more accurate to describe this as a synchronization based on Wine 10.0-era code, with the update also incorporating a subsequent development snapshot.
Developer Justin Miller has stated that he spent over 230 hours on this PR. Even so, he has not described the work as complete. The sheer scale of the change reflects less about how far the project has now reached, and more about how much distance had to be closed to catch up from an older codebase to the current generation.
OpenGL Is the Reality; Vulkan Comes With Conditions
ReactOS's DirectX compatibility functionality does not pass the API seen by Windows games directly to the GPU. Instead, it renders through OpenGL or Vulkan via components like WineD3D. According to the PR description, OpenGL is currently the primary rendering path in use, while the Vulkan path comes with conditions. Using Vulkan reportedly requires either a custom branch or Mesa's software rendering environment, and there is no indication that it is broadly usable in a standard configuration.
This limitation does not diminish the value of the update. If anything, it clarifies that importing the DirectX API is a separate layer from actually establishing the pipeline that renders to the screen. Even as synchronization on the API side progresses, outcomes for individual games can still vary depending on GPU drivers, the level of OpenGL support, and the state of Vulkan path integration.
Indeed, the commits include logic to detect environments where WineD3D cannot be used, along with a change that displays a warning only once per process when 3D rendering is unavailable. This is not proof of a performance improvement; rather, it is a mechanism for the OS to recognize situations where a rendering path cannot be established and to inform the user. When evaluating compatibility improvements, it is necessary to distinguish between whether something launches, whether it renders correctly, and whether it runs at an adequate speed.
Three Boundaries: Code Import, OS Generation, and Test Environment
This DirectX update simultaneously encompasses three distinct efforts: importing Wine 10.0 code, reducing NT5.x-specific dependencies while separating the build for Vista-and-later DLLs, and working around an OpenGL 2.0 constraint in the test environment.
| Boundary | Relevant Commits | Actual Work | What Not to Misread |
|---|---|---|---|
| Wine sync | 9fff962, 76d0793 |
Re-import of DirectX-related code and synchronization of DirectMusic | The line count is not a measure of new feature count or performance gain |
| OS generation gap | a34ee87, 479b23d |
Removing dependencies unnecessary on NT5.x and separating the build for Vista-and-later DLLs | Wine's code was not moved over unmodified |
| Test environment | c725e6a, bd6c202, edc88d4 |
Disabling certain tests on test machines that don't meet OpenGL 2.0, and adjusting tests for compatible environments | Disabled tests do not indicate a passing grade for the feature |
This table categorizes the 19 commits included in the same PR into "sync," "OS generation," and "test environment" roles, based on what is explicitly stated in each commit title. It does not quantify the performance contribution or importance of each change, nor does it represent a comprehensive audit of every individual change. In particular, the changes disabling D3DX9 shader tests and Quartz-related tests until OpenGL 2.0 support is available represent a workaround for the limitations of the testing hardware—not proof that the targeted functionality is complete.
The PR also includes a link to ReactOS Testman, comparing x86 and x64 builds running on KVM. However, based solely on the materials obtained for this article, it is not possible to confirm the pass/fail status of individual tests or whether any regressions occurred. The fact that a large-scale sync has been merged must be kept separate from any assessment of stable operation across a wide range of hardware and games.
"Hundreds of Games" Is a Hypothesis to Verify, Not a Confirmed Result
Miller has suggested that, combined with this update and other pending PRs, hundreds of games that previously failed to launch could potentially now work. As a specific example, he cited "Dragon Age: Origins." Since the update includes changes to reduce dependencies for launching that title under the legacy NT5.x compatibility environment, it can be understood as an illustrative example of the direction of this work.
However, "hundreds of games" is not a tally from a verified list; it is a developer's estimate. Moreover, it presupposes not just this PR alone but its combination with other pending PRs. A game launching is not synonymous with its visuals, audio, and input all working correctly, nor with it being playable at a practical frame rate. The published PR does not include game-by-game reproduction conditions, GPU configurations, frame rates, or a pass/fail list.
Three things remain to be verified next: whether the Vulkan rendering path will be incorporated into the standard configuration, whether the tests disabled due to the OpenGL 2.0 limitation can be restored once a testing environment with OpenGL 2.0 or higher is available, and whether game-by-game results can be accumulated along with reproducible conditions. This merge is not a declaration that ReactOS's game compatibility is now immediately guaranteed to be complete. Rather, it is a major foundational update aimed at closing the gap with Wine and re-establishing a baseline for measuring compatibility.