Why is my weapon mod pack crashing and making models invisible in my load order?

[RyanOG]

I’ve been trying to get a custom weapon pack working with my existing gameplay overhaul, but every time I load in, the new models are invisible or cause a crash. I’m not sure if the issue is a load order problem or if the mods just fundamentally conflict in how they handle the asset pipeline.

[KevinH]

I ran into a similar pain when a custom weapon pack would just vanish on load. The files were there but the models were invisible. I double checked file paths in the mod folder and the manifest, then tried loading again and still got nothing. I ended up removing another texture mod that touched the same asset space and that helped me narrow it to a conflict rather than pure missing assets.

[Riley70]

My gut says this is an asset pipeline clash not a plain order thing. I once had two mods racing to own the same material slot and everything would crash or show nothing. It felt like half of the assets were waiting for a texture that never came.

[Dennis_P]

I tried running with only the weapon pack and the overhaul, then added one extra mod at a time. When I hit the same crash the moment the new pack loaded, I found a log line about a shader mismatch. Swapping the shader set fixed nothing, and I ended up abandoning that combo.

[Jerry.T]

If you want a practical path try a clean profile and add mods one by one and test each time. Check if any mod touches the same model name or texture folder and try to rename or separate them. The idea of load order might be part of it but maybe the real problem is an asset path mismatch that breaks the pipeline.