Closed Ampflower closed 8 months ago
Why is the creeper affecting atlas mipping?
It shouldn't even be in an atlas?
Honestly, I don't know which mod is including it in the block atlas either; it is just what I see from the log.
[20:20:21] [Worker-Main-5/WARN]: Texture geckolib:entity/creeper with size 64x40 limits mip level from 4 to 3
[20:20:21] [Worker-Main-5/WARN]: Texture wilderwild:entity/firefly/nectar with size 487x487 limits mip level from 3 to 0
[20:20:21] [Worker-Main-5/WARN]: minecraft:textures/atlas/blocks.png: dropping miplevel from 4 to 0, because of minimum power of two: 1
There's a lot of mods in here at the moment, may try to bisect which one it is later if you don't recognise one that'd do this.
I don't
But arguably this is their issue, not Geckolib's
Entity textures can be of any size - there's a reason they're not atlas'd
Fair; I'll poke around and find which mod it is then if possible.
Is frankly a weird issue, I just worked around by using a custom resource pack to set textures to be 16x scaling to get mipmaps working good enough for now.
Hi, I noticed that from a mod shoving everything into the block atlas, the creeper.png file provided by geckolib is forcing the mipmap level to 3 instead of 4 due to the height of 40.
The file:
https://github.com/bernie-g/geckolib/blob/1.20.1/Fabric/src/main/resources/assets/geckolib/textures/entity/creeper.png
From F3+S dump:
geckolib:entity/creeper x=1408 y=2000 w=64 h=40
Possible fixes:
Align the creeper to the nearest power of 2 or multiple of 16 that can still fit the atlas, which would be 64 and 48 respectively.
This would allow any mod that for any reason takes the creeper and other entities and throws it into a bigger atlas to work seamlessly.