Here's another inexplicable collision that occurred tonight:
The incident occurred on 2018-01-16 at 9:52 PM, US Eastern time.
This time, I have absolutely no idea why my starfighter exploded. Based on the rapid camera movement and the "Defeated" message, it seems that the game thinks my A-Wing collided with something. I've watched this clip several times, though, and it still doesn't look I hit anything. My ship wasn't even close to any visible objects.
Lol I gave up long ago on this. I guess this would take one helluva revamp - not one that a developer would do after a game's release. I just don't understand that during the long hours of testing, how did nobody notice what I noticed during the first hours of the beta.
@felker_s wrote:Lol I gave up long ago on this. I guess this would take one helluva revamp - not one that a developer would do after a game's release. I just don't understand that during the long hours of testing, how did nobody notice what I noticed during the first hours of the beta.
I wonder the same about the many other bugs. Achievements are showing the wrong amount of completion right after a match (like showing still 7/10 when in fact you alreay have 9/10) so often, it would have been noted during any good beta testing before releasing the game.
Apparently there wasn't much time or resources for a real in-depth testing of the game before releasing it. But more annoying than that is the time they take to fix these things. It can't be that hard to fix a simple counter issue.
Same issue here, first i thought it might be a lag or something. It also happens in sp map
@felker_s wrote:Lol I gave up long ago on this. I guess this would take one helluva revamp - not one that a developer would do after a game's release. I just don't understand that during the long hours of testing, how did nobody notice what I noticed during the first hours of the beta.
This is on their list of bugs they are trying to fix.
https://battlefront-forums.ea.com/discussion/97668/swbfii-known-issues#latest
