<?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 Re: Wrong interpretation of antialiasing options? in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/wrong-interpretation-of-antialiasing-options/m-p/283785#M12304</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume that this is the &lt;A href="https://pro.arcgis.com/en/pro-app/help/mapping/map-authoring/display-options.htm"&gt;antialiasing options&lt;/A&gt; that you are referring to.&lt;/P&gt;&lt;P&gt;The descriptions are there. But you don't need to worry about hardware options if you don't have a high-end graphics card.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Hardware antialiasing enables filtering directly on the graphics card hardware, rather than software-based filtering. Hardware antialiasing can greatly improve the rendering quality of 2D and 3D content, but this option is only supported in hardware on high-end graphics cards. Enabling hardware antialiasing provides higher-quality rendering but may lower performance.&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Oct 2016 09:31:01 GMT</pubDate>
    <dc:creator>DanPatterson_Retired</dc:creator>
    <dc:date>2016-10-03T09:31:01Z</dc:date>
    <item>
      <title>Wrong interpretation of antialiasing options?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/wrong-interpretation-of-antialiasing-options/m-p/283784#M12303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a “Display” tab on the general “Options” window of ArcGIS Pro 1.3.1. and there are three antialiasing related setting: “Antialiasing mode”; “Text antialiasing mode” and “Enable hardware antialiasing”. The first two can be {None | Normal | Fast | Best}. If I change the first two to “None” (there is no antialiasing), then the third option “Enable hardware antialiasing shouldn’t have effect. But it has, especially on thin lines (typical antialiasing), at least in local scenes. I think I misunderstood something. These option are working separately and the first two is only for software antialiasing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Oct 2016 08:33:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/wrong-interpretation-of-antialiasing-options/m-p/283784#M12303</guid>
      <dc:creator>ÁkosHalmai</dc:creator>
      <dc:date>2016-10-03T08:33:25Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong interpretation of antialiasing options?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/wrong-interpretation-of-antialiasing-options/m-p/283785#M12304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume that this is the &lt;A href="https://pro.arcgis.com/en/pro-app/help/mapping/map-authoring/display-options.htm"&gt;antialiasing options&lt;/A&gt; that you are referring to.&lt;/P&gt;&lt;P&gt;The descriptions are there. But you don't need to worry about hardware options if you don't have a high-end graphics card.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Hardware antialiasing enables filtering directly on the graphics card hardware, rather than software-based filtering. Hardware antialiasing can greatly improve the rendering quality of 2D and 3D content, but this option is only supported in hardware on high-end graphics cards. Enabling hardware antialiasing provides higher-quality rendering but may lower performance.&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Oct 2016 09:31:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/wrong-interpretation-of-antialiasing-options/m-p/283785#M12304</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2016-10-03T09:31:01Z</dc:date>
    </item>
  </channel>
</rss>

