AlternativeTo is a free service that helps you find better alternatives to the products you love and hate. The site is made by Ola and Markus in Sweden, with a lot of help from our friends and colleagues in Italy, Finland, USA, Colombia, Philippines, France and contributors from all over the world. That's right, all the lists of alternatives are crowd-sourced, and that's what makes the data. + Asset impairment recognized for accounting purposes: technical adjustment to reflect fast-changing new mobilities and creation of the new unified SNCF Group. Cohesion and social unity within.

Vuforia Engine v9.0.12Bugfixes / FeaturesAllModel Targets. Advanced Model Targets now support training of databases that contain multiple models each with automatic recognition ranges up to 360° detection. Improved recognition of Advanced Model Target databases that were trained using 'realistic' model appearance mode.Area Targets. enables using an entire space, be it a factory floor or retail store, as an AR target. A 3D scan of the desired location can be converted with the. Test your scanned space with the, provided as Unity project and pre-build for Android. Author and simulate your AR experience created around the Area Target 3D representation in the Unity Editor.

See the on how to get started.Additionally, a new type of tracker AreaTracker and trackable AreaTarget have been introduced in the API to support this new feature. See on how to use the new API.Environments.

Per default Vuforia Engine apps now persist the trackable states after a pause/resume interrupt when using the Device Tracker to allow continuation of interrupted AR experiences. Guide your user after a resume to return to the location where the experience was left off. The Device Tracker will then relocalize and recreate anchors from the prior session, reporting also extended tracked targets. Vuforia Engine v8.6.9 and v8.6.10Bugfixes / FeaturesAllModel Targets.

Fixed an issue with 'Realistic Appearance' mode for Advanced Model Targets. If you have previously trained a dataset with this mode, make sure to upgrade your version of Vuforia Engine to 8.6.10 or later.AndroidN/AiOSN/AUWP. Updated the Vuforia HoloLens sample in the Unity Asset Store with a new version that shows integration with the Mixed Reality Toolkit (MRTK) and how to leverage the new hand gesture capabilities of the HoloLens 2. See for instructions.Lumin.

Fixed an issue in the Vuforia Magic Leap sample for Unity that resulted in compiler errors when building the app because of missing.asmdef files.Unity. Fixed support for Cloud Recognition on Magic Leap 1Known IssuesAllModel Targets. Targets with motion hint STATIC are more sensitive to wrongly specified physical size in the dataset. Model targets may switch to EXTENDEDTRACKED more often during very fast user motion when the motion hint is set to STATIC. We recommend using ADAPTIVE if robust tracking during very fast motions is required. Model targets may rapidly switch between TRACKED and NOPOSE when tracked from a large distance without device tracker being active.

Device Tracker reset during Extended Tracking with Model Target might in some cases lead to unexpected relocalization issues. Deactivating/activating the Model Target improves the situation - but user will have to start experience again with detecting the Model Target. The native Model Targets GuideView interface still uses the old y-down camera coordinate system convention in the getPose/setPose methods.Environments. A wrong EXTENDEDTRACKED pose might be reported for Model Targets and other Object Targets after the Device Tracker recovers from limited tracking state. This is seen e.g. If the camera of the device was covered while moving and is mostly seen on devices where ARKit and ARCore are not supported and VISLAM is used for device tracking.

The target pose will be corrected once the target comes into full view again and can be re-detected. If your application requires exact target alignment in such scenarios, it is recommended to discard EXTENDEDTRACKED poses of targets after the Device Tracker reported a LIMITED tracking status info. The target should only be considered tracked again if its tracking status is reported AS TRACKED. In Unity, this is best implemented in a custom TrackableEventHandler script. Using multiple trackables simultaneously with Extended Tracking using Vuforia Sensor Fusion provider, may lead in edge-cases to degraded tracking quality. VISLAM may fail on environments with predominantly edgy structures with fine lines w/o other texture.

Mid-air anchors are now stabilized to the environment map when using Vuforia Sensor Fusion. Vuforia Engine v8.6.7Bugfixes / FeaturesAllDigital Eyewear. Added Beta support for the Magic Leap 1 Creator Edition (Unity only). Please see for more information. Added a Unity sample showing how to build a Vuforia Engine app for the Magic Leap 1.

See for more information. Added Support for the Vuzix m400 eyewear device. Improved performance on HoloLens devices: Performance of deep-learning based features (Advanced Model Targets, Advanced Model Targets 360) has been improved on all UWP devices. In addition, on HoloLens camera mode MODEOPTIMIZESPEED now reduces the camera frame rate to save power, this is best used for experiences where the tracked targets are not moving.Model Targets. Added a new Model Target tracking mode optimized for cars. In Unity, select CARS from the Model Target Tracking Mode dropdown in the Vuforia configuration.

You can also configure this mode with the setHint API. Please refer for more information.Environments. TrackableResults for targets and anchors now have a new tracking status: LIMITED.

