Incompatibility with QMD and particle culling

[AnasDevO]

Describe the bug

Hello, it's me thermonuclear_minecraft_engineer! after some surgeon-worthy dissection (of 600mods lol) i finally found the mods at the origin of the issue. The mods QMD makes any sight go completely crazy and Particle culling made the rendering of particles break(not just fire smoke), as well as smokes of gun make any water body translucent. Please find the videos linked below to illustrate the issue! Thanks for taking time to look at this, i really appreciate your work :D

Zulu-8.2024.06.21.-.18.41.19.01.online-video-cutter.com.mp4

Zulu-8.2024.06.20.-.21.07.09.02.mp4

Reproducibility

• I reproduced this issue with as few other mods as possible installed.
• I am unable to reproduce this issue consistently.

Screenshots and/or videos

No response

Logs

no logs

Debug Logs

No response

Crash Reports

No response

MWC Version

Modern Warfare Cubed 0.1.6

Forge Version

1.12.2 - 14.23.5.2860

Red Core Version

0.5.1

MixinBooter Version

9.1

Java Version

1.8.0.412+8 (Temurin)

Java Virtual Machine

Hotspot

Operating System

Windows 10

GPU Vendor

NVIDIA

Code of Conduct

• I agree to follow this project's Code of Conduct

[AnasDevO]

further investigations show that the MIA mod's size content, powered by artemisLib which changes hitboxes and such, will make it so if it's present with MWC and QMD, right clicking with guns will zoom in and out like that.

Same thing can be noted, but with only Techguns, ModernWarfare and QMD. it is to note that removing any of the mods in the minimum required setup will make the bug unreproducible.

Minimum Setup 1:

• NuclearCraft-2o.6.2-1.12.2
• QMD-1.3.5-1.12.2
• Modern-Warfare-Cubed-0.2-Dev-1
• mia-1.12.2-0.2.2a with size content enabled in line 11 B:"Enable size module"=false in config/mia/base_additions.cfg
• ArtemisLib-1.12.2-v1.0.6

Minimum Setup 2:

• NuclearCraft-2o.6.2-1.12.2
• QMD-1.3.5-1.12.2
• Modern-Warfare-Cubed-0.2-Dev-1
• techguns-1.12.2-2.0.2.0_pre3.2

the Previous Beta build of MWC also has the same issue.

[Desoroxxx]

I won't make a specific fix for both as of right now as they are very obscure.

But they might simply get fixed in 0.2 as there will be a few, big rendering changes