Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

[FIXED B669] Not able to drop a contact

 
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 >> [FIXED B669] Not able to drop a contact Page: [1]
Login
Message << Older Topic   Newer Topic >>
[FIXED B669] Not able to drop a contact - 2/4/2015 9:29:42 PM   
dusky

 

Posts: 42
Joined: 12/1/2014
Status: offline
In the attached save I have a sub contact S101 Manthatisi. The contact "age" is 7 minutes 18 seconds. The contact report shows the last ESM detection was 14 minutes ago (yes, the sub did use a radar). However, when I drop the contact (PgDn) it almost immediately reappears. I would understand this if the sub was still being detected by some sensor. However, when the contact reappears its age is still 7+ minutes.


Attachment (1)

< Message edited by Sunburn -- 2/11/2015 7:38:33 PM >
Post #: 1
RE: Not able to drop a contact - 2/4/2015 9:43:12 PM   
mikmykWS

 

Posts: 11524
Joined: 3/22/2005
Status: offline
We might have a time to drop coded in but would have to check.

Why is this important? Are you just curious or do think its a real game issue?

Thanks!

Mike

_____________________________


(in reply to dusky)
Post #: 2
RE: Not able to drop a contact - 2/4/2015 10:18:49 PM   
dusky

 

Posts: 42
Joined: 12/1/2014
Status: offline
It is a real game issue, at lest for me :). I believed that the contact and its AOU is completely wrong - checking in the editor proves me right, the sub is actually 100nm away from the edge of the AOU. So, I wanted to drop the contact and wait for it to be reacquired.

Also, in an another scenario I saw a ship waste all its ASROCs on such an undroppable & extremely inaccurate contact (it was already marked as hostile). Yes, there are workaround, but none of them really works.
a) I can order the ship to hold fire, but then I need to remember to cancel the order when a bogey appears. But anyway, all the other ASW assets will still race to prosecute the contact. To demonstrate this, just mark the sub as hostile (in the save from the original post) -- the F 39 Betwa will switch to Engaged Offensive and will run in circles above the "bad" contact (while the sub is actually 100nm away).
b) I can mark it as friendly, but then I must remember to mark it back as hostile when it gets reacquired somewhere else.

What is then the indented function of the Drop Contact option (P, PgDn, Num 3) when it is not able to drop a contact that wasn't detected by any sensor for a long time? :) I left the scenario run, the contact is already 45 minutes old, F 39 Betwa is dancing in circles and I'm still not able to drop the contact.

< Message edited by dusky -- 2/4/2015 11:19:10 PM >

(in reply to mikmykWS)
Post #: 3
RE: Not able to drop a contact - 2/4/2015 10:26:51 PM   
dusky

 

Posts: 42
Joined: 12/1/2014
Status: offline
Hmm. I just noticed that here http://www.matrixgames.com/forums/fb.asp?m=3791709 you suggest exactly what I'm trying to do -- drop an old sub contact and wait for it to be reacquired. However, it does not work in this case. The old contact and the old AOU reappear immediately even though no sensor is currently detecting the sub.

< Message edited by dusky -- 2/4/2015 11:27:15 PM >

(in reply to dusky)
Post #: 4
RE: Not able to drop a contact - 2/4/2015 10:33:56 PM   
mikkey


Posts: 3142
Joined: 2/10/2008
From: Slovakia
Status: offline
quote:

ORIGINAL: dusky
It is a real game issue, at lest for me :). I believed that the contact and its AOU is completely wrong - checking in the editor proves me right, the sub is actually 100nm away from the edge of the AOU. So, I wanted to drop the contact and wait for it to be reacquired.
Also, in an another scenario I saw a ship waste all its ASROCs on such an undroppable & extremely inaccurate contact (it was already marked as hostile). Yes, there are workaround, but none of them really works.
a) I can order the ship to hold fire, but then I need to remember to cancel the order when a bogey appears. But anyway, all the other ASW assets will still race to prosecute the contact. To demonstrate this, just mark the sub as hostile (in the save from the original post) -- the F 39 Betwa will switch to Engaged Offensive and will run in circles above the "bad" contact (while the sub is actually 100nm away).
b) I can mark it as friendly, but then I must remember to mark it back as hostile when it gets reacquired somewhere else.
What is then the indented function of the Drop Contact option (P, PgDn, Num 3) when it is not able to drop a contact that wasn't detected by any sensor for a long time? :) I left the scenario run, the contact is already 45 minutes old, F 39 Betwa is dancing in circles and I'm still not able to drop the contact.
Dusan, new Weapon Release Authorization will be very helpful in these situations.

