<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Forum - Feedback - Stripping - Messages</title>
<link>http://www.muvizu.com/Forum/topic1173-stripping.aspx</link>
<description>Forum - Feedback - Stripping - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<generator>Jitbit AspNetForum</generator>
<pubDate>Fri, 22 Jul 2011 20:43:17 GMT</pubDate>
<lastBuildDate>Fri, 22 Jul 2011 20:43:17 GMT</lastBuildDate>
<item>
<link>http://www.muvizu.com/Forum/topic1173-stripping.aspx</link>
<title>Message from ziggy72</title>
<description><![CDATA[Good idea.  That damn set takes sooooo long to load because of all the wine glasses and bottles I had to import.  Being able to pare it down to just one camera angle would be a handy feature.]]></description>
<pubDate>Fri, 22 Jul 2011 20:43:17 GMT</pubDate>
</item>
<item>
<link>http://www.muvizu.com/Forum/topic1173-stripping.aspx</link>
<title>Message from simonheffer</title>
<description><![CDATA[Steady on! <br/>  <br/> I was musing about how long ziggy's cheers set took to load and how I have to save the whole set for every scene and wondered if there was any mileage in a 'strip' function? This would imagine a cone(well I guess, a pyramid) shone out from each camera to select the objects needed for the scene and then delete everything not selected to give a minimal set of objects needed for that scene. Probably need to keep things like lights, effects etc that project into the cone(pyramid) but I somehow imagine we'll just keep them all anyway as their overhead is not too much. <br/>  <br/> Obviously this would work better the sooner you sort your camera angles out. <br/>  <br/> Just some musings as I get ready for my hols. <br/>  <br/> Si]]></description>
<pubDate>Fri, 22 Jul 2011 14:34:42 GMT</pubDate>
</item>
</channel>
</rss>
