Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The second time, I was playing alone. (I had placed down a beacon and was waiting for others to join.) All I can say is that I had been going up a hill in desert terrain, sprinting, when suddenly the bug appeared. The same animation errors from my first post seemed to be present (frozen frame when sprinting, halved movement speed.) This time, I abandoned the mission, but the bug persisted even when I got back to the ship.
Unfortunately, I still don't have a good idea what triggers it - maybe something about when a player is going up a steep slope and the game doesn't recognize how to go between some walking/sprinting frames at a particularly steep angle?
It's still nearly impossible for me to tell what causes it... but in this instance, it seemed tied to some hard-to-generate particle effect or interaction caused b those entities all exploding in close proximity. I know it's not much to go on, but hope this is at least a more testable insight into this issue.
(Responding to post above.) Glad someone noticed this thread...I just figured this bug wasn't quite common enough for it to make Arrowhead's top priorities for now, and I'm not part of the Discord or anywhere else it might be more noticeable. All I can say is that using Steam's 'verify integrity of game files' might help put off the bug. Sorry this thread isn't more useful - I've just been trying to document my interactions with this rare, but effectively game-breaking bug. (Though not game-crashing.)
Played a number of matches, but the bug finally appeared again. We extracted from a mission, and when we got back on the ship, the bug took effect for me. Not much to really add - we dropped stratagems on the landing pad as we left, but the bug was only apparent AFTER I was in the 'mission complete' piece after it loaded our characters back into the ship. So, bug's still there, but fortunately still rare.
Yes, sadly, the bug returned.
(Actually there was another prior instance, but I didn't get around to logging that - call it Note 10.5.)
With under a minute to extraction, there weren't really many enemies around. Everything seemed fine. Then, BAM, something a teammate called dropped in and the bug kicked in. Seemed it was even a bit worse than usual - legitimately could have been 1 frame every 2 to 5 seconds. It was so bad, even the other players noticed. The bug persisted for the entire 'mission complete' screen. (Evidently, did NOT affect other players - for me, it also affected the timer display. When the others extracted, it still said I had 16 seconds or so left.) Eventually, the game snapped - it DID NOT completely crash, but I think I disconnected from the session and then the bug was gone when I loaded back into the ship alone, after it struggled through the mission result screen
Also, new error - in a later mission, it told me something like 'could not maintain connection' and kicked me out of a mission. No prior warning, but it did seem like some other people who were trying to join failed to mid-mission, so maybe that was a genuine bad host connection.
Again, at this point, this thread is mostly to record the bug's persistence across patches. I understand why it might persist, since it seems to be a rarely-triggered thing, and since it doesn't totally crash the game, built-in error reporting that kicks in when the game crashes is irrelevant here. I guess I need to explore the discord server. If anyone else has encountered this bug and already participates in that, feel free to link them to this thread. (Though, without any hard data, I don't know how useful it will be.)
Bot mission, operating roughly in teams of 2, and I had just throw a stun grenade. When it went off, the bug kicked. Curiously, it did not seem as strong as the last incident - the framerate was obviously choppy, but might have been (barely) playable. However, it also completely stopped updating every few seconds, so the net result was still miserable. I left the match after saying I had a bug, and it was still present when I returned to the ship.
So, yeah - highlights were that the bug appeared after a stun grenade this time, for some arcane reason it lost fewer frames than usual, and was still present when I left the match and returned to the ship.