why is there such a mess? why not just deprecate FLAR classes and let
everyone use Ny stuff?
unofficially, I've got it to detect hiro marker by hacking out two
lines of code... this might actually work all the way, ha ha! I should
have went to sleep.
right... but nydetect.getTransmationMatrix (nyresult) returns matrix
full of NaN-s
p.s. I hope you guys don't mind me talking to myself in your mailbox.
basically, FLARManager interfaces with org.libspark.flartoolkit.detector.FLARMultiMarkerDetector, but it has to use some types from org.libspark and others from jp.nyatla. i tried to go with jp.nyatla for types when i could, as they're more generic than the org.libspark types, which often seem to be useless (no additional functionality) wrappers around the nyatla types. but still had to use types from both packages...
-e
my div-by-0 bugfix addresses NaN problem in FLARToolKit-based test but
not in NyARToolKit-based. more debugging ahead :(
btw, I have also committed type mismatch bugfix (r4418), hope that helps.
this was easy, NyARParam does not init screen size.
so,
here's what it boils down to: using rev 4418, you can use NyARToolKit
classes ONLY. (almost) working proof of concept code:
http://pastebin.com/7uNTGfMY swf at http://megaswf.com/serve/72168/
(ignores confidence, use any marker)
the only hack (that I will not commit, because it is *cough* hack) is
to comment NyAS3Utils.assert call out in wrapBuffer. this can only be
resolved by nyatla and rokubou.
finally, bad news:
this is almost 2 times slower than using FLARToolKit detector, so you
guys should reconsider the direction of the project.