Search Issue Tracker
Fixed in 2018.3
Fixed in 2017.4, 2018.2
Votes
14
Found in
2018.1.6f1
2018.2.0b9
Issue ID
1052530
Regression
Yes
[Android] Blit Type "Auto" or "Never" causes Android to show black scene
To reproduce:
1. Download attached project "VRUnity2018-2b9.zip" and open in Unity
2. Open "SampleScene" scene
3. Set Android platform
4. Go to Player Settings > Resolution and Presentation and set Blit Type to "Auto" or "Never"
5. Run logcat
6. Build and run the project on an Android device
7. Observe that Build shows a black screen and there is no Unity splash screen
Notes:
- Logcat is shared in the comments section
- This issue is reproducible only on Android devices
- This issue is not reproducible in iOS devices
- This issue is not reproducible in Windows and OSX Standalones
- This issue is not reproduced in Editor
- Workaround: Switching to Blit Type to "Always" fixes the problem.
Devices:
- Samsung Galaxy S9, OS: 8.0.0, CPU: arm64-v8a, GPU: Mali-G72 - Reproduced
- Google Pixel 2, OS: 8.1.0, CPU: arm64-v8a, GPU: Adreno (TM) 540 - Reproduced
- iPhone 7, iOS: 11.2.6, CPU: A10 - Not Reproduced
Reproduced on Unity 2018.1.6f1, 2018.1.7f1 and 2018.2.0b10 and 2018.3.0a3
Not reproduced on Unity 2018.1.5f1
Regression on Unity 2018.1.6f1
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
- 'Can't add script' pop-up warns about abstract classes when dragging static classes onto GameObjects
- [Hub] Project "Remove from list" option is behind notifications when selecting the most bottom project in the list
- [Android][Vulkan] Black Screen renders on devices with Adreno 640 and Mali GPU's
- Sound/Audio is played when the VideoPlayer's attached AudioSource game object is disabled
- Editor crashes on GenerateSharedVerticesIndexList when importing .3ds file
DogDuck
Jun 19, 2019 12:17
same problem in version 2018.4.1f1
Un4GivN_X
Oct 17, 2018 18:54
I just spent almost a day trying to solve this issue. Following this thread, I started by changing the blit type to never/always/auto without any success.
My project is using unity 2018.2.5f1 + Lightweight renderer. Everything was looking fine until I added a hud camera with the clear flag to Depth only.
Then, I installed and tried all the variants on 2018.2.12f1 and 2018.3.0b5. Same blackscreen.
I started to mess around with every properties that seemed related. I've found that LightweightPipeline -> Render Scale is equal to 1 *AND* that LightweightPipeline -> Depth Texture is DISABLED, it fixes the black screen issue.
I don't totally understand the internal issue here but it's a shame that the Render Scale property isn't working :( I was hoping to tweak this value a lot since our vuforia game is draining to much cpu and power.
tlbon
Oct 09, 2018 12:44
happens also without VR. we've had Never on for ages now and suddenly with unrelated changes commit it stopped working. have to put always or black screen on android versions <7.0
khota_sikka
Aug 15, 2018 11:20
In unity 2018.2.2f1 , On building android VR app , It shows only black screen ,Blit Type to choosen Auto , Always and Never, in all three cases same situation kindly resolve urgently
Feelnside
Aug 02, 2018 04:09
The issue is still reproducible. Used Unity 2018.2.1f.
Is't really fixed? Could you please provide the "future version" where it is fixed?
Antony-Blackett
Jul 25, 2018 04:04
It broke in Unity 2018.1.6 and is still broken in 2018.2.0f2 it works fine in 2018.1.5f1
Davee
Jul 23, 2018 14:10
Found in 2018.2.0b9, Fixed in Unity 2018.1?
Seanm07
Jul 19, 2018 15:49
Leaving a comment incase anyone else encounters the form of this issue where the game is transparent rather than black as what happened in my case.
It caused the app to just not render rather than render black making the last frame of whatever was on the screen as you launched or switched to the app just appear frozen on the screen. (However the app can still be used as normal, it's just that you can't see anything)
Issue happened on my Samsung Galaxy S7 Edge and switching Blit Type to "Always" fixed the issue.