Search Issue Tracker
Won't Fix
Votes
3
Found in
2018.4
2018.4.15f1
Issue ID
1267970
Regression
No
[Hololens] Textures are not rendered when using Camera.SetTargetBuffers
How to reproduce:
1. Open the attached "UWPTest.zip" project
2. Build to UWP
4. Open the Visual Studio Solution file, located in the built project's directory
5. Select the target: Remote machine with Release and x86 options
6. Build and Deploy to Hololens
Expected result: Textures are rendered successfully when using the Camera.SetTargetBuffers
Actual result: Textures are not rendered when using Camera.SetTargetBuffers (see actual.png)
Reproducible with: 2018.4.26f1
Not reproducible with: 2019.4.8f1, 2020.1.2f1, 2020.2.0a20
Notes:
- The issue is reproducible with .NET and IL2CPP backends
-
burns
Sep 01, 2020 14:36
Ha, um ... I appear to have missed the "Resolution Note" when I was reading the first time.
Well, that's embarrassing. :o)
-
burns
Sep 01, 2020 14:35
Won't fix?! Oh, come on Unity folks! At least give us a comment as to why you made that choice. :o(
-
mlongtin
Aug 24, 2020 16:00
This issue is hindering me, as well. Please address this. Many thanks.
-
colin_sullivan
Aug 24, 2020 15:44
This is a major issue that is severely hindering my development for the HoloLens. Please fix!
-
unityUser1120
Aug 18, 2020 12:48
I believe this issue is not limited to the HoloLens. I believe it affect any VR application where Camera.stereoTargetEye is not set to none. According to the Unity documentation, Camera.stereoTargetEye is only used if VR is enabled.
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (2018.4.X):
This issue does not occur in more modern versions of Unity (e.g., 2019.4 & 2020). Updating to more modern version of Unity is the suggested resolution to the issue.