(in reply to dusky)
Post #: 5
RE: Not able to drop a contact - 2/4/2015 11:21:24 PM   
mikmykWS

 

Posts: 11524
Joined: 3/22/2005
Status: offline
Ok. Thanks for explaining Dusan. We'll take a look.

Mike

_____________________________


(in reply to mikkey)
Post #: 6
RE: Not able to drop a contact - 2/11/2015 6:38:21 PM   
Dimitris

 

Posts: 13282
Joined: 7/31/2005
Status: offline
Okay, the problem here is that another side which is allied to the player side keeps detecting the same contact and sharing it with the player. So if the player side drops it from its own list it still gets it from the friend's plate.

Fixed in Build 669 by forcing all friendly sides to drop the same contact.

_____________________________


(in reply to mikmykWS)
Post #: 7
RE: Not able to drop a contact - 2/11/2015 7:08:00 PM   
dusky

 

Posts: 42
Joined: 12/1/2014
Status: offline
Hmm, interesting. However, I'm not sure how it applies to the save attached above.
The only friendly side are the Indian fishermen (awareness level: normal). The enemy submarine is ~75nm away, submerged at -131ft, making 2kts. My two frigates are not able to detect it, but the trawlers are somehow able to detect it with their Mk1 Eyeballs and navigation radars? Also, if a friendly side is detecting a contact, shouldn't the contact "age" reset as well? (It does not it this case.)

(in reply to Dimitris)
Post #: 8
RE: Not able to drop a contact - 2/11/2015 7:13:46 PM   
dusky

 

Posts: 42
Joined: 12/1/2014
Status: offline
Or is this the case of the Indian frigates first sharing the contact with the fishermen and the fishermen then share it back without ever detecting the contact themselves? In that case it would make sense to force them to drop the contact.

< Message edited by dusky -- 2/11/2015 8:14:04 PM >

(in reply to dusky)
Post #: 9
RE: Not able to drop a contact - 2/11/2015 7:35:46 PM   
Tomcat84

 

Posts: 1952
Joined: 7/10/2013
Status: offline
I believe it is indeed the latter. The contact has been shared with the fishermen so now they give it back, even though they dont actually see it.

_____________________________

My Scenarios and Tutorials for Command

(Scenarios focus on air-warfare :) )

(in reply to dusky)
Post #: 10
RE: Not able to drop a contact - 2/11/2015 7:47:54 PM   
Primarchx


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

ORIGINAL: Sunburn

Okay, the problem here is that another side which is allied to the player side keeps detecting the same contact and sharing it with the player. So if the player side drops it from its own list it still gets it from the friend's plate.

Fixed in Build 669 by forcing all friendly sides to drop the same contact.


Got it. So if an ally has the same undetected and now-attenuating contact then we get it back due to our sensor sharing even if we had purged it. The fix would simultaneously purge dead contacts from allies as well to keep that from happening. Cool!

(in reply to Dimitris)
Post #: 11
RE: Not able to drop a contact - 2/11/2015 10:39:06 PM   
mikmykWS

 

Posts: 11524
Joined: 3/22/2005
Status: offline
quote:

ORIGINAL: dusky

Hmm, interesting. However, I'm not sure how it applies to the save attached above.
The only friendly side are the Indian fishermen (awareness level: normal). The enemy submarine is ~75nm away, submerged at -131ft, making 2kts. My two frigates are not able to detect it, but the trawlers are somehow able to detect it with their Mk1 Eyeballs and navigation radars? Also, if a friendly side is detecting a contact, shouldn't the contact "age" reset as well? (It does not it this case.)


We're going to do an open beta cycle so there will be an opportunity to take a look and then fix if there is an issue.

Thanks

Mike

< Message edited by mikmyk -- 2/11/2015 11:39:28 PM >


_____________________________


(in reply to dusky)
Post #: 12
RE: Not able to drop a contact - 3/1/2015 6:28:18 PM   
dusky

 

Posts: 42
Joined: 12/1/2014
Status: offline
I can confirm that I'm able to drop the contact in 1.07RC5. Thanks.
The "Contact ... has been lost." message gets logged twice (I guess because it had to be dropped both by my side and the allied trawlers), but that's a very minor glitch.

< Message edited by dusky -- 3/1/2015 7:28:43 PM >

(in reply to mikmykWS)
Post #: 13
RE: Not able to drop a contact - 3/1/2015 6:29:31 PM   
mikmykWS

 

Posts: 11524
Joined: 3/22/2005
Status: offline
Great news.

Thanks!

Mike

_____________________________


(in reply to dusky)
Post #: 14
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [FIXED B669] Not able to drop a contact Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.750