<?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 on: Normalized Device Coordinates</title>
	<atom:link href="http://www.gamerendering.com/2008/10/05/normalized-device-coordinates/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gamerendering.com/2008/10/05/normalized-device-coordinates/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 13:10:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Molehill3D &#187; Blog Archive &#187; Clip Space</title>
		<link>http://www.gamerendering.com/2008/10/05/normalized-device-coordinates/comment-page-1/#comment-6238</link>
		<dc:creator>Molehill3D &#187; Blog Archive &#187; Clip Space</dc:creator>
		<pubDate>Fri, 04 Mar 2011 10:53:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.gamerendering.com/?p=192#comment-6238</guid>
		<description>[...] probably not zero or one. This means you need to divide all components by this value to obtain normalized device coordinates. This will happen automatically between the vertex shader and fragment shader. Clipping will [...]</description>
		<content:encoded><![CDATA[<p>[...] probably not zero or one. This means you need to divide all components by this value to obtain normalized device coordinates. This will happen automatically between the vertex shader and fragment shader. Clipping will [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

