By bedrocks
on Mon, 02/25/2019 - 18:39
Our applicaton onIy uses image targets. I stumbled across a deprecation warning about FUSION_OPTIMIZE_IMAGE_TARGETS_AND_VUMARKS in the documentation and was wondering if there is any difference (in terms o quality) in recognition or tracking of image targets depending on the used fusion provider?
For example: Is native AR (ARKit and ARCore) via FUSION_PROVIDER_PLATFORM_SENSOR_FUSION better / worse compared to FUSION_PROVIDER_VUFORIA_SENSOR_FUSION (VISLAM) when it comes to image targets?
Do i even need FUSION_PROVIDER_PLATFORM_SENSOR_FUSION when i only using image targets? Does it even make sense to activate it?
About Fusion API
Hello,
Hello,
Vuforia Fusion is not used for the detection and tracking of Image Targets. It is used for Extended Tracking use cases, where the target is either not in view or too distant to be tracked.
Hello medabit,
Hello medabit,
thanks for your feedback and for the clarification.We don't use Extended Tracking because it doesn't work well with our use case.
Here are a few more questions so that we can better understand what the technology is capable of and what's it's boundaries.
Hello,
Hello,
[quote=bedrocks]
1. Does this mean (if we only use image targets and no extended tracking), in theory we don't need a native provider (ARCore / ARKit) at all because detection and tracking is handled by Vuforia CV itself?
[/quote]
Thank you very much for the
Thank you very much for the detailed feedback. I highly appreciate it.