This is used when the inferred pose of the target or anchor is known to have substantially larger inaccuracies than a normal EXTENDEDTRACKED pose. This can occur after the Device Tracker recovers from limited tracking state, e.g. If the camera of the device was covered while moving. Once the inferred pose of the target or anchor is estimated more accurately, it will again start to report EXTENDEDTRACKED poses. If your application requires exact target alignment, it is recommended to discard LIMITED poses of targets since they may have a large offset from the original target location. If accurate alignment is less of a concern, then using LIMITED poses may provide a more continuous tracking experience.Other.

Added commercial support for Unity as a Library. For more information, please see the developer manual at. Added a new feature to create Instant Image Targets at runtime from images, without requiring a Device Database.

Targets can now be created from image files or directly from pixel buffers using a new RuntimeImageSource class or directly from the Editor in Unity. N/AUnity.

Fixed compiler errors seen in the Unity samples with Unity 2019.3 beta 8 and later.Known IssuesAllModel Targets. Model Targets may switch to EXTENDEDTRACKED more often during very fast user motion when the motion hint is set to STATIC. We recommend using ADAPTIVE if robust tracking during very fast motions is required. A wrong EXTENDEDTRACKED pose might be reported for Model Targets and other object targets after the Device Tracker recovers from limited tracking state. This is seen e.g. If the camera of the device was covered while moving, and it is mostly seen on devices where ARKit and ARCore are not supported and VISLAM is used for device tracking.

The target pose will be corrected once the target comes into full view again and can be re-detected. If your application requires exact target alignment in such scenarios, it is recommended to discard EXTENDEDTRACKED poses of targets after the Device Tracker reports a LIMITED tracking status info. The target should only be considered tracked again if its tracking status is reported as TRACKED. In Unity, this is best implemented in a custom TrackableEventHandler script. Model Targets may rapidly switch between TRACKED and NOPOSE when tracked from a large distance without device tracker being active. The native Model Target’s GuideView interface still uses the old y-down camera coordinate system convention in the getPose/ setPose methods.Environments. Under certain conditions when doing fast motions during Extended Tracking using Fusion-provider VISLAM, an apparent shift in augmentation might be observed.

Approaching the original target and/or resetting Device Tracker will resolve the issue.Other. The improvement to detect Image Targets at a greater distance introduced in SDK 7.5.20 does not apply for Cloud Targets. Mid-air anchors are now stabilized to the environment map when using Vuforia Sensor Fusion. Vuforia Engine v8.5.8Bugfixes / FeaturesAllModel Targets. Added a new API to control CPU usage for specific tracking features. In this release, it is only implemented for Model Targets. The API provides a motion hint property, defined in the Object Target class.

Setting the motion hint to STATIC will put the Model Targets tracker into a new tracking mode which is less CPU intensive when the object is moved. The assumption though is that the physical object is absolutely static with respect to the environment, e.g. A large machine. The initial value for the motion hint is defined in the Model Target Generator when the database is created, and it can be changed via native and Unity APIs. See for more information on API usage and on.NOTE: For existing databases created with older versions of the Model Target Generator, the motion hint will default to STATIC, resulting in the new less CPU intensive tracking mode. To return to the old performance on moved objects, please set the motion hint to ADAPTIVE, either in the Unity editor, through an API call or by manually editing the database.xml file.

The Model Targets sample databases have been updated to include the new motion hint. Both models have been set to ADAPTIVE to demonstrate best-practice for small objects that potentially could be picked up.

Fixed an issue where Model Target augmentations appeared slightly shifted in Unity Android apps after a pause-resume.Environments. Improved the availability of DeviceTracker poses when Vuforia VISLAM is in use (non ARKit/ARcore devices). In past releases the DeviceTracker might stop producing poses in challenging tracking situations. The user was required to point the camera to a previously seen view to restart operation.

In 8.5 Vuforia VISLAM will transition to LIMITED operation instead and restart automatically when possible. The system will correct drift accumulated during the LIMITED phase as soon as the user points the camera to a view seen during a previous tracking phase.Other. Support for slot-in viewer type devices and Rotational Device Tracking have been removed. Please see the Vuforia SDK 8.3 release notes for more information about the API. If you need 3DOF tracking, you can now use the PositionalDeviceTracker and use only the rotation part of the pose. Vuforia Engine v8.3.8Bugfixes / FeaturesAllModel Targets. The Model Target trained feature has been consolidated and merged into the Model Target feature.

Unity. Fixed a compiler error in Unity 2018.4.Known IssuesAllModel Targets.

Contradicting documentation ModelTarget::setSize returns true when the dataset is active, while it shall return false. Calling startRecognition on a ModelReco TargetFinder after failure of startInit may lead to a crash. Activating a Trained Model Targets Dataset via ObjectTracker::activateDataset will result in the first Model Target of the dataset being active in the Tracker. UWP. Improved stability of target tracking on HoloLens devices. Fixed an issue with slower detection when using trained Model Target datasets on UWP devices.Unity. Improved stability of target tracking on HoloLens devices.

