Arin Hunter-Schlorholtz

Just got some HDR monitors myself for the first time and I am experiencing this in 1.17.1 as well.

It only happens when Minecraft launches in fullscreen. The HDR setting is unaffected if I play in windowed mode with Minecraft maximized. Not ideal, but at least it is a workaround for the moment.

I would expect the Windows display settings to remain unaffected as the OP said. It is aggravating to have to change back to HDR if I forget and launch in fullscreen.

Edit:

Environment:

OS: Windows 10 Pro, 64-bit
Java Version: Version 17 (build 17+35-LTS-2724)
Monitor: Acer Nitro XV272U
GPU: Nvidia RTX 3080ti
Nvidia GeForce driver Version: 496.49
Processor: Intel Core i7-6700K
Memory: 16 GB

Looks like I am experiencing the same issue playing 20w21a on world with seed "20w21a":

I haven't seen a village but that does appear to be the feature that the crash report mentions. Every time I cross a chunk boundary towards an area I had not previously explored (was trying to lure some sheep towards me haha) I get a full game crash.

I will attach the crash log, screen shot of chunk grid with debug, and screenshot of error output.

 Edit: I forgot to mention I noticed my video card spike to 100% usage each time right before the crash.

That is the correct behavior for falling blocks. Cobblestone walls and other fences are 1.5 blocks tall so that you can't jump over them, but this means that their hitbox extends above the block they are in. The falling block (which is an entity while it is falling) falls down and rests on the taller hitbox of the fence and stays there waiting for you to break the wall so that it can finish falling to the ground and become a block again. It can never reach the y-level it needs to return to being a block because of the taller hitbox of the fence.

[15w46a]

Just in case weight of comments is meaningful, I am experiencing the same behavior. Redstone blocks are strongly powering blocks touching any of their sides. Noticed this when I placed a redstone torch on some stone brick with a redstone block sitting on top of it. The torch went out, and it even lights lamps and redstone lines touching adjacent blocks in contact with it, like in the screenshots. Like Joseph said above, this breaks a lot of things and doesn't add much, hope it gets fixed. 🙂

Ah, good tip. Will do!

Ah, sorry about that duplicate. Looks like the search didn't pick up the other issues because they are all one word ("java.lang.ClassCastException:") and were all linked to various other possible causes. Glad to see that people know about this and that a fix is in the next version. Thanks!

I had to take a few screenshots, but i got one with the item appearing partially inside the dropper.

I am having the same issue, I wanted some droppers to put items downwards into fire but instead they are flying sideways everywhere. I hooked it up to a comparator clock to get a better look at it and the items are indeed showing up partially or fully inside the dropper causing them to move upwards/sideways.