Topic has a solution
Log in or register to post comments

Multi Area Targets - problem with augmentations when in Play Mode

July 26, 2021 - 7:30am #1
Topic solved

Vuforia 9.8.11

Unity 2020.3.13f1

Hi there, in the attached images (Non Play Mode 1,2,3) it shows that I have 2 AreaTargets nested as children of a MultiArea game object using the MultiArea script from your tutorial. Within the MultiArea gameobject, I have 2 area targets :" AreaTarget Home01" and "AreaTarget Home02".

Things start going strange when i enter Play mode.

Issue 1:

In the attached images (Play Mode 1,2,3) it shows that in Unity Play mode, augmentations that were previously children of the Area Targets, are now direct children of the MultiArea object. Is this meant to be correct?

Issue 2:

What is also weird is that in image  "Play mode 3", u can see that the augmentation gameobject that used to belong to "AreaTarget Home02" now has its Sphere collider disabled. This does not happen for augmentation gameobjects that had  "AreaTarget Home01" as their parent. This is causing that object to not interact with the player.

 

Could someone help me here with this anomaly?

AttachmentSize
Image icon Non Play Mode 1.png92.62 KB
Image icon Non Play Mode 2.png92.04 KB
Image icon Non Play Mode 3.png95.64 KB
Image icon Play Mode 1.png92.86 KB
Image icon Play Mode 2.png92.43 KB
Image icon Play Mode 3.png95.67 KB

Multi Area Targets - problem with augmentations when in Play Mode

August 15, 2021 - 8:07am #3

Thanks for the response! Will give that a try

Multi Area Targets - problem with augmentations when in Play Mode

August 3, 2021 - 8:54am #2

Hey there,

First of all, sorry for the delay in response. Let me try to answer your questions below:

1. You're correct. All child augmentations from the area targets are set to be new children of the MultiArea object. Since we're trying to combine area targets into one, all augmentations are also underneath one object, and their positions are set based on the MultiArea object. (see screenshot)

2. I expect this to be caused by the DefaultTrackableEventHandler (see screenshot). Could you see if the issue still persists if you comment out the highlighted sections from the provided screenshot?

Many thanks!

Log in or register to post comments