[Bf-cycles] Cycles GPU render
Brecht Van Lommel
brechtvanlommel at pandora.be
Tue Feb 26 12:44:58 CET 2013
If you enable all kernel features, at least 8 GB before it crashes
here. When disabling most features and using an ambient occlusion only
render, it's about 1 GB.
The way I understand it is basically that AMD graphics cards do not
support true function calls, everything must be inlined. This means
the amount of code becomes so big that the compiler runs out of memory
or some sort of GPU limitation is crossed. This means we either have
to wait for AMD to find a solution to that problem and support
non-inlined functions, or that we rewrite our kernel such that it's
split into small pieces which would be quite complicated to do.
On Tue, Feb 26, 2013 at 1:52 AM, Germano Cavalcante
<germano.costa at ig.com.br> wrote:
> Hello, sorry for the inconvenience but
> Does anyone have data about how much memory Blender takes to compile the
> Nvidia OpenCL (and how long they take)?
> This is to help engineers from AMD to find causing the problem of rendering
> cycles (and perhaps the recursive procedural materials into LuxRender).
> http://devgurus.amd.com/message/1287363 # 1287363
> Germano Cavalcante
> Bf-cycles mailing list
> Bf-cycles at blender.org
More information about the Bf-cycles