Revision a3a4386 by Campbell Barton July 11, 2013, 15:57 (GMT) |
fix [#36105] Bevel UV Flicker interp_weights_poly_v2/3 functions used much too small an epsilon value, caused flickering. |
Revision e6b22d2 by Campbell Barton July 11, 2013, 15:32 (GMT) |
utility function for printing arbitrary sizes vectors. |
Revision c098557 by Campbell Barton July 11, 2013, 14:21 (GMT) |
fix [#36100] bevel lost selection interpolating loop was copying face attributes including selection, checked all users of this function and its safe to remove the call (which is bad to begin with). |
Revision b2a0255 by Howard Trickey July 11, 2013, 13:29 (GMT) |
Fix bevel when there is a gap in faces around vertex. Fixes bug #35927 (Vertex Bevel bug) but even edge bevel didn't work on the example there. Problem was with forming the proper ccw ordering of edges around the bevel. Also appears to fix bug #35582 (Bevel, weird results). |
Revision 48c8d99 by Campbell Barton July 11, 2013, 12:43 (GMT) |
add BM_elem_attrs_copy_ex() which can take a flag arg to define which flags should be copied. (mainly to be able to avoid copying selection/hidden state) |
Revision e64937c by Brecht Van Lommel July 11, 2013, 12:22 (GMT) |
Fix #36091: external render engines like Luxrender don't work well with the save buffers option, it requires specific tile sizes and if they don't match what OpenEXR expects file saving can get stuck. Now I've made support for his optional, with a bl_use_save_buffers property for RenderEngine, set to False by default. |
Revision aa2a243 by Campbell Barton July 11, 2013, 11:38 (GMT) |
fix [#36099] Undo crashes on an armature with ID-Properties armatures undo state now stores ID-properties. |
Revision 9aade87 by Sergey Sharybin July 11, 2013, 11:29 (GMT) |
Code cleanup: de-duplicate display list minmax routines |
Revision 0a24b44 by Sergey Sharybin July 11, 2013, 11:05 (GMT) |
Added an operator to match texture space to object's bounding box This operator could be useful after recent changes to how curve's texture space is calculated. |
Revision 7d8b132 by Sergey Sharybin July 11, 2013, 10:45 (GMT) |
Move curve's boundbox and texspace calculation out of modifier stack There were several issues with how bounding box and texture space are calculated: - This was done at the same time as applying modifiers, meaning if several objects are sharing the same curve datablock, bounding box and texture space will be calculated multiple times. Further, allocating bounding box wasn't safe for threading. - Bounding box and texture space were evaluated after pre-tessellation modifiers are applied. This means Curve-level data is actually depends on object data, and it's really bad because different objects could have different modifiers and this leads to conflicts (curve's data depends on object evaluation order) and doesn't behave in a predictable way. This commit moves bounding box and texture space evaluation from modifier stack to own utility functions, just like it's was done for meshes. This makes curve objects update thread-safe, but gives some limitations as well. Namely, with such approach it's not so clear how to preserve the same behavior of texture space: before this change texture space and bounding box would match bevelled curve as accurate as possible. Old behavior was nice for quick texturing -- in most cases you don;t need to modify texture space at all. But texture space was depending on render/preview settings which could easily lead to situations, when final result would be far different from preview one. Now we're using CV points coordinates and their radius to approximate the bounding box. This doesn't give the same exact texture space, but it helps a lot keeping texture space in a nice predictable way. We could make approximation smarter in the future or add operator like "match texture space to object's bounding box". |
Revision 683db78 by Sergey Sharybin July 11, 2013, 09:15 (GMT) |
Make fonts safe(r) for threading Getting vfont data wasn't safe for threading, because it was modifying font data which is in bmain and could be shared by multiple objects. For now made it so getting vfont uses critical section, meaning vfont->data is initializing from inside a locked mutex. |
Revision 13e3352 by Campbell Barton July 11, 2013, 08:37 (GMT) |
fix for bridge tool where the 2 loops overlap (typical use for scanfill), however its nice to support with bridge too since it can do subdivisions, handles customdata and fills in quads. |
Revision ac0638f by Sergey Sharybin July 11, 2013, 08:25 (GMT) |
Revision 991459d by Campbell Barton July 11, 2013, 05:11 (GMT) |
fix [#36090] Blender displays strange symbol in edge length |
Revision b035ce3 by Campbell Barton July 11, 2013, 04:38 (GMT) |
fix [#36089] crash when using a tiff without TIFFTAG_EXTRASAMPLES |
Revision 7fec23a by Campbell Barton July 11, 2013, 04:24 (GMT) |
fix for problem with edge slide where it would stop shapekey modifier from being applied (because of added vertices), now, instead of making hidden copies of faces, the faces are copied into a temp bmesh. also remove a hash that was being created and not used (old code). |
Revision b36999b by Campbell Barton July 11, 2013, 01:28 (GMT) |
bm_loop_interp_mdisps was doing multiple lookups in the same pointer in a nested loop. only need one, also avoid multiple layer lookups with mdisp calculation/smoothing |
Revision 3a89f98 by Brecht Van Lommel July 10, 2013, 17:25 (GMT) |
Fix #36053: slow GPU render with panorama camera + depth of field. |
Revision 990cad9 by Brecht Van Lommel July 10, 2013, 16:46 (GMT) |
Fix #36082: animation playback not working after rendering of background scenes and multiple render layer nodes. Also fixes issue with database free with vector blur after recent thread safety changes. |
Revision e3a604b by Sergey Sharybin July 10, 2013, 14:26 (GMT) |
Tag object-data level boundbox as invalid rather than freeing it Object update used to free object-data level bounding box to trigger it's re-calculation in the future. Such a freeing performed from object update isn't thread-safe because mesh could be shared between multiple objects. Rather than freeing bounding box, tag it's as invalid, this is safe from threading point of view and also prevents unnecessary memory re-allocation. Object-level bounding box is still reallocating, but think we could change this easily in the future as well. |
|
|
|


Master Commits
MiikaHweb | 2003-2021