glacier-modding / glacier-modding/NavKit
Fix "Collection X already in collection" error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
There is sometimes an error in the blender glacier2obj.py script with this error message:
Collection X already in collection
Investigate the cause and fix the issue.
Example:
[INFO] load_scenario: Nav.Json file: D:\Epic Games\H3 Tools\NavKit\Output\output.nav.json
Blender 4.3.2 (hash 32f5fdce0a0a built 2024-12-17 03:35:23)
Error: Collection 'Scenario_Falcon' already in collection 'Scenario_Falcon'
Error building obj or blend file. The blender python script threw an unhandled exception. Please report this to AtomicForce.
Note from krudd:
"If I do the extract and build obj option instead of just extract, seems to be okay"
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the failure in the Blender glacier2obj.py script using the extract-and-build-obj workflow, then compare it with extract-only. Trace where the Scenario_Falcon collection is created or linked and identify why the same collection is added twice. Done means the reported error no longer occurs and the OBJ or blend build completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100