By default, Unity restricts certain Windows devices known to run Unity applications sub-optimally from using the D3D12 graphics API. However, you might find through testing that some restricted devices actually run your application better with D3D12 API than with D3D11 API. Alternatively, you might want to add further restrictions and prevent some devices from running your application with D3D12 API. Use Allow and Deny Filter Lists to fine tune which devices you want to allow to run your application with D3D12 API.
With Allow Filter List, you can allow certain devices to use D3D12 as the default graphics API to run your application. Alternatively, with the Deny Filter List, you can limit certain devices from using the D3D12 API to run your application. The restricted devices use a fallback graphics API set in the Player settings to run your application. If you don’t include an alternative graphics API, such as D3D11, in your Player settings, your application won’t launch on any devices that meet the rejection criteria. If you set the same values in both Allow and Deny Filter Lists, Unity ignores the criteria defined by those values.
If a device is included in both the Allow and Deny Filter Lists, the Allow Filter takes precedence and the device uses the D3D12 API. You can use these lists to restrict a large category of poorly performing devices from using the D3D12 API, but still allow devices that perform better with D3D12 API to use it. Although you can restrict the use of D3D12 API on a group of devices, you can use the Allow Filter List to enable particular devices from that group to still use D3D12.
To allow Windows devices to always use D3D12 API, use the following steps:
Windows devices that meet the specifications defined in the parameter values will always use D3D12 API for Unity applications.
To restrict Windows devices from using the D3D12 API, use the Deny Filter List and follow the same steps as earlier.