Describe the Bug

When non-block items are placed as the Frequency Channel, they do not display on the Redstone Link. The Link functions properly as though the item is present in the Frequency channel

It seems item textures are displayed "inside" the boundaries (i.e. below the surface) of the Redstone Link texture. This is evident when using a long item such as a Mechanical Belt, which sticks out beyond the side of the Link texture (screenshot included).

This bug occurs on items with flat textures or where most of the "block" is transparent. Occurs for Vanilla items (e.g. Clay Ball, Redstone Torch, ladder, Big Dripleaf) as well as Create items (e.g. Mechanical belt, Redstone Link). This is regardless of orientation of Redstone Link (placed on top, side, or underside of a block).

Blocks, slabs, stairs (with textures size of full block) display normally. Some items partly obscured (e.g. Big dripleaf--only top front edge of leaf is visible)

This may further clarify the behavior noted in Issue #4345

Edit: Checked on various video settings per the Troubleshooting page listed on the Common Issues Thread (#1747)--issue occurs regardless of setting: Fast, Fancy, or Fabulous.

Reproduction Steps

1. Place down Redstone Link
2. Place an item (e.g. Clay Ball, Redstone Torch, Mechanical Belt) in either Freq. 1 or Freq, 2 slot

Visual bug occurs. Item is hidden partially or completely.
...

Expected Result

Texture of Object appears visibly on surface of Redstone Link in Freq 1/Freq 2 slots, as in previous versions of Create.

Alternate suggested result: Redstone Link Frequency Channels "cut into" the Redstone Link texture by half a block (just as they extend outward invisibly half a block) such that even flat-textured items display fully.

Screenshots and Videos

Note that edge of belt texture is visible in Freq 1 slot (near crosshairs). Item in Freq 2 slot is Redstone Torch (obscured entirely)

Item in Freq 1 is Redstone Link (antenna visible); item in Freq 2 is Big Dripleaf (front of leaf visible)

Crash Report or Log

N/A

Operating System

Windows 10

Mod Version

0.5.0i

Minecraft Version

1.19.2

Forge Version

43.2.0

Other Mods

Many mods running on world where bug was first observed (custom modpack)

Bug also occurs in new MC 1.19.2/Forge 43.2.0 world running only Create 0.5.0i with no other mods. (second screenshot)

Additional Context

No response

Upgraded Forge to 43.2.6. This seems to have resolved the issue.

I'm still having this issue with 1.19.2, Forge v 43.2.8, create-1.19.2-0.5.0.i.