Workaround: Issue loading OpenGL on old(er) Intel chipsets / drivers …

…on Windows 10 The issue: Advertising Windows 10 compatibility in the application manifest can lead to a failure with old(er) Intel OpenGL drivers on Windows 10. (Attempting to create an OpenGL context falls back to the "GDI Generic" OpenGL Renderer, which is limited to OpenGL 1.1.0.) See: https://github.com/pal1000/save-legacy-intel-graphics
Warzone2100 · Aug 23, 2019 · 8a755a5 · 8a755a5
1 parent 7ad3174
commit 8a755a5
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 4 deletions.
diff --git a/win32/warzone2100.manifest b/win32/warzone2100.manifest
@@ -26,8 +26,9 @@
 			<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
 			<!-- Windows 8.1 -->
 			<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
-			<!-- Windows 10 -->
-			<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
+			<!-- Windows 10 -->
+			<!-- NOTE: This is commented out to avoid an issue loading OpenGL drivers for old Intel chipsets on Windows 10. -->
+			<!-- <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/> -->
 		</application>
 	</compatibility>
 </assembly>
diff --git a/win32/warzone2100.manifest.in b/win32/warzone2100.manifest.in
@@ -26,8 +26,9 @@
 			<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
 			<!-- Windows 8.1 -->
 			<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
-			<!-- Windows 10 -->
-			<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
+			<!-- Windows 10 -->
+			<!-- NOTE: This is commented out to avoid an issue loading OpenGL drivers for old Intel chipsets on Windows 10. -->
+			<!-- <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/> -->
 		</application>
 	</compatibility>
 </assembly>