Annoying Clan Lrm Issue
#1
Posted 05 October 2014 - 08:23 AM
Basically I get the red of target lock plus the announcement, "Target Aquired" but their seems to be a big delay in ACTUALLY getting a lock. Often, in fact almost every time, I get these notifications only to have my LRMs not actually lock and basically act just like I dumb fired them at the cursor.
Anyone else having the same issue?
#2
Posted 05 October 2014 - 08:29 AM
Viktor Drake, on 05 October 2014 - 08:23 AM, said:
Basically I get the red of target lock plus the announcement, "Target Aquired" but their seems to be a big delay in ACTUALLY getting a lock. Often, in fact almost every time, I get these notifications only to have my LRMs not actually lock and basically act just like I dumb fired them at the cursor.
Anyone else having the same issue?
Yup. Known issues.
Takes about a full second or so after tone to get full lock. I jet expect it and don't really notice anymore. Heck, honestly, it's ok with me as a trade off for being half weight. The stream fire helps to, but lets face it, if one doesn't have AMS, those streams focus damage better than the cloud of IS LRMs, anyhow.
#3
Posted 05 October 2014 - 09:04 AM
go off the beep, not the red cursor or voice.
#4
Posted 05 October 2014 - 09:10 AM
#5
Posted 05 October 2014 - 09:37 AM
#6
Posted 05 October 2014 - 09:42 AM
Monkey Lover, on 05 October 2014 - 09:37 AM, said:
Seems like an easy fix, I mean IS LRMs work like they are suppose to so just copy and paste the code that manages IS LRM locking to the code that manages Clan LRM locking.
#7
Posted 05 October 2014 - 09:53 AM
Viktor Drake, on 05 October 2014 - 09:42 AM, said:
Seems like an easy fix, I mean IS LRMs work like they are suppose to so just copy and paste the code that manages IS LRM locking to the code that manages Clan LRM locking.
I have seen the lock issue with IS lrms too. This showed up right after they put the reconnect code in. What i find funny is the tone lock works most the time. The code they're using for it should be used for the cursor.
Edited by Monkey Lover, 05 October 2014 - 10:00 AM.
#8
Posted 05 October 2014 - 10:24 AM
#9
Posted 05 October 2014 - 10:24 AM
#10
Posted 05 October 2014 - 10:46 AM
#11
Posted 05 October 2014 - 11:10 AM
#12
Posted 05 October 2014 - 11:20 AM
Viktor Drake, on 05 October 2014 - 09:42 AM, said:
Seems like an easy fix, I mean IS LRMs work like they are suppose to so just copy and paste the code that manages IS LRM locking to the code that manages Clan LRM locking.
I'm having the same issue with IS LRMs. Lock, tone, fire. And they were not actually locked... dag nabit.
Edited by Sorbic, 05 October 2014 - 11:21 AM.
#13
Posted 05 October 2014 - 11:24 AM
#14
Posted 05 October 2014 - 11:45 AM
#15
Posted 05 October 2014 - 12:07 PM
151st Light Horse Regiment, on 05 October 2014 - 09:04 AM, said:
go off the beep, not the red cursor or voice.
Yup.
It's also an IS issue, it's just more pronounced on the Clans. I think it's also a bit of a lag issue, where your client registers the lock but the server does not.
#16
Posted 05 October 2014 - 12:25 PM
Bishop Steiner, on 05 October 2014 - 08:29 AM, said:
Takes about a full second or so after tone to get full lock. I jet expect it and don't really notice anymore. Heck, honestly, it's ok with me as a trade off for being half weight. The stream fire helps to, but lets face it, if one doesn't have AMS, those streams focus damage better than the cloud of IS LRMs, anyhow.
At this point, getting used to bug is a bad thing.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
























