<?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 Hi Alastair, in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/Adding-zero-vector-causes-major-change-to-image/m-p/1107749#M87552</link>
    <description>&lt;P&gt;Hi Alastair,&lt;/P&gt;

&lt;P&gt;Thanks, I reported the issue and and will see what the driver team finds.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;-Michael&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Dec 2016 18:37:36 GMT</pubDate>
    <dc:creator>Michael_C_Intel2</dc:creator>
    <dc:date>2016-12-09T18:37:36Z</dc:date>
    <item>
      <title>Adding zero vector causes major change to image</title>
      <link>https://community.intel.com/t5/Graphics/Adding-zero-vector-causes-major-change-to-image/m-p/1107748#M87551</link>
      <description>&lt;P&gt;We think we've found a GLSL shader compiler bug.&lt;/P&gt;

&lt;P&gt;This issue describes the problem in full and links to the relevant files:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://github.com/mc-imperial/shader-compiler-bugs/issues/41" target="_blank"&gt;https://github.com/mc-imperial/shader-compiler-bugs/issues/41&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;System Setup Information:&lt;BR /&gt;
	-----------------------------------------&lt;/P&gt;

&lt;P&gt;System Used: Dell XPS&lt;BR /&gt;
	CPU SKU: i7&lt;BR /&gt;
	GPU SKU: HD 520&lt;BR /&gt;
	Processor Line: U-Series&lt;BR /&gt;
	System BIOS Version: Dell Inc. 1.0.0, 10/09/2015&lt;BR /&gt;
	CMOS settings: I can check on request&lt;BR /&gt;
	Graphics Driver Version: 21.20.16.4542&lt;BR /&gt;
	GOP/VBIOS Version: Intel Video BIOS&lt;BR /&gt;
	Operating System: Windows 10&lt;BR /&gt;
	OS Version: Pro&lt;BR /&gt;
	API: OpenGL&lt;BR /&gt;
	Occurs on non-Intel GPUs?: Haven't tried&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Steps to Reproduce:&lt;BR /&gt;
	-------------------------------&lt;/P&gt;

&lt;P&gt;1. Obtain the latest release of get-image, a simple tool that creates&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; a .png image from a fragment shader (alternatively, use some other&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; method observing the effect of a fragment shader)&lt;/P&gt;

&lt;P&gt;2. From a command prompt, execute:&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp; C:\path\to\get_image\bin\Windows\get_image.exe recipient_reduced_final.frag&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp; This will create output.png, which should look like expected.png&lt;/P&gt;

&lt;P&gt;3. From a command prompt, execute:&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp; C:\path\to\get_image\bin\Windows\get_image.exe variant_52_reduced_29_simplified.frag&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp; This will create output.png, which should look like actual.png&lt;/P&gt;

&lt;P&gt;Expected Results:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	Both shaders should render an image that looks like expected.png.&amp;nbsp; This is because the only difference between the .frag files is:&lt;/P&gt;

&lt;P&gt;- Statement&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; return ObjUnion(obj0(p), obj1(p));&lt;/P&gt;

&lt;P&gt;&amp;nbsp; has been replaced with&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; return ObjUnion(obj0(p + vec3(0.0, injectionSwitch.x, 0.0)), obj1(p));&lt;/P&gt;

&lt;P&gt;&amp;nbsp; in variant_52_reduced_29_simplified.frag&lt;/P&gt;

&lt;P&gt;&amp;nbsp; Because injectionSwitch.x is set to 0.0, this should not have an effect.&lt;/P&gt;

&lt;P&gt;&lt;BR /&gt;
	Actual Results:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	The shaders render completely different images, which they should not.&lt;/P&gt;

&lt;P&gt;Additional Information:&lt;BR /&gt;
	-------------------------------&lt;BR /&gt;
	N/A&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2016 15:52:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Adding-zero-vector-causes-major-change-to-image/m-p/1107748#M87551</guid>
      <dc:creator>Alastair_D_1</dc:creator>
      <dc:date>2016-12-07T15:52:26Z</dc:date>
    </item>
    <item>
      <title>Hi Alastair,</title>
      <link>https://community.intel.com/t5/Graphics/Adding-zero-vector-causes-major-change-to-image/m-p/1107749#M87552</link>
      <description>&lt;P&gt;Hi Alastair,&lt;/P&gt;

&lt;P&gt;Thanks, I reported the issue and and will see what the driver team finds.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;-Michael&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Dec 2016 18:37:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Adding-zero-vector-causes-major-change-to-image/m-p/1107749#M87552</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2016-12-09T18:37:36Z</dc:date>
    </item>
  </channel>
</rss>

