Low FPS in after the Caves and Cliffs update using the hi-res texture pack VanillaBDCraft:
CPU/GPU utilisation does not spike, usually below 50% each
fps come back to normal after exiting specific area, seems unrelated with the amount of structures,
in x32 version of the pack FPS normal, in x64 fps were in the 30s range, but came back to 60 after picking up all dropped items, in x256 fps dropped items lower fps to 5-6 and increase safter picking up dropped items, but max out around 32,
low fps irrespectively of rendering distance (lowered 32 to 8 chunks, no change),
In the Nether FPS around 20, with wirtually no structures added
tested on backup of the same world no change,
on the same seed in creative mode entering the Nether portal causes crash of the game either instantly or under a minute after.
Minecraft version: 1.17.2.0 (not sure why it is not listed to choose)
CPU i5 4670K @4.00 GHz
GPU GTX 1080
RAM: 24 GB
SSD: Samsung 860QVO
Thanks for any help.
Related issues
Comments
kiizde
migrated
Yes, issue persisted and still persists throughout all versions from Caves & Cliffs up to current one (1.17.11).
Issue also reported to texture pack maker (BD Craft), no response so far.
migrated
Can you upload the world affected? Could not reproduce on several test worlds with C&C toggle on.
If not, that seed is affected by the issue?
migrated
The issue appears on any seed but only when using hi-res texture pack VanillaBDCraft and when dropped items are on the ground.
migrated
Thank you for your report!
We're tracking this issue in MCPE-111547, so this ticket is being 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.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Is this still an issue in the latest version (1.17.11)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.