git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2018-03-29	Fix T54455: OpenCL build error after recent changes.	Brecht Van Lommel

2018-03-27	Fix T54420: too much volume render noise with multiple volume objects.	Brecht Van Lommel
	Random numbers for step offset were correlated, now use stratified samples which reduces noise as well for some types of volumes, mainly procedural ones where the step size is bigger than the volume features.
2018-03-19	Fix T54317: overlapping volume render bug after recent changes.	Brecht Van Lommel
	Increasing the samplig dimensions like this is not optimal, I'm looking into some deeper changes to reuse the random number and change the RR probabilities, but this should fix the bug for now.
2018-03-01	Cycles: don't count volume boundaries as transparent bounces.	Brecht Van Lommel
	This is more important now that we will have tigther volume bounds that we hit multiple times. It also avoids some noise due to RR previously affecting these surfaces, which shouldn't have been the case and should eventually be fixed for transparent BSDFs as well. For non-volume scenes I found no performance impact on NVIDIA or AMD. For volume scenes the noise decrease and fixed artifacts are worth the little extra render time, when there is any.
2018-02-22	Cycles: better path termination for transparency.	Brecht Van Lommel
	We now continue transparent paths after diffuse/glossy/transmission/volume bounces are exceeded. This avoids unexpected boundaries in volumes with transparent boundaries. It is also required for MIS to work correctly with transparent surfaces, as we also continue through these in shadow rays. The main visible changes is that volumes will now be lit by the background even at volume bounces 0, same as surfaces. Fixes T53914 and T54103.
2018-02-08	Code refactor: remove unnecessary RNG offset in branched path code.	Brecht Van Lommel
	This is only needed for SSS which bounces to a different shading point.
2018-01-29	Revert "Fix T53914: Volumetric scattering now goes correctly through ↵	Brecht Van Lommel
	transparent surfaces." This reverts commit 3c852ba0741f794a697f95073b04921e9ff94039. This is breaking the regression tests, and maybe requires some deeper changes to really fix.
2018-01-27	Fix T53914: Volumetric scattering now goes correctly through transparent ↵	Stefan Werner
	surfaces. There was a check for volume bounces at every surface intersection. That could lead to a volume scattered path being terminated when passing through a transparent surface. This check was superfluous, as the volume shader evaluation already checks the number of volume bounces and once it passes the max, volume shaders will not return scatter events any more. Reviewers: #cycles, brecht Reviewed By: #cycles, brecht Subscribers: brecht, #cycles Tags: #cycles Maniphest Tasks: T53914 Differential Revision: https://developer.blender.org/D3024
2018-01-19	Cleanup: typos	Campbell Barton

2018-01-12	Cycles: option to make background visible through glass transparent.	Lukas Stockner
	This can be enabled in the Film panel, with an option to control the transmisison roughness below which glass becomes transparent. Differential Revision: https://developer.blender.org/D2904
2017-09-20	Code cleanup: remove hack to avoid seeing transparent objects in noise.	Brecht Van Lommel
	Previously the Sobol pattern suffered from some correlation issues that made the outline of objects like a smoke domain visible. This helps simplify the code and also makes some other optimizations possible.
2017-09-13	Code cleanup: store branch factor in PathState.	Brecht Van Lommel

2017-09-12	Cycles: change AO bounces approximation to do more glossy and transmission.	Mathieu Menuet
	Rather than treating all ray types equally, we now always render 1 glossy bounce and unlimited transmission bounces. This makes it possible to get good looking results with low AO bounces settings, making it useful to speed up interior renders for example. Reviewed By: brecht Differential Revision: https://developer.blender.org/D2818
2017-09-12	Fix Cycles bug in RR termination, probability should never be > 1.0.	Brecht Van Lommel
	This causes render differences in some scenes, for example fishy_cat and pabellon scenes render brighter in a few spots. This is an old bug, not due to recent RR changes.
2017-08-19	Code cleanup: move rng into path state.	Brecht Van Lommel
	Also pass by value and don't write back now that it is just a hash for seeding and no longer an LCG state. Together this makes CUDA a tiny bit faster in my tests, but mainly simplifies code.
