Visual Bug Near Torches with Embeddium

[AxolotlAccount]

Bug Description

Mounting a torch on a wall causes artifacts on the torch's block boundaries (not the boundaries of the torch itself). It is especially noticable when viewed while moving.
Tried disabling Use Compact Vertex Format, didn't fix the problem.
Uninstalled TexTrue's Embeddium Options and Embeddium (Rubidium) Extras, didn't fix the problem.
Uninstalling Embeddium fixed the problem.

Without Embeddium:

With Embeddium:

With Embeddium (marked to show what exactly is the problem)

Reproduction Steps

1. Install Embeddium.
2. Mount a torch onto a wall.
3. Observe the torch. It is especially noticable when moving.

Log File

https://gist.github.com/AxolotlAccount/b5cfce202f8f951fa7b0955f4f49a417

[embeddedt]

Cannot reproduce with only Embeddium installed. There are far too many mods installed to guess what causes the issue; you will need to narrow down what mod is the problem. My educated guess would be Model Gap Fix, as it fiddles with texture coordinates.

[AxolotlAccount]

I uninstalled Model Gap Fix and same issue still happens.

[JoeyTurncoat]

Having this issue as well, disabled Model Gap Fix and disabled all texture packs. I've been trying to narrow the mods down but so far I haven't been able to find the problematic one.

[moninformateur]

Cannot reproduce with only Embeddium installed. There are far too many mods installed to guess what causes the issue; you will need to narrow down what mod is the problem. My educated guess would be Model Gap Fix, as it fiddles with texture coordinates.

I've provided a modlist on Rubidium's issue page where I'm always able to reproduce the issue. Note that it seems to be more visible in higher resolution monitors. It happens with a wide variety of mods.

The common variable is always Rubidium/Embedium. I'm not tech enough, but maybe it's linked to the light rendering since it only happens when there's a light source nearby?

[embeddedt]

While the screenshot does not look exactly like #208, we have enough of an idea of what causes issues like this that we're pretty sure it is the same underlying cause. Since we can replicate the other issue with a test resource pack, but we haven't been able to reproduce this one at all, we're going to close this in favor of #208. It's very likely that whatever ends up fixing #208 will also fix this.