Loading...
> >

Well that was a mistake...

nicsttnicstt Posts: 11,715
in The Commons

Loaded a cube, but on a lot of divisions, and assigned a dforce modifier to it.

It's being doing the springs for about an hour now and its 35% of the way through, but what I did I'll lose if I kill it.

So it got me wondering, what have others done that they had to wait for? I have some time LOL.

Comments

  • LinwellyLinwelly Posts: 6,067

    Fuidos ... letting some drops rund down a sword. took forever and a day ,until I asked and learned about some changes to the settings that tremedously helped speeding up the process

  • FirstBastionFirstBastion Posts: 8,050

    I once set up a render for an animation,  for 720 frames,  about 24 seconds worth,  with each render taking just over a minute to render, clocking in at 12 hours. I watched it for the first few frames, went to bed,  woke up in the morning,  and got to watch the last 50 frames render.  It saved fine. If the end result is worth it, rendering is just a necessary part of the process.

     

  • L'AdairL'Adair Posts: 9,479
    edited October 2019

    @nicstt, If I understand what you're saying, the cube hasn't started to drape yet and you want to stop the process without losing your work up to that point. Have you tried cancelling the simulation? Theoretically, that would stop the springs calculations without affecting the rest of the scene. Then you could save immediately.

    It's taken me some time, (and some lost work,) to get into the habit of saving before I simulate. I have a custom menu for dForce in my menu bar, and I even added Save File there! When I click on that menu to Simulate, I see the option to save the file, which I can select instead of Simulate, if I forgot to save first. That has been a real time/scene saver for me.

    ETA: Before I bought The Beast, all my Iray renders were CPU Only. I've left scenes to render for a week or more, feeling happy to get 2500 samples, or thereabouts.

    Post edited by L'Adair on
  • kyoto kidkyoto kid Posts: 42,044
    edited October 2019

    ...rendered a scene with a 5 frame motion blur in 3DL with UE and it took 16 hours 30 minutes to complete.  Made rendering times in Iray CPU mode look fast.

    Looked great in the end but I feared I'd be awoken by the smoke alarm when I went to bed because my system had a melt down.

    Post edited by kyoto kid on
  • nicsttnicstt Posts: 11,715
    edited October 2019
    L'Adair said:

    @nicstt, If I understand what you're saying, the cube hasn't started to drape yet and you want to stop the process without losing your work up to that point. Have you tried cancelling the simulation? Theoretically, that would stop the springs calculations without affecting the rest of the scene. Then you could save immediately.

    It's taken me some time, (and some lost work,) to get into the habit of saving before I simulate. I have a custom menu for dForce in my menu bar, and I even added Save File there! When I click on that menu to Simulate, I see the option to save the file, which I can select instead of Simulate, if I forgot to save first. That has been a real time/scene saver for me.

    There's no cancel button during the spring-creation process.

    97%, so nearly there.

    That is a definite reature request.

    Post edited by nicstt on
  • L'AdairL'Adair Posts: 9,479
    nicstt said:
    L'Adair said:

    @nicstt, If I understand what you're saying, the cube hasn't started to drape yet and you want to stop the process without losing your work up to that point. Have you tried cancelling the simulation? Theoretically, that would stop the springs calculations without affecting the rest of the scene. Then you could save immediately.

    It's taken me some time, (and some lost work,) to get into the habit of saving before I simulate. I have a custom menu for dForce in my menu bar, and I even added Save File there! When I click on that menu to Simulate, I see the option to save the file, which I can select instead of Simulate, if I forgot to save first. That has been a real time/scene saver for me.

    There's no cancel button during the spring-creation process.

    97%, so nearly there.

    That is a definite reature request.

    I've used the keyboard ESC button to exit a simulation. Maybe it will work during that process…? Worth a shot. (Though if you're that close, you may want to just wait and see what the drape does to the cube, now.)

  • glaseyeglaseye Posts: 1,312

    creating skydome textures in Vue; some took more than100(!) hours to render....  thank goodness for vue's option to pause and save an incomplete render, so you can load and resume it later... 

  • nicsttnicstt Posts: 11,715
    glaseye said:

    creating skydome textures in Vue; some took more than100(!) hours to render....  thank goodness for vue's option to pause and save an incomplete render, so you can load and resume it later... 

    Damn!

     

    L'Adair said:
    nicstt said:
    L'Adair said:

    @nicstt, If I understand what you're saying, the cube hasn't started to drape yet and you want to stop the process without losing your work up to that point. Have you tried cancelling the simulation? Theoretically, that would stop the springs calculations without affecting the rest of the scene. Then you could save immediately.

    It's taken me some time, (and some lost work,) to get into the habit of saving before I simulate. I have a custom menu for dForce in my menu bar, and I even added Save File there! When I click on that menu to Simulate, I see the option to save the file, which I can select instead of Simulate, if I forgot to save first. That has been a real time/scene saver for me.

    There's no cancel button during the spring-creation process.

    97%, so nearly there.

    That is a definite reature request.

    I've used the keyboard ESC button to exit a simulation. Maybe it will work during that process…? Worth a shot. (Though if you're that close, you may want to just wait and see what the drape does to the cube, now.)

    Ha! I did, and the result was terrible; far too much geometry in too small an item.

  • GordigGordig Posts: 10,647

    I'm running a dForce simulation involving maybe 12 pieces of clothing and one hair prop. It's chugging along at around 1% per minute, and the one item that I specifically wanted to simulate has already exploded.

  • WendyLuvsCatzWendyLuvsCatz Posts: 40,417
    Gordig said:

    I'm running a dForce simulation involving maybe 12 pieces of clothing and one hair prop. It's chugging along at around 1% per minute, and the one item that I specifically wanted to simulate has already exploded.

    You do one at a time then freeze simulation and do the next one or you get what you deserve laugh

  • GordigGordig Posts: 10,647

    Oh, I know. Several pieces are already simulated and frozen. I just felt like living dangerously.

Sign In or Register to comment.