DO NOT REPORT AN ISSUE IF YOU HAVEN'T TESTED THE ISSUE WITH THE LATEST VERSION IN CURSEFORGE

**Functional Storage Version: 1.18.2-1.0.7

**Titanium Version: 3.5.6

**Crashlog If Applicable (Upload to pastebin/gist): (N/A seems to be a recursive loop of some sort, not an actual crash happening)

This is purely a rendering issue?

It doesn't crash, but, it does bring the FPS down to 0 FPS (the screen updates about once per 3 seconds, so ~0.33FPS) when using the linking tool while the entangled blocks are linked to the controller of the network. The reason I didn't report this to entangled instead is because the problem seems to be in the rendering of the "box outlines" gone haywire and entangled on its own doesn't seem exhibit any problems on its end.

As you can see, it pretty much speaks for itself. There are four entangled blocks that are linked to the same controller, are all chunk loaded in the same area, and work fine otherwise.

Do I use any special mods on top of SB3?

I use rubdium/occulus normally. But they are not the issue. I tested this problem without them; I got rid of them and checked it out on a clean install, but the problem still happens. It seems to make no real difference except without rubdium and occulus there is a slight decrease in updates (ended up being an update every 5 seconds, so about 0.2FPS without rubdium and occulus included).

Any other mods that are nonstandard? No, nothing other than BetterF3, which uses forge version of fabric config, which I also removed, and tested, and not surprisingly, made no difference.

NVidia GeForce 650
Intel i7 x64
8GB Allocated to Java, Java 17.0.6 LTS, 16GB Total, Win64 (v10.9.0)
Forge 40.1.86

Did you find any solution to this? I'm having the same issue in #194 and it's very frustrating - if I want to link a new drawer to my network it takes about 25 seconds.