<?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: Is this  normal? 18 hours and more for a rendering in Visualization</title>
    <link>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236048#M9399</link>
    <description>Has it exceeded your RAM capacity and started to use your HDD? That would slow things down dramatically...&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Ling.</description>
    <pubDate>Tue, 12 Jan 2021 01:30:28 GMT</pubDate>
    <dc:creator>Lingwisyer</dc:creator>
    <dc:date>2021-01-12T01:30:28Z</dc:date>
    <item>
      <title>Is this  normal? 18 hours and more for a rendering</title>
      <link>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236046#M9397</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I think there is something not quite working here: I am kind of new to Cinerender, so bear with me. I begun a rendering session more than 18 hours ago for a simple pre-set scene (interior light in final mode). Cinerender has been stuck at 9% for the past 18 hours. Here is a screenshot. I don't have any compelx geometry and I am using mostly preset materials. The rendering is a150dpi image in A3 size. I am running a Rog Asus with these specs: Win 10 Home edition. Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz   2.81 GHz, 32 RAM and a Nvidia Geoforce GTX 1080. Yesterday I managed to create the same scene at 72 dpi (842x1191 pixels) within minutes.&lt;BR /&gt;
&lt;BR /&gt;
What I find mostly strange is that Cinerender has been stuck at 9% for at least 15 or more hours. &lt;BR /&gt;
&lt;BR /&gt;
Thanks for tour inputs. &lt;BR /&gt;
PP&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 11 May 2023 09:34:43 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236046#M9397</guid>
      <dc:creator>Paopao</dc:creator>
      <dc:date>2023-05-11T09:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: Is this  normal? 18 hours and more for a rendering</title>
      <link>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236047#M9398</link>
      <description>PP,&lt;BR /&gt;
I have deleted this same question you have made in another of your posts.&lt;BR /&gt;
Please just start a new topic as you have done here rather than asking the same thing in multiple posts.&lt;BR /&gt;
It makes it easier to reply to just one topic and easier if it is all in one place.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
I am no rendering expert either.&lt;BR /&gt;
But is seems likely you are using very high settings that you probably don't need.&lt;BR /&gt;
Try using different render scenes - fast/medium rather than final (or custom).&lt;BR /&gt;
With the 'final' settings you are probably calculating all sorts of reflections, shadows, grass (even though you don't have any) and many other settings that are just not necessary or not needed with such high calculation values.&lt;BR /&gt;
Experiment with the different default rendering scenes. &lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 12 Jan 2021 01:19:09 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236047#M9398</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2021-01-12T01:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: Is this  normal? 18 hours and more for a rendering</title>
      <link>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236048#M9399</link>
      <description>Has it exceeded your RAM capacity and started to use your HDD? That would slow things down dramatically...&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Ling.</description>
      <pubDate>Tue, 12 Jan 2021 01:30:28 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236048#M9399</guid>
      <dc:creator>Lingwisyer</dc:creator>
      <dc:date>2021-01-12T01:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: Is this  normal? 18 hours and more for a rendering</title>
      <link>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236049#M9400</link>
      <description>The default preset scenes tend to not be very well optimised. Medium and final will yield very long render times.&lt;BR /&gt;
&lt;BR /&gt;
The interior presets use very high settings to avoid shadow artifacts (global illumination).&lt;BR /&gt;
&lt;BR /&gt;
The exterior fast (physical) preset should work fine as a starting point.</description>
      <pubDate>Tue, 12 Jan 2021 14:21:15 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Visualization/Is-this-normal-18-hours-and-more-for-a-rendering/m-p/236049#M9400</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2021-01-12T14:21:15Z</dc:date>
    </item>
  </channel>
</rss>