2017-08-12	Code cleanup: fix warning and improve terminology.	Brecht Van Lommel

2017-08-07	Fix Cycles shadow catcher objects influencing each other.	Brecht Van Lommel
	Since all the shadow catchers are already assumed to be in the footage, the shadows they cast on each other are already in the footage too. So don't just let shadow catchers skip self, but all shadow catchers. Another justification is that it should not matter if the shadow catcher is modeled as one object or multiple separate objects, the resulting render should be the same. Differential Revision: https://developer.blender.org/D2763
2017-08-07	Cycles: Cleanup, space after keyword	Sergey Sharybin

2017-08-05	Cycles: remove min bounces, modify RR to terminate less.	Brecht Van Lommel
	Differential Revision: https://developer.blender.org/D2766
2017-06-10	Cycles: Selectively include denoising in kernel	Sergey Sharybin

2017-05-07	Cycles: Implement denoising option for reducing noise in the rendered image	Lukas Stockner
	This commit contains the first part of the new Cycles denoising option, which filters the resulting image using information gathered during rendering to get rid of noise while preserving visual features as well as possible. To use the option, enable it in the render layer options. The default settings fit a wide range of scenes, but the user can tweak individual settings to control the tradeoff between a noise-free image, image details, and calculation time. Note that the denoiser may still change in the future and that some features are not implemented yet. The most important missing feature is animation denoising, which uses information from multiple frames at once to produce a flicker-free and smoother result. These features will be added in the future. Finally, thanks to all the people who supported this project: - Google (through the GSoC) and Theory Studios for sponsoring the development - The authors of the papers I used for implementing the denoiser (more details on them will be included in the technical docs) - The other Cycles devs for feedback on the code, especially Sergey for mentoring the GSoC project and Brecht for the code review! - And of course the users who helped with testing, reported bugs and things that could and/or should work better!
2017-03-27	Cycles: Remove ccl_addr_space from RNG passed to functions	Hristo Gueorguiev
	Simplifies code quite a bit, making it shorter and easier to extend. Currently no functional changes for users, but is required for the upcoming work of shadow catcher support with OpenCL.
2017-03-27	Cycles: First implementation of shadow catcher	Sergey Sharybin
	It uses an idea of accumulating all possible light reachable across the light path (without taking shadow blocked into account) and accumulating total shaded light across the path. Dividing second figure by first one seems to be giving good estimate of the shadow. In fact, to my knowledge, it's something really similar to what is happening in the denoising branch, so we are aligned here which is good. The workflow is following: - Create an object which matches real-life object on which shadow is to be catched. - Create approximate similar material on that object. This is needed to make indirect light properly affecting CG objects in the scene. - Mark object as Shadow Catcher in the Object properties. Ideally, after doing that it will be possible to render the image and simply alpha-over it on top of real footage.
2016-08-25	Fix T49078: Cycles tries to render volume from another render layer when ↵	Sergey Sharybin
	camera is in volume
2016-05-23	Cycles CUDA: reduce stack memory by reusing ShaderData.	Brecht Van Lommel
	57% less for path and 48% less for branched path.
2016-05-22	Cleanup: remove Cycles layer bits checking in the kernel.	Brecht Van Lommel
	At some point the idea was that we could have an optimization where we could render multiple render layers without re-exporting the scene, by just updating the layer bits. We are not doing this now and in practice with the available render layer control like exclude layers it's not always possible anyway. This makes it easier to support an arbitrary number of layers in the future (hopefully this summer), and frees up some useful bits in the kernel. Reviewed By: sergey, dingto Differential Revision: https://developer.blender.org/D2020
