Search Issue Tracker
Fixed in 5.5.2
Votes
3
Found in
5.4.0b14
Issue ID
788515
Regression
Yes
[iOS][Airplay] Camera.SetTargetBuffers doesen't work with GLES2/3
To Reproduce:
1. Build and run the attached project with GLES2 or 3.
2. Enable Airplay with mirroring on your device.
3. Click the 'Two Buffers' toggle.
4. Observe that either both the displays start rendering a black screen, or Display.displays [1] buffer is rendered on top of the main display.
Not reproducible with Metal and on trunk with gles
Comments (1)
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
gamecakestudios
Dec 19, 2016 05:46
I am currently able to reproduce this bug in Unity 5.5.0p2 on GLES2, GLES3 and Metal. All 100% repro for the black screen bug. When was this fixed? It appears to have regressed.