From a8a3ec7bbc3ddb1092dfa5cba87fa8323823d20a Mon Sep 17 00:00:00 2001
From: Ansariel <none@none>
Date: Sat, 19 Nov 2016 10:42:21 +0100
Subject: [PATCH] FIRE-20378 / FIRE-20382: Breaks memory detection an 4K
 monitor workaround; No idea why this was added here to fix DPI override -
 only thing done here is querying data, not setting anything

---
 indra/newview/llappviewerwin32.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/indra/newview/llappviewerwin32.cpp b/indra/newview/llappviewerwin32.cpp
index 0a20e796c5..2817076b9c 100644
--- a/indra/newview/llappviewerwin32.cpp
+++ b/indra/newview/llappviewerwin32.cpp
@@ -642,7 +642,7 @@ bool LLAppViewerWin32::initHardwareTest()
 	// Do driver verification and initialization based on DirectX
 	// hardware polling and driver versions
 	//
-	if (TRUE == gSavedSettings.getBOOL("ProbeHardwareOnStartup") && FALSE == gSavedSettings.getBOOL("NoHardwareProbe"))
+	if (/*TRUE == gSavedSettings.getBOOL("ProbeHardwareOnStartup") &&*/ FALSE == gSavedSettings.getBOOL("NoHardwareProbe")) // <FS:Ansariel> FIRE-20378 / FIRE-20382: Breaks memory detection an 4K monitor workaround
 	{
 		// per DEV-11631 - disable hardware probing for everything
 		// but vram.