Jump to content

Recommended Posts

Posted (edited)

According to the manual PAL is supposed to be restricted to lock only targets up to 15nm. As you can see in the attached track it can even lock targets up to at least 25nm in DCS.

2021-01-31_F-14B_PAL_Lock_at_25nm.trk

Edited by IronMike
Falsley flagged as NO BUG, it is indeed a BUG

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • QuiGon changed the title to PAL locks targets >15nm
Posted (edited)

As Skysurfer said, PAL lock range is determined by the RCS of the target rather than any discrete range. 15NM is the range PAL can acquire the default RCS value in DCS, which happens to be that of an Su-27. Larger targets like Backfires and Transports can be acquired significantly further out. 

Edited by near_blind
Posted (edited)
7 hours ago, Skysurfer said:

It's 20nm afaik. Will depend on RCS mostly, dont think ACM modes have necessarily fixed lock ranges.

 

Really? That's odd for two reasons:

 

1) The manual says otherwise: https://www.heatblur.se/F-14Manual/general.html#pilot-automatic-lockon-pal

Quote
Pilot Automatic Lockon (PAL)

PAL is enabled by the pilot selecting DES on the target designate switch when not in A/G mode.

PAL commands the antenna to a 8-bar ±20° scan pattern locking onto the first target detected out to 15 NM. This mode is indicated by the diamond on the HUD following current antenna line of sight.

 

2) ACM modes  usually have such a range restriction not because of the inability to lock targets further out (you can lock targets much further away in manual pulse mode in the Tomcat), but because they are being used WVR, where it would be quite bad if the radar would not lock onto the bandit right in front of the aircraft, but instead choose to lock a bandit much further away.

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted

For what is worth, it's usually ships that get locked more then 15NM out.

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

Posted (edited)
2 hours ago, captain_dalan said:

For what is worth, it's usually ships that get locked more then 15NM out.

 

In the track file, which I posted above, it's an aircraft.

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted
11 hours ago, QuiGon said:

1) The manual says otherwise:

Be that as it may, PAL is RCS limited, not Range limited. PLM exists for locking up only close targets directly in front of you. 

Posted (edited)
56 minutes ago, near_blind said:

Be that as it may, PAL is RCS limited, not Range limited. PLM exists for locking up only close targets directly in front of you. 

 

I see, thanks! :thumbup:

 

In this case the manual needs to get updated as it currently says that PAL only locks up targets out to 15nm (see above)! @IronMike

Edited by QuiGon
  • Like 1

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted (edited)
22 hours ago, QuiGon said:

 

I see, thanks! :thumbup:

 

In this case the manual needs to get updated as it currently says that PAL only locks up targets out to 15nm (see above)! @IronMike

 

 

EDIT: Please see my next comment below.

Edited by IronMike

Heatblur Simulations

 

Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage.

 

http://www.heatblur.com/

 

https://www.facebook.com/heatblur/

  • IronMike changed the title to [NO BUG] PAL locks targets >15nm
Posted
2 minutes ago, IronMike said:

 

I think that is fine, since it is a guideline value, should maybe add rather that @Naquaii - maybe add a subsentence that it can lock targets with a larger RCS a bit further out than 15nm as well..

That would be great, as it is not clear currently, that this is just a guideline value the way it is written. :smile:

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted
14 hours ago, QuiGon said:

 

In the track file, which I posted above, it's an aircraft.

 

Well that's why i said usually 😄
But yeah, sometimes other things get locked up too.

Modules: FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, F-14A, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, MiG-15, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map, Marianas map, Syria Map, Super Carrier, Sinai map, Mosquito, P-51, AH-64 Apache, F4U Corsair, WWII Assets Pack

Posted (edited)

Correction and apologies, gents, I was wrong, I just talked to Naquaii. PAL locking outside of 15nm is indeed a bug, the WCS "restricts" PAL to 15nm, not the RCS size, I was wrong.

I changed the title to "BUG". My apologies.

Edited by IronMike
  • Like 4
  • Thanks 1

Heatblur Simulations

 

Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage.

 

http://www.heatblur.com/

 

https://www.facebook.com/heatblur/

  • IronMike changed the title to [BUG] PAL locks targets >15nm
Posted (edited)
16 hours ago, IronMike said:

Correction and apologies, gents, I was wrong, I just talked to Naquaii. PAL locking outside of 15nm is indeed a bug, the WCS "restricts" PAL to 15nm, not the RCS size, I was wrong.

I changed the title to "BUG". My apologies.

 

No worries and thanks for double checking! :thumbup:

I was already wondering why the engineers of the AWG-9 would depart from the fixed range restrictions found on pretty much all ACM modes across all modern fighters, as they are there to prevent you from accidentally locking up something in a dogfight that is further away and not part of the dogfight.

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...