So i've taken a look into the mass crashing caused by emp_tropicvendetta_rc4. Cause of the crash: The area around D4 does indeed cause a client side crash. The cause is an invalid memory access and occurs with regards to detail objects. Map issues: Upon loading the map, it causes 2 assertions, with no debug output that indicates this :/ From what i can tell from these assertions, there are 2 entities that have "unreasonable origins", but i don't know exactly what these entities are yet. I will do further investigation. - An unreasonable origin means that some entity is outside the world limits. Theory 1: (false) If these entities are detail entities, and its trying to draw them outside the valid bounds of the world, then this may be causing the crashes. Resolution: Ideally fix these asserts. - I will add some meaningful error output when this occurrs, a map shouldn't have any entities outside the valid coordinate range. - We need to get the vmf for emp_tropicvendetta_rc4, and have an available mapper to move these two entities back into decent coordinates. Step 1: Apparently these crashes were recently introduced as it never happened before, therefore I believe it is something we've changed. I will continue investigating... UPDATE 1: The entities with errors are info_particle_system. These appear to be unrelated to the detail system crash, but still need looking into. UPDATE 2: These crashes only happened recently, therefore it is unlikely to be an issue with the map file. Discounted theory 1. Temporary Solution: This is a map issue, not a code bug. If other maps are found to exhibit similar behaviour, then i will reconsider my conclusion. we have the vmf for this map, i will look into fixing it. Actions i suggest. - Remove emp_tropicvendetta_rc4 from active map rotation, until this issue has been addressed. - Please report any other maps that exhibit similar behaviour.