@@ -1728,23 +1728,10 @@ bool Video::CreateHostDevice(const char *sdlVideoDriver, bool graphicsApiRetry)
17281728 {
17291729 bool redirectToVulkan = false ;
17301730
1731- if (deviceDescription.vendor == RenderDeviceVendor::AMD )
1732- {
1733- // AMD Drivers before this version have a known issue where MSAA resolve targets will fail to work correctly.
1734- // If no specific graphics API was selected, we silently destroy this one and move to the next option as it'll
1735- // just work incorrectly otherwise and result in visual glitches and 3D rendering not working in general.
1736- constexpr uint64_t MinimumAMDDriverVersion = 0x1F00005DC2005CULL ; // 31.0.24002.92
1737- if ((Config::GraphicsAPI == EGraphicsAPI::Auto) && (deviceDescription.driverVersion < MinimumAMDDriverVersion))
1738- redirectToVulkan = true ;
1739- }
1740- else if (deviceDescription.vendor == RenderDeviceVendor::INTEL )
1741- {
1742- // Intel drivers on D3D12 are extremely buggy, introducing various graphical glitches.
1743- // We will redirect users to Vulkan until a workaround can be found.
1744- if (Config::GraphicsAPI == EGraphicsAPI::Auto)
1745- redirectToVulkan = true ;
1746- }
1747-
1731+ // ...
1732+ // There used to be driver redirections here, but they are all free from Vulkan purgatory for now...
1733+ // ...
1734+
17481735 if (redirectToVulkan)
17491736 {
17501737 g_device.reset ();
@@ -1761,10 +1748,6 @@ bool Video::CreateHostDevice(const char *sdlVideoDriver, bool graphicsApiRetry)
17611748 continue ;
17621749 }
17631750 }
1764-
1765- // Hardware resolve seems to be completely bugged on Intel D3D12 drivers.
1766- g_hardwareResolve = (deviceDescription.vendor != RenderDeviceVendor::INTEL );
1767- g_hardwareDepthResolve = (deviceDescription.vendor != RenderDeviceVendor::INTEL );
17681751 }
17691752
17701753 g_vulkan = (interfaceFunction == CreateVulkanInterfaceWrapper);
0 commit comments