reported earlier INU drift and Lima tracking bug

[Moxica]

It has been explained that the FCR find and assign targets, and loading them into the hellfire.
But the hellfires still scan, find and choose target when they get "closer"
Therefore they can not see the difference between a dead tank and a live AAA as they both represent a huge lump of metal.
What I find contradictory, and don't understand in this context, is why then, do they miss when INU is out of whack?
And with miss, I mean going 50-100 feet off target, and hitting empty ground.
What selects that sorry specific point?
Is it downloaded coordinates, or does the built-in agm radar hallucinate?

Edited January 15, 2024 by Moxica

[Moxica]

"Cannot reproduce"? Wut?
I thought this had been verified allready, since it was discussed and verified with tracks and reported in several threads.
Like this one:

 

Edited January 15, 2024 by Moxica

[Tom P]

"Early Access"
What's the range your engaging from? I find short range engagements (under 3k) with the L model hellfire is almost pointless. 

[Moxica]

In my last "case", 4-6 clicks, and I actually changed position, flew in a bit closer while resetting INU, and hit all of 'em.
 

Edited January 15, 2024 by Moxica

[Moxica]

Still there, and in conjunction with the FCR.
INU reset still works as a solution.
I am therefore confused as per my question in this thread:
 

 

[BIGNEWY]

6 hours ago, Moxica said:

It has been explained that the FCR find and assign targets, and loading them into the hellfire.
But the hellfires still scan, find and choose target when they get "closer"
Therefore they can not see the difference between a dead tank and a live AAA as they both represent a huge lump of metal.
What I find contradictory, and don't understand in this context, is why then, do they miss when INU is out of whack?
And with miss, I mean going 50-100 feet off target, and hitting empty ground.
What selects that sorry specific point?
Is it downloaded coordinates, or does the built-in agm radar hallucinate?

 

if you are reporting an issue please include a track replay

49 minutes ago, Moxica said:

"Cannot reproduce"? Wut?
I thought this had been verified allready, since it was discussed and verified with tracks and reported in several threads.
Like this one:

If it is the same issue or related why are you trying to report it again? 

Please understand we can not waste to much time on reports that do not have the data we need or have replies that are off topic or un helpful for a bug report. I have cleaned the thread and merged with the other report.

If you have short track replay examples and you want me to add them to the report please PM me. 

But note 

process should be

1. designate,

2. action hellfire,

3. do NOT move,

4. launch,

5. de-action.

remember time and movement reduce accuracy 
 

thank you