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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.