July 28, 2015, 01:10 (GMT) |
Cleanup: ws & redundant 'struct' |
July 28, 2015, 00:58 (GMT) |
Merge branch 'master' into mathutils_bvhtree |
July 16, 2015, 08:52 (GMT) |
Use PyC_AsArray macro |
July 15, 2015, 17:05 (GMT) |
error in last commit |
July 15, 2015, 17:01 (GMT) |
Check range of triangles passed into new bvhtrees Avoid crashesing on invalid data |
July 15, 2015, 16:52 (GMT) |
Avoid using PySequence functions, instead use PySequence_Fast to support same featureset but avoid slow lookups. Also fixes refcount leak accessing verts. |
July 15, 2015, 16:36 (GMT) |
cleanup |
July 15, 2015, 16:30 (GMT) |
zero 3rd member of 2d arrays passed to mathutils.kdtree |
July 15, 2015, 16:28 (GMT) |
share generic parsing functions |
July 15, 2015, 15:59 (GMT) |
misc docstring tweaks |
July 15, 2015, 11:29 (GMT) |
Minor edits to custom bvh - use array triples & UNPACK macro - replace (int)PyLong_AsLong -> _PyLong_AsInt |
July 15, 2015, 11:28 (GMT) |
Merge branch 'master' into mathutils_bvhtree |
July 14, 2015, 15:27 (GMT) |
Another alternative BVH Tree representation for totally custom user geometry. The new constructor method allows creating a BVHTree from a list of vertices and triangles directly, without a separate mesh representation. |
July 14, 2015, 11:49 (GMT) |
Merge branch 'master' into mathutils_bvhtree |
April 29, 2015, 09:26 (GMT) |
mathutils_bvhtree: Changed parameters for the ray_cast function from point+ray to point+direction+distance. This is more convenient to use in general, and more consistent with the BKE code. |
April 29, 2015, 08:41 (GMT) |
mathutils_bvhtree: Changed type names for bvhtree elements to make them more consistent with other API parts. In particular using TESSFACE instead of FACE for clarity. |
April 29, 2015, 08:38 (GMT) |
mathutils_bvhtree: Support various types of DerivedMesh data, based on requested settings. |
April 29, 2015, 07:37 (GMT) |
mathutils_bvhtree: Removed unnecessary dealloc function for bpy types. |
April 29, 2015, 07:34 (GMT) |
mathutils_bvhtree: Changed return values of find-nearest functions to plain distance instead of squared distance. For bpy API a consistent use of plain distance is less confusing and the overhead is not very relevant. |
April 29, 2015, 07:11 (GMT) |
Merge branch 'master' into mathutils_bvhtree |
|