Assimp Scene to Model
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Hi,
The present assimp importer takes a filename and returns xenko model.
The logic consists two steps:
- Load Assimp Scene using Assimp library
- Map Assimp Scene to Model
Please split this method into two public methods.
Why?
I have some code which generates Assimp scene on the fly. To convert it to Xenko model, I need to write it into a file and then using xenko's importer. If the methods are split as I said, I can avoid writing the file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Assimp importer entry point described in the issue and trace its two current steps: loading the scene and mapping it to a model. Separate those operations into public methods so an in-memory scene can be converted without writing a file, while preserving the existing filename-based import flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100