Captain America Attack bugged on Civil War (PS4)
In addition to the gamebreaking bugs from my other thread, a comparatively minor annoyance on Civil War:
During Captain America attack mode (the one that's triggered via the whirlpool) the first shot you're supposed to make sometimes simply doesn't register.
You are supposed to hit a red target to the right of the whirlpool (I think it's the ramp that also starts fights) but even a full force, clean hit sometimes doesn't register as a successful shot. I managed to hit that thing cleanly 4-5 times during a single mode and it's safe to say that it just bugs out sometimes. I have no idea what may cause this, it seems pretty random. Maybe hitting the target the second the mode starts (you can hit the target before the table is ready - despite the target already being there, there seems to be a short delay before you can acutally hit it and have it register as a hit). At least that's the only thing I can think of. It happened to me about 1 out of 5 times I played that mode; so, it's been a pretty frequent issue.
In addition to the gamebreaking bugs from my other thread, a comparatively minor annoyance on Civil War:
During Captain America attack mode (the one that's triggered via the whirlpool) the first shot you're supposed to make sometimes simply doesn't register.
You are supposed to hit a red target to the right of the whirlpool (I think it's the ramp that also starts fights) but even a full force, clean hit sometimes doesn't register as a successful shot. I managed to hit that thing cleanly 4-5 times during a single mode and it's safe to say that it just bugs out sometimes. I have no idea what may cause this, it seems pretty random. Maybe hitting the target the second the mode starts (you can hit the target before the table is ready - despite the target already being there, there seems to be a short delay before you can acutally hit it and have it register as a hit). At least that's the only thing I can think of. It happened to me about 1 out of 5 times I played that mode; so, it's been a pretty frequent issue.
Comment