devtrackers.gg
Hey, we're already aware of this issue and looking into the cause of it. Thanks for trying to report it though!
Hey, we're already aware of this issue and looking into the cause of it. Thanks for trying to report it though!
Try to stick together with your squad and focus on healing/supplying/reviving your squad mates and the objectives the squad leader picks.
Yep it's high on our todo list, I agree it needs to get sorted asap.
The icon on the right indicates that you had a high latency, so it's probably a connection issue.
I've seen people defend Dice's decision to make leaves impenetrable. It's like the mini garden in favela in MW2 all over again.
It's not a decision, it's a bug. A full sweep of all trees throughout the game is currently being made to ensure leaves don't block bullets.
Thank you for the reply.
I also recall it being 20m from when it was implemented during BF1 and—unless I'm forgetting—in 200h on BFV I've never experienced close range trades like this.
I also find interesting how the game says OP finished 2nd and had the last kill, despite the kill log indicating they died before the enemy. Which of the two should be trusted in this case? Kill log or end of round screen?
That's a good point, I also noticed. Another question I have is what happens when the kill trade is between the last two players.... We'll follow up on these issues. Although rare they need to be sorted.
/u/lytlb1t is kill-trading at close range in Firestorm by design?
I thought the game specifically forbid this under a certain distance.
Hi, yeah I also assumed it was only above a certain distance (20m?). I'll mention it in our internal feedback channel to see if this is a bug or not.
Interesting, I saw some code fixes about similar issues but this one slipped through apparently. I'll make sure to follow up as well.
Ah, BF2 loading screens. Spent more time at 62% loading than playing the game.
Just kidding, but it sure felt that way at times. At least I can hear the menu music any time I want now that its imprinted into my brain.
BF2 had a rough launch as well, btw. It launched with some sort of memory leak that would make it impossible to find servers.
The first time I installed and played bf2 I got stuck at 62% for so long that I decided to reinstall the game since I thought something went wrong.
Ok.So im gonna buy it today.It looks sick
Welcome! :)
Don't worry, our internal feedback channel is constantly being updated with important reddit and twitter links, feedback on this subreddit doesn't go unnoticed.
Thank you for saving me from that fall :3
You're welcome ^^
Haha wow, I wrote that detection code and I didn't know this was possible.
10/10 vault grab very nicely executed
Battlefield 4142
Can u fix this bug where someone is prone under trees for example Narwik and u throw Dynamite on him but the trees absorb the damage from Dynimate ?
This is probably the same issue, QA is doing a sweep on the trees on Narvik already so with a bit of luck this will be fixed soon
I play on PC and I notice trees blocking AA fire on the AA emplacement on the G flag of Twisted Steel and the A flag of Narvik. When tracking planes that are in range and fly behind a tree the shells stop at the tree. I have noticed this with trees on Arras but I was on mobile AA so I am unable to pinpoint a location other than the trees stop AA fire.
Thank you.
Forwarded it to QA. The one on Twisted Steel is probably the same tree, but they'll make sure to test it. Thanks for the feedback :)
Is there a way to make all foliage be able to be shot through? I feel like trees are always blocking my shots. Thanks for responding to the community btw. You guys are doing great.
Leaves shouldn't block bullets, whenever that happens it's a bug. If you tell me where it happens I can forward it to the person who will fix it.
Are tree leaves blocking fixed emplacement AA rounds by design or the same problem as above when shooting at aircraft?
If you give me an exact position we can take a look
Thanks for the video. QA was able to reproduce the issue and spotted the problem. Will be fixed soon :)
Interesting, this is my stuff. I'll get it tracked and look at it later. Seems obvious that the character's velocity is still applied (even though it shouldn't)