Log in or register to post comments

AR image tracking for a tradeshow booth

March 7, 2019 - 6:30am #1

Has anyone dealt with large targets used at a tradeshow booth? Is there a known size limit where if a target is too big, will the app have trouble tracking it?

AR image tracking for a tradeshow booth

June 17, 2019 - 4:58pm #4

Hello @inayo,

You use the Target Manager workflow to create the "template" device database that includes all your targets. You then hand edit the device database XML file to adjust the relative positions of each Image Target to an origin location.

There is a section at the bottom of this article that describes the XML Multi Target fields. I created my own cube target so that I could understand how the relationship authored in this file translates to a Multi Target.

Let me know if you have other questions.

Thanks,

Vuforia Engine Support

AR image tracking for a tradeshow booth

June 17, 2019 - 3:33am #3

This is very interesting! Do you know how to change the cuboid upload to accept murals instead of cubes? When I entered the physical size of the mural... it still seems to want to accept a cube? 

AR image tracking for a tradeshow booth

March 7, 2019 - 12:04pm #2

Hello,

In the past, Vuforia has been used for AR experiences with large building murals. The challenge usually lies in the device camera's field of view, and how far back a user has to get from the image (mural or otherwise) to recognize the large target.

I believe there are a couple of strategies that can be used:

  1. Only recognize a part of the large target, perhaps the most visible part from your booth. Thus, rather than uploading the entire image, you digitally edit it to only include the part of the large image that would be most visible to the user. This can be used for detection and tracking, with Vuforia's Extended Tracking feature helping to continue the experience if/when the edited target is out of the camera's field of view.
  2. Utilize a "flat" Multi-target. Although our library article (and Target Manager workflow) focus upon the cube/cuboid use case for Multi Targets, the device database as downloaded from the Target Manager can be modified to create a flat Multi-Target. In this case, the large target can be divided into "sections" (2 or more), each of which can be recognized by Vuforia. And since Vuforia understands the spacial relationship of each target to one-another (from the modified device database XML file), the entire large target can be used for detection and tracking.

The #2 option is the one I'm most familiar with devs having success with large murals.

Thanks,

Vuforia Engine Support

Log in or register to post comments