Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-11-16Fix T56673: Tara.blend from Blender cloud crashes on loadSergey Sharybin
The issue was caused by dependency cycle solver killing relation which was guaranteed various things: i.e. copy-on-write component orders and pose evaluation order (which must first run pose init function). Now it is possible to prevent such relations from being ignored. This is not a complete fix, but is enough to make this specific rig to work. Ideally, we also need to run copy-on-write operation prior to anything else.
2018-09-03Depsgraph: Use more meaningful name for flags storageSergey Sharybin
2018-06-06Cleanup: styleCampbell Barton
2018-03-02Depsgraph: Fix cycle detector to handle closed loopsSergey Sharybin
It was possible to have relations like A -> B -> C -> A (import thing is that no other operations points into this cluster) which were not detected or reported by dependency cycle solver. Now this is solved by ensuring we don't leave unvisited nodes behind.
2018-02-21Depsgraph: Report overall number of cycles detectedSergey Sharybin
Handy to quickly see if a fix fixed any of the cycles in a real rig, or whether it's introduced new ones.
2017-12-21Depsgraph: Fix mistake in previous commitSergey Sharybin
2017-12-21Depsgraph: Remove one of temporary tags in the nodeSergey Sharybin
No real reason to have that, better to free up space for something much more awesome!
2017-06-06Depsgraph: Only use extern "C" when really neededSergey Sharybin
2017-06-01Depsgraph: Cleanup, use DEG_NODE_TYPE prefix for depsgraph node typesSergey Sharybin
2017-05-30Depsgraph: Use own implementation of stack rather than the one from STLSergey Sharybin
This way we always have predictable behavior, especially from the performance point of view. Additionally, if some bottleneck is found in stack implementation it'll be easier for us to address.
2016-11-15Depsgraph: Fix typo in previous optimization commitSergey Sharybin
Was a residue from another experiment, caused infinite loop when reporting dependency cycles.
2016-11-07Despgraph: Optimize cycles detection algorithmSergey Sharybin
The idea is simple: when falling back to one of the nodes which was partially handled we "resume" checking outgoing relations from the index which we stopped. This gives about 15-20% depsgraph construction time save.
2016-05-27Depsgraph: Cleanup and code simplificationSergey Sharybin
This is mainly a maintenance commit which was aimed to make work with this module more pleasant and solve such issues as: - Annoyance with looong files, which had craftload in them - Usage of STL for the data structures we've got in BLI - Possible symbol conflicts - Not real clear layout of what is located where So in this commit the following changes are done: - STL is prohibited, it's not really predictable on various compilers, with our BLI algorithms we can predict things much better. There are still few usages of std::vector, but that we'll be solving later once we've got similar thing in BLI. - Simplify foreach loops, avoid using const_iterator all over the place. - New directory layout, which is hopefully easier to follow. - Some files were split, some of them will be split soon. The idea of this is to split huge functions into own files with good documentation and everything. - Removed stuff which was planned for use in the future but was never finished, tested or anything. Let's wipe it out for now, and bring back once we really start using it, so it'll be more clear if it solves our needs. - All the internal routines were moved to DEG namespace to separate them better from rest of blender. Some places now annoyingly using DEG::foo, but that we can olve by moving some utility functions inside of the namespace. While working on this we've found some hotspot in updates flush, so now playback of blenrig is few percent faster (something like 96fps with previous master and around 99-100fps after this change). Not saying it's something final, there is still room for cleanup and API simplification, but those might happen as a regular development now without doing any global changes.