<?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: '_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in xxx.obj in FBX Forum</title>
    <link>https://forums.autodesk.com/t5/fbx-forum/iterator-debug-level-value-2-doesn-t-match-value-0-in-xxx-obj/m-p/5787482#M2390</link>
    <description>&lt;P&gt;I found the answer myself. &amp;nbsp;The default value of&amp;nbsp;_ITERATOR_DEBUG_LEVEL in Visual Studio 2013 is indeed differnet, depending on configuration. &amp;nbsp;In release&amp;nbsp;_ITERATOR_DEBUG_LEVEL=0 and in release&amp;nbsp;_ITERATOR_DEBUG_LEVEL=2. From MSDN:&lt;/P&gt;&lt;P&gt;&lt;A href="https://msdn.microsoft.com/en-us/library/hh697468(v=vs.120).aspx" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/hh697468(v=vs.120).aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it was a problem on my side that&amp;nbsp;&lt;SPAN&gt;_ITERATOR_DEBUG_LEVEL=0. &amp;nbsp;I found that this was being explictly set in one of my many .props files and I removed that line. &amp;nbsp;Now it defaults to 2 and everyone is happy.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Aug 2015 19:18:40 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-08-25T19:18:40Z</dc:date>
    <item>
      <title>'_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in xxx.obj</title>
      <link>https://forums.autodesk.com/t5/fbx-forum/iterator-debug-level-value-2-doesn-t-match-value-0-in-xxx-obj/m-p/5785887#M2389</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm setting up my project to use FBX libraries. &amp;nbsp; &amp;nbsp;Everything links wonderfully for my Release configuration (/MD Multi-threaded DLL) but I get several hundred of these errors in my Debug configuration (/MDd Multi-threaded Debug DLL):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in xxx.obj&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;xxx.obj is an object file from my project, not the FBX SDK. &amp;nbsp;The error does make sense as I can see&amp;nbsp;&lt;SPAN&gt;_ITERATOR_DEBUG_LEVEL explictly set to 0 in Preprocessor Definitions:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;_DEBUG&lt;BR /&gt;ASSERTIONS_ENABLED&lt;BR /&gt;WIN32&lt;BR /&gt;_CRT_SECURE_NO_DEPRECATE&lt;BR /&gt;_CRT_NONSTDC_NO_WARNINGS&lt;BR /&gt;_CRT_SECURE_NO_WARNINGS&lt;BR /&gt;_ITERATOR_DEBUG_LEVEL=0&lt;BR /&gt;VALIDATE_IS_ASSERT&lt;BR /&gt;_WINSOCK_DEPRECATED_NO_WARNINGS&lt;BR /&gt;NO_WARN_MBCS_MFC_DEPRECATION&lt;BR /&gt;_MBCS&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So it seems as if&amp;nbsp;_ITERATOR_DEBUG_LEVEL is being explicitly set to 2 in the version of the .lib I am linking against,&amp;nbsp;2016.1\lib\vs2013\x64\debug\libfbxsdk-md.lib. &amp;nbsp;Is this expected? Is it possible that the .lib was incorrectly compiled? &amp;nbsp;_ITERATOR_DEBUG_LEVEL is set to 0 in my project in Release and that links, so that would imply that it is set to different values across&amp;nbsp;the FBX SDK debug/release libs. &amp;nbsp;I'm not sure if that is correct or not.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For further clarification of my project setup, I'm on Win7 using VS2013 and x64 configuration for the project.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Aug 2015 23:24:30 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fbx-forum/iterator-debug-level-value-2-doesn-t-match-value-0-in-xxx-obj/m-p/5785887#M2389</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-08-24T23:24:30Z</dc:date>
    </item>
    <item>
      <title>Re: '_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in xxx.obj</title>
      <link>https://forums.autodesk.com/t5/fbx-forum/iterator-debug-level-value-2-doesn-t-match-value-0-in-xxx-obj/m-p/5787482#M2390</link>
      <description>&lt;P&gt;I found the answer myself. &amp;nbsp;The default value of&amp;nbsp;_ITERATOR_DEBUG_LEVEL in Visual Studio 2013 is indeed differnet, depending on configuration. &amp;nbsp;In release&amp;nbsp;_ITERATOR_DEBUG_LEVEL=0 and in release&amp;nbsp;_ITERATOR_DEBUG_LEVEL=2. From MSDN:&lt;/P&gt;&lt;P&gt;&lt;A href="https://msdn.microsoft.com/en-us/library/hh697468(v=vs.120).aspx" target="_blank"&gt;https://msdn.microsoft.com/en-us/library/hh697468(v=vs.120).aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it was a problem on my side that&amp;nbsp;&lt;SPAN&gt;_ITERATOR_DEBUG_LEVEL=0. &amp;nbsp;I found that this was being explictly set in one of my many .props files and I removed that line. &amp;nbsp;Now it defaults to 2 and everyone is happy.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2015 19:18:40 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fbx-forum/iterator-debug-level-value-2-doesn-t-match-value-0-in-xxx-obj/m-p/5787482#M2390</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-08-25T19:18:40Z</dc:date>
    </item>
  </channel>
</rss>