Fixed an issue where an offset was added to trackables if a scene was additively loaded on HoloLens. Fixed issue in the Unity Extension where an extracted Model Target prefab contains incorrect scale on systems with a regional number format where the decimal point is not '.' . Fixed an issue where augmentations had an offset on HoloLens if the ARCamera was not placed at the scene origin.

For this to work, please make sure that the ARCamera in your scene is tagged with 'MainCamera'.Known IssuesAllModel Targets. Contradicting documentation ModelTarget::setSize returns true when the dataset is active, while it shall return false. Calling startRecognition on a ModelReco TargetFinder after failure of startInit may lead to a crash. Activating a Trained Model Targets Dataset via ObjectTracker::activateDataset will result in the first Model Target of the dataset being active in the Tracker. Model Targets. Added a new feature to add multiple viewpoints to a model target dataset.

Added a new feature to train Model Target Databases containing multiple views and/or multiple objects with automatic recognition. Refer to the documentation Trained Model Target Datasets on how to use these databases. The Model Target feature has been improved to snap more accurately and allow tracking of less complex objects.

The number of false positives on Model Targets detection has been reduced. Various improvements to Model Targets tracking stability have been made. Fixed an issue where the Model Target Guide View would be displayed wrongly in portrait mode on non-16:9 devices (e.g. IPhone X, Galaxy S8/S9).

Vuforia Engine v7.2.20 Bugfixes / FeaturesAll. The Coordinate System of the Camera has changed to an OpenGL convention (x right, y up, - z forward).

All the trackable poses (ImageTarget, CylinderTarget, MultiTarget, VuMark, ObjectTarget, ModelTarget, Anchor, DeviceTrackable) are now all reported in World Coordinate System. Unity developers are not impacted by this change. Please see the for more information. Introducing multiple plane support for Ground Plane. Vuforia Engine v7.1.35 Bugfixes / FeaturesAllN/AAndroidN/AiOS. Fixed an issue where memory was not being freed when closing Vuforia Engine on ARKit devices. Fixed an issue on ARKit 1.5, iOS 11.3 and above where anchors could be flipped following a re-localization by ARKitUWPN/AUnityN/AKnown IssuesSee: and belowAllN/AAndroidN/AiOS.

When producing iOS apps for App Store or Ad Hoc testing (using an Archive build), the app may crash on startup or exit. This may be worked around by setting 'Additional Strip Flags' to '-u' in Xcode's Build Settings.UWPN/AUnityN/A. Vuforia Engine v7.1.34 Bugfixes / FeaturesAllN/AAndroidN/AiOS. Added support for iOS 11.3 and Auto-focus support from ARKit 1.5 is now available.

1080p at 60Hz is now the default resolution. armv7s architecture is no longer supported. Vuforia Engine v7.1.31 Bugfixes / FeaturesAll. Ata manual guide.

Introduced new APIs to access Device 6-DoF pose. See Vuforia::State::getDeviceTrackableResult. Introduced new APIs to access current tracking state. Vuforia Engine v7.0.43 Bugfixes / FeaturesAll. Vuforia Engine continues to expand the number of devices that support Ground Plane by adding support for select Android devices and iOS devices that do not support ARKit. Vuforia Engine v7.0.36 Bugfixes / FeaturesAll. Introducing Vuforia Engine Ground Plane feature that supports anchor positioning on surfaces and in mid-air for iOS.

Introducing Model Targets feature for detection and tracking of objects defined by their 3D modelAndroid. Introducing Vuzix M300 Monocular eyewear device support. Vuforia Engine now supports Android devices on the x86 CPU architecture. Added a new reset api to the PositionalDeviceTracker that destroys all anchors. User Calibration profiles for eyewear devices are now stored within the Vuforia Calibration App. Any calibration profiles created with an earlier version of Vuforia Engine will not be accessible to either the Vuforia Calibration App or Vuforia Engine Apps created using Vuforia Engine 7. Vuforia Engine v6.5.25 (patch 2) Bugfixes / FeaturesAll.

Fixed an issue where old trackable information was retained in State even after stopping a trackerUnity (2017.2.0p3)N/AAndroidN/AiOSN/AUWP. Fixed a crash in Vuforia::onResume on HoloLens. Added error message when using IL2CPP with UWP. Note that Vuforia Engine only supports.NET scripting back-endKnown IssuesAll SDKsNoneAndroid. Tango support has been deprecated and will be removed in Vuforia Engine 7. Enabling Multi-threaded rendering on ODG R-7 can result in a crash or incorrect stereo rendering. Disable multi-threaded rendering for any projects targeting ODG R-7.

Backpack starter second edition. Scene camera position for HoloLens apps must be at the scene origin (Transform Position = 0,0,0) or augmentations will be incorrectly positioned.