ic/magnum - magnum - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Vladimír Vondruš	ba8a3e6f3f	SceneTools: add flattenMeshHierarchyInto(). Now that the data order is pinned down, it's possible to hammer a more efficient underlying API from out under the convenience utility.	4 years ago
Vladimír Vondruš	48bd603236	SceneTools: pin down current flattenMeshHierarchy() behavior. It doesn't discard meshes that are not a part of the hierarchy, but that was the plan in the beginning. However, over the time I realized that a better property for it is that the output is guaranteed to be in the same order and size as the mesh field in the scene. Because that's what I relied on in every use case, and every time I had to dig that property out of the sources because it was deliberately not documented because it was meant to change. No longer. The compatibility with the mesh field ordering is now documented, the behavior regarding loose objects also, and if there's ever a need to discard everything that's not in the reachable hierarchy, it'll probably get its own API. Because it's useful for general asset cleanup and other use cases, not just meshes. I'm still keeping the experimental tag here though, tp be sure.	4 years ago
Vladimír Vondruš	d90c512cc2	SceneTools: use the fancier member-function-slicing APIs. Too verbose otherwise. And I might not be hitting that GCC 4.8 wart this way anymore.	4 years ago
Vladimír Vondruš	822fa0d644	Updated copyright year.	4 years ago
Vladimír Vondruš	8ed08d7733	SceneTools: use a single temp allocation in flattenMeshHierarchy().	4 years ago
Vladimír Vondruš	b0477013f0	SceneTools: utility to flatten mesh hierarchy. Internals doing a few rather big allocations, will convert that to just a single one in a next step.	4 years ago