AR.js
AR.js copied to clipboard
AR-js-org
Jerkiness
Do you want to request a feature or report a bug? Bug
What is the current behavior? I render a image as an entity object and the button is not fixed. It is extremely sensitive to movement and there is jerkiness If the current behavior is a bug, please provide the steps to reproduce.
Please mention other relevant information such as the browser version, Operating System and Device Name
What is the expected behavior? Is there a way I can avoid this shaky behaviour and fix the image in a position? If this is a feature request, what is motivation or use case for changing the behavior?
When the camera is sensitive to movement, then AR.js is probably picking up the wrong camera. What is the make and model of your phone, do you have multiple cameras?. Can you compare the view from AR.js to your mobile camera app and see if AR.js is more zoomed in? If it is then your AR.js is using the wrong camera.
I am using iPhone 11. I had a similiar experience when i am trying the Trex example in image-markers. This is specifically for image-markers only
Hi,
Am not sure if you're using the location-based feature.
But if you are, I find the AR.js documentation helpful for this, you can get some info here:
https://ar-js-org.github.io/AR.js-Docs/location-based/
The document mentioned that there is a code that can help to reduce the shaking effects using a smoothing factor. I've applied this and it works well.
Hope it helps and all the best!
Hi,
Am not sure if you're using the location-based feature.
But if you are, I find the AR.js documentation helpful for this, you can get some info here:
https://ar-js-org.github.io/AR.js-Docs/location-based/
The document mentioned that there is a code that can help to reduce the shaking effects using a smoothing factor. I've applied this and it works well.
Hope it helps and all the best!
Also, use images with at least 300 DPI for NFT feature extraction. This helps a lot in stable tracking.
I'm having the same issues on my device when using NFT. Even when using 300 DPI images the tracking isn't really stable. Is this behaviour due to the performance limits of JS in web browsers?
