++ Noise at the end of a round (sounds like hover over button noise) hundreds of times per second.
++ Return of the Invisible EV bug on white chapel
++ Random blocking collision placed around maps, think its related to downed/gibbed players or molotovs
++ Random crash to desktop on connecting to servers
++ Hand messed up spinning around 1000 times in a second
++ Delayed / De-Synced sticky bomb throwing (not ping related)
++ Invisible Sticky Bombs
++ Cannot plant the C4 on Execution
++ Invisible Bombs on Execution
++ Missing mid game videos on Stopwatch
++ Stopwatch wrong win/loss report
++ Invisible MG nest turrets (MG can still be used)
++ Seen players not always reporting Merc playing on scoreboard
++ Silent Weapons (mainly stark from what I have personally seen)
++ Invisible molotov
++ Incorrect range on molotov (destroys things placed many feet away from flames)
++ Molotov spread fail (molotov only covers a single block worth of space)
Bugs since BIG update...
Did you experience sticky keys? A few times now when I tried to release the crouch or defib button the action still continued. I’m not sure if it’s on my side, thats why I’m asking.
++ Rounds won in execution are counted as amount of rounds your team won at the end of the game, instead of the amount of rounds you actually won. (joining late or switching sides is not accounted for)
molotov sometimes passes through enemy players
molotov sometimes does not ignite, especially when thrown at a ceiling
random file names appearing on the hud during a match
Few ads:
++ Missing ramp on blocker carriage on Trainyard
++ Loading into game as Player501 rather than in game nick
++ When playing stopwatch on Chapel, at mid-game 1st Voiceover is for the incorrect team (ie “Destroy their EV” VO for attackers, then switches to correct VO)
++ White string (?INT?dialogue.rhino.Rhino_Exertion_Fire_Medium_02? or thereabouts) (missing audio file(s) ?)]
HTH,
Just makes me crazy that I have reached a point where I expect more bugs to be added each update then are fixed.
It is really not good enough and it needs to be improved and quickly!
Not only that but bugs that have already been fixed end up turning up broken again months down the line.
We still seem no closer to finding solutions to many other bugs that have been around for almost ever…
- Players stutter when going up and down ramps/stairs
- Downed players revived in position of death and not downed player position
- Downed players float up and down if killed on the edge of something
- Incorrect collision for health and ammo packs
- Inconsistent audio timing on abilities
- Warping while using movement abilities
- Inconsistent reload animation cancel timings
- Instant respawn between waves
and sooo sooo much more.
Duplicate c4-s in execution mode…
How it happened:
Engineer spawned with bomb.
Engineer died, dropped bomb.
I revived engineer and picked up the bomb.
Engineer went in and planted the bomb he did not have.
???
In stopwatch mode, the voice overs in the introduction of the 2nd round are instructions for the other team.
On Execution, players can join mid game that would be given the bomb, and they are. But they have not actually spawned in yet. So teams have a 30 second wait with a connecting char who has the bomb, the connecting guy can do nothing about this, apart from join 30 seconds-ish later to find he’s being votekicked.
Game locked up just now. Windows forced close, then restarted and entered a match. Followed some guy carrying the obj for a while then went to revive someone and OH WAIT PRIMARY FIRE AND SECONDARY FIRE AND THE USE KEY ARE UNBOUND
For the love of god I am SICK OF THIS ISSUE. How can you not deal with this SD? It’s embarrassing!
[QUOTE=mccrorie;540645]Game locked up just now. Windows forced close, then restarted and entered a match. Followed some guy carrying the obj for a while then went to revive someone and OH WAIT PRIMARY FIRE AND SECONDARY FIRE AND THE USE KEY ARE UNBOUND
For the love of god I am SICK OF THIS ISSUE. How can you not deal with this SD? It’s embarrassing![/QUOTE]
This issue is known and was not introduced with the latest update. They are aware but it is hard to find the cause of the bug. Was mentioned in one of the bug topics.
Yes, this has happened to me many times, but this is the first time a crash coincided with those functions losing their binds.
[QUOTE=PixelTwitch;540576]
++ Incorrect range on molotov (destroys things placed many feet away from flames) [/QUOTE]
This is so annoying! Radius of destruction seems to be the double of the animated flames.
especially above the flames. If i double walljump in the flames and get higher than one character’s height, im still getting ticked to death. Could it be that flame hit detection is also client-based?