usamike opened this issue on Mar 04, 2008 · 100 posts
aRtBee posted Sun, 26 February 2012 at 7:15 AM
Glad to give some info too. Scene downloaded, unpacked and run, no flaws.
Score: 14-15 seconds to render, either internal or as external process (consistent over 6 runs).
When rendering external, shadow maps have to be calculated first unless re-used from an earlier run (check the menu option), this adds 5 to 10 sec and seems to be a 1-thread process. When rendering internally, things seem to be slightly different (= much faster).
When rendering the first time textures have to be found, this takes 40-50 sec additionally. Its a 1-thread process whether you render internally or externally. Speed depends on the size of the Poser Runtime folders which have to be searched, mine are 45-50Gb, the default Poser one is about 10% of this. The search result is stored in a Temp folder, so the search has to be redone only when this is cleared between scenes or Poser launches or - as in my case - machine reboots.
Specs:
win7 Pro Sp1 64-bit, PPro 2010 64-bit, CPU: i990X @4GHz (6 cores, 12 threads), RAM: 24Gb incl 4Gb Ram-disk for Temp, C: on SSD (program only, no data), Data on 9x2Tb disk unit, nVidia GTX560Ti OC/1Gb.
Indirect Lighting anyone? I just checked the box in Render Settings.
4.5 min (=270 sec) preparation, 95 sec rendering = 365 total. That's say 25 times as long compared to No IDL. No additional memory required. CPU temp ramped up to 75C = 170F (Idle=45*C). This is fun. Note that using LuxRender might need 30 mins to get a full blown photoreal result (well, not for this scene I guess), which is again 5 times longer.
- - - - -
Usually I'm wrong. But to be effective and efficient, I don't need to be correct or accurate.
visit www.aRtBeeWeb.nl (works) or Missing Manuals (tutorials & reviews) - both need an update though