Initially in the project I was having trouble viewing my AR(t) in the layer AR viewer. The phone could "see" the pieces, but I certainly couldn't see them through my phone. It turns out it was a sizing issue. My object size & scaling factor were both defaulting to 0, which made the object invisible. Side fact - it turns out the l3d model converter doesn't actually store a scale value for the layar object, all the scale, position and gps settings are only managed through the SQL admin site.
So onto today's amusing screenshots of errors- (I can't help documenting/disclosing this - blame my game dev background I have to show my uglies as well as my pretties).
I worked on two pieces; Bridge_ and eCubed as well as fleshing out the visuals and a narrative behind the six pieces, (these are very much artistic sketches and by no means represent the final works or final title of the piece).
Proposed positions of AR(t) (not recommended viewing positions)
Poi 01 : -28.001311, 153.416108
Poi 02 : -28.000915, 153.416231
Poi 03 : -27.999649, 153.417415
Poi 04 : -28.001217, 153.421389
Poi 05 : -28.001006, 153.418216
Poi 06 : -28.001547, 153.417709
Its going to be interesting to see how people re-capture these pieces on their phones/3G tablets. How they re-interpret them through how they frame the AR(t) pieces. I imagine people will be taking selfies with the pieces that interest them and trying to re-frame the work into the viewers personal context.
The phone for me is a portal onto the work but a portal on can re-frame and manipulate by moving the camera or by inserting oneself into the shot.
The AR(t) pieces are not self occluding and can be seen from multiple viewpoints and not just where I place the GPS markers.
And I still have to finalize the AR(t) pieces individual scales, positions add rotations and positional offsets. Loads more to do.