<?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 Incorrect shader calculations in Intel HD 2000 in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103412#M87504</link>
    <description>&lt;P&gt;We have user with probably Win8.1 installed and i5-2500 cpu which have Intel HD 2000 integrated (according with CPU specs). He have latest driver installed - 4229.&lt;BR /&gt;
	When we render texture with shader that makes final alpha 0, he see dots in result. Our shader code:&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.r = dot(c0, p0); // color correction&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.g = dot(c0, p1);&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.b = dot(c0, p2);&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.a = dot(c0, p3); // alpha correction&lt;/P&gt;

&lt;P&gt;where p3 is:&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;vec.x = 0; vec.y = 0;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;vec.z = 0; vec.w = ((float) lAlpha) / 255.0f;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;map[3] = vec;&lt;/P&gt;

&lt;P&gt;I think there maybe some calculation errors in dot(c0, p3) call. Or maybe also primitive rendering with alpha 0.&lt;BR /&gt;
	Our application uses D3D11 by default.&lt;/P&gt;</description>
    <pubDate>Tue, 26 Jan 2016 07:50:56 GMT</pubDate>
    <dc:creator>Vladimir_H_</dc:creator>
    <dc:date>2016-01-26T07:50:56Z</dc:date>
    <item>
      <title>Incorrect shader calculations in Intel HD 2000</title>
      <link>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103412#M87504</link>
      <description>&lt;P&gt;We have user with probably Win8.1 installed and i5-2500 cpu which have Intel HD 2000 integrated (according with CPU specs). He have latest driver installed - 4229.&lt;BR /&gt;
	When we render texture with shader that makes final alpha 0, he see dots in result. Our shader code:&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.r = dot(c0, p0); // color correction&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.g = dot(c0, p1);&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.b = dot(c0, p2);&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;Out.a = dot(c0, p3); // alpha correction&lt;/P&gt;

&lt;P&gt;where p3 is:&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;vec.x = 0; vec.y = 0;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;vec.z = 0; vec.w = ((float) lAlpha) / 255.0f;&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;map[3] = vec;&lt;/P&gt;

&lt;P&gt;I think there maybe some calculation errors in dot(c0, p3) call. Or maybe also primitive rendering with alpha 0.&lt;BR /&gt;
	Our application uses D3D11 by default.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 07:50:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103412#M87504</guid>
      <dc:creator>Vladimir_H_</dc:creator>
      <dc:date>2016-01-26T07:50:56Z</dc:date>
    </item>
    <item>
      <title>Hi Vladimir,</title>
      <link>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103413#M87505</link>
      <description>&lt;P&gt;Hi Vladimir,&lt;/P&gt;

&lt;P&gt;HD 2000 only supports up to D3D 10.1, it is not a D3D 11 GPU. Additionally HD 2000 supported anymore, our last driver release was June 2015 and there are no new driver releases that support HD 2000 in the current plan.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Sorry I can't be of more help on this.&lt;/P&gt;

&lt;P&gt;-Michael&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 16:38:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103413#M87505</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2016-01-26T16:38:55Z</dc:date>
    </item>
    <item>
      <title>Quote:Michael C. (Intel)</title>
      <link>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103414#M87506</link>
      <description>&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;Michael C. (Intel) wrote:&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;HD 2000 only supports up to D3D 10.1, it is not a D3D 11 GPU. Additionally HD 2000 supported anymore, our last driver release was June 2015 and there are no new driver releases that support HD 2000 in the current plan.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;

&lt;P&gt;I think there some misunderstanding. I think you mean D3D10.1 feature level but I mean D3D11 API. D3D11 API supports different feature levels. See&amp;nbsp;D3D11CreateDevice function and&amp;nbsp;D3D_FEATURE_LEVEL enumeration (9.1, 9.2, 9.3, 10.0, 10.1, 11.0, 11.1, 12.0, 12.1). Our application requires at least 10.1 feature level.&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 13.008px; line-height: 19.512px;"&gt;Our application have D3D11 and D3D9 rendering engines and it uses D3D11 mode by default but it switches automatically to D3D9 and it works similar. I will confirm what mode was actually active for user.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;PS You mean "Additionally HD 2000 NOT supported anymore" ? We will also send this information to user. Do you have some article on Intel website?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 17:39:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103414#M87506</guid>
      <dc:creator>Vladimir_H_</dc:creator>
      <dc:date>2016-01-26T17:39:00Z</dc:date>
    </item>
    <item>
      <title>Yes I meant to say the HD</title>
      <link>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103415#M87507</link>
      <description>&lt;P&gt;Yes I meant to say the HD 2000 does not have driver support anymore and no new drivers are planned.&lt;/P&gt;

&lt;P&gt;Looking at the driver download page for version 4229 it states the follow:&lt;/P&gt;

