Loading...
> >

And the Render Nightmare Award goes to...

CHWTCHWT Posts: 1,191
in The Commons
It's a double winner: i13 Neighborhood Bar (causes DS to crash every time) and i13 New Addition Living (way behind the 95% convergence ratio when DS hit its default max render time limit i.e., 3 days). I know, I know, maybe it's my hardware not up to par, and to be honest i13 New Addition Living renders beautifully even if it's far from finished but still... yeah. What are your render nightmare products?

Comments

  • thd777thd777 Posts: 945

    Might well be your hardware. Here is the Neighborhood Bar. Just loaded and rendered. Render Time 5 min 10 sec. I do not have the other one so I cannot try it. For comparison, my setup is a i9 10980XE processor (18 core) with 128Gb of RAM. GPUs are one GTX1080ti and one RTX 2080ti.

    What is your setup?

    Ciao

    TD

    Neighborhood Bar.png
    1200 x 675 - 1M
  • nonesuch00nonesuch00 Posts: 18,830

    almost surely running out of ram....set the optimization in the render settings to be for memory

  • CHWTCHWT Posts: 1,191
    thd777 said:

    Might well be your hardware. Here is the Neighborhood Bar. Just loaded and rendered. Render Time 5 min 10 sec. I do not have the other one so I cannot try it. For comparison, my setup is a i9 10980XE processor (18 core) with 128Gb of RAM. GPUs are one GTX1080ti and one RTX 2080ti.

    What is your setup?

    Ciao

    TD

    Haha, it's definitely the processor and the RAM. Nah it's too embarassing to tell you how subpar my hardwares are. But my usual rendering time for a 1564 x 1564 image is usually less than an hour, so these two i13 sets really are 'special' to me.
  • CHWTCHWT Posts: 1,191
    nonesuch00 said:

    almost surely running out of ram....set the optimization in the render settings to be for memory

    Good tip. Thanks mate !
  • richardandtracyrichardandtracy Posts: 7,501
    edited August 2021

    This render using 'Brooke' by LiquidRust caused me to give up with DS for 12 years. Would that count as a nightmare?

    It took 26 hours, 43 minutes on my PC of the time (2007). It used the new-fangled V4 with all that extra geometry compared to V3, a hugely heavy 47k facet hair model (IIRC), and ray tracing in DAZ Studio 1.0.something using the incredibly powerful, realistic and oh so slow, '3Delight' rendering engine. I also used reflection maps and kept the shadow maps as small as I could get away with. It convinced me there was no point in trying again until I had a computer with a bit of grunt. So, when my work got rid of our 2013 vintage Xeon based machines in 2019, I grabbed one and have enjoyed playing with DS again. 

    Oh yes, the original machine's specs: 1Gb Ram, 1.2Ghz, running Win XP and a 4Mb (yes MB) graphics card.

    Regards,

    Richard

    Post edited by richardandtracy on
  • CHWTCHWT Posts: 1,191
    edited August 2021
    richardandtracy said:

    This render using 'Brooke' by LiquidRust caused me to give up with DS for 12 years. Would that count as a nightmare?

    It took 26 hours, 43 minutes on my PC of the time (2007). It used the new-fangled V4 with all that extra geometry compared to V3, a hugely heavy 47k facet hair model (IIRC), and ray tracing in DAZ Studio 1.0.something using the incredibly powerful, realistic and oh so slow, '3Delight' rendering engine. I also used reflection maps and kept the shadow maps as small as I could get away with. It convinced me there was no point in trying again until I had a computer with a bit of grunt. So, when my work got rid of our 2013 vintage Xeon based machines in 2019, I grabbed one and have enjoyed playing with DS again. 

    Oh yes, the original machine's specs: 1Gb Ram, 1.2Ghz, running Win XP and a 4Mb (yes MB) graphics card.

    Regards,

    Richard

    Yes, it WAS a nightmare in 2007 (but I guess it was worth it) and no it isn't a nightmare now for a 26-hour render (given my 3-day nonsensical fiasco lol)
    Post edited by CHWT on
  • JOdelJOdel Posts: 6,322

    In 2011 it took DS3 five days (and nights) to render a christmas tree. DS3 was still 32-bit on a Mac.

  • nicsttnicstt Posts: 11,715

    So basically, an xmas scene took 12 days? wink

  • AllenArtAllenArt Posts: 7,175

    CHWT said:

    It's a double winner: i13 Neighborhood Bar (causes DS to crash every time) and i13 New Addition Living (way behind the 95% convergence ratio when DS hit its default max render time limit i.e., 3 days). I know, I know, maybe it's my hardware not up to par, and to be honest i13 New Addition Living renders beautifully even if it's far from finished but still... yeah. What are your render nightmare products?

    Seems to render fine and very fast for me. I have a measly 980Ti with 6 gigs on it, but I do have 64 gigs of ram and two Xeons with 8 cores each. Not sure which is contributing ;). 

    i13 Neighborhood Bar.jpg
    1600 x 900 - 790K
  • FSMCDesignsFSMCDesigns Posts: 12,851

    loaded and rendered fine for me also. Took about 8 minutes with a 2080ti.

    My biggest render nightmare is Ultrascenery WITH figures in it. by itself, I can render it fine, but add a couple of figures, hair, clothing, etc, maybe a couple of props and I really have to optimize the crap out of it to get it to even render and then it takes forever.

  • MistaraMistara Posts: 38,675

    ever try to load the sakura tree?  lonnnng load time, infinity and then some. it is a nice tree tho

  • JOdelJOdel Posts: 6,322
    edited August 2021

    nicstt said:

    So basically, an xmas scene took 12 days? wink

    There were five trees, a room and a few other decorations. And I had to render the trees, the room and the foreground all separately. I think it came to something more like 15-16 days all told. Admittedly that tree was the worst of the lot.

    Trying to work in a 32-bit program was a PITA.

    Otoh, Abraham Hair in DS4 with 3DL shaders tied up my last machine for about 4 days, and it was only in middle distance. But I suspect that was a special case.

    Post edited by JOdel on
Sign In or Register to comment.