osvaldoHeyy, Just wanted to know if those :had known side effects such as longer loading times or even errors due to mismatching files being kept for too long.lzma_persistent_buffer 1 // Keep the LZMA compression system in memory to prevent reloads of it cl_always_flush_models 0 // Keep models loaded in between map loads //cl_always_flush_models 1 // Remove models from memory every map load mat_levelflush 0 // Do not clear temp mem at the beginning of a level load //mat_levelflush 1 // Clear temporary memory
lzma_persistent_buffer 1 only affects the compression system not being initialized every time
cl_always_flush_models 0 doesn't prevent model unloads, it just doesn't aggressively unload models, which is only useful if you are on a low memory system
mat_levelflush 0 skips resetting material system temporary memory on level loads
These settings would reduce load tjmes, not increase them. And I'm pretty sure they wouldn't cause errors.
MalkrazmastercomsJust to be clear, are you having these problems when there are more players, or just certain areas, even when empty?It's definitely when there are other players within the same section of the map as me, though the amount varies.
I think I mentioned that earlier but probably wasn't clear enough.
It might be the networking system. Try copying the network settings from the stripped addon and see if it affects your FPS. If so, then we will know that the net code is bottlenecking the performance.