Releases: needle-mirror/com.unity.xr.oculus
Releases · needle-mirror/com.unity.xr.oculus
4.5.0
[4.5.0] - 2024-12-11
Added
- Added Optimize Multiview Render Regions setting for Meta Quest devices. Multiview Render Regions enables the GPU to skip shader invocations (and rendering work) for screen areas outside of the user's view. Requires Vulkan and Multiview
Changed
- Reorient position delta of SpaceWarp's app space delta position to be relative to the current view space
- Changed build process to keep Bluetooth permissions tag if present in the manifest
Fixed
- Fixed an issue where headtracking would get desynced after switching from Game view to Scene view when using Meta Quest Link
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtimeUnity.XR.Oculus.Stats.AppMetrics
entries return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/
Acceleration
andAngularAcceleration
values on tracked poses currently return0
when using the OpenXR runtime. This is a limitation of the OpenXR API
4.4.0
[4.4.0] - 2024-09-26
Added
- Added Quest 3S target device checkbox
- Updated the
SystemHeadset
enum to includeMeta_Quest_3S
andMeta_Link_Quest_3S
entries
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtimeUnity.XR.Oculus.Stats.AppMetrics
entries return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/
Acceleration
andAngularAcceleration
values on tracked poses currently return0
when using the OpenXR runtime. This is a limitation of the OpenXR API
3.4.1
[3.4.1] - 2024-09-10
Fixed
- Made Y-flip logic consistent across engine and XR providers
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtime, which is the default in the 2.x and 3.x versions of the Oculus XR Plugin packageUnity.XR.Oculus.Stats.AppMetrics
entries currently return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/
- Enabling mobile Depth Submission may cause crashes on application startup if MSAA is disabled. Enabling MSAA will resolve the issue. This will be resolved in future versions of Unity
4.3.0
[4.3.0] - 2024-07-30
Added
- Added support for Unity's new common Foveated Rendering API, with improved URP support
4.3.0-pre.1
[4.3.0-pre.1] - 2024-07-18
Added
- Added support for Unity's new common Foveated Rendering API, with improved URP support
Changed
- Improved Symmetric Projection texture resolution calculations
Fixed
- Fixed an issue with eye poses being incorrect in certain situations
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtimeUnity.XR.Oculus.Stats.AppMetrics
entries return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/
Acceleration
andAngularAcceleration
values on tracked poses currently return0
when using the OpenXR runtime. This is a limitation of the OpenXR API
3.4.0
[3.4.0] - 2024-02-12
Changed
- Bumped up required XR Management version to 4.4.0 to fix issues with Android Manifest cleanup
- Updated documentation to inform users that Phase Sync is always active when using the Oculus OpenXR Runtime
Fixed
- Removed Android manifest cleanup that removed the manifest file, existing projects need to do a clean build to completely remove the issue
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtime, which is the default in the 2.x and 3.x versions of the Oculus XR Plugin packageUnity.XR.Oculus.Stats.AppMetrics
entries currently return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/
- Enabling mobile Depth Submission may cause crashes on application startup if MSAA is disabled. Enabling MSAA will resolve the issue. This will be resolved in future versions of Unity
4.2.0
[4.2.0] - 2024-01-18
Added
- Environment Depth APIs to allow for real world depth to be sampled from a depth texture
Changed
- Updated
GetConnectedControllers
to match the Oculus Integration Package's implementation - Removed PhaseSync setting since it is now always active
- Updated Oculus plugins to v60
Fixed
- Fixed issues with play in editor on ARM64 Windows devices
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtimeUnity.XR.Oculus.Stats.AppMetrics
entries return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/
4.2.0-exp-env-depth.2
[4.2.0-exp-env-depth.2] - 2023-12-14
Added
- New Environment Depth APIs:
bool GetEnvironmentDepthSupported()
bool GetEnvironmentDepthHandRemovalSupported()
bool SetEnvironmentDepthHandRemoval(bool isEnabled)
Changed
- Updated Oculus plugins to v60
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtimeUnity.XR.Oculus.Stats.AppMetrics
entries return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/
4.1.2
[4.1.2] - 2023-11-06
Fixed
4.2.0-exp-env-depth.1
[4.2.0-exp-env-depth.1] - 2023-10-06
Added
- Environment Depth APIs to allow for real world depth to be sampled from a depth texture
Known Issues
Unity.XR.Oculus.Stats.PerfMetrics
entries currently return0
when using the OpenXR runtimeUnity.XR.Oculus.Stats.AppMetrics
entries return0
on all Oculus runtimes- For both of the above, the suggested replacement is to use the profiling tools available via the Oculus Developer Hub: https://developer.oculus.com/documentation/unity/ts-odh-logs-metrics/