Page 2 of 6
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 16:09
by F_leon
Somehow the Merkava's Turret got bugged, theres no collision anymore!!
the shells goes right through and we can walk through it too. maybe the "Weak spot change"
Posted: 2017-10-29 16:12
by Mineral
F_leon wrote:Somehow the Merkava's Turret got bugged, theres no collision anymore!!
the shells goes right through and we can walk through it too. maybe the "Weak spot change"
Thanks! We are aware of the problems with merkava and asked server owners to avoid any maps with it.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 16:19
by Outlawz7
TBoy205 wrote:Pls discontinue changes to coop. There are way too many issues in deployment that need fixing. Better yet just discontinue coop.
Fixing co-op doesn't take away from fixing issues in PvP.
VTRaptor wrote:I might be wrong. I just never seen this layot being played after atgm nerf.
I've seen it in the past year.
Ok now that's a bug.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 16:25
by Allahu Akbar
F_leon wrote:Somehow the Merkava's Turret got bugged, theres no collision anymore!!
the shells goes right through and we can walk through it too. maybe the "Weak spot change"
Ancient Da'at Yichud phase-shift technology has been noticed by goyim! Oy Vey!
Updated BMP-2M ATGM tubes to move less up and down.
Is this a visual effect or is actual depression/elevation of the weapon changed?
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 16:30
by F_leon
back again, Lasing is bugged, as you get a insta lock and can even bomb upside down from the jet
and you can't get out of the map in the Jet anymore? because we are getting a 10 sec warning ( tested on Khamisyah)
and the merkava ( test in Bijar )
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 16:38
by AlonTavor
Lase locking logic wasn't changed, bombs were always like this, they will have to be adjusted after laser feedback as they were intended to work with static lasers.
Jet out-of-bounds will be fixed.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 16:43
by F_leon
[R-DEV]AlonTavor wrote:Lase locking logic wasn't changed, bombs were always like this, they will have to be adjusted after laser feedback as they were made to work with static lasers.
Jet out-of-bounds will be fixed.
thanks again!!
but hey, the new lasing system overall is pretty good and i loved it. no hate from my part
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 17:06
by AfterDune
Luiibr wrote:When will ww2 come out?
That will be a v1.5.x patch.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 18:11
by Mostacho
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 18:22
by DogACTUAL
Updated all choppers have 60 flares that fire in pairs of 2 alternating to front and side.
Thank you DEVs.
Updated missile trial of ATGM and AA missiles to be slightly longer.
What does that mean, clarification please.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 18:38
by Lugi
Is anyone else having much bigger ping on all servers after this patch?
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 20:00
by DogACTUAL
B2P1 wrote:I noticed an issue with the new lazing system. You can't laze any vehicle that's skylining itself. If the point of aim after the vehicle doesnt cross any terrain, you won't be able to laze.
This is true, i tested it on the mountain ridge on test airfield with a challenger 2, you can't see any lase symbol on it and the LGB won't hit the challenger 2, but like DEV suggested it is only if you lase friendly vehicles, hostile vehicles work perfectly.
Was similar before the update, if you lased a friendly vehicle or anywhere close to it friendly LGBs wouldn't hit it, but hostile LGBs could.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 20:07
by AlonTavor
There's also an issue where the officer is unable to see the laze he's placing when standing next to terrain or static, The laser will be at the correct position even if you're unable to see it.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 20:22
by FFG
TOW HUMVEE HYPE
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 20:23
by DogACTUAL
Yeah, noticed that one too, was standing behind some hescos and lased the mountain ridge, but it still works just as advertised.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 21:07
by Kurt117
I can't update to this version. The update window just closes in the middle of installing the update. i even reinstalled the whole game but the same thing happened when the launcher was updating the game to 1.4.18.0
what can cause this problem?
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 21:23
by ctbear1996
TBoy205 wrote:Pls discontinue changes to coop. There are way too many issues in deployment that need fixing. Better yet just discontinue coop.
LOL am I reading something wrong? People are actually making statement like this? Btw great update on coop
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 21:51
by SWAT-
What happened with the map boundaries when flying? I can't seem to go outside map with any jet, there's like a timer and I start bleeding as if I was on foot
By the way, good job for keep the game as updated as possible.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-29 23:46
by Singh408
[*]Wanda Shan
- AAS64: Replaced Z-9 transport with Z-10, replaced Huey with Tiger.
ooooh shit! I suggested that

thanks and you're welcome all you CAS whores out there.
re: PR:BF2 v1.4.18.0 & v1.4.19.0 Changelog
Posted: 2017-10-30 02:57
by DogACTUAL
Invisible vehicle mines after the update. Could be a preexisting thing, but this seems new to me. Was on the server the whole round without interrution from the beginning. Couldn't see a mine on a bridge on Vadso while my driver could, even though he joined the round late. Next bridge was examined carefully while crossing and then we ran over the invisible mine. Could just have something to do with the brdiges on Vadso, maybe the mines sink into the concrete too deep.