Revision 40d6765 by Campbell Barton November 28, 2011, 18:43 (GMT) |
validate the index values when an operator finishes since the arrays are looped over anyway. |
Revision 79ffbe9 by Campbell Barton November 28, 2011, 18:21 (GMT) |
fix for error filling in index data |
Revision 3ff8ff9 by Sergey Sharybin November 28, 2011, 17:55 (GMT) |
Reset V3D_RENDER_SHADOW flag on file loading. This flag shouldn't be saved in .blend files but because of strange reason some files contains this flags which leads to object disappearing when disabling buffer shadow in material. Current trunk shouldn't be saving this flag and most probably buggy files were saved in some intermediate version of blender where this flag can be be saved. This should fix remained issue in #29255: Object invisible and weird polygons appearance |
Revision 9aaa67c by Campbell Barton November 28, 2011, 17:19 (GMT) |
corrections for docs |
Revision f641895 by Thomas Dinges November 28, 2011, 17:10 (GMT) |
* Never, ever use "col2" or something like that as UI variable name. |
Revision 063dd4f by Campbell Barton November 28, 2011, 17:09 (GMT) |
svn merge ^/trunk/blender -r42197:42221 |
Revision c126bfb by Campbell Barton November 28, 2011, 16:44 (GMT) |
view3d - replace magic numbers with an enum to be used with mesh_foreachScreenVert, mesh_foreachScreenEdge since it wasnt clear how the values are used. also resolved use of un-initialized variable. |
Revision 9c156c5 by Sergey Sharybin November 28, 2011, 16:25 (GMT) |
Fix #29434: Cone collision bounds is on the wrong axis Because of strange reason, cone boundbox was rotated and it wasn't reflecting physics engine which used "correct" cone boundbox. Changed displaying of cone bounding box type. |
Revision 0b5ba70 by Sergey Sharybin November 28, 2011, 16:10 (GMT) |
Rename tracking settings presets to something which makes more sense. |
Revision 424acd9 by Bastien Montagne November 28, 2011, 15:41 (GMT) |
Fixes and tweaks to RNA messages (found while translating in french). Also setting better default values in WeightVGProximity modifier |
Revision 173b956 by Campbell Barton November 28, 2011, 15:31 (GMT) |
fix for missing NULL check in remove doubles. |
Revision 7baaa08 by Brecht Van Lommel November 28, 2011, 14:55 (GMT) |
Fix #29389: cycles viewport render not updating on frame changes. This sort of worked by accident before, because of flags that weren't cleared properly. Now moved the call to update render engines into scene_update_* itself. |
Revision 9f3c921 by Sergey Sharybin November 28, 2011, 13:49 (GMT) |
Camera tracking: moved camera solver into it's own job In some cases solving can take a while (especially when refining is used) and keeping interface locked is a bit annoying. Now camera solver is moved to job system and interface isn't locking. Reporting progress isn't really accurate, but trying to make it more linear can lead to spending more effort on it than having benefit. Also, changing status in the information line helps to understand that blender isn't hang up and solving is till working nicely. Main changes in code: - libmv_solveReconstruction now accepts additional parameters: * progress_update_callback - a function which is getting called from solver algorithm to report progress back to Blender. * callback_customdata - a user-defined context which is passing to progress_update_callback so progress can be updated in needed blender-side data structures. This parameters are optional. - Added structure MovieTrackingStats which is placed in MovieTracking structure. It's supposed to be used for displaying information about different operations (currently it's only camera solver, but can be easily used for something else in the future) in clip editor. This statistics structure is getting allocated for time operator is working and not saving into .blend file. - Clip Editor now displays statistics stored in MovieTrackingStats structure like it's done for rendering. |
Revision 24cc4a6 by Sergey Sharybin November 28, 2011, 13:27 (GMT) |
Camera tracking: missed this presets files in previous commit |
Revision a3623a0 by Sergey Sharybin November 28, 2011, 13:26 (GMT) |
Camera tracking: merging tracking presets stuff from tomato branch This commit implements: - Configurable settings for newly creating tracks Now it's possible to set tracking algorithm and it's settings for all newly creating tracks including manual tracks creation and tracks creation by "Detect Features" operator. - Moves margin, frames limit and adjust frame inside per-track settings. Was request from Francois for this. - Adjust Frames replaced with menu called Pattern Match where it's possible to choose between matching pattern from keyframe frame or from previously tracked frame. Didn't see somebody used adjust frames values differ from 0 and 1, and this menu should make things more clear here/ |
Revision 48c5820 by Sergey Sharybin November 28, 2011, 13:08 (GMT) |
Camera tracking: move margin, frames limit and adjust frames to per-track settings Also replace adjust frames integer slider with menu to choose between matching pattern from keyframe position of from previous frame. think this settings wouldn't be so confusing now. |
Revision e73176d by Andrew Wiggin November 28, 2011, 10:57 (GMT) |
fix for [#29437] normals incorrect using bevel modifier in edit mode |
Revision 911be02 by Antonis Ryakiotakis November 28, 2011, 08:38 (GMT) |
remove duplicate extern_colamd from blenderplayer cmake |
Revision f1538cf by Sergey Sharybin November 28, 2011, 07:18 (GMT) |
Fix typo in track selection operator. Found by Campbell Barton, thanks. |
Revision 2e4d122 by Campbell Barton November 28, 2011, 07:02 (GMT) |
fix for building as a python module |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021