10 replies to this topic

[MasterGoa]

Hey boys and girls!

It was reported that LRM target aquisition is sometimes buggy.

Well it happened quite a few times today.

Simple symptoms:

Get visial contact.

Tag.

Reticle becomes red.
Press fire button.

LRM's dumb fire at what ever the reticle was pointed at and do not track at all.

Happenes 1 in 20 times maybe?

So yeah.

Note: Stalker with a 50 shot of LRMs in one salvo, Beagle and Advance Range module...
And tags.

Edited by Marvyn Dodgers, 14 July 2014 - 02:48 PM.

[xengk]

I get this always and I have chalk it up to distance lag from being on the other side of the globe.
Even normal target acquisition, pressing R, is badly delayed, I have been relying more on visual to judge damage on enemy.

But your location is Montreal, you are in the same country as the server, this shouldn't be happening.
Unless there is another Montreal that I didn't know of.

Edited by xengk, 14 July 2014 - 12:18 AM.

[Bigbacon]

I am also with it being lag as I've been using LRMs a lot of the last week and as someone who plays with 300 pings and pings that swing wildly from 60 to 300 my LRMs are all over the place. I can hear the tone, press fire, there is a slight delay (not door based) and the missiles either don't track or dump into the ground. Usually happens when I fire at the tone.

i also think it has to do with the visual + the sound.

target acquisition with my pings is also very delayed.

[Petard]

You will get TWO tones before you have a hard lock with lrm's, if you fire after the first they will dumb fire, the second tone sometimes seems to have more of a delay for some reason....

[DAEDALOS513]

MasterGoa, on 13 July 2014 - 06:42 PM, said:

It was reported that LRM target aquisition is sometimes buggy. Well it happened quite a few times today.
Simple symptoms:
Get visial contact.
Tag.
Reticle becomes red.
Press fire button.

LRM's dumb fire at what ever the reticle was pointed at and do not track at all.
Happenes 1 in 20 times maybe?

Nah it happens way more than 1 in 20. This started happening since clan patch. They need to fix this, it's beyond annoying.

xengk, on 13 July 2014 - 11:42 PM, said:

I get this always and I have chalk it up to distance lag from being on the other side of the globe.
Even normal target acquisition, pressing R, is badly delayed, I have been relying more on visual to judge damage on enemy.

But your location is Montreal, you are in the same country as the server, this shouldn't be happening.
Unless there is another Montreal that I didn't know of.

It's not distance lag, this started happening right after clan patch.

Edited by DAEDALOS513, 14 July 2014 - 02:22 PM.

[DarthPeanut]

Bug with lock on indicator for LRMS both IS and Clan.

Hopefully it will be addressed in the coming patch.

Edited by DarthPeanut, 14 July 2014 - 02:23 PM.

[Naduk]

Been getting this also
Its just a lag between the lock visual/sounds and actual lock happening
Give it another half a second or full second before you fire (that is after lock is full red wait a bit more then fire)

Its good to have a work around but this bug needs fixing

[xengk]

DAEDALOS513, on 14 July 2014 - 02:23 PM, said:

It's not distance lag, this started happening right after clan patch.

I dont think it is the Clan patch, might be something before this.
I start experiencing this after one of the early patch, before then I could run my Awesome 8R Lurmboat with no problem.
I assume it was a network issue, my ISP is not known for good maintenance.

Now there is a long delay.
I would press R and heard Betty confirm the new target, but it will be 10+ seconds before the target appear on the HUD.
It get particularly worst when there are multiple enemy on screen or even with just one up close.
Even having Target Info module and BAP could not help.
Have to shelf all my LRM mechs.

The rate of me getting black screen after match loading have also increase.
My Ping is between 250 to 300ms.

[jollyrancher1]

I have it happen with artemis + bap almost every time

[DAEDALOS513]

xengk, on 15 July 2014 - 01:30 AM, said:

I dont think it is the Clan patch, might be something before this. I start experiencing this after one of the early patch, before then I could run my Awesome 8R Lurmboat with no problem. I assume it was a network issue, my ISP is not known for good maintenance.

Now there is a long delay. I would press R and heard Betty confirm the new target, but it will be 10+ seconds before the target appear on the HUD. It get particularly worst when there are multiple enemy on screen or even with just one up close.

Even having Target Info module and BAP could not help.
Have to shelf all my LRM mechs.

When you say one of the earlier patches when do you think exactly? One patch before clan? Two patches? I'm not positive but I'm pretty sure it was during clan patch, but it may have been one patch earlier. I'm just trying to narrow it down for PGI.

Anyone else know for sure.

PS. I also run 8R as my rainboat.. sweet, sweet mech.

Edited by DAEDALOS513, 15 July 2014 - 05:52 AM.

[xengk]

DAEDALOS513, on 15 July 2014 - 05:51 AM, said:

When you say one of the earlier patches when do you think exactly? One patch before clan? Two patches? I'm not positive but I'm pretty sure it was during clan patch, but it may have been one patch earlier. I'm just trying to narrow it down for PGI.

Anyone else know for sure.

PS. I also run 8R as my rainboat.. sweet, sweet mech.

Sometime early this year, Feb or March, not long after Battlemaster was released.
I was still running Battlemaster 1S with LRM at that time, and locking still works fine.
After the Griffin was released in Cbill that I start noticing locking problem on my Griffin 1S LRM support.
Didn't have any problem with it when I got them early from my Phoenix Pack.

It was also during then that I heard my ISP was attacked, I though they never recover from it which cause my connection to deteriorate.