2016-01-07	Cycles: Refactor how we pass bounce info to light path node.	Thomas Dinges
	This commit changes the way how we pass bounce information to the Light Path node. Instead of manualy copying the bounces into ShaderData, we now directly pass PathState. This reduces the arguments that we need to pass around and also makes it easier to extend the feature. This commit also exposes the Transmission Bounce Depth to the Light Path node. It works similar to the Transparent Depth Output: Replace a Transmission lightpath after X bounces with another shader, e.g a Diffuse one. This can be used to avoid black surfaces, due to low amount of max bounces. Reviewed by Sergey and Brecht, thanks for some hlp with this. I tested compilation and usage on CPU (SVM and OSL), CUDA, OpenCL Split and Mega kernel. Hopefully this covers all devices. :)
2015-05-09	Cycles: OpenCL kernel split	George Kyriazis
	This commit contains all the work related on the AMD megakernel split work which was mainly done by Varun Sundar, George Kyriazis and Lenny Wang, plus some help from Sergey Sharybin, Martijn Berger, Thomas Dinges and likely someone else which we're forgetting to mention. Currently only AMD cards are enabled for the new split kernel, but it is possible to force split opencl kernel to be used by setting the following environment variable: CYCLES_OPENCL_SPLIT_KERNEL_TEST=1. Not all the features are supported yet, and that being said no motion blur, camera blur, SSS and volumetrics for now. Also transparent shadows are disabled on AMD device because of some compiler bug. This kernel is also only implements regular path tracing and supporting branched one will take a bit. Branched path tracing is exposed to the interface still, which is a bit misleading and will be hidden there soon. More feature will be enabled once they're ported to the split kernel and tested. Neither regular CPU nor CUDA has any difference, they're generating the same exact code, which means no regressions/improvements there. Based on the research paper: https://research.nvidia.com/sites/default/files/publications/laine2013hpg_paper.pdf Here's the documentation: https://docs.google.com/document/d/1LuXW-CV-sVJkQaEGZlMJ86jZ8FmoPfecaMdR-oiWbUY/edit Design discussion of the patch: https://developer.blender.org/T44197 Differential Revision: https://developer.blender.org/D1200
2015-05-08	Cleanup: Remove unused ray type flags.	Thomas Dinges
	They were added for completeness, but it seems we don't need them.
2014-12-25	Cleanup: Fix Cycles Apache header.	Thomas Dinges
	This was already mixed a bit, but the dot belongs there.
