<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Long Cinema 4D render time in Visualization</title>
    <link>https://community.graphisoft.com/t5/Visualization/Long-Cinema-4D-render-time/m-p/93811#M23171</link>
    <description>Bill,&lt;BR /&gt;
&lt;BR /&gt;
Thanks... 21 Minutes! Quality looks the same to me. The smaller prepass an "is that what that does?" time saver.&lt;BR /&gt;
&lt;BR /&gt;
You saved me a day and since time is money where do I send the check? Trial and error would have taken a lot longer.. Starting with low settings and increasing to the point of diminishing returns seems to be best when it comes to rendering.&lt;BR /&gt;
&lt;BR /&gt;
Fixed the grass too.. procedural?? &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_confused.gif" style="display : inline;" /&gt;</description>
    <pubDate>Wed, 12 Jan 2005 02:35:20 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2005-01-12T02:35:20Z</dc:date>
    <item>
      <title>Long Cinema 4D render time</title>
      <link>https://community.graphisoft.com/t5/Visualization/Long-Cinema-4D-render-time/m-p/93809#M23169</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;I did this render with C4D default radiosity and 10% sharpening.. Can't figure why it took 37+ hours!.. All non-essentials were turned off in AC prior to 3ds export.. The plants are low polygon VB+Visual bits...&lt;BR /&gt;
&lt;BR /&gt;
Object Info:&lt;BR /&gt;
Points:  172,862&lt;BR /&gt;
Polygons: 140,654&lt;BR /&gt;
Objects: 88&lt;BR /&gt;
&lt;BR /&gt;
Rendered in Picture Window, 640x480 NTSC&lt;BR /&gt;
&lt;BR /&gt;
My equipment is not exactly low end &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_eek.gif" style="display : inline;" /&gt;&lt;/R&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="37h26m Left Front.jpg" style="width: 640px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/11557i00D16232C7D34F8B/image-size/large?v=v2&amp;amp;px=999" role="button" title="37h26m Left Front.jpg" alt="37h26m Left Front.jpg" /&gt;&lt;/span&gt;</description>
      <pubDate>Thu, 11 May 2023 10:39:30 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Long-Cinema-4D-render-time/m-p/93809#M23169</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-11T10:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: Long Cinema 4D render time</title>
      <link>https://community.graphisoft.com/t5/Visualization/Long-Cinema-4D-render-time/m-p/93810#M23170</link>
      <description>Rashid&lt;BR /&gt;
&lt;BR /&gt;
in render settings &amp;gt; radiosity:&lt;BR /&gt;
&lt;BR /&gt;
change diffuse depth to 1 (for internal scenes 2 or possibly 3 might be needed)&lt;BR /&gt;
&lt;BR /&gt;
reduce accuracy to around 55% (i find that a high setting can actually reduce the quality of the render, particularly with interiors). increase if necessary&lt;BR /&gt;
&lt;BR /&gt;
reduce the pre-pass size to 1/4 or less&lt;BR /&gt;
&lt;BR /&gt;
use 'render region' on a small part of the scene to check for quality/artifacts before running a final render (if you're getting artifacts on surfaces increase 'min samples', for artifacts at internal corners increase 'max samples')&lt;BR /&gt;
&lt;BR /&gt;
hth&lt;BR /&gt;
&lt;BR /&gt;
bill&lt;BR /&gt;
&lt;BR /&gt;
and make a procedural material for the grass. obviously tiled surfaces really let down any render</description>
      <pubDate>Tue, 11 Jan 2005 22:30:22 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Long-Cinema-4D-render-time/m-p/93810#M23170</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-01-11T22:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: Long Cinema 4D render time</title>
      <link>https://community.graphisoft.com/t5/Visualization/Long-Cinema-4D-render-time/m-p/93811#M23171</link>
      <description>Bill,&lt;BR /&gt;
&lt;BR /&gt;
Thanks... 21 Minutes! Quality looks the same to me. The smaller prepass an "is that what that does?" time saver.&lt;BR /&gt;
&lt;BR /&gt;
You saved me a day and since time is money where do I send the check? Trial and error would have taken a lot longer.. Starting with low settings and increasing to the point of diminishing returns seems to be best when it comes to rendering.&lt;BR /&gt;
&lt;BR /&gt;
Fixed the grass too.. procedural?? &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_confused.gif" style="display : inline;" /&gt;</description>
      <pubDate>Wed, 12 Jan 2005 02:35:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Long-Cinema-4D-render-time/m-p/93811#M23171</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2005-01-12T02:35:20Z</dc:date>
    </item>
  </channel>
</rss>

