• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dual GPU by way of a DX12 API plugin?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
What would stop nVidia's drivers from shutting down their card if it detects another card in the system?

You mean render their card inoperable? Microsoft WHQL. NVIDIA would lose WHQL validation for their driver.

With PhysX, NVIDIA had proprietary control over their IP. With D3D12, they don't.
 
You have to remember that unlike SLI and CrossfireX, Multi-Adapter is API bound in D3D12 and tied directly to the D3D API and not the software driver. Software drivers don't have any control over multi-adapter, the API and the Game Developer does. In this case, the authors, Stardock, and the D3D12 API control this tech. Not AMD or NVIDIA.

If NVIDIA tried to circumvent this tech, they'd lose D3D12 support qualifications and it would be construed as a "cheat" by Microsoft.
 
In theory, its awesome because it can provide multi-GPU scaling where there is none or poor scaling due to developers just foregoing support for CF/SLI these days.

The added bonus would be mix-match GPUs. All Stardock need would be a simple performance profile for each GPU and in SFR, they can assign more or less portions to each GPU to render.

Possible with DX12 as the added overhead for a software layer approach will easily be offset by DX12's CPU efficiency gains.

Hopefully it eventuates.
 
Back
Top