<?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: Shawn Elliot&#8217;s Reviews Symposium &#8211; My Thoughts</title>
	<atom:link href="http://thereticule.com/2009/02/shawn-elliots-reviews-symposium-my-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://thereticule.com/2009/02/shawn-elliots-reviews-symposium-my-thoughts/</link>
	<description>The Reticule a PC gaming website focused on innovative articles and more.</description>
	<lastBuildDate>Sat, 31 Jul 2010 23:23:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Greg Wild</title>
		<link>http://thereticule.com/2009/02/shawn-elliots-reviews-symposium-my-thoughts/comment-page-1/#comment-714</link>
		<dc:creator>Greg Wild</dc:creator>
		<pubDate>Fri, 13 Feb 2009 21:49:12 +0000</pubDate>
		<guid isPermaLink="false">http://thereticule.com/?p=2178#comment-714</guid>
		<description>Very true that, I guess bugs aren&#039;t one that should come into it for the reason they&#039;re relying on an inherently flawed version. As a guy who still has to buy the games he reviews, I&#039;ve not had that dilemma to consider yet actually.
Performance and implementation could well still be covered however I believe - I remember PC Gamer used to do a &quot;performance comparison&quot; for most reviews where they would test how the same game ran on two different systems. I think this is a nice way of doing it - I&#039;m surprised they stopped putting it in, especially because it was a pretty small, but very useful part of any review. I&#039;d do it myself, but the disparity would be huge - my mid-high system versus my 3 year old craptop. In circumstances where more than one of us on the team has a game, I think I&#039;ll be suggesting we do a performance comparison actually. 
Cheers for the input Andrew!</description>
		<content:encoded><![CDATA[<p>Very true that, I guess bugs aren&#8217;t one that should come into it for the reason they&#8217;re relying on an inherently flawed version. As a guy who still has to buy the games he reviews, I&#8217;ve not had that dilemma to consider yet actually.<br />
Performance and implementation could well still be covered however I believe &#8211; I remember PC Gamer used to do a &#8220;performance comparison&#8221; for most reviews where they would test how the same game ran on two different systems. I think this is a nice way of doing it &#8211; I&#8217;m surprised they stopped putting it in, especially because it was a pretty small, but very useful part of any review. I&#8217;d do it myself, but the disparity would be huge &#8211; my mid-high system versus my 3 year old craptop. In circumstances where more than one of us on the team has a game, I think I&#8217;ll be suggesting we do a performance comparison actually.<br />
Cheers for the input Andrew!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Martin</title>
		<link>http://thereticule.com/2009/02/shawn-elliots-reviews-symposium-my-thoughts/comment-page-1/#comment-713</link>
		<dc:creator>Andrew Martin</dc:creator>
		<pubDate>Fri, 13 Feb 2009 21:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://thereticule.com/?p=2178#comment-713</guid>
		<description>I really agree it&#039;s an excellent series of entries although in the first entry about scores it started really going in circles.  

Just a note about the technical aspect.  No matter how diverse a lineup of PCs a reviewer or a gamer has they&#039;re still only going to have like their stuff.  So let&#039;s say being generous PC gamer could test Fallout on 25 different systems in a review period.  

THat&#039;s still just 25 different configurations.  That kind of stuff may only creep up when the game is out in the wild being played on billions of different hardware permutations that exsist.  So no matter what a reviewers rigs are like it&#039;s still entirely conceivable that they could have no problem on however many computers they try it on and it get out in the wild and see bugs bugs bugs.  Or conversely they could have the configuration that&#039;s riddled with bugs and the dells and HPs that exsist could get along fine.  

I think it&#039;s inherent in reviewing PC games on not entirely final code that it&#039;s something of a crapshoot.</description>
		<content:encoded><![CDATA[<p>I really agree it&#8217;s an excellent series of entries although in the first entry about scores it started really going in circles.  </p>
<p>Just a note about the technical aspect.  No matter how diverse a lineup of PCs a reviewer or a gamer has they&#8217;re still only going to have like their stuff.  So let&#8217;s say being generous PC gamer could test Fallout on 25 different systems in a review period.  </p>
<p>THat&#8217;s still just 25 different configurations.  That kind of stuff may only creep up when the game is out in the wild being played on billions of different hardware permutations that exsist.  So no matter what a reviewers rigs are like it&#8217;s still entirely conceivable that they could have no problem on however many computers they try it on and it get out in the wild and see bugs bugs bugs.  Or conversely they could have the configuration that&#8217;s riddled with bugs and the dells and HPs that exsist could get along fine.  </p>
<p>I think it&#8217;s inherent in reviewing PC games on not entirely final code that it&#8217;s something of a crapshoot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
