[Bf-cycles] CUDA error with Cycles_standalone

Brecht Van Lommel brechtvanlommel at pandora.be
Fri Feb 21 15:42:04 CET 2014


I couldn't reproduce this problem on Mac OS X, I'm not sure what is
going on. Perhaps your graphics card doesn't support an OpenGL feature
that we use, but even then it's not clear to me why it would give this

Which graphics card(s) do you have?


On Wed, Feb 19, 2014 at 12:05 AM, Zhanpeng Feng <jumpjump88 at hotmail.com> wrote:
> Hi,
> I was trying to use the cycles_standalone and and got the following error. I
> am wondering if anyone has seen similar issues?
> Error message:
> D:\blenderSVN_2\cmake-build\bin\Debug>cycles --device cuda --samples 10
> monkeyte
> st.xml --output this.bmp
> CUDA error: Invalid context in cuGraphicsMapResources(1,
> &pmem.cuPBOresource, 0)
> Refer to the Cycles GPU rendering documentation for possible solutions:
> http://wiki.blender.org/index.php/Doc:2.6/Manual/Render/Cycles/GPU_Rendering
> CUDA error: Not mapped in cuGraphicsResourceGetMappedPointer(&buffer,
> &bytes, pm
> em.cuPBOresource)
> CUDA error: Not mapped in cuGraphicsUnmapResources(1, &pmem.cuPBOresource,
> 0)
> CUDA error: Launch failed in cuCtxSynchronize()
> In the cycles standalone GUI I am able to see the rendering progresses and
> the scene is actually being rendered fine. No error occurs until tonemap()
> is called in the
> void Session::update_status_time(bool show_pause, bool show_done) function
> of session.cpp
> else if(show_done) {
> status = "Done";
> tonemap();
> progress.set_status("Writing Image", params.output_path);
> display->write(device, params.output_path);
> }
> If I run it using --device cpu everything works fine.
> Any help is appreciated.
> Thanks a lot,
> Feng
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> http://lists.blender.org/mailman/listinfo/bf-cycles

More information about the Bf-cycles mailing list