<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for TurboSquid Blog</title>
	<atom:link href="http://blog.turbosquid.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.turbosquid.com</link>
	<description>The world’s leading source for quality 3D models.</description>
	<lastBuildDate>Tue, 18 Jun 2013 17:44:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5</generator>
	<item>
		<title>Comment on CheckMate Pro v2: Submissions and Topology Requirements by Michele Bousquet</title>
		<link>http://blog.turbosquid.com/2013/06/13/checkmate-pro-v2-submissions-and-topology-requirements/comment-page-1/#comment-38964</link>
		<dc:creator>Michele Bousquet</dc:creator>
		<pubDate>Tue, 18 Jun 2013 17:44:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.turbosquid.com/?p=5284#comment-38964</guid>
		<description><![CDATA[Having said all that, we are open to suggestions on how to improve the specification. We know there will be exceptions, but we&#039;re not sure what they are yet; as you bring up your concerns (as with the question about architecture models) we will look at them and respond, either with specification changes, or information on why a spec change is not necessary.

The Lightwave question is a great example of this also. We don&#039;t have a lot of native Lightwave files in CheckMate and the specification change seemed to work with those, but if you have an idea on how to make it better, please let us know.]]></description>
		<content:encoded><![CDATA[<p>Having said all that, we are open to suggestions on how to improve the specification. We know there will be exceptions, but we&#8217;re not sure what they are yet; as you bring up your concerns (as with the question about architecture models) we will look at them and respond, either with specification changes, or information on why a spec change is not necessary.</p>
<p>The Lightwave question is a great example of this also. We don&#8217;t have a lot of native Lightwave files in CheckMate and the specification change seemed to work with those, but if you have an idea on how to make it better, please let us know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CheckMate Pro v2: Submissions and Topology Requirements by Michele Bousquet</title>
		<link>http://blog.turbosquid.com/2013/06/13/checkmate-pro-v2-submissions-and-topology-requirements/comment-page-1/#comment-38963</link>
		<dc:creator>Michele Bousquet</dc:creator>
		<pubDate>Tue, 18 Jun 2013 17:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.turbosquid.com/?p=5284#comment-38963</guid>
		<description><![CDATA[I will try to clarify a few points here.

Our CheckMate Advisory Board, and our customers, want models that are made in one of two ways: 
- Group 1: Perfect edge flow, suitable for most customer needs such as editing, re-texturing, rigging, subdivision. OR
- Group 2: Minimal polygons, to be used for background, realtime, or game uses.

All CheckMate Pro models must now be made to fit into one of these groups. Most of the models currently in CheckMate Pro fit in Group 1, or could fit in this group with some work. In reviewing the architecture models on TurboSquid, I found that most fit in Group 2, which is fine for CheckMate Pro.

In any case, customers expect that a model with perfect edge flow will have more polygons than a realtime model or a model with a lot of odd triangles. As processors get faster and computers have more memory than ever before, polygon count is much less of an issue than it has been in the past. Customers are much more interested in saving their own time, ie. being able to edit or re-texture a model quickly. Clean edge flow makes this possible.]]></description>
		<content:encoded><![CDATA[<p>I will try to clarify a few points here.</p>
<p>Our CheckMate Advisory Board, and our customers, want models that are made in one of two ways:<br />
- Group 1: Perfect edge flow, suitable for most customer needs such as editing, re-texturing, rigging, subdivision. OR<br />
- Group 2: Minimal polygons, to be used for background, realtime, or game uses.</p>
<p>All CheckMate Pro models must now be made to fit into one of these groups. Most of the models currently in CheckMate Pro fit in Group 1, or could fit in this group with some work. In reviewing the architecture models on TurboSquid, I found that most fit in Group 2, which is fine for CheckMate Pro.</p>
<p>In any case, customers expect that a model with perfect edge flow will have more polygons than a realtime model or a model with a lot of odd triangles. As processors get faster and computers have more memory than ever before, polygon count is much less of an issue than it has been in the past. Customers are much more interested in saving their own time, ie. being able to edit or re-texture a model quickly. Clean edge flow makes this possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CheckMate Pro v2 Coming Soon by POPA_3D</title>
		<link>http://blog.turbosquid.com/2013/05/31/checkmate-pro-v2-coming-soon/comment-page-1/#comment-38944</link>
		<dc:creator>POPA_3D</dc:creator>
		<pubDate>Tue, 18 Jun 2013 12:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.turbosquid.com/?p=5257#comment-38944</guid>
		<description><![CDATA[@stefan
CM Tools v2.0 is not compatible with 3ds Max Design only 3ds Max standard is supported there are some errors that occur in design version I havn&#039;t find time to make it compatible with this version maybe in the futur.this is why it is not included in the installer.
but just so you know this hasn&#039;t any relatiion with CM v 2.0 the tool is designed  for CM V1.]]></description>
		<content:encoded><![CDATA[<p>@stefan<br />
CM Tools v2.0 is not compatible with 3ds Max Design only 3ds Max standard is supported there are some errors that occur in design version I havn&#8217;t find time to make it compatible with this version maybe in the futur.this is why it is not included in the installer.<br />
but just so you know this hasn&#8217;t any relatiion with CM v 2.0 the tool is designed  for CM V1.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CheckMate Pro v2 Coming Soon by stefan</title>
		<link>http://blog.turbosquid.com/2013/05/31/checkmate-pro-v2-coming-soon/comment-page-1/#comment-38924</link>
		<dc:creator>stefan</dc:creator>
		<pubDate>Mon, 17 Jun 2013 18:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.turbosquid.com/?p=5257#comment-38924</guid>
		<description><![CDATA[i get an error message when trying to install checkmate pro v2
&quot;cannot find a compatible version of 3dsmax installed on this machine&quot;
i have both 3ds max design 2013 and 3ds max design 2014 installed.]]></description>
		<content:encoded><![CDATA[<p>i get an error message when trying to install checkmate pro v2<br />
&#8220;cannot find a compatible version of 3dsmax installed on this machine&#8221;<br />
i have both 3ds max design 2013 and 3ds max design 2014 installed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CheckMate Pro v2: Submissions and Topology Requirements by digitaldoc3d</title>
		<link>http://blog.turbosquid.com/2013/06/13/checkmate-pro-v2-submissions-and-topology-requirements/comment-page-1/#comment-38917</link>
		<dc:creator>digitaldoc3d</dc:creator>
		<pubDate>Mon, 17 Jun 2013 16:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.turbosquid.com/?p=5284#comment-38917</guid>
		<description><![CDATA[Why would you want to subdivide a hard surfaced model that is optimized for render?  It creates exponentially more polys to render.

Lightwave doesn&#039;t use the &quot;levels of subdivision&quot; in models that you are referencing.  That occurs in Layout when the model is rendered.

Shouldn&#039;t the version 2 specs be available in the Checkmate Pro and Lite specs on the front page of the website?]]></description>
		<content:encoded><![CDATA[<p>Why would you want to subdivide a hard surfaced model that is optimized for render?  It creates exponentially more polys to render.</p>
<p>Lightwave doesn&#8217;t use the &#8220;levels of subdivision&#8221; in models that you are referencing.  That occurs in Layout when the model is rendered.</p>
<p>Shouldn&#8217;t the version 2 specs be available in the Checkmate Pro and Lite specs on the front page of the website?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CheckMate Pro v2: Submissions and Topology Requirements by mostlysquare</title>
		<link>http://blog.turbosquid.com/2013/06/13/checkmate-pro-v2-submissions-and-topology-requirements/comment-page-1/#comment-38759</link>
		<dc:creator>mostlysquare</dc:creator>
		<pubDate>Fri, 14 Jun 2013 20:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.turbosquid.com/?p=5284#comment-38759</guid>
		<description><![CDATA[I am all for good topology. But, &quot;thumbnails showing the model at subdivision level 0, and one level higher&quot; was clearly written with 3ds Max users in mind.  

In lightwave smoothing is handled on a surface by surface basis and does not deforms geometry. Subdividing oval or cylindrical mesh will ruin smoothing.]]></description>
		<content:encoded><![CDATA[<p>I am all for good topology. But, &#8220;thumbnails showing the model at subdivision level 0, and one level higher&#8221; was clearly written with 3ds Max users in mind.  </p>
<p>In lightwave smoothing is handled on a surface by surface basis and does not deforms geometry. Subdividing oval or cylindrical mesh will ruin smoothing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->