Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Layer ordering issue on randomized textures using Immediately Fast #344

Open
Estecka opened this issue Jan 5, 2025 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@Estecka
Copy link

Estecka commented Jan 5, 2025

Describe the issue

Villagers have two textures applied to the same model: the villager's underwears/skin, and the biome-specific clothing. Where the two textures overlap, the clothing texture should take priority.

When Immediately-Fast is installed, the underwear sometimes takes priority over the clothing.

Having multiple visible villagers with different random textures is required. This doesn't occur if all visible villagers use the same texture. The bug will affect different villagers depending on your angle and position, but all villagers using the same texture will be affected (or unaffected) together in the same way. There seems to always be exactly one unaffected villager texture at any given time.

Screenshots
The pack here contains nothing but a villager2.png with inverted colours.

Only arms and legs are affected, because the torso clothings are on a different cube, slightly bigger and with different UVs. That part of the clothing doesn't compete with the underwear.

Blue villagers have their sleeves off :
2025-01-05_12 30 39

With a different viewing angle, regular villagers are now the ones with their sleeves off :
2025-01-05_12 30 38

Crash log
Nothing noticeable in the log:
https://paste.ee/p/XDMOt

Your setup:

  • Minecraft version: 1.21.4
  • ModLoader: Fabric 0.16.9 + Fabric API 0.114.0
  • ETF Version: 6.2.10
  • EMF Version: 2.4.1
  • Does the issue persist with only ETF installed? No
  • Have you checked the FAQ in the Readme, or Discord, to see if it is a known issue? Yes

Noticed the same issue in MC 1.21.3, but not in MC 1.21.1

@Estecka Estecka added the bug Something isn't working label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants