Official Open Asset Import Library Repository. Loads 40+ 3D file formats into one unified and clean data structure.
so I was able to build assimp for android by using gradle and cmake
I'd then like to get a build system down for ios.
Finally, I think it would be really cool if we could create build systems online so that everytime a major release is put out we can supply everyone downloadable binaries for mobile and desktop operating systems.
I'd love to make it extremely easy to get up and running using assimp for developers who are not well versed in C++ and CMAKE
latest cmake apparently now supports visual studio builds for android
at least according to their cmake
changelog
matias-lavik chriscamacho (Gitter):
Well, here are some:
- Urho3D
- MonoGame
- Godot game engine (I heard they have been making their own FBX importer now, so not sure if they still use it)
There are plenty of closed source software/games using Assimp as well. And a bunch of smaller game (engine) projects you can find on GitHub (such as my own Ming3D). When we were hiring developers at my job, half of the candidates were already familiar with it 😁
Reaching out again ... anyone interested in creating a build system for assimp for Android and iOS? I have budget for it. email me or DM. Email is m@615.io
iOS will be harder
@RichardTea done, just cleaned them up
@RadiumP strongly depends on USD support
at this moment I try to get an idea
but we could :-)
Trying to make my own "importer" (loading assimp data structures directly) to use the export features. Looking at texture.h, it seems like we should be able to load aiTexel info a,r,g,b values and set the hint to "rgba8888", but when I do that, nothing can open a glb or gltf that's generated. Is there something we should be doing in that scenario to allow the data to be written correctly?
In this example, the texture is a 512x2 image - gets into GLTF as:
"images": [
{
"uri": "data:image/rgba8888;base64,/woAAf8MAAH/DgAB/xAAAf8SAAH/FAAB/xYAAf8YAAH/GgAB/xsAAf8dAAH/HwAB/yEAAf8jAAH/JQAB/ycAAf8pAAH/KwAB/y0AAf8uAAH/MAAB/zIAAf80AAH/NgAB/zgAAf86AAH/PAAB/z4AAf8/AAH/QQAB/0MAAf9FAAH/RwAB/0kAAf9LAAH/TQAB/08AAf9QAAH/UgAB/1QAAf9WAAH/WAAB/1oAAf9cAAH/XgAB/2AAAf9hAAH/YwAB/2UAAf9nAAH/aQAB/2sAAf9tAAH/bwAB/3EAAf9zAAH/dAAB/3YAAf94AAH/egAB/3wAAf9+AAH/gAAB/4IAAf+EAAH/hgAB/4gAAf+KAAH/jAAB/44AAf+PAAH/kQAB/5MAAf+VAAH/lwAB/5kAAf+bAAH/nQAB/58AAf+hAAH/owAB/6UAAf+nAAH/qAAB/6oAAf+sAAH/rgAB/7AAAf+yAAH/tAAB/7YAAf+4AAH/ugAB/7sAAf+9AAH/vwAB/8EAAf/DAAH/xQAB/8cAAf/JAAH/ywAB/8wAAf/OAAH/0AAB/9IAAf/UAAH/1gAB/9gAAf/aAAH/3AAB/90AAf/fAAH/4QAB/+MAAf/lAAH/5wAB/+kAAf/rAAH/7QAB/+4AAf/wAAH/8gAB/vMAAf30AAH89QAB+/YAAfr3AAE="
}
],
(which seems too small, tbh - 1024*4x8 bit seems like it should be longer than that?)
With regards to PR #3614 :
The problem on macOS (and presumably also Linux) appears to be that the Google Draco shared library is not exporting the necessary symbols.
According to nm, it's not exporting any public function symbols at all, just some typeinfo
($ nm -gU libdracod.1.dylib)
The problem on macOS (and presumably also Linux) appears to be that the Google Draco shared library is not exporting the necessary symbols.
According to nm, it's not exporting any public function symbols at all, just some typeinfo
($ nm -gU libdracod.1.dylib)
Does anyone have any suggestions as to why that might be?
you can add this manually
I'm not entirely sure what the difference is myself, both use "STP"
Hello all, here's a generic purpose model viewer project based on ASSIMP: https://github.com/Gargaj/Foxotron
could be helpful for testing assimp loaders
Will it work on different platforms?