2014-09-25	Cycles: Add support for cameras inside volume	Sergey Sharybin
	Basically the title says it all, volume stack initialization now is aware that camera might be inside of the volume. This gives quite noticeable render time regressions in cases camera is in the volume (didn't measure them yet) because this requires quite a few of ray-casting per camera ray in order to check which objects we're inside. Not quite sure if this might be optimized. But the good thing is that we can do quite a good job on detecting whether camera is outside of any of the volumes and in this case there should be no time penalty at all (apart from some extra checks during the sync state). For now we're only doing rather simple AABB checks between the viewplane and volume objects. This could give some false-positives, but this should be good starting point. Need to mention panoramic cameras here, for them it's only check for whether there are volumes in the scene, which would lead to speed regressions even if the camera is outside of the volumes. Would need to figure out proper check for such cameras. There are still quite a few of TODOs in the code, but the patch is good enough to start playing around with it checking whether there are some obvious mistakes somewhere. Currently the feature is only available in the Experimental feature sey, need to solve some of the TODOs and look into making things faster before considering the feature is ready for the official feature set. This would still likely happen in current release cycle. Reviewers: brecht, juicyfruit, dingto Differential Revision: https://developer.blender.org/D794
2014-07-10	Cleanup: Always assign num_samples, there is no need for this special define.	Thomas Dinges

2014-06-22	Fix cycles "Is Singular Ray" being on for Camera rays, now is off.	Brecht Van Lommel
	This appears to be a wrong interpretation of the OSL docs, and it's more convenient to have it off.
2014-05-29	Fix T39804: cycles smoke domain visible in rendering.	Brecht Van Lommel
	Transparent objects could become subtly visible by the different sampling patterns for pixels covered and not covered by the object. It still converged to the right solution but that can take a while. Now we try to use the same sampling pattern here.
2014-03-29	Cycles code refactor: replace magic ~0 values in the code with defines.	Brecht Van Lommel

2014-03-04	Fix volume scatter render issue introduced by recent bugfix.	Brecht Van Lommel

2014-01-09	Fix T38134: missing cycles update when removing world volume scatter shader.	Brecht Van Lommel

2014-01-07	Fix CUDA/OpenCL compile errors in scattering commit.	Brecht Van Lommel

2014-01-07	Cycles Volume Render: scattering support.	Brecht Van Lommel
	This is done by adding a Volume Scatter node. In many cases you will want to add together a Volume Absorption and Volume Scatter node with the same color and density to get the expected results. This should work with branched path tracing, mixing closures, overlapping volumes, etc. However there's still various optimizations needed for sampling. The main missing thing from the volume branch is the equiangular sampling for homogeneous volumes. The heterogeneous scattering code was arranged such that we can use a single stratified random number for distance sampling, which gives less noise than pseudo random numbers for each step. For volumes where the color is textured there still seems to be something off, needs to be investigated.
2014-01-03	Code refactor: move random number and MIS variables into PathState.	Brecht Van Lommel
	This makes it easier to pass this state around, and wraps some common RNG dimension computations in utility functions.
2013-12-30	Cycles Volume Render: heterogeneous (textured) volumes support.	Brecht Van Lommel
	Volumes can now have textured colors and density. There is a Volume Sampling panel in the Render properties with these settings: * Step size: distance between volume shader samples when rendering the volume. Lower values give more accurate and detailed results but also increased render time. * Max steps: maximum number of steps through the volume before giving up, to protect from extremely long render times with big objects or small step sizes. This is much more compute intensive than homogeneous volume, so when you are not using a texture you should enable the Homogeneous Volume option in the material or world for faster rendering. One important missing feature is that Generated texture coordinates are not yet working in volumes, and they are the default coordinates for nearly all texture nodes. So until that works you need to plug in object texture coordinates or a world space position. This is work by "storm", Stuart Broadfoot, Thomas Dinges and myself.
2013-12-28	Cycles Volume Render: add support for overlapping volume objects.	Brecht Van Lommel
	This works pretty much as you would expect, overlapping volume objects gives a more dense volume. What did change is that world volume shaders are now active everywhere, they are no longer excluded inside objects. This may not be desirable and we need to think of better control over this. In some cases you clearly want it to happen, for example if you are rendering a fire in a foggy environment. In other cases like the inside of a house you may not want any fog, but it doesn't seem possible in general for the renderer to automatically determine what is inside or outside of the house. This is implemented using a simple fixed size array of shader/object ID pairs, limited to max 15 overlapping objects. The closures from all shaders are put into a single closure array, exactly the same as if an add shader was used to combine them.
2013-12-28	Cycles Volume Render: support for rendering of homogeneous volume with ↵	Brecht Van Lommel
	absorption. This is the simplest possible volume rendering case, constant density inside the volume and no scattering or emission. My plan is to tweak, verify and commit more volume rendering effects one by one, doing it all at once makes it difficult to verify correctness and track down bugs. Documentation is here: http://wiki.blender.org/index.php/Doc:2.6/Manual/Render/Cycles/Materials/Volume Currently this hooks into path tracing in 3 ways, which should get us pretty far until we add more advanced light sampling. These 3 hooks are repeated in the path tracing, branched path tracing and transparent shadow code: * Determine active volume shader at start of the path * Change active volume shader on transmission through a surface * Light attenuation over line segments between camera, surfaces and background This is work by "storm", Stuart Broadfoot, Thomas Dinges and myself.
2013-11-18	Cycles: change __device and similar qualifiers to ccl_device in kernel code.	Brecht Van Lommel
	This to avoids build conflicts with libc++ on FreeBSD, these __ prefixed values are reserved for compilers. I apologize to anyone who has patches or branches and has to go through the pain of merging this change, it may be easiest to do these same replacements in your code and then apply/merge the patch. Ref T37477.
2013-09-08	Cycles:	Thomas Dinges
	* Refactor PathState struct and functions into its own file.