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

Age	Commit message (Collapse)	Author
2021-09-23	Fix T91641: crash rendering with 16k environment map in Cycles	Brecht Van Lommel
	Protect against integer overflow.
2021-09-21	Cycles: merge of cycles-x branch, a major update to the renderer	Brecht Van Lommel
	This includes much improved GPU rendering performance, viewport interactivity, new shadow catcher, revamped sampling settings, subsurface scattering anisotropy, new GPU volume sampling, improved PMJ sampling pattern, and more. Some features have also been removed or changed, breaking backwards compatibility. Including the removal of the OpenCL backend, for which alternatives are under development. Release notes and code docs: https://wiki.blender.org/wiki/Reference/Release_Notes/3.0/Cycles https://wiki.blender.org/wiki/Source/Render/Cycles Credits: * Sergey Sharybin * Brecht Van Lommel * Patrick Mours (OptiX backend) * Christophe Hery (subsurface scattering anisotropy) * William Leeson (PMJ sampling pattern) * Alaska (various fixes and tweaks) * Thomas Dinges (various fixes) For the full commit history, see the cycles-x branch. This squashes together all the changes since intermediate changes would often fail building or tests. Ref T87839, T87837, T87836 Fixes T90734, T89353, T80267, T80267, T77185, T69800
2021-05-19	Fix T87793: Cycles OptiX crash hiding objects in viewport render	Brecht Van Lommel

2020-10-05	Cycles: Add NanoVDB support for rendering volumes	Patrick Mours
	NanoVDB is a platform-independent sparse volume data structure that makes it possible to use OpenVDB volumes on the GPU. This patch uses it for volume rendering in Cycles, replacing the previous usage of dense 3D textures. Since it has a big impact on memory usage and performance and changes the OpenVDB branch used for the rest of Blender as well, this is not enabled by default yet, which will happen only after 2.82 was branched off. To enable it, build both dependencies and Blender itself with the "WITH_NANOVDB" CMake option. Reviewed By: brecht Differential Revision: https://developer.blender.org/D8794
2020-06-08	Cycles: Add support for P2P memory distribution (e.g. via NVLink)	Patrick Mours
	This change modifies the multi-device implementation to support memory distribution across devices, to reduce the overall memory footprint of large scenes and allow scenes to fit entirely into combined GPU memory that previously had to fall back to host memory. Reviewed By: brecht Differential Revision: https://developer.blender.org/D7426
2020-03-19	Cleanup: `make format` after SortedIncludes change	Dalai Felinto

2020-03-12	Fix memory leak in recent Cycles image texture refactor	Brecht Van Lommel

2020-03-12	Cleanup: add device_texture for images, distinct from other global memory	Brecht Van Lommel
	There was too much image texture specific stuff in device_memory, and too much code duplication between devices.
2020-03-11	Cleanup: stop encoding image data type in slot index	Brecht Van Lommel
	This is legacy code from when we had a fixed number of textures.
2019-12-09	Cycles: Add OptiX acceleration structure compaction	Patrick Mours
	This adds compaction support for OptiX acceleration structures, which reduces the device memory footprint in a post step after building. Depending on the scene this can reduce the amount of used device memory quite a bit and even improve performance (smaller acceleration structure improves cache usage). It's only enabled for background renders to make acceleration structure builds fast in viewport. Also fixes a bug in the memory management for OptiX acceleration structures: These were held in a dynamic vector of 'device_memory' instances and used the mem_alloc/mem_free functions. However, those keep track of memory instances in the 'cuda_mem_map' via pointers to 'device_memory' (which works fine everywhere else since those are never copied/moved). But in the case of the vector, it may decide to reallocate at some point, which invalidates those pointers and would result in some nasty accesses to invalid memory. So it is not actually safe to move a 'device_memory' object and therefore this removes the move operator overloads again. Reviewed By: brecht Differential Revision: https://developer.blender.org/D6369
2019-11-05	Fix T71071: errors when using multiple CUDA/Optix GPUs and host mapped memory	Ha Hyung-jin
	The multi device code did not correctly handle cases where some GPUs store a resource in device memory and others store it in host mapped memory. Differential Revision: https://developer.blender.org/D6126
2019-08-26	Cycles: support move semantics for device_memory	Patrick Mours
	Ref D5363
2019-04-17	ClangFormat: apply to source, most of intern	Campbell Barton
	Apply clang format as proposed in T53211. For details on usage and instructions for migrating branches without conflicts, see: https://wiki.blender.org/wiki/Tools/ClangFormat
2018-07-06	Cleanup: strip trailing space for cycles	Campbell Barton

2018-07-04	Cycles Denoising: Correctly handle target buffer in tile unmapping and move ↵	Lukas Stockner
	device swap logic to the device_memory
2018-01-19	Fix T53830: Cycles OpenCL debug assert on macOS,	Brecht Van Lommel
	This was probably harmless besides some unnecessary memory usage due to aligning allocations too much.
2018-01-03	Cycles: CUDA support for rendering scenes that don't fit on GPU.	Brecht Van Lommel
	In that case it can now fall back to CPU memory, at the cost of reduced performance. For scenes that fit in GPU memory, this commit should not cause any noticeable slowdowns. We don't use all physical system RAM, since that can cause OS instability. We leave at least half of system RAM or 4GB to other software, whichever is smaller. For image textures in host memory, performance was maybe 20-30% slower in our tests (although this is highly hardware and scene dependent). Once other type of data doesn't fit on the GPU, performance can be e.g. 10x slower, and at that point it's probably better to just render on the CPU. Differential Revision: https://developer.blender.org/D2056
2018-01-03	Cycles: make CUDA code a bit more robust to host/device alloc failures.	Brecht Van Lommel
	Fixes a few corner cases found while stress testing host mapped memory.
2017-11-05	Code refactor: device memory cleanups, preparing for mapped host memory.	Brecht Van Lommel

2017-10-25	Code refactor: remove MEM_WRITE_ONLY, always use MEM_READ_WRITE.	Brecht Van Lommel
	It's unlikely the driver can do useful optimizations with this, and if we sum multiple samples we are reading from the memory anyway.
2017-10-24	Code refactor: move more memory allocation logic into device API.	Brecht Van Lommel
	* Remove tex_* and pixels_* functions, replace by mem_. Add MEM_TEXTURE and MEM_PIXELS as memory types recognized by devices. * No longer create device_memory and call mem_* directly, always go through device_only_memory, device_vector and device_pixels.
2017-10-24	Code refactor: store device/interp/extension/type in each device_memory.	Brecht Van Lommel