- User Since
- Mar 31 2015, 9:29 AM (151 w, 6 h)
May or may not be related to T53914.
Thu, Feb 1
Wed, Jan 31
That sounds like a good approach. I suspect that in general, transparent intersections can lead to incorrect path termination. Note how for example how an environment light with diffuse bounces = 0 will not provide direct illumination through transparency. Volume emission currently also provides direct light to surfaces inside the volume's bounds, but not to surfaces outside of the volume's bounds.
Tue, Jan 30
I see what you mean.
Sat, Jan 27
Mon, Jan 22
Thanks, that was quick.
You're right, D2766 only made the issue more visible - it was present in earlier revisions as well when the min transparency parameter was set low enough.
It looks like this happens with plain transparency too - branched path tracing and plain path tracing give different results. See the attached scene.
Dec 13 2017
It is strange, it fails the unit tests because of different noise patterns, but appears to converge to the same result. I'll do some more investigating to find out where things take a different path.
Dec 4 2017
Dec 2 2017
- Cycles: Changed object properties offset to match new data structure size
Dec 1 2017
Nov 29 2017
Nov 28 2017
Yes, Embree is a new dependency. For best results, you should use a patched version of Embree that (like Cycles) ignores ray/ribbon intersections when the ray origin is inside the ribbon. My patched version can be found here: https://github.com/skwerner/embree/tree/cycles_compatible
Nov 27 2017
Nov 26 2017
Nov 21 2017
Nov 20 2017
Nov 12 2017
Nov 10 2017
Even more so, we could use this for the on-demand kernel compilation in device_cuda.cpp. Since it is possible to load PTX directly from the CUDA runtime (with the driver taking over the ptxas step), this should enable on-demand compilation on any operating system without any dependencies other than the CUDA driver.
Nov 9 2017
Nov 8 2017
Since CUEW wraps NVRTC, it could also be an option to use NVRTC directly instead of trying to find and launch nvcc from the command line. That way, this feature would be independent of a 3rd party compiler tool chain and would have less platform-dependent code.
Nov 7 2017
Is there anything holding up a commit? I have a few extensions to this patch to make it work on my system. I see that here the CUDA installer set an environment variable where we can grab the Toolkit location from on Windows. Since it defaults to "C:\Program Files\etc" it also needs slight changes to have quotation marks in the right places to deal with the spaces in the path.
Nov 6 2017
Thanks for your work, this is looking good! Especially the addition for sharing memory with CPU devices is good.