-
Notifications
You must be signed in to change notification settings - Fork 69
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
HOWTO Recognize 4x4 markers #109
Comments
Hi, what you want is basically these pattern markers: https://github.com/artoolkit/ARToolKit5/tree/master/doc/patterns |
Thank you for your answer. |
They are pre-configured in a way that you don't need to create the patt files. You still need to tell the tracker which markers you are looking for. Meaning you need to 'load' (I guess instantiate is the better word) them. |
Everything's clear. That's the answer i was looking for... Thank you!!! |
Yeah, that I can't say. And honestly, I'm wondering why you would want that many markers at once. |
Every marker would be associated to a specific customer, so I need them all in order to have as many "available slots" as possible. |
Hm, I guess I would need to understand your complete app to get what you are aiming for :). |
Hi @mrcesc0 the multi marker feature Is intended to be used ti improve the detection and tracking, in the sense more markers acting like only one. I can point you to the docs, i have a repo in my profile, but searching on my smartphone Is not easy...🙂 |
Hello,
I'd like to build a react native app able to read 4x4 markers, so a number of 8191 markers.
Which way should i follow to achieve that?
I took a look at this example https://github.com/artoolkitx/jsartoolkit5/blob/master/examples/multimarker_barcode_threejs.html but have some doubts on how to generate a *.dat file (as in the example: arController.loadMultiMarker('Data/multi-barcode-4x3.dat') that contains all the markers I need and if that's the proper way to the reach the goal or i should consider another method.
Thank you so much
Francesco
The text was updated successfully, but these errors were encountered: