Search Issue Tracker
Fixed
Fixed in 0.4.5-exp.1
Votes
0
Found in [Package]
Issue ID
AXRB-148
Regression
No
ARCameraManager continuously tries to create light estimation tracker even after it fails
Sometimes a device may not support light estimation, therefore everytime ARCameraManager tries to call TryGetLatestFrame the native code should not continuously try to create light estimation tracker if light estimation is not supported, otherwise it spams the log.
[https://github.cds.internal.unity3d.com/unity/xr.sdk.androidxr-openxr/blob/main/com.unity.xr.androidxr-openxr/Source~/Source/Providers/CameraProvider.cpp#L22]
This function should probably have a check if it tried to create light estimation tracker previously but failed due to no support, it should not try to create a tracker again.
In essence, there should be some sort of mechanism to not spam log and have a one time error mentioning that light estimation will not be used if it failed to create light estimator due to unsupported error.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment