- #Control directx 11 or 12 drivers
- #Control directx 11 or 12 windows 10
- #Control directx 11 or 12 windows
Just remember that the new functionality may not be supported by the hardware/driver, so you need to query for support. Yes, you can still call the old version of those functions. You can either do it in advance and store separate pointers for each version, or you can call it as-needed.ģ. You can QueryInterface at runtime to get one interface version from another. So you can use D3D11.3 to target hardware with FEATURE_LEVEL_11_0, you'll just get runtime failures if you try to use functionality that's not supported.Ģ. Like I mentioned earlier 11.3 is just an API, not a mandated feature set. And to answer your follow up question "does 11.3 hardware support 12 as well", there really isn't any such thing as "11.3 hardware". I would only go down that route if you think you'll really benefit from the reduced CPU overheard and multithreading capabilities, or if you're looking for an educational experience in keeping up with the latest API's. Regarding 11.3 vs 12: D3D12 is very very different from D3D11, and generally much harder to use even for relatively simple tasks. You need to query for it at runtime to ensure that your GPU can do it. Either way you'll probably need fallback paths if you want to use new functionality like conservative rasterization, because the API doesn't guarantee that the functionality is supported. However you can still support different rendering paths by querying the supported API and feature set at runtime.
#Control directx 11 or 12 windows
If you want to run on Windows 7, then you'll need to support D3D11.0 as your minimum.
#Control directx 11 or 12 windows 10
If you're okay with Windows 10 only, then you can just target D3D11.3 or D3D12 and that's fine. You should probably choose your minimum API based on the OS support.
This means that you can't use features like conservative rasterization, even though the API supports it.ġ.
#Control directx 11 or 12 drivers
As an example, take GPU's that run on Nvidia's Kepler architecture: their drivers support D3D12 if you run on Windows 10, however if you query the feature level it will report as FEATURE_LEVEL_11_0. However using a newer API doesn't guarantee that the functionality will actually be supported by the hardware. So if you use D3D11.3 instead of D3D11.0, there are more functions and therefore more potential functionality available to you.
In general, the API version dictates the maximum feature set that can be available to your app. The feature set tells you which functionality is actually supported by the GPU and its driver. Which API you can use is primarily dictated by the version of Windows that your program is running on, but it can also be dependent on the driver. The API determines the set of possible D3D interfaces you can use, and the functions on those interfaces. So there's two separate concepts here that you need to be aware of: the API, and the supported feature set.
0 kommentar(er)
