playcanvas / playcanvas/engine
Specular aliasing after using envAtlas
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16.8k
- Forks
- 2k
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 222
Description
Here is my project's screenshot, it is built on top of v1.50.2(the environment lighting is using prefilteredCubemaps)
https://github.com/user-attachments/assets/b81d3270-8711-46f0-9ef7-a7f9bfc3a766
But after I upgrade it to v1.51.7, v1.52.6, v1,53.4(the environment lighting migrated to envAtlas), the specular aliasing is really terrible:
https://github.com/user-attachments/assets/f8535f02-cec2-4d53-900d-71d8151dc4fb
I also try playcanvas online editor(v2.15.2 now), the specular aliasing is still terrible...
Here is the public project: https://playcanvas.com/editor/scene/2418205
https://github.com/user-attachments/assets/350d98c7-fefc-402f-91c2-c4baf6fb6117
v1.51.0 is released at 2021.12. Almost 4 years later, this bug is still here... 😭
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
Reproduce the issue in the linked PlayCanvas public project and compare the v1.50.2 prefilteredCubemaps result with the later envAtlas versions. Start by tracing the environment-lighting migration and specular aliasing behavior in the engine; done means the envAtlas result no longer shows the reported severe aliasing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100