Dynamic Target
 |
Dynamic Targets currently support only Model Targets. To ensure proper functionality, the Resource URL must be set before accessing the view containing the Dynamic Target. For optimal use, consider creating a secondary view to handle the binding with an application parameter.
|
What Does This Widget Do?
The Dynamic Target widget enables loading various target datasets from both local and remote resources. Depending on your use case, it can dynamically load any required target during runtime.
When Should I Use This Widget?
Use a Dynamic Target when you want to reference Model Targets in your experience that can be loaded dynamically at runtime, or if you want to reference an external target resource.
For more information, see Use Case: Load and Compare Assets Dynamically.
Dynamic Target vs. Model Target
Model Targets should be used when you want to define and generate Model Targets directly within your experience. This approach is ideal for static configurations but is not optimized for asset reusability.
For scenarios where you need to load pre-generated Model Target assets—whether hosted in your Experience Service, bundled with the experience, or served from a third-party source—use the Dynamic Target widget. This widget is designed for runtime flexibility and does not include the Model Target Editor, as it assumes your assets are already prepared and accessible.
Are There Any Special Properties, Services, Events, or Actions?
To view a list of common widget properties, services, and events, see Common Widget Properties, Services, and Events.
|
|
If you are unsure about which version of the Experience Service you are running, contact your administrator.
|
|
Property Name
|
JavaScript
|
Type
|
Description
|
||
|---|---|---|---|---|---|
|
Resource
|
src
|
string/resource_url
|
The direct URL to the .dat file. This should include the full path to the file including the suffix .dat. For example: app/resources/Uploaded/mytarget.dat
|
||
|
External Resource
|
srcType
|
boolean
|
Select this checkbox if using an external resource, and enter the URL. For example: https://myserver/mytarget.dat
This property changes the datatype of Resource, and enables a drop-down menu for local project files or an input field for external links.
|
||
|
Target Type
|
targetType
|
string
|
Defines the Target Type of the linked resource. This field is not editable and is set to vuforia-model://.
|
||
|
Tracked
|
isTracked
|
boolean
|
Is enabled when the camera recognizes the target.
|
||
|
Stationary
|
stationary
|
boolean
|
Select this checkbox if the target will be in a stable environment and won't be moved by the user. Selecting this checkbox may improve tracking performance.
|
||
|
Target Size
|
size
|
number
|
Defines the width of the target. This can be useful when the target is generated with measurements from the CAD data, but the tracking takes place on a smaller model.
|
|
Event
|
JavaScript
|
Description
|
|---|---|---|
|
Tracking Acquired
|
trackingacquired
|
Triggered when tracking is initiated.
|
|
Tracking Lost
|
trackinglost
|
Triggered when tracking is lost.
|
|
Target Loaded
|
targetLoaded
|
Triggered when the target is fully loaded.
|
Example Use Case
Known Limitations
|
Limitation
|
Recommendation and Workaround
|
|---|---|
|
When using a Dynamic Target widget (potentially in combination with a Product widget), target snapping may fail if the app is sent to the background while the target is still loading. Upon returning to the foreground, the experience may not resume tracking correctly.
|
Recommendation: Remain in the app until the target has fully loaded to ensure proper snapping behavior.
Workaround: If the issue occurs, simply reload the experience in Vuforia View to restore functionality.
|