<?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: Game developers &#8211; submit a SIGGRAPH Talk before February 18!</title>
	<atom:link href="http://www.realtimerendering.com/blog/game-developers-submit-a-siggraph-talk-before-february-18/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.realtimerendering.com/blog/game-developers-submit-a-siggraph-talk-before-february-18/</link>
	<description>Tracking the latest developments in interactive rendering techniques</description>
	<lastBuildDate>Mon, 17 Jun 2013 03:17:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Real-Time Rendering &#183; Three ways to show off your game at SIGGRAPH 2010</title>
		<link>http://www.realtimerendering.com/blog/game-developers-submit-a-siggraph-talk-before-february-18/comment-page-1/#comment-370</link>
		<dc:creator>Real-Time Rendering &#183; Three ways to show off your game at SIGGRAPH 2010</dc:creator>
		<pubDate>Tue, 20 Apr 2010 01:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.realtimerendering.com/blog/?p=979#comment-370</guid>
		<description>[...] we need your participation to help make this the biggest game SIGGRAPH ever! A few months ago I posted about the February 18th deadline. That deadline is long gone, but several venues are still open. This is your chance to show off not [...]</description>
		<content:encoded><![CDATA[<p>[...] we need your participation to help make this the biggest game SIGGRAPH ever! A few months ago I posted about the February 18th deadline. That deadline is long gone, but several venues are still open. This is your chance to show off not [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Naty</title>
		<link>http://www.realtimerendering.com/blog/game-developers-submit-a-siggraph-talk-before-february-18/comment-page-1/#comment-289</link>
		<dc:creator>Naty</dc:creator>
		<pubDate>Mon, 08 Feb 2010 21:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.realtimerendering.com/blog/?p=979#comment-289</guid>
		<description>Mauricio,

That&#039;s a great question. Companies differ in their approaches to this. Some (like Crytek and Bungie) happily divulge detailed technical information even before the games using the techniques have shipped. Others have a policy against ever disclosing anything; most are somewhere in the middle.  If your company is more on the secretive side, there are several responses. One is that the companies with the most open policies are often the most successful, so this openness doesn&#039;t seem to be hurting them.  A good compromise is to wait until the game has shipped before disclosure; then any competitors who copy the technique will be chasing your tail as you evolve improved techniques for the next game. Some companies make sure to submit patent applications before publication. I&#039;m personally against software patents, but this does give one possible answer to the lawyers, and if you were going to patent it anyway you might was well publish it afterwards (NOTE: I&#039;m not a lawyer and none of this is to be construed as legal advice of any kind).

Game development isn&#039;t zero-sum; all developers make heavy use of techniques invented by others, from the most basic (shadow mapping) to the more arcane (SSAO). Publishing advanced algorithms is positive PR for the company, and helps recruit good people (smart people will want to work where other smart people are, and publication is a good way to show this).

Finally, by publishing your technique, you will get many eyes looking at it, and quite likely some of them will find flaws that you didn&#039;t see, or think of extensions and improvements. Although nothing forces these people to inform you of these improvements, in practice after you publish most people will, often in excited conversations just after the presentation. This is another direct benefit; you can think of it as encouraging development in a direction which your company has already found useful, to your future benefit.</description>
		<content:encoded><![CDATA[<p>Mauricio,</p>
<p>That&#8217;s a great question. Companies differ in their approaches to this. Some (like Crytek and Bungie) happily divulge detailed technical information even before the games using the techniques have shipped. Others have a policy against ever disclosing anything; most are somewhere in the middle.  If your company is more on the secretive side, there are several responses. One is that the companies with the most open policies are often the most successful, so this openness doesn&#8217;t seem to be hurting them.  A good compromise is to wait until the game has shipped before disclosure; then any competitors who copy the technique will be chasing your tail as you evolve improved techniques for the next game. Some companies make sure to submit patent applications before publication. I&#8217;m personally against software patents, but this does give one possible answer to the lawyers, and if you were going to patent it anyway you might was well publish it afterwards (NOTE: I&#8217;m not a lawyer and none of this is to be construed as legal advice of any kind).</p>
<p>Game development isn&#8217;t zero-sum; all developers make heavy use of techniques invented by others, from the most basic (shadow mapping) to the more arcane (SSAO). Publishing advanced algorithms is positive PR for the company, and helps recruit good people (smart people will want to work where other smart people are, and publication is a good way to show this).</p>
<p>Finally, by publishing your technique, you will get many eyes looking at it, and quite likely some of them will find flaws that you didn&#8217;t see, or think of extensions and improvements. Although nothing forces these people to inform you of these improvements, in practice after you publish most people will, often in excited conversations just after the presentation. This is another direct benefit; you can think of it as encouraging development in a direction which your company has already found useful, to your future benefit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mauricio</title>
		<link>http://www.realtimerendering.com/blog/game-developers-submit-a-siggraph-talk-before-february-18/comment-page-1/#comment-288</link>
		<dc:creator>Mauricio</dc:creator>
		<pubDate>Mon, 08 Feb 2010 21:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.realtimerendering.com/blog/?p=979#comment-288</guid>
		<description>Some companies are squeamish about releasing information that they consider &quot;trade secrets,&quot; whether or not they are really secret.  How do you convince your employer that it is in the best interest of the company (not just yourself) to give a talk like this?</description>
		<content:encoded><![CDATA[<p>Some companies are squeamish about releasing information that they consider &#8220;trade secrets,&#8221; whether or not they are really secret.  How do you convince your employer that it is in the best interest of the company (not just yourself) to give a talk like this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>