Thanks for the info… I supose I’m a nerd

One question though… if the analysis is being done on a black/white image…. why in the pat file there are info for each RGB channel?

Shouldn’t be enough to have each direction in bw ?

You’re correct to point out that we misspoke when we suggested the physical dimensions are directly related the pixel size. However, they are still important — for example, if you’re tracking two markers and they’re different sizes, yet marked as the same physical size, FLARToolKit will still display everything correctly, but the smaller of the two markers will be “further away”, if that makes sense. So while they will appear that they are sitting on the same plane (if on a table), they actually won’t be within papervision. Though admittedly this is only a problem when you start trying to get the symbols to interact.

Again, as you correctly pointed out, the numbers themselves don’t _really_ matter, but more the relationship. For example, if marker A is twice as big as marker B, you could just put its size in as “2″ and “1″ respectively so that FLAR renders out the scene in a way that more closely mirrors the actual physical relationship. So while it’s not necessary, it’s probably a best practice to at least create a way to adjust physical sizes appropriately.

We’ve updated the posted according.

Thanks!
Jon

[WORDPRESS HASHCASH] The comment’s actual post text did not contain your blog url (http://www.squidder.com/2009/03/05/for-nerds-only-custom-flar-markers-explained) and so is spam.

We’ve gone ahead and released our classes for detecting multiple markers and multiple patterns here:
http://www.squidder.com/2009/03/06/flar-how-to-multiple-instances-of-multiple-markers/

Enjoy!
Jon

We have yet to come up against a hard limit for the number of patterns you can read or the number of them you can have on screen (see our drum kit). So far, it’s really just been a challenge to fit that many patterns on the screen!

It’s actually very easy to do multiple patterns (with some minor tweaking to FLARMultiMarkerDetector). The tricky part is dealing with multiple instances of the same pattern and always making sure you’re changing the appropriate object. We’re still messing around with that here, but once we nail it, we’ll be sure to share!

Cheers,
Jon

Many many thanks, really cool stuff you’re doing here.