<?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: Test if a plane is within the view of the camera (aka testing if culled)</title>
	<atom:link href="http://pv3d.org/2009/07/01/test-if-a-plane-is-within-the-view-of-the-camera-aka-testing-if-culled/feed/" rel="self" type="application/rss+xml" />
	<link>http://pv3d.org/2009/07/01/test-if-a-plane-is-within-the-view-of-the-camera-aka-testing-if-culled/</link>
	<description>Papervision3D, ActionScript, and Flex examples and tutorials by John Lindquist</description>
	<lastBuildDate>Sat, 13 Mar 2010 10:45:00 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jesse Freeman</title>
		<link>http://pv3d.org/2009/07/01/test-if-a-plane-is-within-the-view-of-the-camera-aka-testing-if-culled/comment-page-1/#comment-2635</link>
		<dc:creator>Jesse Freeman</dc:creator>
		<pubDate>Sat, 18 Jul 2009 04:35:56 +0000</pubDate>
		<guid isPermaLink="false">http://pv3d.org/?p=641#comment-2635</guid>
		<description>This is great, I was actually doing this by hand by calculating the distance between objects and the camera then removing the objects out of view. Checking for the culled value is going to be much faster. 

One question though, do you think testing every DisplayObject3D on the render tick is intensive? Wondering how to better optimize something like this. Does PV3D take advantage of stage invalidation? It would be nice to do all of this before the screen is rendered so you make sure you are only rendering exactly what you need. Going to play around with it right now.

I would love to see more posts about high level optimization for papervision sites.</description>
		<content:encoded><![CDATA[<p>This is great, I was actually doing this by hand by calculating the distance between objects and the camera then removing the objects out of view. Checking for the culled value is going to be much faster. </p>
<p>One question though, do you think testing every DisplayObject3D on the render tick is intensive? Wondering how to better optimize something like this. Does PV3D take advantage of stage invalidation? It would be nice to do all of this before the screen is rendered so you make sure you are only rendering exactly what you need. Going to play around with it right now.</p>
<p>I would love to see more posts about high level optimization for papervision sites.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
