missing track file FCR not picking up targets visible in VR

[KungFu]

So started flying with the FCR as I fly on a MP server that limits them of course.

I come up to an area with an SA6, site is huge with all kinds of launchers and supporting vehicles and a couple of shilkas.   They are on a pretty flat open area.  Im in VR and can see them easily, I would say there were 20 or so vehicles about 2km out

Hit the FCR, nothing.   Make sure it's covering the area, yep....set to continuous...no returns.  I'm at like 100ft agl and I then play with the elevation, nope nothing returned.    However like 10mins earlier this thing was picking up stuff behind trees, so I know it's working.

I wind up having George find them and fire on them with tads designation.  Most of them missed, in fact they hit the exact same empty place with different targets. (Yes I made sure the lased and got valid point tracks)

So what other than the obvious (FCR looking elsewhere, wrong elevation, etc) what would cause it to not see things that are obviously there and out in the open?

Edited August 8, 2024 by KungFu

[Raptor9]

The next update should include improvements to the FCR elevation control that restores the FCR detection capability at shallow scan angles, so you can adequately mask the aircraft behind cover and detect/engage targets (flat terrain or otherwise).

[The_Nephilim]

29 minutes ago, Raptor9 said:

The next update should include improvements to the FCR elevation control that restores the FCR detection capability at shallow scan angles, so you can adequately mask the aircraft behind cover and detect/engage targets (flat terrain or otherwise).

that would be awesome

[GrEaSeLiTeNiN]

Yeah the FCR is great esp with LINK to bypass those Xs (already destroyed targets).
I hope the bugged C-Scope symbols get fixed too.

[Recluse]

On 8/8/2024 at 3:52 PM, KungFu said:

So started flying with the FCR as I fly on a MP server that limits them of course.

I come up to an area with an SA6, site is huge with all kinds of launchers and supporting vehicles and a couple of shilkas.   They are on a pretty flat open area.  Im in VR and can see them easily, I would say there were 20 or so vehicles about 2km out

Hit the FCR, nothing.   Make sure it's covering the area, yep....set to continuous...no returns.  I'm at like 100ft agl and I then play with the elevation, nope nothing returned.    However like 10mins earlier this thing was picking up stuff behind trees, so I know it's working.

I wind up having George find them and fire on them with tads designation.  Most of them missed, in fact they hit the exact same empty place with different targets. (Yes I made sure the lased and got valid point tracks)

So what other than the obvious (FCR looking elsewhere, wrong elevation, etc) what would cause it to not see things that are obviously there and out in the open?

 

SAME HERE!!  Haven't flown the Apache for a while and decided to check out the LINK and C-Scope functions.  Had the same experience in VR clearly seeing targets ahead.  7 Km, 6 km, 5 km, 100 ft, 300 ft altitude, NOTHING.  Messed with the FCR elevation.. NOTHING.  ONE target to the left of the main group got picked up and 2 LIMAs missed it completely

FCR  finally did pick  up the main body about 2-3 km away and they were shooting at me by then.  Also, with NTS and ANTS marked I fired off some LIMAs and not a single one hit.  Have to go back and try again, as maybe I was below min range by then. Not ruling out OPERATOR ERROR, but everything seemed to be set correctly.

Edited August 14, 2024 by Recluse

[Raptor9]

@Recluse (and anyone else), feel free to try again after the latest update from last week. There were substantial improvements to the FCR elevation control logic so you should see improved behavior.

[Recluse]

4 minutes ago, Raptor9 said:

@Recluse (and anyone else), feel free to try again after the latest update from last week. There were substantial improvements to the FCR elevation control logic so you should see improved behavior.

@Raptor9 My test was done Last Night, so would have been after the patch.  We'll see what happens after today's hotfix, though there is nothing in the changelog for this..

[Raptor9]

55 minutes ago, Recluse said:

My test was done Last Night, so would have been after the patch.

If you encounter an issue, please post a track file. There could be any number of factors that effect detection of units.

EDIT: And yes, I meant after the previous update from last week, not the one just released today.

Edited August 14, 2024 by Raptor9

[Recluse]

18 minutes ago, Raptor9 said:

If you encounter an issue, please post a track file. There could be any number of factors that effect detection of units.

EDIT: And yes, I meant after the previous update from last week, not the one just released today.

 

Thanks,  I just tried a quick test and in NON-VR it seems to work as expected. Have to load up in VR and double check.  Also the issue of the LIMAs not killing the targets was TOTALLY my fault... I forgot that I had set the targets to IMMORTAL in the mission editor for some other testing...

[corbu1]

vor 14 Stunden schrieb Recluse:

. I forgot that I had set the targets to IMMORTAL in the mission editor for some other testing...

Maybe could this also cause the detection problems you have with the FCR ?

[Recluse]

6 hours ago, corbu1 said:

Maybe could this also cause the detection problems you have with the FCR ?

No, separate issue.  I tried it last night and all seemed OK (even in VR) I didn't realize that range for Stationary targets was only 6 km, so I had to get closer than I thought. In some cases, though, even inside 6 km I couldn't see them until I decreased the scan zone to focus on the target area. Once it picked them up, I could widen the scan zone again and still pick them up. THAT might be a bug, but I have to do more testing before I report it as such.

[Raptor9]

1 hour ago, Recluse said:

even inside 6 km I couldn't see them until I decreased the scan zone to focus on the target area.

Just to double-check, you are aware the FCR page will only display the 16 highest-priority targets? So even if the total target count in the top right corner of the FCR page says 42 or something, only 16 targets will ever be displayed on the FCR page. Just wondering if that is a detail that was missed, since changing the scan size, the scan area, changing the priority schemes, or activating fire zones may yield different results on the FCR page.

[Recluse]

8 minutes ago, Raptor9 said:

Just to double-check, you are aware the FCR page will only display the 16 highest-priority targets? So even if the total target count in the top right corner of the FCR page says 42 or something, only 16 targets will ever be displayed on the FCR page. Just wondering if that is a detail that was missed, since changing the scan size, the scan area, changing the priority schemes, or activating fire zones may yield different results on the FCR page.

Yes I am aware. In my test mission there were only 5 targets and it was either NOTHING or SOMETHING showing up. Generally all 5 showed up once ANYTHING showed up.

Edited August 15, 2024 by Recluse

[Raptor9]

18 minutes ago, Recluse said:

 In my test mission there were only 5 targets and it was either NOTHING or SOMETHING showing up.

As before, if you keep encountering the issue, please provide a track file so we can review it. Without that, it could be any number of factors that is causing your issues.

I was using the FCR just yesterday and it was working fine. So for us to see what you are seeing, please provide us with a track file. If not, then there is nothing that can be done.