<?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: 12 Reasons to refuse to Render!</title>
	<atom:link href="http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/</link>
	<description>Architecture News: The latest buildings, projects and competitions every day.</description>
	<lastBuildDate>Mon, 23 Nov 2009 22:10:15 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Markus</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-77544</link>
		<dc:creator>Markus</dc:creator>
		<pubDate>Thu, 19 Nov 2009 23:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-77544</guid>
		<description>This isn&#039;t good or bad. It&#039;s just the way of things. Nothing stays the same.</description>
		<content:encoded><![CDATA[<p>This isn&#8217;t good or bad. It&#8217;s just the way of things. Nothing stays the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shaderkul</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-31160</link>
		<dc:creator>Shaderkul</dc:creator>
		<pubDate>Fri, 15 May 2009 08:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-31160</guid>
		<description>Originally Posted by AJLynn @ CGArchitect.com
&quot;You&#039;re all missing the point. This article isn&#039;t for aspiring 3D guys, it&#039;s for junior architects (the most underappreciated form of life). Junior architects don&#039;t want to get better at rendering. They want to become senior architects.

The way to do this is for them to practice working on architecture, but senior architects keep giving the junior architects rendering work (which is not architecture work) to do. The better the junior architect gets at rendering, the more rendering work is assigned, until it becomes almost impossible for the junior architect to do real work. The rendering work is unappreciated because the senior architects don&#039;t consider it real work, thinking it&#039;s something a computer does and not something a skilled junior architect does.

The best approach for the junior architect is to pretend not to know how to render.&quot;

Just wanted to share this post so you all can understand the point of this article</description>
		<content:encoded><![CDATA[<p>Originally Posted by AJLynn @ CGArchitect.com<br />
&#8220;You&#8217;re all missing the point. This article isn&#8217;t for aspiring 3D guys, it&#8217;s for junior architects (the most underappreciated form of life). Junior architects don&#8217;t want to get better at rendering. They want to become senior architects.</p>
<p>The way to do this is for them to practice working on architecture, but senior architects keep giving the junior architects rendering work (which is not architecture work) to do. The better the junior architect gets at rendering, the more rendering work is assigned, until it becomes almost impossible for the junior architect to do real work. The rendering work is unappreciated because the senior architects don&#8217;t consider it real work, thinking it&#8217;s something a computer does and not something a skilled junior architect does.</p>
<p>The best approach for the junior architect is to pretend not to know how to render.&#8221;</p>
<p>Just wanted to share this post so you all can understand the point of this article</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-26116</link>
		<dc:creator>George</dc:creator>
		<pubDate>Wed, 22 Apr 2009 06:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-26116</guid>
		<description>I&#039;m a professional 3D/visualisation guy at an architectural practise. It is absolutely the best setup to have. This article is somewhat ludicrous. We have the technology to see the building before it is built, like we had pencil sketches before then, and the reason this guy presents for not doing them? - they take too long! This is, like all newly introduced technology, something for the new architect to learn, not to reject.

Having said that, it is better to have someone dedicated to the task, because as you point out, it&#039;s time consuming. As for the Dubai thing - that&#039;s on account of them having warehouses full of people paid $1 a day.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a professional 3D/visualisation guy at an architectural practise. It is absolutely the best setup to have. This article is somewhat ludicrous. We have the technology to see the building before it is built, like we had pencil sketches before then, and the reason this guy presents for not doing them? &#8211; they take too long! This is, like all newly introduced technology, something for the new architect to learn, not to reject.</p>
<p>Having said that, it is better to have someone dedicated to the task, because as you point out, it&#8217;s time consuming. As for the Dubai thing &#8211; that&#8217;s on account of them having warehouses full of people paid $1 a day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aufi</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-25965</link>
		<dc:creator>aufi</dc:creator>
		<pubDate>Tue, 21 Apr 2009 10:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-25965</guid>
		<description>its not a crime to enhance the quality of ur works..</description>
		<content:encoded><![CDATA[<p>its not a crime to enhance the quality of ur works..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ralf</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-25452</link>
		<dc:creator>Ralf</dc:creator>
		<pubDate>Fri, 17 Apr 2009 00:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-25452</guid>
		<description>A perfect render can impress to a client but can not convince them.</description>
		<content:encoded><![CDATA[<p>A perfect render can impress to a client but can not convince them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kc</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-25409</link>
		<dc:creator>kc</dc:creator>
		<pubDate>Thu, 16 Apr 2009 16:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-25409</guid>
		<description>Rendering 3d shouldn&#039;t be the final say (too bad it is) and is not worth THAT much stress and time. In 20 years these images will look like...</description>
		<content:encoded><![CDATA[<p>Rendering 3d shouldn&#8217;t be the final say (too bad it is) and is not worth THAT much stress and time. In 20 years these images will look like&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonasll</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-25388</link>
		<dc:creator>jonasll</dc:creator>
		<pubDate>Thu, 16 Apr 2009 15:05:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-25388</guid>
		<description>As a student, i would have to say that renders are part of what we learn, but this has to be learned on our own... no techers to give us tips, etc...  so thats kinda frustrating when you get into a studio critics day, and all your getting criticized about are your damn renderings (theyre not showing things, too dark, not realistic enough, etc, etc, etc....)  what about architecture....   what are selling the packaging, not the product...</description>
		<content:encoded><![CDATA[<p>As a student, i would have to say that renders are part of what we learn, but this has to be learned on our own&#8230; no techers to give us tips, etc&#8230;  so thats kinda frustrating when you get into a studio critics day, and all your getting criticized about are your damn renderings (theyre not showing things, too dark, not realistic enough, etc, etc, etc&#8230;.)  what about architecture&#8230;.   what are selling the packaging, not the product&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stan</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-24945</link>
		<dc:creator>Stan</dc:creator>
		<pubDate>Wed, 15 Apr 2009 03:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-24945</guid>
		<description>As for me - as and architect - I tend to see images and glimpses of a real building in my head. Then I have to try and transcribe some of these into an organic building by rough sketches, cardboard assemblages. After that I think modeling in Sketchup is invaluable in providing feedback since you can view and shape the building at so many levels. You can make so many cool images from a textured sketchup model and also adding creative touches in Photoshop. These models still have an open ended creative possibility conveyed. Beyond this you can render more realistically and quickly in SU with Podium or IDX Renditioner ( I just discovered!)

In my opinion this should be developed by the architect in design or someone working with him. The client should be in on the progress and only then should the CD&#039;s or BIM model be detailed. If your BIM software is flexible like I have found Archicad to be - then you can quickly convert that SU model into Archicad for further work.

This whole problem is occurring because Architects are not designing in 3d to begin with and the project progresses so far in a vague way in 2d before the 3d &#039;experts&#039; are called in. Oh! and then they finally see what they have been working on all along and are surprised. Then they want changes. 

We live in an amazing age to have a tool like Sketchup and that process blows away all the old 2d methods in my opinion. Be thankful and show the architects how stupid they are to not design in 3d. There should be no excuses.</description>
		<content:encoded><![CDATA[<p>As for me &#8211; as and architect &#8211; I tend to see images and glimpses of a real building in my head. Then I have to try and transcribe some of these into an organic building by rough sketches, cardboard assemblages. After that I think modeling in Sketchup is invaluable in providing feedback since you can view and shape the building at so many levels. You can make so many cool images from a textured sketchup model and also adding creative touches in Photoshop. These models still have an open ended creative possibility conveyed. Beyond this you can render more realistically and quickly in SU with Podium or IDX Renditioner ( I just discovered!)</p>
<p>In my opinion this should be developed by the architect in design or someone working with him. The client should be in on the progress and only then should the CD&#8217;s or BIM model be detailed. If your BIM software is flexible like I have found Archicad to be &#8211; then you can quickly convert that SU model into Archicad for further work.</p>
<p>This whole problem is occurring because Architects are not designing in 3d to begin with and the project progresses so far in a vague way in 2d before the 3d &#8216;experts&#8217; are called in. Oh! and then they finally see what they have been working on all along and are surprised. Then they want changes. </p>
<p>We live in an amazing age to have a tool like Sketchup and that process blows away all the old 2d methods in my opinion. Be thankful and show the architects how stupid they are to not design in 3d. There should be no excuses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ion</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-24782</link>
		<dc:creator>Ion</dc:creator>
		<pubDate>Tue, 14 Apr 2009 14:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-24782</guid>
		<description>If you don&#039;t have a passion for rendering you&#039;r doomed :) 
You have to be able to visualy express your product as good as possible to win.
 On the other hand I&#039;m all too familiar with the story: an ANALPHABET in 3D asks for an awesome looking render in no time, hocus-pocus stuff. He does&#039;n know the necessary effort requaired, he won&#039;t be able to appreciate it or recompensate for it, nor allocate time and resource (man-hours load). He knows 2 things : 1-he needs the renders in no time; and 2- if he pushes you maybe you&#039;ll be able to do it.
 Let&#039;s face the options: 
 a) you don&#039;t do it coz it&#039;s too little time for too much work and you have other stuff to live for (like running after ciks, drink beer and discuss the future of humanity with friends). output: you&#039;ll take all the blame for the failure, like it&#039;s your fault that 3d doesn&#039;t appear instantly from poor 2d.
 b) you do it poorly, fast minimalistic stuff. output:again you&#039;ll take the blame for practical failure and risk overnight remakes for no good whatsoever regarding the finish product 
 c) do it properly, against time am odds, changing the change of the change and then going back 5 steps, you know, proper f**k. output: you live one more month in that miserable office, reading articles about how successful and awesome your boss is (guess how good you&#039;r gonna feel about yourself, and just wait till the next deadline...)

So this is a NO-WIN situation. The only way to win from this is to make clear the conditions for doing a proper render (if your able to do one in the first place): moooooooooney and a deadline for modifications. (don&#039;t forget you have the boss by his balls, he needs the renderings).
otherways just avoid at all costs. only pain and sorrow involved.</description>
		<content:encoded><![CDATA[<p>If you don&#8217;t have a passion for rendering you&#8217;r doomed :)<br />
You have to be able to visualy express your product as good as possible to win.<br />
 On the other hand I&#8217;m all too familiar with the story: an ANALPHABET in 3D asks for an awesome looking render in no time, hocus-pocus stuff. He does&#8217;n know the necessary effort requaired, he won&#8217;t be able to appreciate it or recompensate for it, nor allocate time and resource (man-hours load). He knows 2 things : 1-he needs the renders in no time; and 2- if he pushes you maybe you&#8217;ll be able to do it.<br />
 Let&#8217;s face the options:<br />
 a) you don&#8217;t do it coz it&#8217;s too little time for too much work and you have other stuff to live for (like running after ciks, drink beer and discuss the future of humanity with friends). output: you&#8217;ll take all the blame for the failure, like it&#8217;s your fault that 3d doesn&#8217;t appear instantly from poor 2d.<br />
 b) you do it poorly, fast minimalistic stuff. output:again you&#8217;ll take the blame for practical failure and risk overnight remakes for no good whatsoever regarding the finish product<br />
 c) do it properly, against time am odds, changing the change of the change and then going back 5 steps, you know, proper f**k. output: you live one more month in that miserable office, reading articles about how successful and awesome your boss is (guess how good you&#8217;r gonna feel about yourself, and just wait till the next deadline&#8230;)</p>
<p>So this is a NO-WIN situation. The only way to win from this is to make clear the conditions for doing a proper render (if your able to do one in the first place): moooooooooney and a deadline for modifications. (don&#8217;t forget you have the boss by his balls, he needs the renderings).<br />
otherways just avoid at all costs. only pain and sorrow involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pixel</title>
		<link>http://www.archdaily.com/19360/12-reasons-to-refuse-to-render/#comment-24761</link>
		<dc:creator>Pixel</dc:creator>
		<pubDate>Tue, 14 Apr 2009 12:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.archdaily.com/?p=19360#comment-24761</guid>
		<description>It&#039;s true, It&#039;s better to leave the renderings to the guys who only do that.
It leaves more time for the architect to do his/hers job and at the end of the day the renderings look good because they were done by professionals.</description>
		<content:encoded><![CDATA[<p>It&#8217;s true, It&#8217;s better to leave the renderings to the guys who only do that.<br />
It leaves more time for the architect to do his/hers job and at the end of the day the renderings look good because they were done by professionals.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
