-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aliasing issue in latest A-frame 0.7.0 while viewing 3D model in VR mode #3354
Comments
Note that antialiasing is a setting you can control, have you tried putting |
see also #2666, i'm not sure where/if it is documented how antialiasing behaves by default. Also I suggest checking the model against a "just threejs" viewer like #2666, as Sketchfab's viewer is highly customized and will not necessarily match our results. There are also some z-fighting artifacts in all versions, but those are part of the model itself. |
Yes, I've tried that as well. No luck. The model still looks bad in VR on latest version while it looks fine on 0.5.0. With or without the setting. |
We prioritize performance over visual fidelity. That’s why antialiasing is disabled by default. Sketchfab is a single model viewer with limited interactivity so they can make different choices. |
I try to force antialias with |
|
I think i've found a solution to this problem... A manual fix (that worked for me) would be:
I hope this fix will be implemented soon. |
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.
The text was updated successfully, but these errors were encountered: