McManning / McManning/Coherence
Add support for multiple scenes / cross scene references
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The sample mech file I'm trying to stress test with has two mains scenes - one contains the actual mech geometry and the other contains a reference to that for composition:
While loading the composition scene into Coherence - the mesh data isn't transferred because it's not digging into that referenced collection for objects to load.
--
This also poses an interesting question about organizing the output scene in Unity - and how much it should replicate Blender's scene(s). I want to say that collections themselves should also be transferred over as an empty GO object type.
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
No file or test is named. Start by reproducing the sample mech file with its composition scene and referenced collection, then trace how Coherence loads scene objects into Unity. Done should include mesh data from referenced collections and a decided mapping for multiple scenes and collections in the Unity output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, unity
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100