Version Info

• Minecraft, 1.20.1
• Fusion, 1.1.1-forge-mc1.20.1

What mod loader are you using?: NeoForge

Are you using OptiFine: No

Description of the Bug

Installing fusion alongside tinker's construct (tested on 3.10.1.76 and 3.10.2.92) interferes with correct rendering of all glass pane blocks added by tconstruct in certain orientations.

Expected behavior: Tinker's construct glass panes should render normally (no lines between connected panes) with or without fusion installed.
Current behavior:

• Tcon glass panes with connections to the west only do not appear correctly
• Tcon glass panes with connections to the west and north only do not appear correctly
• Tcon glass panes with connections to the north, south, and east do not appear correctly

Steps to Reproduce

Install the following mods:

• Fusion v1.1.1-forge-mc1.20.1
• Mantle v1.11.71
• SuperMartijn642's Config Lib v1.1.8-forge-mc1.20
• SuperMartijn642's Coore Lib v1.1.12a-forge-mc1.20
• Tinkers' Construct v3.10.2.92

Then generate a new world and place any variant of glass pane from the Tinkers' Construct mod to see the issue.

Minimally, 2 panes can be used - place them adjacent to one another in line with the X axis (east-west)

Screenshots

Expected appearance:

Actual appearance: (borders appear incorrectly between connecting panes)

You are using years old versions of my mods. Try updating them to up to date versions.

Sorry about that, I didn't think to check curseforge. The most recent versions on modrinth are all 2 years old.

You are using years old versions of my mods. Try updating them to up to date versions.

Modrinth has all the same versions of my mods that CurseForge has. The most recent file for Fusion on Modrinth is from 5 days ago 🤔

Modrinth has all the same versions of my mods that CurseForge has. The most recent file for Fusion on Modrinth is from 5 days ago 🤔

I think I know what happened - I made my modpack with the modrinth app/launcher and it's weird about forge/neoforge mod compatibility on 1.20.1. The forge versions of Fusion for 1.20.1 are not all marked as NeoForge compatible even though they still work just fine with it, so they were not appearing when I went to add them to my pack. Sorry again for this confusion on my part.

Ah I see, the files for 1.20.1 were indeed not marked for NeoForge. 1.20.1 is rather annoying as people should ideally just use Forge on that version as NeoForge doesn't add anything and just lacks development compared to Forge on that version.
I have marked the latest 1.20.1 Forge file for NeoForge as well now.