Build: 4545 Mode: Multiplayer Dedicated, Survival SERVER NAME: N/A SEED-ID: N/A If applicable: MODIFIED PLAYFIELDS: No Reproducibility: Often Severity: Major Type: Combat/PvP Summary: CoQ spam due to network packet content exception Description: This issue has been rather annoying to reproduce, and there's no way we can reliably reproduce the issue, but we know it does happen in relatively short order after PvP has started. The issue occurs when 3 or more factioned players are in SV PvP in the same space playfield. The blueprint doesn't seem to matter, but the issue occurs when a player in an occupied cockpit (doesn't matter which one) is destroyed by enemy fire in a tight space. The weapon has to be some kind of hitscan weapon usually (we used miniguns that triggered it reliably, although rocket launcher has been more reliably producing the issue as of late). This CoQ error makes the server think the dead player is still piloting the ship, even though the ship doesn't have a cockpit anymore. Using entity commands shows the player still as as the pilot of the dead ship, even though the player has since respawned. Any number of actions done by this player will then trigger a CoQ for all other players in the same playfield (but not the player who was shot at). Actions known to cause CoQs at this point include firing weapons, using gm command, entering cockpits, turning a ship on and off, and probably others. The CoQ frequency varies from player to player initially, but eventually it will affect all players. The only known fix is to fully reset the server, which stops the CoQ spam, or maybe logging all players off, it's hard to tell. The error seems to occur reliably when the player and cockpit are destroyed while occupied, but we are unable to reproduce this always, generally though it occurs once every 20 or so cockpit destructions. Steps to Reproduce: 1) Have at least 2 ships controlled by 2 hostile factions 2) Engage in PvP with 3 or more players rendered/present in a faction 3) Attacking a player with hitscan weapons only, destroy the players cockpit (not the player) while they are in 1st person, ideally try and trigger both cockpit and player destruction simultaneously 4) CoQ happens with specific error (see logs), at this point the dead player may trigger more CoQs as they continue to interact on the playfield 5) Have temporary resolution by restarting the server. The affected player no longer triggers CoQs by their actions. Screenshots, Crash Logs, any other Relevant Information or Download links: Can provide a list of BPs we have reproduced the error with. There is one additional player log too large to upload on here. BAD WORKAROUND: Since the issue is caused by the cockpit being destroyed, the temporary (but hacky) solution to all this is ensure the cockpit can never be destroyed in PvP. The means by which we did this is to remove weapon colliders on the SV cockpits, as well make a new material that effectively nullifies blast damage from all sources (high hardness value). This is not a great workaround of course because now players are unable to remove cockpits (they can repair them for some reason), and when the ship's power inevitably dies the player must sit and wait for the ship to fully stop before being allowed to exit the ship. It is possible to use the detach command to mitigate the latter issue tho.