&lt;UL&gt;
	&lt;LI&gt;&lt;STRONG&gt;Microsoft Windows* 8.1**&lt;/STRONG&gt;

		&lt;UL&gt;
			&lt;LI&gt;**This driver will install on Microsoft Windows* 8.1 though is not certified for this version of OS and is provided "as is" and is not supported by Intel Technical Support or any other department at Intel.&lt;/LI&gt;
		&lt;/UL&gt;
	&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;A href="https://downloadcenter.intel.com/download/24970/Intel-HD-Graphics-Driver-for-Windows-7-8-8-1-32bit"&gt;https://downloadcenter.intel.com/download/24970/Intel-HD-Graphics-Driver-for-Windows-7-8-8-1-32bit&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;-Michael&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 21:51:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103415#M87507</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2016-01-26T21:51:59Z</dc:date>
    </item>
    <item>
      <title>Thank you for provided</title>
      <link>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103416#M87508</link>
      <description>&lt;P&gt;Thank you for provided information. But sorry, then I have to ask, will Intel provide support if we can reproduce same bug in Win7 or Win8 ? Can you please also provide some link to official information that Intel has been cancelled support for mentioned cases also?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2016 08:17:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103416#M87508</guid>
      <dc:creator>Vladimir_H_</dc:creator>
      <dc:date>2016-01-27T08:17:33Z</dc:date>
    </item>
    <item>
      <title>Hi Vladimir,</title>
      <link>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103417#M87509</link>
      <description>&lt;P&gt;Hi Vladimir,&lt;/P&gt;

&lt;P&gt;As I said in a prior post no further driver releases for HD 2000 (&amp;amp; HD 3000) are planned. So even if the issue reproduces on Win 7 or 8.0 I afraid no fix will be provided. There is no official press release or article on the Intel site stating this. Generally this information is propagated through the Intel Community forums as the topic comes up.&lt;/P&gt;

&lt;P&gt;Currently supported products:&lt;BR /&gt;
	Intel® HD Graphics 530 for 6th Generation Intel® Core™ Processors&lt;BR /&gt;
	Intel® HD Graphics 510 for Intel® Pentium® Processors&lt;BR /&gt;
	Intel® HD Graphics 515 for 6th Generation Intel® Core™ M Processors&lt;BR /&gt;
	Intel® HD Graphics 520 for 6th Generation Intel® Core™ Processors&lt;BR /&gt;
	Intel® Iris™ Pro Graphics 580 for 6th Generation Intel® Core™ Processors&lt;BR /&gt;
	Intel® Iris™ Graphics 540 for 6th Generation Intel® Core™ Processors&lt;BR /&gt;
	Intel® Iris™ Graphics 550 for 6th Generation Intel® Core™ Processors&lt;BR /&gt;
	5th Generation Intel® Core™ Processors with HD Graphics 5500&lt;BR /&gt;
	5th Generation Intel® Core™ Processors with HD Graphics 5600&lt;BR /&gt;
	5th Generation Intel® Core™ Processors with HD Graphics 6000&lt;BR /&gt;
	5th Generation Intel® Core™ Processors with Iris™ Graphics 6100&lt;BR /&gt;
	5th Generation Intel® Core™ Processors with Iris™ Pro Graphics 6200&lt;BR /&gt;
	Intel® Core™ M with Intel® HD Graphics 5300&lt;BR /&gt;
	4th Generation Intel® Core™ Processors with Intel® Iris™ Pro Graphics 5200&lt;BR /&gt;
	4th Generation Intel® Core™ Processors with Intel® Iris™ Graphics 5100&lt;BR /&gt;
	4th Generation Intel® Core™ Processors with Intel® HD Graphics 5000/4600/4400/4200&lt;BR /&gt;
	Intel® Pentium® Processor 3558U/3560M/3561Y/G3220/G3220T/G3240/G3240T/G3250/G3250T/G3258/G3320TE/G3420/G3420T/G3430/G3440/G3440T/G3450/ G3450T/G3460 with Intel® HD Graphics&lt;BR /&gt;
	Intel® Pentium® Processor 3550M/3556U/3560Y with Intel® HD Graphics&lt;BR /&gt;
	Intel® Celeron® Processor 2957U/2961Y/2970M/2981U/G1820/G1820T/G1820TE/G1830/ G1840/G1840T/G1850 with Intel® HD Graphics&lt;BR /&gt;
	Intel® Celeron® Processor 2000E/2002E/2950M/2955U/2980U with Intel® HD Graphics&lt;/P&gt;

&lt;P&gt;Here is still some support for the 3rd Generation Intel® Core™ Processors graphics but what little support there is will go away soon.&lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;-Michael&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2016 15:21:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Incorrect-shader-calculations-in-Intel-HD-2000/m-p/1103417#M87509</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2016-01-27T15:21:00Z</dc:date>
    </item>
  </channel>
</rss>

