- User Since
- Feb 8 2013, 4:34 PM (349 w, 1 d)
Fri, Sep 27
You may also want to hit F12. Using viewport rendering does not reproduce the error on my machine. Hitting F12 will crash Blender instantly.
I can fully reproduce this both on my windows computer (Nvidia GTX 980) and on our Linux servers (Nvidia K80). It may be a Nvidia only issue.
Forgot to mention, this is affecting Blender 2.80 official release.
Dec 28 2018
Nov 30 2018
These are official builds (those flagged beta on this page: https://builder.blender.org/download/). They do run on a server with Cuda 10 installed though.
Nov 2 2018
Oct 17 2018
This script seems to detect correctly the devices. Thanks!
I changed a bit the script so it prints more information. Here is the script and the output:
Mar 17 2017
I can now confirm the same error will happen on the latest ubuntu as well. Slightly different error message though:
In fact, it works on CentOS 7 for 99.95% of projects. It's just some of them that crash. We do render a significant number of projects (as in hundreds per day) and they are very varied, coming from lots of customers who use the RenderStreet service. I opened this bug hoping I would help you track why it crashes on these few cases.
Mar 16 2017
Aug 4 2015
Thanks for sending this update.
Aug 3 2015
Jan 19 2015
@Sergey Sharybin (sergey), I have only tested the 64 thread version (on an 172 thread power8 machine, 2.69 version from apt-get) and was scaling quite nicely. I have only tested the Cycles rendering part though, not the others.