Hello all

Ok first some info. I have desktop with quad core 2.4G and 8 gig of memory. 1Tb HDD so that should be ok.

The problem:
I have scene that takes long render time above 6 hours so I want to do at night. The problem is I start render around let say 9 pm and can see it goes ok until I sleep. This night I even checked around 3 am when was short awake. This morning however DS 3adv program was closed. I had same yesterday so me lost why.

I turned the sleep mode of my system OFF just to make sure,

I looked at the log file also but cant find reason or even statement at give dates that DS closed.

Hope you have tips

thks

What did the end of the log file say? Are you sure it wasn't something like an update causing a system reset?

thks for help offer. Maybe indeed system update or something. The log file just shows close of DS like normal. I did the render again during day and worked normal

thks

 Hi, I used to have similar issues on my old system - it turned out to be Windows going into power save mode two hours after I'd left it alone.

What I ended up doing was going into my control panel and turning off all the functions like 'sleep', 'power save mode' and then in the system management tab, turning up automatic updates as this can prompt the machine to restart.

I then manually switched the screen off, put the keyboard upright so the cats couldn't land on it and went to bed :) all worked fine. 

The next day I just re-enabled the power save modes and automatic updates. It only took a couple of minutes, once I'd figured it out.

Best of luck! I know how frustrating it can be to see a blank screen or half a file where you're hoping for a beautiful render. 

I do almost all of that on my system as well...except I stuff my keyboard tray under the desk cause my cats always seem to stand on the power button...then there's the touchscreen controls for my monitor....

Come to think of it, most of my prep work for a midnight render involves cat proofing!

ahahaha thks all. Yes cats are a 3D hazard for sure. LOL

Actually, I should have mentioned that any time I have that problem it's usually because of something updating, or my system went into sleep-mode or some such. Once those details were looked after I've been able to do 87 hour renders. (don't ask)