Below you will find all the latest changes being introduced with AR3S (formerly known as ARES) 188.8.131.52. It was published on November 24, 2020 and is now available on Microsoft Store. This release is focused on feedback we’ve received from users via our Feedback and Support Portals as well as our product roadmap.
The 184.108.40.206 Update follows the first larger iterative version of AR3S. Its primary focus is the implementation of Content Creation features for performing Measurements. Improvements were done to the precision of the Stylus as well as to various Saving/Loading aspects.
NEW – Content Creation - Set, Save and Recall of measurement lines
IMPROVED – Stylus Measurement Cursor
As part of our mission we continuously aim to improving AR3S. And bugs are no exceptions. Based on feedback from users, partners and internal developers the following bugs have been squashed.
FIXED – Export - HLCAD Export is very slow
FIXED – JT Import - Imports unnecessary multiple materials
FIXED – Measurement - Cannot press Menu Buttons after moving a Measurement
FIXED – Measurement - Single Measurement (Start) Points remain when closing Menu panel
FIXED – Object Interaction - No Pointer passed to get focused object
FIXED – PathTypePropertyDrawer does not show the Property's name in the inspector
FIXED – Scene Management - Loading/Saving does not align imported model with aligned app world
FIXED – TMP Input Field not pressable
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.
- Application Instability w/ various versions of Stylus Toolkit – In some rare scenarios, the AR3S application may experience a crash when utilizing the stylus. This is dependent on the integrated version of the STK (Stylus Toolkit). Please insure that you're on the latest firmware version of the StylusXR and AR3S.
App crashes when using Stylus – From time to time there are app crashes occurring while Stylus is in usage. We are investigating what exactly is causing this malfunction and plan to fix it as soon as possible.
Main Menu breaks when clicking Real World Reference Button during Menu Close/Open Animation – Once the app registers a click on the “Toogle Real World Reference” button while the Main Menu Animation is running, the Main Menu cannot be operated anymore.
Multi-User disconnects when manipulating a shared object – When manipulating an object while it is being (exported and) shared with another person in Multi-User, the connection is lost and cannot be recovered.
Import Scale for objects saved as HLCAD is not correct – When saving non-HLCAD objects as HLCAD the difference in import scales is not taken into account.
User Experience must be revamped– Several Buttons are hard to press and the Far Interaction feels clunky at times. When using Far Interaction e.g. to rotate an object with the Rotation widget, the interaction feels blocked. Some placeholder texts have to be reworked for a more polished User Interface.
Licensing QR Codes may be difficult to read – QR Codes without border are possibly not readable when displayed on a black surface. As the licensing website has set up a white background you can read the QR Code on the webpage without issues.
Proxy Server prevents communication with Licensing Server – If there is a Proxy Server between the devices using the AR3S licensing and the Licensing Server, communication does not work. Which direction exactly is blocked/hindered (possibly both) has to be investigated.
Interaction Input is possibly blocked by Scrollbar – Scrollbar blocks Near Interaction Touch, if the Poke Pointer is near to the scrollbar.
- Multi-User – Random Network Adapter – Starting a Multi-User Session on a PC as a host can result in the Networking Library taking a networking adapter by random, possibly a virtual adapter. These preinstalled virtual adapters have to be explicitly activated in Windows 10, proving as taxing for non tech-savvy users. We are currently on the lookout for a robust solution.
- QR Code Scanning Visual too small – When a user needs to activate the license via QR Code, the visual, which indicates how far a user needs to be away, so that the camera can identify the QR Code, is too small. Therefore the user needs to be closer than the visual is indicating. This can be confusing and lead to a situation where a user thinks the QR Code scanning does not work.