Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a4
Issue ID
1160846
Regression
No
[XR][WindowsMR] XRSettings.eyeTextureWidth and eyeTextureHeight return incorrect value at Start()
Steps to reproduce:
1. Download attached project
2. Open SmapleScene
3. Switch platform to UWP
4. Make sure that XR support is enabled
5. Enter play mode
6. Check Console window
Expected results: Start and Update method returns the same eyeTextureWidth and eyeTextureHeight values
Actual results: Start and first two frames return incorrect results for eyeTextureWidth and eyeTextureHeight
Reproduced with: 2019.3.0a6, 2019.2.0b6, 2019.1.7f1, 2018.4.2f1, 2017.4.27f1
Note:
- Not reproducible with OpenVR SDK
- Not reproducible in UWP Build
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Customer has indicated workaround by waiting before calling eyeTextureWidth or eyeTextureHeight. This does not meet our current bug bar, so we won't be fixing this.