As I’m investigating the Translation kit, I was wondering if it would be a good idea to have Data Translators for 3D formats based on Assimp library ?
It would allow any Haiku native program to import and export in any 3D format recognized by translators without having to deal with the format implementation.
However it would mean to have an “internal” format in Haiku API like for B_TRANSLATOR_BITMAP but for 3D objects.
What do you think ?
4 Likes
Is there a 3D kit already? It could be used a bit like FFmpeg.
More info on their website https://assimp.org/
Ok I see. No there’s isn’t currently.
It means Vertex/Material/Mesh/Model must be first available ( in a beta 3D kit? ) before being able to work on 3D data translators based on Assimp.
There’s a embryo for sure but, it was probably only helping rendering. Also formats have multiplied since it was written. Maybe should you check sources of old BeOS demo 3DMov?
Also check STLover, if there is something, I’d bet @3DEyes took advantage of it.
1 Like
I had a quick look at STLover but it’s limited to the below:
- Vertex : yes, ColoredVertex
- Material : no, rgb_color only
- Mesh : via GLM if I’m not wrong
- Model : partial via admesh/
stl_file but it’s not really a model (no material)
So I guess there’s nothing today, I mean to have a standard class on Haiku like the BBitmap class linked to B_TRANSLATOR_BITMAP.
It would mean to have a B3DModel (having Vertex/Material/Mesh/…) linked to B_TRANSLATOR_3DMODEL for instance.