January 6, 2015, 08:39 (GMT) |
minor edits: use common prefix for BVHTree types |
January 6, 2015, 08:22 (GMT) |
minor cleanup use PyTuple_SET_ITEMS, remove unneeded ZERO float's |
January 6, 2015, 08:14 (GMT) |
Merge branch 'master' into mathutils_bvhtree |
January 6, 2015, 03:50 (GMT) |
Merge branch 'master' into mathutils_bvhtree |
January 5, 2015, 09:46 (GMT) |
mathutils.bvhtree submodule functions for ray cast and find-nearest now support non-Vector tuples like the rest of mathutils. Also the keywords have been removed for slight performance improvement. |
January 3, 2015, 10:05 (GMT) |
Added mathutils.bvhtree submodule to the excluded modules list in the sphinx doc build files. |
January 3, 2015, 10:05 (GMT) |
Nicer doc strings for BVHTree subclasses. |
January 3, 2015, 10:05 (GMT) |
Properly register `mathutils.bvhtree` as a submodule. |
January 3, 2015, 10:05 (GMT) |
Minor doc string fixes. |
January 3, 2015, 10:05 (GMT) |
Splitting the BVHTree python type into two distinct subclasses for DerivedMesh and BMesh support. This avoids messy code due to mixed data in the same py type. And makes it clear at any point what kind of data the BVHTree instance represents. Both types are based on the common BVHTree type, which currently does not have any functionality of its own. Eventually it could implement common BVH functions (find-nearest and ray casting) as well as return read-only info about the size and type of BVH data. Note: While the BVH functions already use callbacks for providing a common interface in C, using this for python types would be redundant. It also still requires specialized data for some details of testing elements. |
January 3, 2015, 10:05 (GMT) |
Use separate result tuple constructors for ray_cast and find_nearest. These are technically the same, but the semantics are slightly different (distance vs squared distance). |
January 3, 2015, 10:05 (GMT) |
Support for BVHTree construction and ray casting from a BMesh. |
January 3, 2015, 10:05 (GMT) |
Optional argument `use_poly_index` of the ray_cast method. This allows turning off the default poly_index return value and using plain tessface indices instead if needed. The tessface -> poly lookup now also includes a range sanity check. |
January 3, 2015, 10:05 (GMT) |
Nearest element search method for BVHTree submodule. |
January 3, 2015, 10:05 (GMT) |
Simplified dm_tessface_to_poly_index, no need to keep two version of this around. |
January 3, 2015, 10:05 (GMT) |
find_nearest implementation for bmesh BVHTree type. This uses only mesh vertices, since this function is supplied by the bmesh bvhutils. Nearest face lookup could be added later. |
January 3, 2015, 10:05 (GMT) |
Some fixes for uninitialized variables with bmesh bvh trees. |
January 3, 2015, 10:05 (GMT) |
Distinguish `use_poly_index` flag based on FACES/POLYS type instead of an explicit argument. This avoids meaningless cases when setting `use_poly_index` for vertex or edge BVHs and is nicer for bmesh which does not yet support both index types (only polys). Eventually BMeshBVHTree could support tessfaces as well, at which point it could get a similar type enum. |
January 3, 2015, 10:05 (GMT) |
New mathutils submodule for BVH tree support in python. |
January 3, 2015, 10:05 (GMT) |
Added object vertex and edge constructors for the BVHTree type. |
|