instead of making universal marker, one should make universal matcher.
this is actually perfectly possible at the moment for single marker
detector - you take single marker detector and replace standard
matcher with code that detects direction from marker contents in some
deterministic way. you obviously lose the ability to recognize things
(i.e. to return meaningful confidence level), but the rest of
flartoolkit operation will be unaffected.
anyone up for a job? eric? don't make me do it myself again :P
-e
the problem is non-existant in the case of 1 marker, flartoolkit
cannot derive physical dimensions from bitmap and therefor does not
care if your marker is 2mm and photographed through microscope or 200
km and photographed from satellite.
the size of marker you enter into flartoolkit is logical size in
virtual 3D space, and it only matters for correct scaling your 3D
models.
> Another idea, is maybe we have have the marker displayed on a mobile
> device, e.g. iphone, for people that don't want to bother with
> printing out markers to easily start playing with AR (and it saves
> trees too).
what about power wasted to charge your phone? any way, this was
already discussed here, in fact I tried that myself and my webcam was
not working with my digital camera lcd in specific application that I
did not want to print a marker for.
>
> ok just tried it, tested a marker on my iphone, works pretty well, but
> then again the size of the marker is significantly smaller then that
> the app specified :(
so what?