ValveSoftware / Source-1-Games

Source 1 based games such as TF2 and Counter-Strike: Source
640 stars 74 forks source link

[TF2] Invisible Rottenburg barricade #3699

Open pixl-creator opened 2 years ago

pixl-creator commented 2 years ago

The barricade that can get crushed by tanks on Rottenburg always appears to be invisible now. It used to sometimes not appear when joining mid-match but now it's never visible, even after it has respawned.

shaiko2k commented 2 years ago

I'm not sure the specific cause for the issue, but I can confirm that I have noticed the barricade model disappearing at times. It is present when I first load up the map, though.

rabscootle commented 2 years ago

Adding onto this:

REPRO STEPS

  1. Load into mvm_rottenburg and begin a wave with tanks ("tf_mvm_jump_to_wave" can be used)
  2. After tank has destroyed barrier, reload map ("map mvm_rottenburg") Repro video: https://www.youtube.com/watch?v=ybvyD-z8CRk

    The barricade entity in mvm_rottenburg has an issue where the barricade's model can be invisible for the entirety of the match. The collisions and other logic continue to function like normal, however, which can confusion for players.

hl2_BnpfjkOCiE

hl2_QzliGuL2gO

mtxfellen commented 6 months ago

This can be fixed by parenting the barricade prop to the particle system used when it breaks so that it always passes the PVS check, though the true nature of the issue seems to be related to the fact that the barrier's origin lies quite far outside the map, so this fix is not guaranteed to work for any other maps that use this barrier (Rottenburg is the only Valve map that does so).

Related to this is that the barricade prop also has collision enabled on it; collision is supposed to be handled by a func_door in the same location, resulting in laggy collision with the barrier on high ping. Both can be applied in the map .vmf like so:

entity
{
    "targetname"  "Barricade"
    [...]
    "solid"    "0"
    "parentname"  "Tank_Barricade_Particle"
}