Item Enchantment Glint and Item Entities Removing Rendering of Some Objects
RosiePies opened this issue ยท 4 comments
Describe the bug
Enchanted items have the whole texture face glinted.
Item entities' UV faces remove the rendering of water, item frames, and tile entities.
To reproduce
Steps to reproduce the behavior:
- Join any world.
- Place water, an item frame, or a tile entity.
- Throw an item (enchanted or not) on the ground in front of any object referenced in 2.
- See error
Expected behavior
Items' enchantment glint applies to opaque/translucent pixels of an item only.
Item entities do not obstruct rendering of water, item frames, or tile entities.
Screenshots or videos
Which Minecraft versions does this bug affect?
1.20.1
Mod loader
Which mod loaders does this bug affect?
- [ Yes ] Forge - 47.1.3
- [ Maybe ] Fabric
Mods list
emissive-plugin-1.20.1-1.1.1-forge
moremcmeta-1.20.1-4.2.4-forge
Resource pack
None
MoreMcmeta uses translucent (partially transparent) emissive overlays. I believe this is an issue with vanilla Minecraft rendering when item models have translucent faces. You can cause this issue to happen in vanilla Minecraft by throwing stained glass panes on the ground near water. I will take a closer look to ensure that is the case.
I have noticed that this issue does not happen on Fabric, if you are able to use that instead of Forge.
I have some early plans for a v2 of this mod where overlays will not support translucence by default, but you can enable it on a per-overlay basis. That would help with a lot of these issues related to the translucent rendering, since almost all existing emissive packs don't need partial transparency. I don't have an ETA on that as it's still in a planning phase. The vast majority of issues reported have been translucence-related, so I'll likely create a separate tracking issue for this until v2 is released.
I've found the cause of the issue; it seems like the easiest way to fix this is likely to work on the v2 update. v2 looks to be simpler to implement than I expected, so hopefully this issue and other issues will all be resolved.
I have a working 2.x development version that fixes this issue. I am hoping for a release this weekend if no issues are discovered while I do more thorough testing.