assimp / assimp-net

Automatically exported from code.google.com/p/assimp-net
192 stars 82 forks source link

New version needed #55

Open RSConsulting06 opened 4 years ago

RSConsulting06 commented 4 years ago

Hi, The latest beta version is old Could you build another release using the latest assimp dll please ? Thank you Romain

McallyD74 commented 4 years ago

I'm running into problems myself with the assimp importer and exporter not working correctly for helixtoolkit.sharpdx. Is there any hope? Or do you think this is kind of dead?

Starnick commented 4 years ago

I do not own this repo, the "official" one I work off of and make nuget releases is here => https://bitbucket.org/Starnick/assimpnet/src

I generally only update when the native assimp library does a version release, which still looks to be the patched 5.0

What problems are you having?

McallyD74 commented 4 years ago

I'm using Helixtoolkit.wpf.sharpdx.assimp and having trouble importing gltf models. Some older example models from Khronos group work fine, but anything I export from Blender using the current plugin results in an error when attempting to import into Helixtoolkit using the file load demo.

I opened an issue asking about Importing in helixtoolkit. I couldn't figure out why material parameters/maps weren't preserved. I was told gltf works just fine, but it doesn't. I was told assimp could be the issue " it depends on assimp.net. Assimp.net is using old version of assimp, there are some bugs in it too.": https://github.com/helix-toolkit/helix-toolkit/issues/1376

I tried to see if I could get an older version of the blender exporter to circumvent the issue, but no luck: https://github.com/KhronosGroup/glTF-Blender-IO/issues/1143

So it kind of sucks, I can import the damagedhelmet file (the one I mentioned in the Khronos group thread) and it preserves the materials perfectly, but for some reason, I can't get any files that I export myself to preserve material attributes, or in many cases the assimp importer simply crashes the program.