Aliasing issue in latest A-frame 0.7.0 while viewing 3D model in VR mode
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
So, I downloaded a gltf model from sketchfab and put it on different versions of A-frame, Here are my observations -
On A-frame version 0.5.0, the model looks good. There is minor aliasing issue in the edges but it is negligible.
Link - http://aframe5gltf.surge.sh/
On A-frame version 0.7.0 which is the latest, There is a lot of aliasing and it looks very bad in VR.
Link - http://aframe07gltf.surge.sh/
Interestingly if viewed in Sketchfab viewer in VR mode, the model looks perfect, not even minor aliasing.
Link - https://sketchfab.com/models/192bf30a7e28425ab385aef19769d4b0
Please do watch in a VR headset to clearly observe the issue. I hope to get this solved with your help.
- A-Frame Version: 0.7
- Platform / Device: Samsung S8 / Daydream VR headset / Chrome browser
- Reproducible Code Snippet or URL: Given above
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 comparing the linked A-Frame 0.5.0 and 0.7.0 examples in a Samsung S8 with a Daydream VR headset and Chrome. Investigate the rendering difference responsible for the aliasing, and consider the issue done when the 0.7.0 model has comparable edge quality in VR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- ar-vr-xr, computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100