- User Since
- Mar 11 2016, 4:04 PM (170 w, 6 d)
Mar 15 2019
In case the debug logs are useful again, those are from running the blender_debug_gpu.cmd again but with the complete reset Blender and the test scene from the last comment.
Seems like it doesn't even show the error, in some of the crashes I recorded the error also did not show up at the end, not sure if it just crashes faster then it can log, or how that works.
Okay, I think we can eliminate those two addons.
I already reset the usersettings (basically deleting the 2.80 folder in appdata, besides the two addons), in terms of non-standard things there would only be Animation Nodes addon and my small little render button addon.
I did once test removing the my own addon and nothing changed.
Don't think that can cause anything but I will admit its a hack copy/paste job from 2.79 over to 2.80 and I have little clue about python really.
Can confirm that the GUI was slower, like the camera was slower.
The rendering times per frame seemed to be on par with before though in Eevee.
Mar 14 2019
Here is the Log with Cycles in 2.8.
Quite big because it did render a bunch.
I can confirm that this also happens in Blender 2.8 with Cycles.
2.79 seems stable with GPU rendering from a test I'm currently running which already went through 800 frames in the past 8:30min.
Mar 11 2016
Forgot to name my OS: Windows 10 64bit (v1511)
And in the image is a small error, it should say Blender 2.77 RC2 instead of Blender 2.77 RC.
(My first report here.)