February 24, 2017, 23:27 (GMT) |
Little utility macros getter/setter compiler hints |
February 24, 2017, 23:07 (GMT) |
Add WorkSpaceHook struct as bridge between workspace and window-manager This way we can keep workspace and window-manager data separate and further steps are made a bit easier. |
February 24, 2017, 21:14 (GMT) |
Cleanup Change name and organize position of functions |
February 24, 2017, 20:33 (GMT) |
February 24, 2017, 20:19 (GMT) |
February 24, 2017, 18:47 (GMT) |
Simplification and comments |
February 24, 2017, 18:10 (GMT) |
`dm->release(dm)` accidentally removed I do not know if this call is really necessary, but in doubt I'll leave it as it is |
February 24, 2017, 17:21 (GMT) |
Merge branch 'snap_system_clip_planes' of git@git.blender.org:blender.git into snap_system_clip_planes # Conflicts: # source/blender/editors/transform/transform_snap_object.c |
February 24, 2017, 17:14 (GMT) |
Fix crash due to dereferenced array od edges and clean debug printfs |
February 24, 2017, 15:48 (GMT) |
Fix fix for realloc! |
February 24, 2017, 15:47 (GMT) |
Fix building on linux (gcc). |
February 24, 2017, 15:46 (GMT) |
Fix MEM_reallocN use |
February 24, 2017, 15:40 (GMT) |
Innitial commit: Snap system - Adds Clip Plan support and simulates occlusion The main alterations here were made in the transform_snap_object.c file. The main change add the "clip plans" of the `rv3d->clip` to bypass the snap to unseen elements. This solution continues to take advantage of the BVH. Since we can use clip planes, we can now simulate occlusion (ie ignore what is behind a face), first a raycast is made to get the normal and coordinates of the polygon of the hit. Then a plane is created just behind the polygon, thus ignoring everything that is behind it when a snap is made for vertex or edge. This is not the ideal occlusion solution, but it is already a good step to get the perfect occlusion test. In addition to this change other changes were made: Now snap_to is a flag that can indicate whether the snap is made for one, two or all elements at the same time (this will not change much for the user, the only operator using mixed snap is the ruler) ; if the object is in wireframe mode or Bounding Box, they are ignored in snap to face (good idea?); use the BVHTree of looptris to snap vertices and edges (saves memory); |
Revision bc0208f by Sybren A. Stüvel February 24, 2017, 15:35 (GMT) |
Alembic: simplified conditional statements |
Revision fe9c8be by Sybren A. Stüvel February 24, 2017, 15:35 (GMT) |
Alembic import: nicer progress updates |
Revision df4feb3 by Sybren A. Stüvel February 24, 2017, 15:35 (GMT) |
Alembic import: fixed bug where local matrix from Alembic was used as object matrix Also renamed AbcObjectReader::readObjectMatrix to setupObjectTransform, as it does more than just reading the object matrix; it also sets up an object constraint if the Alembic Xform is animated. |
Revision 75597c0 by Sybren A. Stüvel February 24, 2017, 15:35 (GMT) |
Alembic import: separated reading matrix and getting the appropriate Xform object Also added a bit better error reporting, instead of silently ignoring invalid Alembic data. |
Revision 9bf69ab by Sybren A. Stüvel February 24, 2017, 15:35 (GMT) |
Alembic import: don't crash on instances Importing instances (i.e. Alembic objects that reference instance sources rather than contain data for themselves) isn't supported yet, but with this change at least it doesn't crash Blender. |
Revision 74e42c9 by Sybren A. Stüvel February 24, 2017, 15:35 (GMT) |
Alembic import: be more lenient towards unknown object types. Alembic is an interchange and caching format, that can contain custom object schemas. Blender shouldn't crash (because of failing asserts) just because it doesn't know such an object type. |
Revision 2074d26 by Sybren A. Stüvel February 24, 2017, 15:35 (GMT) |
Alembic: don't call object.getFullName() multiple times. |
|
|
|


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