February 14, 2015, 21:55 (GMT) |
Cycles: Fix wrong attribute count calculation in prevous commit The workaround for generated texture coordinates is to be done before calculating number of elements for attribute, otherwise counter wouldn't include those attributes. |
February 14, 2015, 21:01 (GMT) |
Cycles: Optimize memory usage when creating mesh attributes The idea behind the change is to pre-allocate attribute arrays in advance, which avoids re-allocation of arrays later for each of meshes being handled. This reduces peak memory used by Cycles database from 1.3G to 0.9G for victor.blend from Gooseberry. It doesn't mean every file will benefit from this change since peak memory usage is happening in the different places of the rendering code. Also, unfortunately, attributes export might not cause the peak of render preparation stage. That said, it's actually object_to_mesh() which causes the memory to peak in the same test file. So we really need to optimize that part first in order to get visible results for artists. But in any case it's now quite easy to track hotspots in Cycles itself which is good. |
February 14, 2015, 21:01 (GMT) |
Cycles: Add ifdef switch to use blender's guardedalloc for vector allocation It's actually a bad level call, but it's inside ifdef block and disabled by default and only intended to be used for development purposes. Main idea of this change is to combine statistics coming from Cycles and Blender during scene synchronization step, to see if further changes are actually reducing memory footprint. |
February 14, 2015, 21:01 (GMT) |
Cycles: Add utility method to vector which totally frees memory used the vector The method is called vector::free_memory(). Use with care since it'll invalidate all the pointers to vector memory, all iterators and so on. Currently unused, but might become handy when clearing unused data. |
February 14, 2015, 21:01 (GMT) |
Cycles: Report system memory usage and peak after scene device update This only happens when built with WITH_CYCLES_DEBUG flag, memory statistics is coming from guarded STL allocator. |
February 14, 2015, 21:01 (GMT) |
Cycles: Implement guarded allocator for STL classes The commit implements a guarded allocator which can be used by STL classes such as vectors, maps and so on. This allocator will keep track of current and peak memory usage which then can be queried. New code for allocator is only active when building Cycles with debug flag (WITH_CYCLES_DEBUG) and doesn't distort regular builds too much. Additionally now we're using own subclass of std::vector which allows us to implement shrink_to_fit() method which would ensure capacity of the vector is as big as it should be (without this making vector smaller will still use all previous memory allocated). |
February 14, 2015, 21:01 (GMT) |
Cycles: Replace own aligned allocator with system one This replaces our own implementation of aligned malloc with system calls, which depends on which operation system you're on. This is probably really minor noticeable change, but in the same time it might reduce amount of wasted memory. |
February 14, 2015, 20:54 (GMT) |
Outliner: Toggle restrict buttons only for selectable child objects D404 by @rupp with minor edits by me. |
February 14, 2015, 19:57 (GMT) |
Cleanup: Comment block for sse helpers. |
February 14, 2015, 19:44 (GMT) |
Cycles: Small improvement for volume render (decoupled) Simplify branching here a bit, helps ~3% in volume_light_sampling.blend (Branched MIS scene). |
February 14, 2015, 16:33 (GMT) |
Cycles: Fix compilation error of Cycles standalone with Libmv disabled |
February 14, 2015, 15:40 (GMT) |
Revert "Fix T43471, based on patch submitted by @sean_loh." This reverts commit b2b54b0902045ec4f0c1a4cae3209be863878f5b. The patch breaks particle distribution even in simple cases, not worth doing this for keeping a hackish loophole open. |
February 14, 2015, 11:29 (GMT) |
object drawing: only use halo-draw in object mode |
February 14, 2015, 11:06 (GMT) |
Bring copy/free operations into line with changes in previous commit |
February 14, 2015, 11:06 (GMT) |
Bugfix: Referencing actions from Action Actuator was not setting a user This reverts the change made in 8872cba7e956a9d9a840e55e5323945497524795 which was contributing to actions being lost in some cases [1], even when they were assigned to those actuaters, which needed them to be able to function. Now there's one less case where users are needed but were missing :) Note that this still doesn't solve the core issue where nothing is responsible for associating actions created for a particular datablock (and not currently being used in its active action slot, or in the NLA stack) with that datablock. That issue is the cause of most action disappearances as well as for other problems (such as renaming bones being unable to fix unreferenced/unused actions) where there are diifferences between users' mental models and the data model. Proper fixes are coming soon (restoring fake users here isn't a proper fix, as it only masks the fundamental mismatch/problem here). [1] http://blenderartists.org/forum/showthread.php?357021-BGE-loses-actions |
February 14, 2015, 10:13 (GMT) |
CMake: Enable JeMalloc by default It's really handy to have blender linked against jemalloc because of much better memory fragmentation handling by that library. To be noted: if jemalloc library is not found it'll be disabled with message about that, no compilation error should happen. |
February 14, 2015, 07:29 (GMT) |
CMake: Add search path for jemalloc which corresponds to own and studio setup |
February 13, 2015, 21:28 (GMT) |
Rework job multi-level listing - factorize even more and avoid recursion. This is much cleaner than previous code... |
February 13, 2015, 21:00 (GMT) |
Refactor array_utils out of BLI_array BLI_array.h is for resizing array macros, where as array_utils can operate on any arrays. |
February 13, 2015, 21:00 (GMT) |
cleanup: doxy comments |
|
|
|


Master Commits
MiikaHweb | 2003-2021