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
- [Build Callbacks] Build is not failing when BuildFailedException is thrown in the PostProcessScene Callback
- Custom Event do not fire on builds
- [WebGL] Mouse input is blocked after a few moves when using Edge browser
- Builds that contain terrain using the Nature/Terrain/Standard shader produce errors when run in headless mode
- When the registry value for "TimeZoneKeyName" is invalid, "TimeZoneNotFoundException" exceptions are thrown
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.