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
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
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
- The Scene view Camera does not move when clicking the middle mouse button on a GameObject in the Scene view
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.