Below you will find all the latest changes being introduced with ARES 1.0.3.0. Now available in the Microsoft Store. This release is focused on feedback we’ve received from users via our Feedback and Support Portals.
OVERVIEW
IMPROVED - Smart User Notifications during Multi-User Sessions - i.e. when leaving a session, joining a session.
IMPROVED - Instead of showing IP addresses in user lists/notifications, display names are presented during Multi-User Sessions.
IMPROVED - Users are able to continuously jump up to the next parent from the button up while using smart selection and highlighting the inherited parent.
IMPROVED - Listing of Multi-User Sessions remains persistent throughout the session's active state.
IMPROVED - Correct order of objects for all connected users is assured when deleting an object in a Meeting Session.
IMPROVED - Object Movement in Realtime Interaction is now shared with all connected Clients, ensuring a fluid movement experience throughout.
IMPROVED – Bounding Box no longer provides one-handed rotation of an object. A new Selection Tool allows now for free-hand rotation.
FIXES
As part of our mission we continuously aim to improving ARES. And bugs are no exceptions. Based on feedback from users, partners and internal developers the following bugs have been squashed.
FIXED – Settings - Running multiple Microsoft Accounts on one HoloLens device calls/renders Settings Menu twice - resulting in unusability
FIXED – GUI - Graphical user interface not optimally adapted to User Experience
FIXED – Licensing - Release License button appears greyed out or does not function
FIXED – Licensing - Generated E-mails from Licensing Portal are incorrectly marked as spam/quarantined as phishing
KNOWN ISSUES
Below you will find a list of known issues. These issues are defined as bugs, or at times missing features, that is known to the development team and are being actively investigated or developed.
- JT VERSIONS 9.X & 10.X – The importer is experiencing performance drops on UWP ARMx64. Due to this constraint we’ve opted to exclude this functionality from 0.9.3.0 to avoid a degraded user experience.
Comments
0 comments
Article is closed for comments.