Why is the Recon time not updating?

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

Why is the Recon time not updating?

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> Why is the Recon time not updating?

Page: [1]

Message

<< Older Topic Newer Topic >>

Why is the Recon time not updating? - 10/18/2018 3:19:45 PM

LMychajluk

Posts: 126
Joined: 10/8/2017
Status: offline

Sorry... Been playing a lot recently and trying to get more into the nuances of this game and refine my tactics. Will probably have more questions, but here's today's:

In the attached save, I have a Fire Scout off the Zumwalt hovering at 2000ft about 1.5 miles outside the Airport at 1am with clear skies. It's been there for a little while, and I had it circle around a couple of times as well. The FLIR camera on the FireScout has a range of 45 miles, and is arguably one of the latest sensors available. The FireScout is supposed to be recon'ing the area for future mop-up by the Super Cobras off the America, which have a similar 3rd gen IR sensor.

If you look at the Airfield (or the individual units of it), the contact report says the last recon was ~6 hours ago (at the time of the last strike), and the 'Last Detection' panel shows no detection of any of it by the FireScout. Also, the FireScout can't seem to ID/Classify the Mobile contacts, though they are currently being detected. The FLIR is probably more useful at sea, but I would think it should work fine in this situation.

So, 2 questions:
1) Why can't the FireScout update the recon on the Airport and ID the hosted units?
2) Why is it so difficult to ID or classify the Mobile unit? (It always seems like it's harder to ID 'Mobile' units vs. others.)

Thanks for any insights.

-Lee

Attachment (1)

Post #: 1

RE: Why is the Recon time not updating? - 10/18/2018 7:13:43 PM

Uzabit

Posts: 77
Joined: 7/13/2018
Status: offline

Hi there, concerning the mobile units: Those are small MANPAD units with following detection and classification ranges:

0,8 nautical miles for detection (infrared)
0,005 nautical miles for classification (infrared)

That might be helpful in this case. Don't know if there are range modifiers for different FLIR generations. I think a moving unit will also be more likely to give away its position, but I haven't done any thorough testing here.

There are no updates on the detections for the hosted units because they've already been destroyed. I think there's a older discussion on this topic in an earlier thread. The symbol for hosted units doesn't disappear automatically - one first has to drop the contact manually and wait for redetection.

(in reply to LMychajluk)

Post #: 2

RE: Why is the Recon time not updating? - 10/19/2018 1:26:50 AM

LMychajluk

Posts: 126
Joined: 10/8/2017
Status: offline

Thanks! That makes sense, and now I've learned how to read and apply that info from the DB.

Still, I would've thought a modern sensor like the one on the FireScout would be able to see a squad of soldiers at more than .8nm, though I can also see the squad hunkered down in a camouflaged foxhole and being real hard to spot.

I'll see if I can find the thread on the recon thing with hosted units. Sounds like a bug(?).

(in reply to Uzabit)

Post #: 3

RE: Why is the Recon time not updating? - 10/19/2018 7:09:40 AM

De Savage

Posts: 79
Joined: 6/16/2014
Status: offline

Stationary units are hard to spot. If unit is moving they are much easier to spot.

For land units it would be useful to have couple 'stations'. Example moving, stopped, camouflaged and entreched/fortified. It could take few hours to prepare fortified station, maybe half hour camouflage. Or maybe we could add foxholes or fortification next to unit. In same group they could use extra sheter to reduce damage and make them harder to spot. Situations are different. Scenario makers should make manpads units to patrol and move or only make them stationary if needed.

< Message edited by De Savage -- 10/19/2018 7:10:54 AM >

(in reply to LMychajluk)

Post #: 4

RE: Why is the Recon time not updating? - 10/20/2018 9:18:43 AM

c3k

Posts: 369
Joined: 4/25/2017
Status: offline

.005 NM is about 30 feet! Most weapons are much more readily identifiable from FLIR than needing have the camera 30 feet away. Especially a MANPAD.

I would think that perhaps the database classification range is too short.

(in reply to De Savage)

Post #: 5

RE: Why is the Recon time not updating? - 10/20/2018 9:20:20 AM

rmunie0613

Posts: 202
Joined: 1/2/2018
Status: offline

As far as the original question, I wonder as well, why a specific recon asset does not update the "last recon" of - not a mobile unit, but aircraft on a runway or damage to a facility... I do this with TARP pods also.

(in reply to De Savage)

Post #: 6

RE: Why is the Recon time not updating? - 10/20/2018 3:51:32 PM

Primarchx

Posts: 3102
Joined: 1/20/2013
Status: offline

I find it a bit wacky. Yeah, I spotted the two a/c on that tarmac and smacked them with an LGB. There are no longer two a/c there but the intel will say they were last seen there x hours ago. If they're not there anymore, shouldn't it reflect that nothing was seen there on the last sensor observation? Sometimes you need to confirm that you have a sensor currently observing the location and note that the last platform spotted there was well in the past to then make the logical conclusion that nothing is there NOW.

(in reply to rmunie0613)

Post #: 7