ValveSoftware / Source-1-Games

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

[TF2 x64] [BUG] Damage taken while uber is active #5993

Open a428c1z673f4b42 opened 5 months ago

a428c1z673f4b42 commented 5 months ago

Issue (and explanation of shared video clip): Two medics "uber chaining" and whilst ubered, the ubering medic takes damage despite being in an ubered state. The medic being ubered however, is invulnerable. In conclusion, one medic is invulnerable, and the other loses their invulnerability.

Technical: Both clients were using Windows and playing TF2 on the x64 bit version.

A theory: Could be if medic A has an active uber ongoing and medic B activates uber on medic A. Medic A is invulnerable while medic B can still take damage as the invulnerability disappears from the previous active uber (which of course should not be happening).

This has happened multiple times in the game.

A proof of concept clip of the issue: https://streamable.com/cidk48

JoriKos commented 5 months ago

I'm fairly certain this is a well-known bug with Übering someone while you're already under the effect of an Über. The Über was being used in the clip, but you didn't actually have the Über effect, so it's not exactly correct to say you got damaged "while Übered".

a428c1z673f4b42 commented 5 months ago

I've never experienced this bug before and just a month ago, I've seen other medics uber chaining and they didn't seem to experience the same issue. they were invulnerable, both of them.

jh34ghu43gu commented 5 months ago

At least a 4 year old bug as far as I can recall.

Kacey2k commented 5 months ago

Age of the bug is not really relevant, what matters if properly documenting it and making steps of reproduction clearer.

Looks to me the game just sees the uber running out from the 1st uber and removes your invulnerability since you were still under their uber when you activated your own.

It seems the 1st uber has priority to remove the invuln effect, when it should instead be overwritten by the user's own uber.

While it is old, it would be nice to see a fix sometime in the future as I am sure everyone has experienced this at least once, and it is quite frustrating to encounter.

jh34ghu43gu commented 5 months ago

Age of the bug is not really relevant,

Sometimes it is since it can be helpful to know what patch caused it. I brought up the age because the OP makes it seem like x64 caused it when it is much older than that patch.

Doclic commented 4 months ago

Technical: Both clients were using Windows and playing TF2 on the x64 bit version.

This also happens on the x86_64-linux-gnu clients, and servers (both the dedicated and integrated ones).

Edit: But I highly doubt the client matters here, this sounds like a server logic issue.