AccessViolationException with latest assimp version
- Dominant language
- C#
- Stars
- 218
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
I'm trying to use AssimpNet with the most recent Assimp library, which I just compiled from source code.
Reading an object work fine, but when I try to save an object I get a AccessViolationException:
> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
It used to work with an Assimp DLL I compiled before in december 2016, so I guess there are some changes in Assimp since then that are not compatible with AssimpNet. Did anybody experience this before?
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the AccessViolationException in AssimpNet when saving an object with the most recent Assimp DLL compiled from source, then compare the behavior with the DLL compiled in December 2016. Review the AssimpNet save path and the corresponding Assimp library changes; done means identifying the compatibility cause or documenting the missing version and reproduction details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100