readme.md

Two resource packs for latest 1.17 snapshot. Try them both!

BlusteryDay.zip

MipInf.zip

also nowhere in the shader code do i see anything related to leaves, does this mean it's impossible for shaders to edit a certain block? (Say a shader only editing a crafting table)?

In the shader code, there is a part that says:

if (UV0.x >= 288.0 / 1024.0 && UV0.x <= 304.0 / 1024.0) {
    if (UV0.y >= 64.0 / 1024.0 && UV0.y <= 80.0 / 1024.0) {
        xs = sin(position.x + animation);
        zs = cos(position.z + animation);
    }
}

Basically, the if condition is checking which block it is rendering. You can remove the if condition and it will apply to all blocks with that rendertype

It does not work in 21w11a

Yes, because certain things where changed.

also nowhere in the shader code do i see anything related to leaves, does this mean it's impossible for shaders to edit a certain block? (Say a shader only editing a crafting table)?

uv0 is a texture atlas of all the textures in the game, it is dependant on the resource pack, so that is why some resource packs break this shader. The check of uv0.x or uv0.y is the location of the current pixel relative to what texture it is, so for example, one of the the leaf textures is between an X of 288 and 304, and a Y of 64 and 80. (If you recall, textures are usually 16x16, that is why there is a range in which the pixel would qualify as a leaf).

They will hopefully provide a better way to check what block it is (when 1.17 fully releases) than getting it from the texture atlas, as if resource packs break the shader, then that is no good.

Hopefully this built-in shader feature gets improved more and more so that we don't have to rely on optifine anymore.
And also hope that sodium can cope with these changes and if both shaders and sodium work somewhere down the line, optifine will be even more redundant.

aw this doesn't work anymore ;-;

Hopefully this built-in shader feature gets improved more and more so that we don't have to rely on optifine anymore.
And also hope that sodium can cope with these changes and if both shaders and sodium work somewhere down the line, optifine will be even more redundant.

I'm sure sodium will be perfectly fine, I'm more worried about canvas

canvas already has a snapshot port going strong, so I guess they'll be fine as well

Ye, not working in 1.17.0

:(

not working for me I have fabulous graphics enabled and have edited the pack.mcmeta to make sure it is compatible for 1.17, still nothing. I am looking at it in visual studio and it all looks fine.

i have the same issue lol