- User Since
- Feb 25 2017, 4:16 AM (99 w, 3 d)
Sun, Jan 13
Alright after 8 hours of rendering, I think the problem has fixed itself.. Must've been the updates from AMD drivers.. I rendered as images for 8 hours and nothing happened until I decided to use a little bit too much cpu when I was on the pc and it crashed. I'm sure that rendering as a video would most likely yield the same result. I'm certain my problem has been fixed by something new in blender builds or AMD drivers over the months. Thanks for your help!
Thu, Jan 10
Speak of the devil... as I made that reply it just crashed. I didn't get a chance to read the command log, I assume it's the same thing but is there a way to read the command log again? It seems to have gone for a lot longer this time, it reached frame 600 until it crashed, so something went right..
I apologize for not being active in this thread, I'm making this reply for now before someone starts figuring out what's wrong. I've downloaded the latest build and updated my drivers, I retried rendering the test scene again and it seems to work. I'm rendering a scene I made a few months ago that I didn't get to render, and seeing if it'll crash after a night of rendering.
Dec 2 2018
problem still around in build blender-2.80.0-git.925380050d0-windows64
Nov 27 2018
problem still present in build 26b1aa99436
Nov 21 2018
can confirm it's the same problem in latest build, git.63150511a29-windows64
Nov 20 2018
https://www.youtube.com/watch?v=hU3D6HdR7gw Here's a fixed link, also I just noticed this after playing the video back a couple times. https://gyazo.com/070f42381105410fa9dd207f033c9a51 it's in the video aswell. Also, I made sure to have my graphics driver updated.
Apologies, sent the wrong .blend, here's the correct one: https://drive.google.com/open?id=1aTdQUwLl-pJpHm4GtNlu2llsvqoGngJA