Ad Verhoeven

The final error id=1281... GL_INVALID_VALUEis when I closed the game, so while it probably means some failure to properly clean up stuff, it is however not related to this bug.

JVM arugments have 0 effect on this bug, they didn’t cause the bug in previous versions and don’t fix the bug in the reported versions.

My drivers DO NOT have any updates.

before and after F3+T

Updating the JDK to 25.0.1 (and rebooting my machine just in case) resulted in the same textures being black.

Also, could you please elaborate how any of the following can achieve the following:

Textures are black only upon launching versions of minecraft after 1.21.11, but can be fully restored anyway using F3+T or other means to reload the textures.

Again, this is not a matter of my hardware not being able to run minecraft, it is minecraft not running/loading properly upon launching the game. I can play perfectly fine with no visual artifacts or bad performance after doing a single F3+T.

System specs:

CPU

Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz

Base speed:	2.40 GHz
Sockets:	1
Cores:	2
Logical processors:	4
Virtualisation:	Enabled
L1 cache:	128 KB
L2 cache:	512 KB
L3 cache:	4.0 MB

Memory

8.0 GB DDR3

Slots used:	1 of 2
Form factor:	SODIMM
Hardware reserved:	589 MB

Available	2.6 GB
Cached	2.3 GB
Committed	4.8/8.4 GB
Paged pool	461 MB
Non-paged pool	364 MB
In use (Compressed)	4.7 GB (47.2 MB)

GPU 0

Intel(R) HD Graphics 5500

Driver version:	20.19.15.5166
Driver date:	08/08/2020
DirectX version:	12 (FL 11.1)
Physical location:	PCI bus 0, device 2, function 0

Utilisation	0%
Dedicated GPU memory	
Shared GPU memory	0.4/3.7 GB
GPU Memory	0.4/3.7 GB

I have no issues with menu buttons at all.

As stated before, the game runs without any texture issues on all release versions prior to 1.21.11. The issue is therefor most unlikely anything different but a code change on that version.

Device manager is unable to find any driver updates.

None of the above should be the issue when it ran in all versions prior to 1.21.11 should it? I haven’t checked any snapshots between 1.21.10 and 1.21.11, but it seems very unlikely to me that it is intended behavior to break.

I am not using a modded installer to “fix” something, as that defeats the purpose of this bug-tracker.

I had 0 issues prior to 1.21.11 and using any method to reload/restart the ResourceManager fixes the issue.

Turning off/on fullscreen had no effect at all.

F3+T or changing resourcepacks (in the menu) does fix it. F3+T does not have any significant changes in logs compared to launch.

Starting the game with a non-vanilla resourcepack has the same results (black textures)

last attachment surely makes no sense, a coral reef and full lukewarm/warm ocean surounded by cold beach/iceplains????

Is it intended that cold beach is directly next to lukewarm ocean?

I would really appreciate if oceans made more sense. There is no ice to be found near any lukewarm ocean et vice versa.

Right now I find more lukewarm ocean then cold/frozen ocean near coldbeaches and other cold/snowy biomes. e.g. it is more likely for a weird combination to happen then it is to find a normal combination. Feels like the good old days you had ice plains next to a desert.

i WOULD consider this a bug, minecarts and other entities DO bounce in horizontal motion if I am not mistaken, not to mention the simple fact that it is strange that you do not remain horizontal speed if you try to boost your height with a piston contraption.

(tripwire in front of a sticky piston with some slimeblocks so they activate while you fly just a few inches above them.

perhaps a feature suggestion, but not a strange one

This is indeed a block-state bug, I made that clear about 1 year ago with my set of screen-shots. I am not fully sure whether it is going to be fixed easily since it has to do with the time the game takes to calculate these changes. It all seems to be about slight differences in timing, most likely only a few game ticks.

I do think that this isn't what is intended to happen, but it might be useful for some redstone machines nonetheless.

the first picture shows how i tried to make a very easy system to demonstrate this bug/feature in a few screenshots, the left side pistons are only to show that there has been a pulse.

the third screenshot (which should've shown both pistons extended) however failed, it remained stable.

upon removing the repeater i did get the original output i was expecting.

screenshot https://bugs.mojang.com/secure/attachment/79165/2014-08-20_12.23.46.png and https://bugs.mojang.com/secure/attachment/79166/2014-08-20_12.23.51.png show what i was expecting to happen (which happens if you do not use repeaters to power the inverter)

I hope this information is detailed enough for someone to get hold on this strange bug.

I just checked this bug for 14w34c again.

those pictures i showed now give slightly different results.

the visuals do have effect on the pulse (therefore i think this might actually be a feature??)

if the comparator is off it will give a pulse on an downward slope et vice versa for a comparator which is fully lit.

the inverter I am using: https://bugs.mojang.com/secure/attachment/30893/2013-06-04_00.58.36.png

wow. this is very strange, a repeater used to power this changed it to my previous findings (it only gives a pulse when the comparator isn't lit/on)

Bug is indeed fixed. the strange cap on water-blocks to be absorbed makes it hard to tell weather all bugs are fixed. I would suggest choosing for a sphere/cube around the sponge and change the cap to the water blocks fitting in such a shape. like in the old days when a sponge just didnt absorb any water that was more then 2 blocks away. (it makes it easier to check for bugs/glitches)

Has there been any respond from the developers?

As i stated before, there are things which could be considered features... but some most definitely defy logic.

just to clarify a last bit, placing the sponge on the spot where the yellow wool is will drain ALL the water. (again make sure the water has stopped flowing into air blocks) placing it on top of the yellow wool will leave 6 blocks of water including 2 source-blocks which will then fill a part of the hole again.

I've added the reproduction steps, yet still you seem to deny the fact that this is a bug or at-least something that is illogical to 99% of the people playing minecraft. Without any other comments on how to make it clearer... i actually can't help the fact that most people will post here as soon as 1.8 gets out (or make duplicates)

I've also confirmed that it is still not fixed/changed.