The main menu on certain computers. For mine for sure has it.
Has extremely severe CPU lag. It shows a pause, unpause kind of effect at a set intervel of 1 - 3 seconds and unfreezes 1 second after it freezes..
It effects not just the game but the Entire computer. Only when in the main menu. This bug might not be able to be fixed however.
A new option to be able to be toggle would help a lot for some people.
An option to disable the panorama view on main menu screen will help greatly. Bug can't be pinned pointed from my end on what does it. But it occurs no matter what when in main menu when you first launch game.
UPDATE:
In latest snapshot 13w41b
This issue spread to the ingame menu's also. The game is slowly becoming unplayable.
Linked issues
Attachments
Comments 12
The issue might still be present in 1.5.1 I will check. I would suspect it will still be present for all versions with animated background on main menu screen.
The issue might still be present in 1.5.1 I will check. I would suspect it will still be present for all versions with animated background on main menu screen.
Issue still is there.
There is a simple fix for this. Well its like a fix. Add a new option to options to disable background animation and use the old static dirt background.. From whatever version that was 😛
This issue is quite annoying. Especially if someone forgets that they opened minecraft and they are using another application...
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Can we just add a new option to the options menu to disable the animated menu and use the old dirt background or something. This bug might be a bug with specific video cards or something.
I can no longer update ticket. I no longer run on the affected operating system..
The issue is not present on my current computer.
This proves to be a system dependant issue.
I recently got a new computer.
This ticket is incomplete, because we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.
Please review the guidelines before reporting issues.
Confirmed in 13w02b.