Search Issue Tracker
Fixed in 5.0.X
Votes
20
Found in
4.5.2p1
Issue ID
620787
Regression
No
BackBuffer alpha channel is always set to 1 on android devices
Alpha channel BackBuffer is always set to one on android devices from Unity 4.3
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 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
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
Sudhir.Singh2k2
Sep 11, 2014 23:47
"The only way to solve this problem right now (that I can see) is to render to an intermediate rt and then blit to the screen as a last step. This might be something we will do behind the scenes in the future if we can find a way of detecting buggy compositors. But as of now you will have to do this yourself."
Can you give example code of how to do this?
bitter
Sep 10, 2014 09:07
This was an intentional change - "Android: 32bit display buffer without alpha is now the default to avoid compositor bugs on android." (rel. notes 4.3)
The thing is that a lot of devices have problems using alpha in the screen framebuffer. Prior to 4.3 alpha presence would be random depending on the device. While working on Unity 4.3 a version of JB was released that pretty much screwed up the alpha channel on all devices so at that point we decided to make it consistent/deterministic by disabling alpha in the default framebuffer.
The only way to solve this problem right now (that I can see) is to render to an intermediate rt and then blit to the screen as a last step. This might be something we will do behind the scenes in the future if we can find a way of detecting buggy compositors. But as of now you will have to do this yourself.
ps. I didn't close the bug with "by design" because I would really like to find a solution to this problem.