Decals and VisRegions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
A small but noticeable bug when working on Tiam:
When an object has both a decal (for footprints, for instance) and a Visibility Set attached, it causes the decal to not appear. Perhaps we need an error thrown when these two modifiers are used on the same object?
EDIT: In further testing, this only seems to affect MOUL, not PotS/CC.
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 problem in MOUL with an object that has both a decal and a Visibility Set, then compare the result with PotS and CC. Trace how these two modifiers are handled during age export; done when the decal appears in MOUL or the conflict produces a clear validation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blender, python
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100