@LuckyRoot Yeah, no problem

I see. It's a lot more complicated than it seems.
Understood. Please ignore my request.
Thank you for replying and the insight.

@LuckyRoot That issue requires decompiling and recompiling the weapon's viewmodel to fix it which is something I don't want to do. As you know, decompiling the weapon's viewmodel will result in unintended consequences such as broken meshes and not being able to decompile it at all.

Denny凯妈's original firing sound has this issue where it abruptly cuts off or becomes completely muffled upon shooting a zombie when used with MANACAT's "[Improved] Headshot Feedback Effect" mod( https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2582265366 ) .
And I noticed that this mod has the same issue as well.

Could you consider changing the sounds or making another version with different sounds, similar to some of your recent weapon mods? It can be any sound. @snygaming99 on Youtube has a video of JAK Warden, a model 1887 akimbo from COD MW3, you can use as well:
https://www.youtube.com/watch?v=DHq5OY5Vmkw

@Táiga Rivers When it comes to decompiling and recompiling .mdl files, I actually did that once when I tried to add additional sound events to a weapon mod. However, as you mentioned, its viewmodel meshes got messed up so badly that I decided it wasn't worth the hassle. Heck, even splitting .smd files into multiple parts is something I don't want to touch to prevent further frustration. With that being said, these compressed mods only reduce the risk of experiencing low FPS and audio bugs, they don't fully eradicate them. Increasing the game's heapsize value in the launch options can only do so much.

@Táiga Rivers Well that's a nugget worth of info there. Much like Dokun, the reason I made these compressed mods is to ensure that people don't suffer that occasional low FPS and no audio bugs as often as before. Still, none of them are immune to crashes.

Sorry for flooding the comments section. Just wanted to share some useless knowledge

On the opposite side, these two: HQ G3 and HQ M14 , have so many vertices in their SMDs that they occasionally crash the game or will give you a guaranteed crash when you get killed by the Witch or pounced by the Hunter because their attacks create a lot of decals in a short amount of time. Disabling the decals in their VMTs ($nodecal 1) solves only half of the problem, but it becomes unnecessary after proper optimisation (which I did because I am playing with these)

Guess I should also note that many weapon models are initially optimised or simply consist of acceptable amount of vertices, like these M570 , UMP9 , M4A1 Mod 3

Probably low-resolution textures make the game run better for tomato-PC owners, but I would not be so sure — it is mostly about the weight of the texture that takes time/bandwidth and space to load into the VRAM of your graphics card; not the resolution. A friend of mine who have been playing on a broccoli-PC also confirmed that even if the model had 256×256 textures, it still was making his game unstable because of the model having just one SMD with a ton of vertices in it

You do not have to start learning all this complicated stuff about models. Also because not every model can be optimised without breaking its animations (or meshes in case of some of Denny's mods) — it requires much more modding skills than simply dividing a solid model into several parts and exporting each part as separate file. I am just sharing some probably-useless-for-non-modders-but-still information while doing some self-taught modding as a hobby and not being some mad scientist

I have decompressed the textures of my mods, too, but it did not help at all in all the campaigns I have tested that method of optimising the mods. Then, after I optimised every weapon model with the aforementioned method (by dividing the SMDs) and restored the 2K textures (even 4K are fine, in fact) which most of my mods had, no crashes at all unless the campaign itself is made like… like Execution Exhibit, Left 4 China or the fourth chapter of The Hive that can even crash a dedicated server itself and not just clients with and without any mods
Do not ask me how this works if all these SMDs get compiled in one MDL file in the end — "It just works" ©

Not saying that compressing the textures is useless, but…
Decompiling the model and dividing its SMD file(s) (except for animation SMDs) into parts really helps against unstable FPS, audio cuts and especially crashes — if the SMDs contain over 17,433 vertices each (the limit stated in the official Source engine model creation documentation ), they can cause the game to crash regardless of textures. The default models consist of 14-16,000 vertices for v_models (first-person models) and about 8,000 for w_models (world models)

Will you be able to compress this RGL-80 GL from BaiFckmouse if you can? https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2957406425

I really like how you compress these just to make it wooden PC-friendly. It's very frustrating to me that whenever I install HQ mods, my FPS keeps dropping. I guess those HQ mods are meant for PC gamers who has better and improved hardware than what I have now though...

You are doing great work, make those good but game-crash mods usable

Can you make a compressed and non rng version of this? https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2969698603

Oh ok, thanks anyway

@Sam The La Pofum No. Because I don't have any knowledge on how to modify the animation sequences. When it comes to L4D2 modding skills, I only have the skills to make both the custom HUD icon and scripts as well as compress the weapon mod's .vtf texture files. That's it.

Hey could you remove the inspect animations?
Or tell me how i can do that