playcanvas / playcanvas/engine
Should we be using premultipled alpha for UI images?
Open
Nobody has claimed this yet.
area: graphics
area: ui
enhancement
- Dominant language
- JavaScript
- Stars
- 16.8k
- Forks
- 2k
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 222
Description
We have some threads around fringing of UI assets:
- https://forum.playcanvas.com/t/artifacts-on-our-2d-assets/14834
- https://forum.playcanvas.com/t/why-do-my-9-slice-sprites-look-terrible/21081
Should we be using premultipled alpha as this article suggests? https://forum.playcanvas.com/t/why-do-my-9-slice-sprites-look-terrible/21081
Or is there performance issues that should be considered? Maybe we can give users an option
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 by reading the linked forum threads on UI asset fringing and 9-slice sprite artifacts, then locate the engine's UI image and alpha-handling entry points. No files or tests are named; done would require a decided premultiplied-alpha approach, consideration of performance and user options, and corresponding implementation coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100