Official Open Asset Import Library Repository. Loads 40+ 3D file formats into one unified and clean data structure.
Hello. I'm looking for advice on using the latest version of Assimp with C# in .NET 5.0. I have been able to use 4.x and 5.0.1 with the Nuget.org package called AssimpNet but I wonder if anyone has made an update to target 5.1.x? I tried reaching out to the developer on BitBucket but got no response so I thought I'd ask here just in case. Is anyone currently using Assimp 5.1.x with .NET 5.0?
At this moment, the latest versions are not available.
how do you guys build the viewer?
having issues with fbx files with animations
And you have to keep in mind: the viewer will only work on windows
you can create it via: cmake CMakeLists.txt -DASSIMP_BUILD_ASSIMP_VIEW=ON
This will generate projectfiles for the viewer on windows
Hi, I have the same question as @PiKeyAr, is there someone working on the Assimp .NET wrapper? I'm trying to export files to gltf2, but the gltf2 output in AssimpNet 4.1.0 is not up to the glTF standards and shows errors on opening in https://gltf-viewer.donmccurdy.com/
I have also tried the 5.0.1 beta package, that one works well for the gltf2 exports. But the issue here is that the application crashes after every export. I have tried the AssimpNet wrapper (both 4.1.0 and 5.0.0-beta1) with the newer Assimp releases. But those are not compatible anymore with Assimp, at least not for exporting to gltf2 files, starting from version 5.1.x and up.
I would of course prefer to use the newest version of Assimp with the C# wrapper so have all the latest fixes for gltf2 included. So I am wondering if someone is still working on it / will pick it up and if yes, is there any indication about when we can expect it? Or if it's better to set this idea aside for now and maybe try to pick it some other time.
I have also tried the 5.0.1 beta package, that one works well for the gltf2 exports. But the issue here is that the application crashes after every export. I have tried the AssimpNet wrapper (both 4.1.0 and 5.0.0-beta1) with the newer Assimp releases. But those are not compatible anymore with Assimp, at least not for exporting to gltf2 files, starting from version 5.1.x and up.
I would of course prefer to use the newest version of Assimp with the C# wrapper so have all the latest fixes for gltf2 included. So I am wondering if someone is still working on it / will pick it up and if yes, is there any indication about when we can expect it? Or if it's better to set this idea aside for now and maybe try to pick it some other time.
I guess not. I tried to update this package but saw a looot of build failures. So I was not able to solve them at this moment
So if someone is interested in working on this, feel free!
hey kim, been auditing my assets bought from the unity store and I found that the fbx file's position vertices has been imported X,Z,Y instead of X,Y,Z. This was found after converting the original file into collada. Is there any flags in assimp to manipulate vector component order?
Are all vertices rotated or is the global coord system of your model rotated in such a way?
4 replies
Maybe some rotations has applied after importing the asset? Normally we will not touch the xyz components of our positions.
Hi Kim, I'm using 5.2.0 to export and all the file formats are working fine, apart from the glTF ones (both gltf, glb & gltf2, glb2)... Is there anything different within the 'aiScene' that i need to set for these formats? The exports are failing with aiReturn_FAILURE.
Many thanks!
Do you have a small example which can be used to reproduce the issue?
Would you like a zipped project or code snippet?
Hi,
I'm a french intern, and I have been tasked with contributing to Assimp's STEP support, especially regarding the AP242 schema. So I wanted to know, has anyone started to work on this and would have any progress on the matter? I've worked on it by myself for the past 3 weeks or so, mainly doing some research to better understand the format. Right now, one of my main problems are complex entities, so would anyone by chance have any suggestions on how to represent them inside Assimp (I've already added their parsing)?
Thanks a lot in advance!
I'm a french intern, and I have been tasked with contributing to Assimp's STEP support, especially regarding the AP242 schema. So I wanted to know, has anyone started to work on this and would have any progress on the matter? I've worked on it by myself for the past 3 weeks or so, mainly doing some research to better understand the format. Right now, one of my main problems are complex entities, so would anyone by chance have any suggestions on how to represent them inside Assimp (I've already added their parsing)?
Thanks a lot in advance!
Hi, I am working with ASSIMP and I'm trying to solve an issue, I want to weld vertices in proximity (0.01f or so), if I modify the aiProcess_JoinIdenticalVertices epsilon I get the desired result, however UV is wrong, anyone worked on something similar that also fixes the UV?
I guess not. I tried to update this package but saw a looot of build failures. So I was not able to solve them at this moment
It looks like the BitBucket repo got a pull request that got merged. Apparently it works with 5.2.x now. But a Nuget package is not available and apparently x86 support wasn't updated.
I have compiled the latest assimp 5.2.4 with (ASSIMP_BUILD_DRACO=ON), everything compiles properly, but when I attempt to open a GLB that has draco compression, I get the error: GLTF: Invalid accessor without data in mesh meshes[0]. Is that to be expected, or is there something additional I'm missing when building assimp to enable draco support?
stepping into the code, it gets stuck here: glTF2Importer.cpp:
Accessor::Indexer data = prim.indices->GetIndexer();
if (!data.IsValid()) {
throw DeadlyImportError("GLTF: Invalid accessor without data in mesh ", getContextForErrorMessages(mesh.id, mesh.name));
}
I'm struggling to correctly load and transform a skinned mesh using assimp. The documentation regarding this was relatively vague. Are there any recommended resources I could dive into to understand the way assimp handles this data better?