[MCPE-11910] Green Screen After Splash Screen Created: 01/Dec/15  Updated: 21/Aug/17  Resolved: 21/Aug/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.13.0
Fix Version/s: None

Type: Bug
Reporter: Matt S
Resolution: Cannot Reproduce Votes: 0
Labels: None

Attachments: PNG File 3cfb0X0.png     PNG File jbmQdif.png    
Issue Links:
Duplicate
is duplicated by MCPE-14009 Greenscreen Which Makes Game Unplayable Resolved
Relates
relates to MCPE-10402 When I Enter A New World A Mysterious... Resolved
Confirmation Status: Unconfirmed
Platform: Windows

 Description   

After the 0.13.0 update, MCPE displays a green screen after the splash logo. I can still interact with menu options despite the green screen. If I manage to load up a world, the world loads and works fine, but all 2D UI isn't rendered (ex: sign text, hotbar, crosshair, etc).

This only happens on one of my PC's, and 0.13.0 works fine on all my other computers. The affected PC is using 2 Nvidia GTX 980's, and the Nvidia driver is version 358.91. The issue does not appear to go away after updating drivers.

This issue is different from MCPE-10402, since this happens immediately after the splash screen and not upon loading a world. This issue also appeared only after the 0.13.0 update, and didn't exist in 0.12.x



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 21/Aug/17 ]

This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+)

Comment by AMAN4700 [ 02/Jun/16 ]

Does this bug still appear in 0.14.3? Please respond.

Comment by Matt S [ 16/Jan/16 ]

The problem somehow went away after using a new monitor. I still do not know what the actual cause behind the issue was, or what exactly fixed it. It seems related to MCPE because this issue happened immediately after updating to 0.13.0 and launching game, where just prior to updating the game still worked fine.

Comment by Jesus Palacios [ 25/Dec/15 ]

This "Green Screen" Still Appears In 0.13.1!

Generated at Sat Jan 11 14:53:58 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.