July 14, 2021, 05:16 (GMT) |
adaptive_cloth: Mesh: flip_edge_triangulate() initial implementation Need to implement across seams support. |
July 13, 2021, 13:19 (GMT) |
adaptive_cloth: Mesh: collapse_edge_triangulate(): across_seams option |
July 13, 2021, 06:25 (GMT) |
adaptive_cloth: fix: Mesh: collapse_edge_triangulate(): delete node only if no other vert refers to it |
July 13, 2021, 05:06 (GMT) |
adaptive_cloth: fix: Mesh: collapse_edge_triangulate() invalid faces generated The edge between v1 and ov should be removed only if the edge doesn't have any linked faces. If it has any linked faces, it will make those faces invalid and cause problems down the line. For the face to have (v2, ov, vx), this becomes impossible since (v1, ov) has been removed, this is wrong. |
July 12, 2021, 13:47 (GMT) |
adaptive_cloth: Mesh: collapse_edge_triangulate() version 2 |
July 11, 2021, 16:51 (GMT) |
adaptive_cloth: fix: Mesh: split_edge_triangulate() crash when edges are realloced Took the new edge index by reference instead of copy leading to wrong memory access when the edges are reallocated by the arena. |
July 11, 2021, 12:35 (GMT) |
adaptive_cloth: Mesh: make split_edge_triangulate() work with new deletion methods |
July 11, 2021, 12:35 (GMT) |
adaptive_cloth: Mesh: delink face edges |
July 11, 2021, 12:33 (GMT) |
adaptive_cloth: Mesh: const get checked elements |
July 11, 2021, 08:02 (GMT) |
adaptive_cloth: Mesh: better deletion of the elements This new way of deleting elements ensures that no links can be missed out on. The deletion of the elements has to happen in a certain order leading to lesser number of errors. This is API breaking, so all functions refering to deletion of the elements have to be updated. This includes, Mesh::split_edge_triangulate() and Mesh::collapse_edge_triangulate(). |
July 10, 2021, 11:45 (GMT) |
modifier: adaptive_remesh: select split or collapse edge operation |
July 10, 2021, 11:43 (GMT) |
adaptive_cloth: Mesh: collapse_edge_triangulate() first draft |
July 9, 2021, 05:58 (GMT) |
adaptive_cloth: Mesh: write to MeshIO: allow gaps in the Arena(s) There can be gaps in the `Arena`s introduced due to removing elements in the middle of the `Arena`. Now this can lead to wrong indexing when writing the positions and the uvs. For this, create a `Map` between the element's arena index and it's true index in the vectors created for them. |
July 8, 2021, 18:18 (GMT) |
adaptive_cloth: Mesh: split_edge_triangulate(): support for across seams In the `Mesh` structure, `Edge` stores a tuple of `Vert`s which means, it is based on the UV coordinates, although this is quite useful, sometimes it is important to have the mesh operation happen across the UV seams as well. So consider all the edges formed by the `Vert`s stored in the `Node` of the given `Edge`'s `Vert`s. Confusing, yes, but simple. |
July 8, 2021, 12:55 (GMT) |
adaptive_cloth: Mesh: append non duplicate vert indices in node.verts |
July 8, 2021, 12:17 (GMT) |
adaptive_cloth: Mesh: split edge: remove completed todo comment |
July 8, 2021, 07:31 (GMT) |
adaptive_cloth: fix: Mesh: delete_face(): wrong starting index |
July 8, 2021, 06:54 (GMT) |
adaptive_cloth: MeshIO: DNA Mesh: combine repeating UVs |
July 7, 2021, 13:54 (GMT) |
modifier: adaptive_remesh: Run split edge of specified edge index This is for testing the cloth_remesh.cc::Mesh::split_edge_triangulate() function. |
July 7, 2021, 13:50 (GMT) |
adaptive_cloth: Mesh: split_edge_triangulate() |
|