You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Changes in this version:
Implemented Optimized ROI (Region of Interest).
The new optimized ROI will reduce CPU usage dramatically and is enabled by default.
Instead of analyzing the whole tracker stream it will analyze chunks instead to save CPU cycles.
HMDs ROI will still have the old behavior due to insufficient testing.
You can change the option in %AppData%\PSMoveService\TrackerManagerConfig.json with "optimized_roi": "true"
Implemented Projection Occlusion Areas.
Occlusion areas are created when trackers lose their projection target (e.g. when the PSmove bulb is not visible to the tracker).
The tracker will not re-gain the controller if the PSmove bulb is near the trackers occlusion area.
In some cases trackers projections can flicker (gain/lose projections continuously) if the PSmove bulb is too far away and patently blocked by objects. This will cause annoying controller jitter in pose tracking. This feature will fix this issue.
You can change the option in %AppData%\PSMoveService\TrackerManagerConfig.json with "min_occluded_area_on_loss": "4"
Improved tracking quality with multiple cameras.
Added Advanced Settings option in PSMoveService Tool for faster config access.
Added controller battery status in PSMoveSerivce Tool > Controller Settings.
Support for 6 PSmove controllers (previously 5 only)