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
2012-08-23Fix #32389: scons was compiling without iksolver and only itasc since a few ↵Brecht Van Lommel
days, which gave performance issues.
2012-08-18cmake option to build without iksolverCampbell Barton
2012-07-29Fix compile error, IK_STRETCH_STIFF_EPS was undefined. Thomas Dinges
2012-07-29code cleanup:Campbell Barton
- building without python works again - rename maxi/mini to i_max/i_min (so thay are available for function names) - some minor edits to IK stretch setting (no functional changes).
2012-07-29code cleanup: replace MIN2/MAX2 with minf/maxfCampbell Barton
2012-07-28defines to make it easier to manage ik stretch constants (these may need to ↵Campbell Barton
be tweaked to fix [#32174])
2012-07-11code cleanup: use const for passing vectorsCampbell Barton
2012-07-08style cleanupCampbell Barton
2012-07-03More spell and typo fixes (mostly visualise->visualize, grey->gray, ↵Bastien Montagne
normalise->normalize).
2012-07-01style cleanupCampbell Barton
2012-06-07Fix [#31430] part 2: crash in iTaSC when end effector is a fixed bone. This ↵Benoit Bolsee
situation was causing access to invalid index in the joint angle array although the end effector doesn't need any joint angle to compute its pause. Fixed this by changing the internal API of joint array: return pointer instead of reference so that NULL pointer can be returned instead of crashing when the index is invalid.
2012-06-07Fix unaligned array crash in Eigen3 because of compilation option. The ↵Benoit Bolsee
EIGEN_DONT_ALIGN_STATICALLY compilation option was added for Win32 only in revision 41283 because of some compilation problem. But this option is causing alignment problem for Eigen3 local variables when SSE optimization is enabled. I do not have any compilation problem when the option is not defined, so I just remove it as it should.
2012-06-03Fix bug [#31588]: iTaSC does not handle armature scaling correctly. iTaSC ↵Benoit Bolsee
solver operates in world reference, therefore armature scale is used to build the ik scene. But the scaling was not taken out when applying the pose at the end of the simulation.
2012-05-25style cleanupCampbell Barton
2012-05-18Fix #31430: itasc solver assertion failure with debug builds.Brecht Van Lommel
2012-05-05code cleanup: naming - pose/armature/image Campbell Barton
also use ..._find_name(..., name) rather then ..._find_named(..., name) --- both were used.
2012-04-29style cleanup: whitespace / commasCampbell Barton
2012-04-28style cleanup: changes to brace placement / newlines - for/while/if/switchCampbell Barton
2012-04-20Fix [#31008] IK armature resize goes ugly (Pose mode resize).Bastien Montagne
This affected legacy solver. Note that even if I don't expect any, this fix *may* break some other IK setups, so animators, please check your IK rigs using legacy solver. ;) Easy to revert if needed, anyway. Note that iTaSC solver is also buggy with some scaled parent, but here IK'ed bones just can’t get scaled in any way (either from parent or from there own transformation)... Will try to find what's happenning, though the code is even harder than legacy solver to follow :/
2012-03-28style cleanupCampbell Barton
2012-03-24style cleanup: follow style guide for/with/if spacingCampbell Barton
2012-03-24style cleanup: pep8, indentationCampbell Barton
2012-03-24style cleanup: follow style guide for formatting of if/for/while loops, and ↵Campbell Barton
else if's
2012-03-09style cleanup: comment blocksCampbell Barton
2012-03-02style cleanupCampbell Barton
- spelling - turns out we had tessellation spelt wrong all over. - use \directive for doxy (not @directive) - remove BLI_sparsemap.h - was from bmesh merge IIRC but entire file commented and not used.
2012-02-28patch [#30331] Support clang-3.0Campbell Barton
from Yasuhiro Fujii (y-fujii) only small part of the patch for now.
2012-02-27style cleanup (mostly whitespace)Campbell Barton
2012-02-17unify include guard defines, __$FILENAME__Campbell Barton
without the underscores these clogged up the namespace for autocompleation which was annoying.
2011-12-16Math lib: matrix multiplication order fix for two functions that wereBrecht Van Lommel
inconsistent with similar functions & math notation: mul_m4_m4m4(R, B, A) => mult_m4_m4m4(R, A, B) mul_m3_m3m4(R, B, A) => mult_m3_m3m4(R, A, B) For branch maintainers, it should be relatively simple to fix things manually, it's also possible run this script after merging to do automatic replacement: http://www.pasteall.org/27459/python
2011-11-13Fix #29041: parenting problem with tree IK for iTaSC and iksolver, where itBrecht Van Lommel
would use the wrong bone as parent on brancing. Patch by Juha Maki-Kanto.
2011-11-11quiet -Wdouble-promotion warningsCampbell Barton
2011-11-07Bugfix [#29064] armature with curve contraint - crashJoshua Leung
Spline IK and Auto-IK working together on the same bone chain could crash due to the somewhat hacky way that they were sharing the same list for the "iktree" forest. Resolved by doing what I should have done from the beginning, and made Spline-IK save its ik chains off into a separate list. While this fixes the crash, it might be worth investigating outright disabling this from working in this case, since it can be a bit confusing to have it appear to not work.
2011-11-07replace VECCOPY with copy_v3_v3, same for 2d copy, also added vec copy ↵Campbell Barton
functions for int & char.
2011-10-25Fix compilation error for win32.Sergey Sharybin
That static align trick i've wrote about is still necessary.
2011-10-25Libraries upgrade:Sergey Sharybin
- Upgrade Eigen2 library to Eigen3 - Upgrade colamd library and placed in extern/ so other libraries from extern/ can use it NOTE: With previous version of Eigen (3.0.1) it was necessary to define EIGEN_DONT_ALIGN_STATICALLY macro to make it compilable on windows 32bit. After latest upgrade it seems to be unnecessary (at least when was testing libmv), so i removed that defines which can reduce speed and lead to other problems.
2011-10-23remove $Id: tags after discussion on the mailign list: ↵Campbell Barton
http://markmail.org/message/fp7ozcywxum3ar7n
2011-07-17cmake: cleanup include paths, some duplicates and going up some unneeded dirs.Campbell Barton
2011-05-31cmake maintenanceCampbell Barton
blender_add_lib now takes a separate include argument to suppress warnings in system includes (mostly ffmpeg & python). also only build wm_apple.c on apple+carbon configuration.
2011-03-27clear some c++ warnings.Campbell Barton
2011-03-03replace 0 with NULL when used as a pointerCampbell Barton
2011-02-27doxygen: blender/ikplugin tagged.Nathan Letwory
2011-02-23doxygen: prevent GPL license block from being parsed as doxygen comment.Nathan Letwory
2011-01-30remove nan-makefilesCampbell Barton
2011-01-07remove references to BKE_utildefines where its not needed.Campbell Barton
- move GS() define into DNA_ID.h - add BLI_utildefines as an automatic include with makesrna generated files.
2011-01-07split BKE_utildefines.h, now it only has blender specific defines like GS() ↵Campbell Barton
MAKE_ID, FILE_MAXDIR, moved the generic defines to BLI_utildefines.h. no functional changes.
2010-12-23rename blenderlib to blender_add_libCampbell Barton
2010-12-08use lowercase for cmake builtin names and macros, remove contents in else() ↵Campbell Barton
and endif() which is no longer needed.
2010-11-29include headers in cmake source, added a script to check for consistency, ↵Campbell Barton
reporting missing headers & C files. this is important so IDE's using CMake integration always get blender headers. - QtCreator & MSVC for eg, probably others too.
2010-10-27remove include paths which dont exist, fix for doc upload script which was ↵Campbell Barton
getting the blender version twice and not working sometimes.
2010-10-23use explicit file paths for CMake rather then globing, This is recommended ↵Campbell Barton
by cmake devs. globbing vs explicit is discussed here. http://www.cmake.org/pipermail/cmake/2008-December/025694.html Practical implications are: - developers need to keep CMakeLists.txt files up to date. - Users wont get strange linking errors if they build after a file is added, since CMake detects CMakeLists.txt is modified and automatically reconfigure.