Product: Star Wars Battlefront IIPlatform:Microsoft XBOX OneWhat is your issue related to? GeneralSummarize your bug Your ship blows up for no real reason. You don't touch any building, ship, floating object, whatever - but the game detects that you did and kills you.What is your gamertag/PSN ID/EA Account name?How often does the bug occur? Every time (100%)Can you tell us the date (MM/DD/YYYY) that you saw the bug?What time did you see the bug? (HH:MM AM/PM)In what game mode did the bug occur? Starfighter AssaultWhat is your time zone?Steps: How can we find the bug ourselves? Play Starfighter Assault and try to do a move that involves going close to some object. What happens when the bug occurs? You'll blow up without actually touching anything. Sometimes when you go too close, the game just blatantly slaps you into the surface. What do you expect to see?Please select your region EuropeAMD or Nvidia Model NumberIt's like the textures don't even matter. You can imagine the whole thing as two bricks: the small one being your starship, and the big one an object on the map. Now, they seemingly sculpted these bricks into finely shaped things, yet they still retain their invisible... Brickness.But I guess this is something that could have only been corrected earlier in the development phase, not a simple "patch-thing". Shame, because SA is a highlight of the gameplay, but you can't really pull any impressive moves because of this.

Here's an example of a "collision" that occurred just a couple of nights ago despite a minimum 2 m distance from the visible surface of the battleship: https://youtu.be/RJwGfRAowtMJust before the Y-Wing explodes, you may notice that it pitches up very rapidly; that's because the collision caused the ship to change its orientation before exploding. You can see by the aiming reticle that I had just begun to pitch down before the collision.

Here's another inexplicable collision that occurred tonight:https://youtu.be/Rnbfs3dAiFQThe 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.

@grimmace2No, server lag is definitely there at times, but this is different. And yes, they took out the "ships crashing into each other" aspect totally. I guess the thought behind that is that a high percentage of players in the first game "solved" the Slave I vs Falcon battles by simply flying into the other one. I think in the final state of the game, it is even possible to do that in a way that you survive the crash, while the other hero ship is destroyed, provided you have high enough health on collision.What I'm talking about is noticeable even without the rubber banding. While dodging obstacles, sometimes you just crash, that's kinda inevitable - but more than a few times, it is totally clear that you did not in fact touch anything.The other aspect I said, with you being a bit thrown around, is also connected to this. Fly close to a large surface (for example a Star Destroyer), then make just a slight mistake. The game will detect that you touched the surface (while you didn't), then it will redirect you because of this "damage", many times simply crashing you into the surface for good. Sometimes you can survive these slight collisions with random debris, that's how I noticed this redirection that follows it.

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_sNow that I think about it, yes, I do follow what you're saying. I have had a couple of instances on Fondor where I'm flying close to the "bubble" part of the structure, thought I was hugging the surface but exploded out of nowhere. Thought it was my piloting skills but maybe it was the collision detection?

Starfighter Assault: Horrible collision detection

13 Replies

grimmace2
8 years ago
@felker_s
Are you experiencing the sporadic lag as well? I've had similar issues occur (most noticeably on the D'Qar map for me) where I'm flying straight, with no obstacles in front of me, inside of a structure (reactor core, superstructure, etc.), I experience a little "jitter", next thing you know I'm flying directly into a wall. I have chalked up the "jitter" to server lag as one second I'm looking at a void, next second I'm exploding. Could be collision detection but I have flown directly through many teammates and enemies with no ill effects. Next time you're in a map and someone gets a Falcon, trying flying through them. Absolutely no collision detection there! Obviously I know it's different for hard targets (buildings, ships, etc) but your issue may be server lag more than anything else?
felker_s
8 years ago
@grimmace2
No, server lag is definitely there at times, but this is different. And yes, they took out the "ships crashing into each other" aspect totally. I guess the thought behind that is that a high percentage of players in the first game "solved" the Slave I vs Falcon battles by simply flying into the other one. I think in the final state of the game, it is even possible to do that in a way that you survive the crash, while the other hero ship is destroyed, provided you have high enough health on collision.
What I'm talking about is noticeable even without the rubber banding. While dodging obstacles, sometimes you just crash, that's kinda inevitable - but more than a few times, it is totally clear that you did not in fact touch anything.
The other aspect I said, with you being a bit thrown around, is also connected to this. Fly close to a large surface (for example a Star Destroyer), then make just a slight mistake. The game will detect that you touched the surface (while you didn't), then it will redirect you because of this "damage", many times simply crashing you into the surface for good. Sometimes you can survive these slight collisions with random debris, that's how I noticed this redirection that follows it.
grimmace2
8 years ago
@felker_s
Now that I think about it, yes, I do follow what you're saying. I have had a couple of instances on Fondor where I'm flying close to the "bubble" part of the structure, thought I was hugging the surface but exploded out of nowhere. Thought it was my piloting skills but maybe it was the collision detection?
NOTMYSCVS
8 years ago
Second. Collision detection is horrible! Also, I have def experienced the 'flying straight one minute only to be suddenly flying into a wall the next' phenomenon. I just try to be really careful and not even come TOO CLOSE to enviro objects when i dont have to.
narion_k
Seasoned Veteran
8 years ago
Here's an example of a "collision" that occurred just a couple of nights ago despite a minimum 2 m distance from the visible surface of the battleship: https://youtu.be/RJwGfRAowtM
Just before the Y-Wing explodes, you may notice that it pitches up very rapidly; that's because the collision caused the ship to change its orientation before exploding. You can see by the aiming reticle that I had just begun to pitch down before the collision.
felker_s
8 years ago
@narion_k
Thanks for the video, things like this are exactly what I'm talking about.
narion_k
Seasoned Veteran
8 years ago
Here's another inexplicable collision that occurred tonight:
https://youtu.be/Rnbfs3dAiFQ
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.
felker_s
8 years ago
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.
Anonymous
8 years ago
Approved
@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.
narion_k
Seasoned Veteran
8 years ago
@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