Releases: Azure/azure-remote-rendering
Releases · Azure/azure-remote-rendering
Release 1.0.7
Important Service Updates
- SDK updated to version 1.0.7
Bug Fixes
- Add Unity scene changes from the Validate Project Tool to the undo stack, so they are correctly preserved. Fixes #22.
- Changed
ARRServiceUnity
's auto-renewal logic: elapsed session time is now taken into account when calculating session renewal time. Fixes #33. - Fixed a bug where the conversionToolVersion value in .info.json files was a constant string rather than an actual version.
- When the service cannot convert a model because it exceeds system resources, we now record that fact in the .result.json file.
- Connection state changes are now immediate on connecting and disconnecting (issue #32).
Sample Updates
- Showcase: update MRTK dependency to 2.5.1 and move to packages. The assets are therefore not part of this repository anymore.
Release 1.0.6
Important Service Updates
- SDK updated to version 1.0.6
Features
- Adding support for Unity skybox (issue #27)
- Adding support for multi-sampled antialiasing for Unity Editor and Desktop-based Unity applications (issue #26)
- Video streaming CPU usage reduced by around 10%.
Bug Fixes
- Fixed possible deadlock on disconnect when using wifi on desktop (issue #29)
- Per-frame CPU time is now reported more accurately in performance assessment queries.
- Fixed an issue introduced in 1.0.5 in our low level network stack that could potentially cause a blue screen.
Sample Updates
- All samples: replace uses of "account domain" by "remote rendering domain" and "account authentication domain" by "account domain" for consistency with the API.
- Scripts: change package registry for Azure Spatial Anchors packages in
unity_sample_dependencies.json
Release 1.0.5
Important Service Updates
- SDK updated to version 1.0.5
Features
- CPU usage of video streaming reduced by ~35% on HoloLens2.
Bug Fixes
- Fixed an issue where a failed connection attempt would cause the server to take 20sec to timeout instead of the intended 5sec, resulting in TransportPortBusy response on further connect attempts until the 20sec timeout was hit.
- Added improvements to reduce the likelyhood of a client failing to connect with result TransportPortBusy. The client should now receive TransportConnectionFailed in case the UDP transport connection failed.
- Removed ambiguity in namespace resolution for
Windows.Storage
andWindows.System
in ARRServiceUnity.cs.
Sample Updates
- Tutorial-Complete: Improved error handling in
RemoteRenderingCoordinator.cs
Release 1.0.4
Important Service Updates
- SDK updated to version 1.0.4
Bug Fixes
- Misc stability fixes for client libraries.
- Fixed arrInspector "collect debug information" feature not working.
- Fixed a rare crash when losing tracking on HoloLens2.
Sample Updates
- All Unity samples: update Unity version to LTS 2019.4.
- All Unity samples: unify project names and meta information.
- Showcase: support non-GUID ids for session overrides.
- Showcase: show current session id in session performance panel.
- TutorialAssets: update TutorialAssets.unitypackage.
Release 1.0.2
Important Service Updates
- SDK updated to version 1.0.2
Bug Fixes
- Fixed incorrect projection when using planar LSR which caused jittering.
Release 1.0.1
Important Service Updates
- SDK updated to version 1.0.1.
Bug Fixes
- Fixed an internal error which could cause conversion to fail. It occurred when the number of normals in a mesh didn't match the number of vertices.
- Fixed issue #23: Clipping Fade Colour and Length reset after toggling clip enabled state of a Clip Plane.
- C++ and C# API calls to start/stop a session and start a conversion now have a built-in retry mechanism (e.g. to compensate for network timeouts).
Release 1.0.0
Important Service Updates
SDK updated to version 1.0.0
With this release Azure Remote Rendering leaves the public preview phase and becomes a fully fledged Azure service. We'd like to thank all our amazing partners for their feedback that helped us to get ARR into shape for this milestone.
API Changes
- The enum value
Status::Success
has been removed to avoid confusion with the real success code, which isStatus::OK
.