Copied and pasted from my reddit post to maintain consistency:
"EDIT 1, Jun. 14th: While not solved entirely, the issue has been narrowed down almost certainly to high resolution texture packs on certain Windows 10 edition hardware configurations regardless of machine capabilities, anything I've tried at 16x16 works fine on the "buggy" machines, but any higher and frame drops start immediately, if anybody has any other insight aside from what's already in this post, it'd be greatly appreciated.
Sorry if this is long winded, I'm detailing EVERY step of troubleshooting I've done to prevent redundancy.
1.16 ran like a dream (like every prior release of bedrock has on my hardware), I host a private server for 3 (total) on multiple different machines usually for 3-6 months at a time, and haven't had a problem with Bedrock performance on any of my devices... until 1.17 released.
To preface, the machines I've tried this on that DO have performance problems after updating to 1.17 include (all w10):
My main Rig:
Ryzen 5 3600x (tried with my new 5800x in the same configuration, same results)
EVGA GTX 1080
16gb DDR4-3200
500gb boot SSD w/multiple HDDs
My laptop:
i7-7700hq
GTX 1050 ti
16gb DDR4-2400
500gb boot SSD w/multiple HDDs
Friend 1s Rig:
i5-9400
GTX 1070
16gb DDR4-2666
500gb boot SSD w/multiple HDDs
On the other hand, the machines I've tried this on that DO NOT have performance problems after updating to 1.17 include:
Nintendo Switch
Nintendo Switch Lite
Xbox One (Base Model)
Xbox Series X
Playstation 5
One Plus 7 Pro
Pixel 5a
Friend 2s Rig:
Same as mine, but a 2060Super instead of a 1080, every other part is identical.
So, very clearly, machines that shouldn't (and for years haven't ever) had a problem playing on our server are suddenly getting lag spikes (from 120fps+ to 3, just by moving a few blocks or turning the camera, even in chunks with very little entities in them) on 1.17.
Here's what I've tried for troubleshooting:
New server files
fresh OS install on client AND server machines (Windows AND Ubuntu)
new game installs on ALL clients, even ones that did fine, no change in result
driver installs, even updating the bios on one of the boards, with no change in result
copied world, tried removing chests, all mobs including our pets, containers like hoppers, and any entities I could think of that could be causing ANY lag, no change in results
manually inspected over 240 chunks in our laggy areas for overflowing pending tick data, deleted 500 bytes of pending ticks (not a lot, pending tick data hasn't been a problem for a few updates afaik), no change in results
firewall, port forwarding, static IPs, etc, completely redone, no change in result
Frankly, I'm just exhausted.
I can't figure out why devices entirely capable can't run 1.17, especially considering nothing major was changed in world generation.
Anybody experiencing this as well, or that has any idea what could be the cause/solution, I'd appreciate the discussion 🙂)
Thanks."
Fix this, please, Mojang. It's obviously negatively effecting players enjoyment. Between VR support practically breaking on most headsets and this issue, it's starting to feel like potentially the Renderdragon wasn't ready to be released to the public just yet.
Clarkzer0
Copied and pasted from my reddit post to maintain consistency:
"EDIT 1, Jun. 14th: While not solved entirely, the issue has been narrowed down almost certainly to high resolution texture packs on certain Windows 10 edition hardware configurations regardless of machine capabilities, anything I've tried at 16x16 works fine on the "buggy" machines, but any higher and frame drops start immediately, if anybody has any other insight aside from what's already in this post, it'd be greatly appreciated.
Sorry if this is long winded, I'm detailing EVERY step of troubleshooting I've done to prevent redundancy.
1.16 ran like a dream (like every prior release of bedrock has on my hardware), I host a private server for 3 (total) on multiple different machines usually for 3-6 months at a time, and haven't had a problem with Bedrock performance on any of my devices... until 1.17 released.
To preface, the machines I've tried this on that DO have performance problems after updating to 1.17 include (all w10):
My main Rig:
Ryzen 5 3600x (tried with my new 5800x in the same configuration, same results)
EVGA GTX 1080
16gb DDR4-3200
500gb boot SSD w/multiple HDDs
My laptop:
i7-7700hq
GTX 1050 ti
16gb DDR4-2400
500gb boot SSD w/multiple HDDs
Friend 1s Rig:
i5-9400
GTX 1070
16gb DDR4-2666
500gb boot SSD w/multiple HDDs
On the other hand, the machines I've tried this on that DO NOT have performance problems after updating to 1.17 include:
Nintendo Switch
Nintendo Switch Lite
Xbox One (Base Model)
Xbox Series X
Playstation 5
One Plus 7 Pro
Pixel 5a
Friend 2s Rig:
Same as mine, but a 2060Super instead of a 1080, every other part is identical.
So, very clearly, machines that shouldn't (and for years haven't ever) had a problem playing on our server are suddenly getting lag spikes (from 120fps+ to 3, just by moving a few blocks or turning the camera, even in chunks with very little entities in them) on 1.17.
Here's what I've tried for troubleshooting:
New server files
fresh OS install on client AND server machines (Windows AND Ubuntu)
new game installs on ALL clients, even ones that did fine, no change in result
driver installs, even updating the bios on one of the boards, with no change in result
copied world, tried removing chests, all mobs including our pets, containers like hoppers, and any entities I could think of that could be causing ANY lag, no change in results
manually inspected over 240 chunks in our laggy areas for overflowing pending tick data, deleted 500 bytes of pending ticks (not a lot, pending tick data hasn't been a problem for a few updates afaik), no change in results
firewall, port forwarding, static IPs, etc, completely redone, no change in result
Frankly, I'm just exhausted.
I can't figure out why devices entirely capable can't run 1.17, especially considering nothing major was changed in world generation.
Anybody experiencing this as well, or that has any idea what could be the cause/solution, I'd appreciate the discussion 🙂)
Thanks."
Fix this, please, Mojang. It's obviously negatively effecting players enjoyment. Between VR support practically breaking on most headsets and this issue, it's starting to feel like potentially the Renderdragon wasn't ready to be released to the public just yet.