<?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 Lightworks Bump Mapping with &amp;quot;Match with Internal Engin in Visualization</title>
    <link>https://community.graphisoft.com/t5/Visualization/Lightworks-Bump-Mapping-with-quot-Match-with-Internal-Engin/m-p/53230#M22719</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Thought I'd share a small discovery.&lt;BR /&gt;
&lt;BR /&gt;
The standard "Brick-Alpha" material has an alpha channel for bump mapping the morter.&lt;BR /&gt;
&lt;BR /&gt;
The default settings (or if you manually click on  the "Match with Internal Engine" button in the LW materials settings - see attached screenshot), seen by unchecking "Show Essential Only", show that an amplitude for the bump is 0.10 (positive 0.10).  If you render, you'll find that this is the opposite bump: the bricks go into the wall, and the mortar comes out.  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_rolleyes.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
Changing the value of Amplitude to -0.03 (negative 0.03) gives a result as shown in the image.&lt;BR /&gt;
&lt;BR /&gt;
An equivalent rendering with the internal engine is shown at the bottom.  Note that even for this low-grade texture, the LW engine provides vastly superior results.  Not really sure what is going on with the internal antialiasing.&lt;BR /&gt;
&lt;BR /&gt;
Karl&lt;/R&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;IMG src="http://community.graphisoft.com/t5/image/serverpage/image-id/71736i6E11FC1C68D68AA1/image-size/large?v=v2&amp;amp;px=999" border="0" alt="brick-alpha.png" title="brick-alpha.png" /&gt;</description>
    <pubDate>Thu, 11 May 2023 10:40:41 GMT</pubDate>
    <dc:creator>Karl Ottenstein</dc:creator>
    <dc:date>2023-05-11T10:40:41Z</dc:date>
    <item>
      <title>Lightworks Bump Mapping with "Match with Internal Engin</title>
      <link>https://community.graphisoft.com/t5/Visualization/Lightworks-Bump-Mapping-with-quot-Match-with-Internal-Engin/m-p/53230#M22719</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Thought I'd share a small discovery.&lt;BR /&gt;
&lt;BR /&gt;
The standard "Brick-Alpha" material has an alpha channel for bump mapping the morter.&lt;BR /&gt;
&lt;BR /&gt;
The default settings (or if you manually click on  the "Match with Internal Engine" button in the LW materials settings - see attached screenshot), seen by unchecking "Show Essential Only", show that an amplitude for the bump is 0.10 (positive 0.10).  If you render, you'll find that this is the opposite bump: the bricks go into the wall, and the mortar comes out.  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_rolleyes.gif" style="display : inline;" /&gt; &lt;BR /&gt;
&lt;BR /&gt;
Changing the value of Amplitude to -0.03 (negative 0.03) gives a result as shown in the image.&lt;BR /&gt;
&lt;BR /&gt;
An equivalent rendering with the internal engine is shown at the bottom.  Note that even for this low-grade texture, the LW engine provides vastly superior results.  Not really sure what is going on with the internal antialiasing.&lt;BR /&gt;
&lt;BR /&gt;
Karl&lt;/R&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;IMG src="http://community.graphisoft.com/t5/image/serverpage/image-id/71736i6E11FC1C68D68AA1/image-size/large?v=v2&amp;amp;px=999" border="0" alt="brick-alpha.png" title="brick-alpha.png" /&gt;</description>
      <pubDate>Thu, 11 May 2023 10:40:41 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Lightworks-Bump-Mapping-with-quot-Match-with-Internal-Engin/m-p/53230#M22719</guid>
      <dc:creator>Karl Ottenstein</dc:creator>
      <dc:date>2023-05-11T10:40:41Z</dc:date>
    </item>
  </channel>
</rss>

