| Age | Commit message (Collapse) | Author |
|---|
|
extra-face bug
|
|
|
|
|
|
|
|
replaces inline code.
BLI_array_fixedstack_declare()
BLI_array_fixedstack_free()
|
|
confusion
This is the first step in a few changes to cleanup confusing/missing DM funcs
|
|
- renamed BM_Compute_Face_Center() to BM_Compute_Face_CenterBounds() and added BM_Compute_Face_CenterMean() since there was code inline to find the mean center in transform.
|
|
each quad would result in 2 duplis.
|
|
The ratios were only being maintained between the altered weights when they were redistributed,
and the resulting weights did not fully respect the locks--now they do.
|
|
|
|
changes
|
|
(rectangle patterns are getting enlarged to square like it's happening for KLT)
|
|
the switch statement when BMIter_New() is called with the define (which is common).
|
|
also added inline iterator file (not yet used)
|
|
one day before release, and good incitation to finish 2.5/6 index before release!
|
|
edges/faces/verts if its not needed, but if set wrong it could crash too so added verification when built with debeg.
also added debug define to help solve invalid values with valgrind's memcheck.
gives noticeable speedup since there was a loop no all faces to set index values on redraw.
|
|
looped over anyway.
|
|
|
|
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
|
|
|
|
|
|
|
|
mesh_foreachScreenVert, mesh_foreachScreenEdge since it wasnt clear how the values are used.
also resolved use of un-initialized variable.
|
|
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.
|
|
|
|
Also setting better default values in WeightVGProximity modifier
|
|
|
|
worked by accident before, because of flags that weren't cleared properly. Now
moved the call to update render engines into scene_update_* itself.
|
|
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.
|
|
|
|
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/
|
|
|
|
|
|
Found by Campbell Barton, thanks.
|
|
|
|
now there very close, some hard to redo cases to check on.
|
|
- comment BM_SetIndex as setting dirty.
- have alloc_flag_layer validate the index data and clear the dirty flag since it loops on the data anyway.
|
|
BLI version of strdup().
|
|
modifier since it calls out to the bevel operator.
- edge angles are ok
- width is interpreted as percent
added BMESH_TODO comments with details about what needs working on.
|
|
angles, rather then looping over all faces and looking at every faces-edges-fance which would compare faces twice.
|
|
|
|
length comparison can be done without sqrt for baking.
|
|
|
|
mistake)
so make into a function: BM_Edge_Share_Vert()
|
|
|
|
|
|
- curve map insert point had a nested loop which used the same value to index different arrays.
- dynamic paint used ternary operator where both outcomes were the same.
|
|
|
|
iterator for now.
|
|
track on mouse selection operator.
|
