SUMMARY:
When using a high definition resource pack, the game fails to automatically select a resolution that will allow the game to load.
DETAILS:
On January 14th, I attempted to log into my realm. Before connecting, it prompted me to download the texture pack. I assumed this means there was an update. I elected to download the update and it finished successfully.
I was then taken to the screen that's says Joining Realm... Loading Resources... Then Minecraft locked up and a black screen appeared. I was then taken back to the XBOX Home screen.
DEBUGGING STEPS:
The first thing I did was clear cached data on the XBOX, by holding the power button until it shut down. That didn't work.
Next I uninstalled and re-installed the game. That didn't work.
Next, I moved the game from external to internal storage. That didn't work.
Next, I downloaded my realm world locally. That didn't work.
Next, I reconfigured the world and deactivated the VanillaBDCraft resource packs. THIS WORKED!
So, I proceeded to reach out to the developer of the resource pack...
Discussion Here: January 14th update crashes Minecraft on XBOX One X
They informed me that the game is supposed to automatically detect available memory and pick the highest quality based on my system's configuration, but that sometimes it doesn't get it right. They explained how I could use the resource pack's settings "gear icon", to override that logic and force it to a lower resolution.
This solution worked.
So... That is one issue that probably needs to be looked into. The reason I'm submitting it instead of using the workaround permanently is because other people joining my realm might experience the same crash and not know how to fix it. As well as other players experiencing the same problems with their own systems.
...And... The settings under Global Resources aren't getting saved, so every time I start the game, I have to go in and configure that texture pack with a limit of 128x.
MCPE-62385 - Global Resource Settings aren't being saved
Here are two game-play videos, showing what happens...
Linked issues
Attachments
Comments 7
The VanillaBDCraft texture pack has many resolutions included...
32x, 64x, 128x, & 256x
I believe you should use that texture pack for testing, to avoid differences and increase the chances of duplicating the issue.
NOTE: When I contacted BDcraft about the problem, I was informed that they were going to push out an update, removing the 256x option from the pack. My machine has not received that update yet and 256x is still available. However, it's possible that you might get the updated pack, which would hinder your attempts to duplicate this issue.
Minecraft is supposed to pick the highest version available, that will run without memory issues on the machine.
The first time it happened, I manually set it to 128x and it worked. Later that day, the 128x caused it to crash too, so I had to set it to 64x in order for it to load. Since that time, 128x has been working.
This leads me to believe that the calculation of the memory capacity of the machine vs. the memory requirements of the pack, is yielding an invalid result.
Prior to January 14th, this detection worked perfectly. I had never needed to configure the max resolution in Global Resources. Now I have to do it every time I start the game, due to the fact that...
MCPE-62385 - Global Resources settings are not being saved between game sessions.
I should also mention that my XBOX One X is configured to be part of the "preview program", so depending on the changes coming up, the version of the XBOX Operating System that I'm running, may require more memory or contain a bug that's preventing Minecraft from accurately calculating the correct texture pack resolution.
Today I noticed that hotfix v1.14.30 seems to have fixed the memory calculation problem for me, with the VanillaBDCraft texture pack. When configuring the texture pack in Global Resources, it reports that the 256x resolution is not available due to the lack of memory.
I'm not sure if the developer pushed out an update of the pack with 256x disabled or if the hotfix contained the fix, but the problem isn't happening for me any longer.
Perhaps @Asher is using a different texture pack and can confirm the fix...
Thank you for your report!
We're tracking this issue under MCPE-40666 so I've requested this report be resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
Quick Links:
📓 Issue Guidelines – 💬 Community Support Discord – 📧 Mojang Customer Support – 📖 Game Wiki
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.Observed Results:
(Briefly describe what happens)Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Experiencing this as well on xbox.
This also means that for players on a realm who haven't purchased the pack themselves, they have no way to make it work, since they can't change the setting.