Closed sinano1107 closed 2 years ago
markers.zip markers is this tabekko.JPG.zip
@sinano1107 this is not a bug you are using a marker with 72 dpi, the recommended dpi value is 300, also width and height need to be increased; You need to recreate your marker with 300 dpi.
@kalwalt Thank you. I had a big misunderstanding about DPI. I mistakenly thought that by changing the dpi of the original image that generates the marker to 300, it would also change the dpi of the marker. However, I noticed that there is a field for dpi in nft-marker-creator.
So I have one question. By setting dpi to 300, it runs comfortably on pc, but fps seems to be reduced on iphone. Can this problem be solved by setting dpi below 300? Please let me know if there is any other best solution.
By setting dpi to 300, it runs comfortably on pc, but fps seems to be reduced on iphone. Can this problem be solved by setting dpi below 300?
If you provide less dpi you will get that issue: object disappear because is not detected/tracked because has less feature and key points. I haven't an iPhone so i can't say more about this issue.
Do you want to request a feature or report a bug? bug
What is the current behavior?
If you run this code on localhost and test it by accessing it from a smartphone, you will get a bug like the one in the video. Tracking is working, but objects that are far from the camera do not seem to render properly.
https://user-images.githubusercontent.com/45984123/149292488-e3982318-8909-487d-9f7b-7f1651104c0c.mov
If the current behavior is a bug, please provide the steps to reproduce. Save the above code as an html file and run it
Please mention other relevant information such as the browser version, Operating System and Device Name Mac iPhone13 pro safari
What is the expected behavior? I want the object to be visible as long as it's being tracked, even if it's away from the NFT.
If this is a feature request, what is motivation or use case for changing the behavior?