Question about the SEA radar

[jojojung]

Hallo Guys,

I have a few questions about the sea radar in the viper.
1) In the viper it is just like a GM radar with maybe some filtering of waves etc but I dont know if this is implemented yet. The radar screen shows the picture and the user has to interpret it. Thats correspond to real life, right?
In the hornet the sea radar has the ability to show all sea vessels as "contact bricks". This mean it can interpret the radar picture itself. Does this also correspond to real live or is it just one of ED gamerism like changing lasercodes in flight etc.?

2) What should happen if i press TMS up on the sea radar screen in the viper with the TGP? I would think the tgp should slew it the SPI of the radar but it doesnt at the moment. Its a bug, right? When you press TMS up again it cycles through OA1 and OA2. Is this right?

 

Thanks!

 

[Frederf]

FCR GM/SEA modes don't generate synthetic identifiers like GMT (hence the term GMTI). There are trackable "hot spots" called discretes in mapping modes but it's similar to Maverick video tracking, looking for the edges in a kinda analog type logic. Certain large targets (trains/ships) can frustrate tracking if the object is larger than the range resolution. It's stated that GMT mode can have superior detection capabilities to SEA of small/slow vessels. Selecting a target in GM/SEA requires the pilot recognizing the bright spot (or general landscape shape) on the image and slewing cursors accordingly. If the pilot wants FTT then designate with cursor over discrete although this is not commonly done, SEA mode disables drift detection for FTT although both GM and SEA can FTT moving ships provided the return doesn't degrade. There is no logically "stepping" through targets on GM/SEA or anything like that. If you want synthetic "logical" objects, you want GMT mode. Difficulty occurs with essentially stopped target vessels which GMT naturally disregards by its principle of operation. GMTT is done by designating from GMTI and the radar goes through an acquisition process for a moving target belonging to an indication in the previous mode at the cursor position.

Slewing FCR cursor or FCR tracking in an AG/NAV preplanned mode should have all slaved sensors (i.e. TGP) forced to equal the radar's. This is the F-16's "single LOS" principle and it should be impossible to move or have tracking FCR while TGP is tracking simultaneously. Right now it doesn't and it's a known issue. The workaround is to keep cycling the sighting point (even if the label doesn't change) which will force the TGP to update LOS to the radar cursors at the moment of sighting point change. TMS up shouldn't cycle sighting point through OAPs, that would be TMS right on most SOIs (except for SOIs which use TMS right for something else). Anyway OAPs should not be in the rotary list if their RNG value in DEST is 0 feet which disables them from use.

[jojojung]

vor 20 Stunden schrieb Frederf:

FCR GM/SEA modes don't generate synthetic identifiers like GMT (hence the term GMTI). There are trackable "hot spots" called discretes in mapping modes but it's similar to Maverick video tracking, looking for the edges in a kinda analog type logic. Certain large targets (trains/ships) can frustrate tracking if the object is larger than the range resolution. It's stated that GMT mode can have superior detection capabilities to SEA of small/slow vessels. Selecting a target in GM/SEA requires the pilot recognizing the bright spot (or general landscape shape) on the image and slewing cursors accordingly. If the pilot wants FTT then designate with cursor over discrete although this is not commonly done, SEA mode disables drift detection for FTT although both GM and SEA can FTT moving ships provided the return doesn't degrade. There is no logically "stepping" through targets on GM/SEA or anything like that. If you want synthetic "logical" objects, you want GMT mode. Difficulty occurs with essentially stopped target vessels which GMT naturally disregards by its principle of operation. GMTT is done by designating from GMTI and the radar goes through an acquisition process for a moving target belonging to an indication in the previous mode at the cursor position.

Slewing FCR cursor or FCR tracking in an AG/NAV preplanned mode should have all slaved sensors (i.e. TGP) forced to equal the radar's. This is the F-16's "single LOS" principle and it should be impossible to move or have tracking FCR while TGP is tracking simultaneously. Right now it doesn't and it's a known issue. The workaround is to keep cycling the sighting point (even if the label doesn't change) which will force the TGP to update LOS to the radar cursors at the moment of sighting point change. TMS up shouldn't cycle sighting point through OAPs, that would be TMS right on most SOIs (except for SOIs which use TMS right for something else). Anyway OAPs should not be in the rotary list if their RNG value in DEST is 0 feet which disables them from use.

Great THX.

Do you know if the bricks in the hornet are there in real life or is it a simplification?

 

[Harker]

Great THX.
Do you know if the bricks in the hornet are there in real life or is it a simplification?
 

Synthetic targets in SEA and GMT are correct for the Hornet, based on publicly available info.