[MCPE-17987] When you enter the portal nether the player gets stuck and unable to move for a few seconds Created: 05/Nov/16  Updated: 04/Sep/18  Resolved: 04/Sep/18

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

Type: Bug
Reporter: FREDDYFAZBEAR (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None

Confirmation Status: Confirmed
Platform: Tablet - Android - Samsung Galaxy Tab 2
CHK:

 Description   

Update by Bemoty:
Summary:
When entering a nether portal, there is a very short lag before the loading screen appears.

Steps to Reproduce:

  1. Jump into a nether portal in creative mode and keep moving the mouse

Observed Results:
The game lags for a moment before the loading screen appears

Expected Results:
The loading screen appears instantly without lag.

Screenshots/Videos attached: No


Original Description:

When you enter the portal nether the player gets stuck and unable to move for a few seconds



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 04/Sep/18 ]

Cleaning up old tickets: This ticket has not been updated recently (1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

Comment by Thomas Kreeger [ 12/Jan/17 ]

confirmed iPad 4 / iOS 10.2 / MCPE 1.0.1.

Also, the first time crossing a portal is usually quick, "Generating Terrain" dirt screen shows nearly immediately. Each time back through leaves the GUI frozen for more and more seconds until the dirt screen loads, and then the terrain progress indicates that it takes slightly longer and longer to complete.

If you wait a few minutes, before going through a portal, then it goes back to being quick again. Seems to be worse with local multiplayer for all players.

Comment by PHO [ 06/Nov/16 ]

Confirmed on iOS / iPad 3rd gen.

Generated at Sat Jan 11 15:17:35 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.