<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic WebGL issue with HD 5000 in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/WebGL-issue-with-HD-5000/m-p/1172564#M87845</link>
    <description>&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;We are developing a Qt application with QtWebEngine (which uses Chromium under the hood). When we view certain WebGL content in this application on a specific computer, rendering is often incorrect - objects appear black or near-black, as though lighting and/or texturing is not working properly. And without certain features disabled, WebGL content does not work at all. The same content and app work fine on other hardware; this seems to be specific to the Intel driver and/or GPU hardware that we're using. Details below.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;System Setup Information:&lt;BR /&gt;
	-----------------------------------------&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;System Used: Microsoft Surface Pro 3&lt;BR /&gt;
	CPU SKU: i7-4650U&lt;BR /&gt;
	GPU SKU: HD5000&lt;BR /&gt;
	Processor Line: U series&lt;BR /&gt;
	System BIOS Version: America Megatrends 3.11.2150, 4/26/2017&lt;BR /&gt;
	CMOS settings:&lt;BR /&gt;
	Graphics Driver Version:20.19.15.4568, 15.40.36.4703&lt;BR /&gt;
	GOP/VBIOS Version:&lt;BR /&gt;
	Operating System: Windows 10 Pro&lt;BR /&gt;
	OS Version:&lt;BR /&gt;
	API:&lt;BR /&gt;
	Occurs on non-Intel GPUs?: No&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Steps to Reproduce:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	0. Close all open instances of google chrome browser.&lt;BR /&gt;
	1. Launch any recent version of google chrome browser with --use-gl=desktop and --ignore-gpu-blacklist flags.&lt;BR /&gt;
	2. Navigate to a webgl test page such as&amp;nbsp;https://get.webgl.org/&lt;BR /&gt;
	*3. The page reports that webgl is disabled even though the hardware supports it (see also chrome://gpu).&lt;BR /&gt;
	4. Once again close all open instances of the browser.&lt;BR /&gt;
	5. Launch the browser again with the above flags, and the additional --disable-es3-gl-context flag.&lt;BR /&gt;
	6. Navigate to&amp;nbsp;https://threejs.org/examples&lt;BR /&gt;
	*7. Many examples work fine, but many render objects as black, such as&amp;nbsp;https://threejs.org/examples/#webgl_lights_hemisphere&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Expected Results:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	At step 3, we expect the spinning cube and a message saying opengl is working.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;At step 7, we expect that object surfaces are properly lit and colored.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Actual Results:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	As noted, we observe that at step 3, webgl is disabled. And at step 7, we see surfaces as black / unlit.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Additional Information:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	If we omit the flags, then Chrome browser uses ANGLE to render WebGL content rather than the system-installed opengl32.dll, and that works fine. Also, if we use a software-only opengl implementation rather than the system-installed one, the content also works fine. So we suspect a fault in the Intel driver and/or the opengl implementation that ships with it.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Aug 2017 17:17:19 GMT</pubDate>
    <dc:creator>Matt_A_</dc:creator>
    <dc:date>2017-08-24T17:17:19Z</dc:date>
    <item>
      <title>WebGL issue with HD 5000</title>
      <link>https://community.intel.com/t5/Graphics/WebGL-issue-with-HD-5000/m-p/1172564#M87845</link>
      <description>&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;We are developing a Qt application with QtWebEngine (which uses Chromium under the hood). When we view certain WebGL content in this application on a specific computer, rendering is often incorrect - objects appear black or near-black, as though lighting and/or texturing is not working properly. And without certain features disabled, WebGL content does not work at all. The same content and app work fine on other hardware; this seems to be specific to the Intel driver and/or GPU hardware that we're using. Details below.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;System Setup Information:&lt;BR /&gt;
	-----------------------------------------&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;System Used: Microsoft Surface Pro 3&lt;BR /&gt;
	CPU SKU: i7-4650U&lt;BR /&gt;
	GPU SKU: HD5000&lt;BR /&gt;
	Processor Line: U series&lt;BR /&gt;
	System BIOS Version: America Megatrends 3.11.2150, 4/26/2017&lt;BR /&gt;
	CMOS settings:&lt;BR /&gt;
	Graphics Driver Version:20.19.15.4568, 15.40.36.4703&lt;BR /&gt;
	GOP/VBIOS Version:&lt;BR /&gt;
	Operating System: Windows 10 Pro&lt;BR /&gt;
	OS Version:&lt;BR /&gt;
	API:&lt;BR /&gt;
	Occurs on non-Intel GPUs?: No&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Steps to Reproduce:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	0. Close all open instances of google chrome browser.&lt;BR /&gt;
	1. Launch any recent version of google chrome browser with --use-gl=desktop and --ignore-gpu-blacklist flags.&lt;BR /&gt;
	2. Navigate to a webgl test page such as&amp;nbsp;https://get.webgl.org/&lt;BR /&gt;
	*3. The page reports that webgl is disabled even though the hardware supports it (see also chrome://gpu).&lt;BR /&gt;
	4. Once again close all open instances of the browser.&lt;BR /&gt;
	5. Launch the browser again with the above flags, and the additional --disable-es3-gl-context flag.&lt;BR /&gt;
	6. Navigate to&amp;nbsp;https://threejs.org/examples&lt;BR /&gt;
	*7. Many examples work fine, but many render objects as black, such as&amp;nbsp;https://threejs.org/examples/#webgl_lights_hemisphere&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Expected Results:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	At step 3, we expect the spinning cube and a message saying opengl is working.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;At step 7, we expect that object surfaces are properly lit and colored.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Actual Results:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	As noted, we observe that at step 3, webgl is disabled. And at step 7, we see surfaces as black / unlit.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;Additional Information:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	If we omit the flags, then Chrome browser uses ANGLE to render WebGL content rather than the system-installed opengl32.dll, and that works fine. Also, if we use a software-only opengl implementation rather than the system-installed one, the content also works fine. So we suspect a fault in the Intel driver and/or the opengl implementation that ships with it.&lt;/P&gt;

&lt;P style="word-wrap: break-word; font-size: 12px;"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2017 17:17:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/WebGL-issue-with-HD-5000/m-p/1172564#M87845</guid>
      <dc:creator>Matt_A_</dc:creator>
      <dc:date>2017-08-24T17:17:19Z</dc:date>
    </item>
  </channel>
</rss>

