- User Since
- Oct 28 2019, 5:42 AM (91 w, 6 d)
Mon, Jul 26
I can't actually upload the file due to NDA. However working on another file (which I also can't share) which is totally seperate, after rendering multiple 4K images out over the course of working on the file for a few hours. I got the error message "System out of GPU memory". I escaped, didn't close the file but tried to re-render, same message came up and wouldn't start. I then went from LookDev to the internal shade view (forget what its called), pressed render then it started rendering.
Thu, Jul 22
Yes I was able to re-render after starting the render again. First time it got to frame 155 and then continued on from that frame which it got to frame 206. I would have expected it to have rendered another 155 frames but it only rendered 51.
Wed, Jul 21
Nov 29 2019
Nov 26 2019
This is an issue with 2.81 and is well known about where Eevee stops rendering.
@Omar Rahim (3Omar9) I have the issue on a 2017 MacBook Pro 15inch Touch and with a 2016 MacBook Pro 15inch Retina. 2017 happens on Mojave and Catalina and the 2016 happens on High Sierra.
Nov 22 2019
Nov 19 2019
Nov 14 2019
VRAM would certainly make sense. I just used the factory default 2.81.16 (one released 13th November) and created a metaball, added a multi-resolution modifier with 3 sub-divisions. Sculpted a bit, turned on Render viewport, added a second lamp into the scene and then selected the other lamp, and then the metaball disappeared.
Nov 7 2019
Issue still happening in v2.81.16