[1.3.3] Large Electrolytic Seperators causing massive FPS drops while the player is nearby.

[LeakingAmps]

Checked for existing issues / 已检查现有问题

• I have checked for existing issues, and have found none. / 我已检查现有问题，未发现相同报告。

Tested latest version / 已测试最新版本

• I have checked that this occurs on the latest version. / 我已确认此问题在最新版本中出现。

Mekanism MoreMachine Version / Mekanism MoreMachine 版本

1.3.3

Mekanism Version / Mekanism 版本

10.7.19

Minecraft Version / Minecraft 版本

1.21 NeoForge

Environment / 环境

Multiplayer - Dedicated Server / 多人游戏 - 专用服务器

Cross-Mod Interaction / 跨模组交互

Unsure / 不确定

Other Installed Mods / 其他已安装模组

ATM10 plus:
Alchemancy
Alchemancy x Create
Create: Bits - n - Bobs
Blockprints Merged
Create: Prismatic Shine
Create: Connected
Databank
ExclusionsLib
Fairy Lights (Neoforge)
FindMe
Freecam (Neoforge)
Just Dyna Things
Just Enough Resources
LDLib2
Neo Eco AE
Occult Engineering
PacketFixer
Pastel
Shadered

Expected Behavior / 预期行为

Performance should, at most, vary minor by proximity.

Actual Behavior / 实际行为

I drop from 80-100 FPS to well below 1 FPS, depending on proximity.

Steps to Reproduce / 重现步骤

Place 1 or more Large Electrolytic Separators
Open your FPS chart (F3 + 3)
Get close (In this case I'm flying around shrunk and using a phase ring to fly through blocks)
Lag

Additional Information / 附加信息

It appears to have an inverse geometric or exponential relationship with distance - Being half a block away drops me to about 20 FPS. While looking at it at this distance drops me to around 10 FPS, it's functional. Getting within a quarter block leaves me at under 1 FPS.

The lag is worst with the player's position at the halfway point between the top and bottom of the machine, rather than the base or top.

This is more exacerbated with multiple machines - seeming to stack multiplicative with each machine in proximity. being 1 block away from and able to see 4 machines dropped me below 0.1 FPS.

This impact occurs even if I cannot see the machines, though they do tax the renderer noticeably even when far away.

This effect goes away if you move inside the machine.

Example Frame Time chart just moving up and down near two machines. (The big red spike above 500ms/frame is while I was close to the machine)

[lostmyself8]

This issue has been around for a long time, and there is currently no solution to fix it. Please be patient

[LeakingAmps]

No worries! I didn't see this in the issues already posted, and didn't see a known issues page, so I assumed it was not known.

[andrewsf]

I've been seeing reports about this for a really long time. I was astonished that no one, including the author, filed an issue until this month.

That particular machine is made of around 111 cuboids with no face culling, many of which are pretty superfluous and could probably just be replaced with texture detail.

Re: server performance, it also has a VoxelShape of around 104 boxes. Around 10% of the boxes are zero-volume and many of them are almost/entirely contained within other boxes. Maybe Mekanism's call to optimize() fixes some of this, I'm not sure, but if you shrink your model down, you can stand on the tiniest little bits of the model. That means way more collision/raycasting work.

I have heard (but not verified) that there are similar issues for the other large machines.

[lostmyself8]

I've been seeing reports about this for a really long time. I was astonished that no one, including the author, filed an issue until this month.

That particular machine is made of around 111 cuboids with no face culling, many of which are pretty superfluous and could probably just be replaced with texture detail.

Re: server performance, it also has a of around 104 boxes. Around 10% of the boxes are zero-volume and many of them are almost/entirely contained within other boxes. Maybe Mekanism's call to fixes some of this, I'm not sure, but if you shrink your model down, you can stand on the tiniest little bits of the model. That means way more collision/raycasting work.VoxelShape``optimize()

I have heard (but not verified) that there are similar issues for the other large machines.

I also think it's a model issue, but face culling doesn't seem to work on large machines. I'm also considering whether we can update the model, but it's a big project, and I may need more time to do it