FFG Towed array problem (bug?)

Shadowmind · 08-31-06, 02:55 PM

I’ve looked around and haven’t seen anyone else post about this problem. Sometimes when I switch to the FFG towed array screen I see the broadband display is “washed out”. It isn’t the same washed out look as when the array is being dragged on the ocean floor or due to high speed. It just looks like there is one very large contact that covers the entire broadband display. Once I have switched to the towed array screen the latest data that gets displayed is correct. But I have lost all history information and must wait minutes to get good ITA or LTA data. Is this a bug or am I doing something that causes this?

Another problem is sometimes when I look at the narrow band display (beam overview) I can see a contact on a certain beam. Then I double click on a beam but it shows no waterfall data. I have to wait several seconds as new waterfall data scrolls down the screen. I would think the waterfall data should still be there. This isn’t as bad as the first issue, but it is frustrating.

08-31-06, 02:55 PM	#1
Shadowmind Watch Join Date: Aug 2006 Location: Frozen plans of ND Posts: 17 Downloads: 3 Uploads: 0	FFG Towed array problem (bug?) I’ve looked around and haven’t seen anyone else post about this problem. Sometimes when I switch to the FFG towed array screen I see the broadband display is “washed out”. It isn’t the same washed out look as when the array is being dragged on the ocean floor or due to high speed. It just looks like there is one very large contact that covers the entire broadband display. Once I have switched to the towed array screen the latest data that gets displayed is correct. But I have lost all history information and must wait minutes to get good ITA or LTA data. Is this a bug or am I doing something that causes this? Another problem is sometimes when I look at the narrow band display (beam overview) I can see a contact on a certain beam. Then I double click on a beam but it shows no waterfall data. I have to wait several seconds as new waterfall data scrolls down the screen. I would think the waterfall data should still be there. This isn’t as bad as the first issue, but it is frustrating.