Sensor questions

[Beamscanner]

I have some questions before I start reporting bugs. 

 

In regards to the TGP, should it be able to:

• display the TGP TD box in the HMD?
• display the Bull on TGP page?

 

In regards to the radar, should it be able to:

• utilize a 120 degree scan (A6) in RWS-SAM?
• utilize Spotlight search in TWS?
• should RWS bricks be ground-stabilized in range and azimuth? or is the current implementation (display-stabilized in range/ground-stabilized in azimuth) correct?

Edited December 20, 2021 by Beamscanner

[Machalot]

On 12/19/2021 at 7:35 PM, Beamscanner said:

should RWS bricks be ground-stabilized in range and azimuth? or is the current implementation (display-stabilized in range/ground-stabilized in azimuth) correct

Can you explain what this means? 

[WHOGX5]

3 hours ago, Machalot said:

Can you explain what this means? 

As I understand it he's saying that, in the current DCS implementation, if you turn left with an RWS brick on your FCR, the brick will move right on the FCR page to stay in the same position over the ground, or at the same coordinates, hence it's ground stabilized. However, say that you're really close to a target and you're flying towards it at a high speed, then the brick will remain stationary relative to you distance-wise on the FCR even though you're constantly closing in on it; the RWS bricks real world coordinates will change so that it maintains the same position on the display, hence it is display stabilized.

As should be obvious, ground stabilization is preferred as it gives you the correct location of the last hit irregardless of ownship maneuvering while display stabilized only shows you where the contact was relative to you at the last hit; the more your distance or azimuth to the target changes, the higher the deviation between the actual and indicated position of display stabilized returns.

[TEOMOOSE]

On 12/19/2021 at 10:35 PM, Beamscanner said:

I have some questions before I start reporting bugs. 

 

In regards to the TGP, should it be able to:

• display the TGP TD box in the HMD?
• display the Bull on TGP page?

 

I think this is what you are after as far as tgp box/hmd.


The TGP will not display bullseye information as far as i know. It is available on the HSD page, and also the tgp position is marked on the HSD with a "larger" crosshair. That way you can make bullseye calls of detected targets.

Edited December 22, 2021 by TEOMOOSE

[TEOMOOSE]

On 12/19/2021 at 10:35 PM, Beamscanner said:

In regards to the radar, should it be able to:

• utilize a 120 degree scan (A6) in RWS-SAM?
• utilize Spotlight search in TWS?

 

Technically you wan to search in RWS modes first, and built a track file of the different contacts that are on the scope. The spotlight is utilized in rws since it gives you a high chance to reacquire a "lost" contact since it goes to A1 4bar. Than STT if you are after a single target, this gives you the best chance to support the missile without "loosing" the contact. 

 If there are multiple contacts and used rws to gather enough information and identified hostile, you could enter in to tws which uses "less" energy to track it. This means if a contact start maneuvering in to the notch you will most likely to loose track or "lost lock", but you can target and shoot multiple target all at once. TWS also dose not warn contacts of a incoming missile until it goes active "pitbull".

 

Edited December 22, 2021 by TEOMOOSE

[Frederf]

On 12/19/2021 at 10:35 PM, Beamscanner said:

• display the TGP TD box in the HMD?
• display the Bull on TGP page?
• utilize a 120 degree scan (A6) in RWS-SAM?
• utilize Spotlight search in TWS?
• should RWS bricks be ground-stabilized in range and azimuth? or is the current implementation (display-stabilized in range/ground-stabilized in azimuth) correct?

• No such thing as a "TGP TD box", only TD box. Sensor LOSs themselves are invisible on the HUD/HMCS. If the TGP is defining A-G TD box position then you'll see that.
• May vary by OFP: Ownship BE only present in A-A FCR and HSD, not A-G FCR or A-G TGP or A-G WPN. HSD BE symbol requires FCR A-A mode (?).
• Yes, SAM azimuth limits are the lower of the dynamic requirement and the pilot "A" setting. Full azimuth is possible in permissive conditions.
• Yes, spotlight in TWS (except EXP). Note different from APG-66.
• RWS contacts are positioned in geographic space. E.g. like flying at a static ground point.

[Crptalk]

On 12/19/2021 at 10:35 PM, Beamscanner said:

I have some questions before I start reporting bugs. 

 

In regards to the TGP, should it be able to:

• display the TGP TD box in the HMD?

 

 

The M3 manual does mention dotted A-A TGP target box and dotted target locator line for the JHMCS.

Edited December 22, 2021 by Crptalk

[Beamscanner]

After having reviewed some videos online, it seems that its pretty common to stabilize RWS bricks/hits in azimuth but maintain a static range on the display (display stabilized in range). (ie old bricks move left/right with ownship maneuvers, but don't come closer as you fly toward the brick)

 

 I saw this with the APG-63 and the APG-66, two separate air radar manufacturers. 

 

Its possible that pilots prefer this, as it makes it easier to move your curser onto the brick. If it was ground stabilized in range (ie the brick gradually moves closer as you fly toward it), it could make it more difficult for the pilot to chase it down with their cursor. Especially at close range. 

 

Unless someone has documentation, I'll assume that the current implementation is correct.