It seems like there is a serious problem when you try to run a game built with the default Android build settings on BlueStacks emulator. The opening scene shows a black screen without crashing. On contrary,other emulators such as LDPlayer and Memu work just fine.
This BlueStacks issue bothers me because there might be real devices out there that have a similar issue and since the scene does not crash you may never know how many real users see a black screen and can’t play your game. Keep in mind that a lot of Unity games are working just fine on BlueStacks.
SOLUTION
I thought this was specific to my game, but having tried URP and 3D templates without any scripts, I have seen that they all show a black screen.
After spending several days on this weird issue, I figured out that in build settings the following options may cause instability for BlueStacks:
My blit type was chosen “Auto”. I switched it to “Always”.
I have specifically chosen to create custom main manifest (AndroidManifest.xml) even though I should not need it.
My Unity Editor is 2020.3.9f1
Scripting backend is IL2CPP
I have the same issue. I have even tried a new URP project, it shows a black screen after the unity logo on BlueStacks. I tried checking the “Custom Main Manifest” box and changing blit type to “Always”, it still shows me a black screen. =/
I’m also having this issue (with and without URP, in a fresh project and my existing project, with custom / clean manifest). Nothing obvious in adb logcat to shed light on the issue.
Did’nt saved me, is there a different alternative please ?
If the game is released in play store marked with Optimized Frame Pacing , and when installed in bluestacks through play store it gives black screen…
What if the production build was supposed to build with Optimized Frame Pacing.
I cannot maintain two different builds with this one single change.
punkrooks, Did you find any solution for this?
disabling Optimized Frame Pacing would fix bluestack problem but then the game run a little more jittery in android device!
this looks like a big issue, has anyone else found a solution for it?
I wonder is this a bluestack only issue or could it be an issue also for some other devices/emulators? Anyway I find it’s a real shame that I have to disable that option for now, I’d like to know the solution too.