@Lukas Stockner (lukasstockner97) can you check that one? Thanks.

Issue is not present in rB78c2063685cb6e0d0bcb895cf4eb70686455d596
Issue is present in rBdb333d9ea4881d9f48e3cc4b1ec59b4dafb27cc0

This was not the behaviour in rB7f86afec9d6

Some more inline comments.

Thanks for the link to CUDA-Z! Very helpful tool.
It is a system wide problem and not blender-related.
I passed this error to the GENTOO developer crew.
This task/ticket can closed.

Please check:

• If there is a separate package that needs to be installed for CUDA support.
• If there exists a libcuda.so.1 or libcuda.so in your computer and where it is located.

Confirmed, @Brecht Van Lommel (brecht) not sure if that’s known limitation or actual bug?

@Bastien Montagne (mont29) If you save the file, it will not crash anymore. You need to reproduce exactly this steps.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

@Brecht Van Lommel (brecht) after CUDA issues, OpenCL one…

@Brecht Van Lommel (brecht) I guess that one is for you? ;)

2.79.6 Win7 32

i tried and even on blender-2.80-0e8bd6ba8a2 crashes.

Hi guys,
some observations and wishes for microdisplacement.

• I wish you could have continuous displacement even in flat shading, especially for quick set ups of walls etc. (I think Vray has this option)
• the only workflow that does not rip geometry is smooth shading, subdivision to avoid artefacts, and box uv projection (3.)
• UV unwrapping produces beautiful edges (4.) unless you place a UV seam which rips the geometry, This should be fixed easily since box projection (3.) projects different image portion on cube face too, but does not rip the geometry.

I'm seeing CUDA renders on macOS giving wrong results starting with rBd611cf923358 (determined via git bisect, MBP Retina, 15-inch, Late 2013, GeForce GT 750M, Xcode 9.2, CUDA 9.2). The code in rBd611cf923358 looks innocent to me, may be that commit just exposed a compiler bug on macOS?

I'm not sure why you can't do much, seems like blender isn't interacting with the cuda libraries to detect gpus. Can you explain more?

Hi! Any thoughts on this one?

Layer weight is a camera view dependent effect, and for baking we assume every pixel is being viewed head on. The corresponding layer weight value is 0.0, so the baking result is black.

Thanks for testing, seems it was just running out of memory then.

i just found the problem:
the page file was too small (was set to 256MB), made it bigger and now it renders perfectly.

i tried to locate the object that is causing the issue.

Hey all,

I am not strong in this kind of things)) can anyone on Mac try this one?

I just gave it another try. Both with 2.79 latest master and 2.80 latest. This time under Windows. No artefacts there as well. So it might be a Mac thing, maybe OpenCL related?!

And also there is no artifacts if i render CPU only. Its only in Hybrid mode

Yes, sorry its my fault about the material =( but when i correct this its also the same artifacts here in the latest version of 2.79((( and if i render this in older 2.79.4 version its ok, even with the mistake in the material! maybe this issue on Mac Os, because you said that you have Linux Mint