You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.
I got partway through writing a .dae file decoder for a robotics project when I started wondering what type to use to store the result. The problem is that we currently assume (in MeshIO and in this package) that the mesh you get from a file is basically always exactly one HomogenousMesh. But what about meshes with textures or material properties? We don't really have a type that encompasses those.
In MeshCat, I have the notion of an Object, which contains a Material and a Geometry, where that geometry could be a HomogenousMesh. Would something like that be useful in GeometryTypes? Or should the mesh type be expanded to allow things like textures or material properties?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I got partway through writing a
.dae
file decoder for a robotics project when I started wondering what type to use to store the result. The problem is that we currently assume (in MeshIO and in this package) that the mesh you get from a file is basically always exactly oneHomogenousMesh
. But what about meshes with textures or material properties? We don't really have a type that encompasses those.In MeshCat, I have the notion of an
Object
, which contains aMaterial
and aGeometry
, where that geometry could be a HomogenousMesh. Would something like that be useful in GeometryTypes? Or should the mesh type be expanded to allow things like textures or material properties?The text was updated successfully, but these errors were encountered: