CubeTheThird

@unknown, the resolution type is "Working as Intended".

Reopened as requested.

I logged this report in response to certain users with Surface X tablets who experienced this problem. I do not however have the means to reproduce this myself. That being said, seeing as how 32 bit support is being phased out entirely, I don't know that this report should stand as valid.

Reproducing it was to simply try to launch the game, without modifying the java arguments, on one of these devices.

You seem to have misread the other report. It was resolved as Invalid, as this is considered to be a feature request.

@unknown, as was mentioned in previous comments, this report's main purpose is to gather information. Comments that are not directly contributing helpful information should be taken to the linked subreddit. Seeing as you previously indicated your issue was resolved with updated graphics drivers (at least for 1.17), I'd recommend you provide new profiling details, along with screenshots, as per this report's instructions.

@unknown, for future reference, every time you edit a comment, an email notification is sent out to those watching a report. I would recommend you make all your edits at once.

@unknown, this bug report is mostly about the issue affecting users in single-player, since it is only a setting in multi-player. The reason it is enabled for the purpose of preventing data loss is for Windows users specifically, and as such it is not enabled by default (again, in single-player) on Linux. The ability to change the default setting is the easy solution to not experience this problem on Linux servers.

For any additional discussions about bug reports, please take them onto our subreddit.

@unknown, can you confirm that you downloaded the

world, and not the other one? I just double-checked and I'm able to open that version in 1.17.

@unknown, please follow the directions in the ticket description to provide helpful diagnostic information. Any other comments or discussions should be taken to the linked subreddit thread here.

It has been decided that these types of performance issues will be linked to this report: MC-219639.

Please follow the instructions on that ticket to document your performance decrease so that it will be standard with others who experience similar problems.

It has been decided that these types of performance issues will be linked to this report: MC-219639.

Please follow the instructions on that ticket to document your performance decrease so that it will be standard with others who experience similar problems.

It has been decided that these types of performance issues will be linked to this report: MC-219639.

Please follow the instructions on that ticket to document your performance decrease so that it will be standard with others who experience similar problems.

21w08b: 265 FPS
21w10a: 190 FPS

21w11a profiling results:

OS: Linux (Arch) 64 bit
CPU: AMD Ryzen 1600
GPU: NVIDIA Geforce GTX 1060 3GB 460.56

Please follow these instructions to get a dxdiag report, and attach the report here.

@unknown, as indicated in the report, this has been resolved as "Works As Intended". In other words, this is considered a feature, not a bug.

@unknown, please do not use the bug tracker as a communication forum, particularly on tickets closed 6 years ago like this. The preferred place for discussions would be, for instance, on the mojira subreddit. Please also note that the support center and account support are run by Mojang directly, while the bug tracker is maintained predominantly by community volunteers.

@unknown, while appreciated, it isn't necessary to confirm a report for a certain game version when it is already part of the "Affects Version" list. Understandable if you happen to miss it though, since it's fairly lengthy at this point.

Whether or not a block can be waterlogged falls into the territory of a feature request (except for valid parity issues), as this is solely up to the developers to decide.

In any case, there has been much discussion on this report, and I ask that further discussions be taken onto the mojira subreddit. Further comments left here should be contributing to this report specifically (ways to reproduce, updates, confirmations, etc.).

@unknown, this report was previously flagged for review, and the developers verified it, so it is not WAI.
It has also been assigned a "Mojang Priority", which is another indicator that it will be worked on.

@unknown, please take all discussions about reports (especially 8 year old ones like this) off here and onto our subreddit.