documentation
Release date: 01.02.2019 Release info: New Year Pre-Release
lineSearchLengthTracking and lineSearchLengthTrackingRelative value of a model-based tracking configuration at runtime didn't work since version 18.9.1. Changing them should now work properly again.-portrait to the deviceID. The calibrationDB has been bumped to v2 therefore while it still has its old format. When loading an 'old' (version 1) camera calibration data base, all intrinsics having an aspect < 1 will be saved twice interally (rotated CCW) and with deviceID-portrait.*.mtl) files of 3D models will no longer lead to an error, but will output a warning. This will not affect the tracking quality. device, deviceID, calibration or calibrationURI) were specified (the "camera" image source already behaved like this). Previously some arbitrary other camera calibration was used in this case, which would cause big problems, if the aspect ratio of the camera image was different from this calibration.resolution in the generic input section (see External SLAM (ARKit/ARCore) Support or Configuration File Reference)WindowsSpeechRecognitionBehaviour.cs). It is included in the HoloLens example. Saying change model will switch the tracking model (and the displayed content).keyFrameRotation parameter of the model-tracker at runtime."camera" image source on Windows systems. See the "Controlling Camera Parameters" section of Handling Input Sources for further details. vlWorker_PollEvents / vlWorker_WaitEvents call. Previously the events of up to 5 frames were buffered and the registered listeners were notified in rapid succession. This could cause performance issues.vlWorker_PollEvents / vlWorker_WaitEvents. Previously a slow event listener could cause a displacement between the different event types (e.g. the camera pose is newer than the camera image).VLRuntimeParameterBehaviour didn't work correctly on Windows systems with certain region settings. The VLRuntimeParameterBehaviour should now be independent from the region setting.keyFrameRotation parameter to the VLRuntimeParameters_ModelTracker_v1 prefab.keyFrameRotation parameter to the AdvancedModelTrackerExample scene.local_storage_dir scheme in the filename given to the VLWorkerBehaviour.StartTracking function. Since the directory pointed to by local_storage_dir is writeable, one can update the vl-file without having to re-deploy the whole application. Take a look at the "Integrated Schemes" section in Configuration File Reference to find out to which directory the local_storage_dir scheme points for each platform.VLModelTracker_v1 behaviour has been added, which will encapsulate all relevant functions for the ModelTracker pipeline.setModelURI function to VLWorkerBehaviour.cs. With this function, the URI of the model used for tracking can be changed during runtime.ChaneModelBehaviour.cs. This behaviour enables the user to exclusively switch between several models in both displaying and tracking.AdvancedModelTrackerExample scene. With this button, one can switch between different models.