cl_flushentitypacket 1 was designed as a nuclear option against this. If the server sends an empty packet (often a sign that it is "committing" the current world state without changes), the client interprets this as: "There have been no changes, but you should also forget any entities that might be stale."
Leave cl_flushentitypacket 0 in your config.cfg . Do not add it to your autoexec. Do not bind it to a key. The only time you should touch it is if you are a server administrator debugging a bizarre entity persistence bug on a legacy mod. cl-flushentitypacket cs 1.6
occurs when the client continues to render an entity (e.g., a player model, a dropped weapon, a grenade) at a certain location, but the server has already moved or removed that entity. Packets containing the "removal" instruction are lost. The client's buffer stubbornly holds onto the outdated entity, creating a "ghost" that the player can see but not interact with. Shooting a ghost does nothing, but it can obscure real enemies. cl_flushentitypacket 1 was designed as a nuclear option