Ability to not perform FXAA pass for in imagery
Open
Nobody has claimed this yet.
category - graphics
type - enhancement
- Dominant language
- JavaScript
- Stars
- 15.8k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
Stemming from #3279, it would be useful to be able to not have FXAA affect imagery. It can make tiles blurrier and is especially a problem for imagery with labels baked into them.
The current workaround is to disable FXAA entirely, but leads to jagged edges for geometry.
```js
viewer.scene.postProcessStages.fxaa.enabled = false;
```
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 with the issue's workaround, viewer.scene.postProcessStages.fxaa.enabled, and review the related issue #3279 for context. Trace how the FXAA post-process stage is applied to imagery and geometry. Done means imagery can bypass FXAA while geometry still receives it, without disabling the FXAA pass entirely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100