Jump to content

Recommended Posts

Posted

Hey all.

Since the update yesterday, the guys and I have noticed that the TGP gets "stuck" or keeps flipping to INR instead of point/area track when the pod is NOT masked. We've also been seeing the laser go inoperable after a short firing of IR pointer (i.e. IR pointer laser fire for target ID via NVG for 5 seconds, then unable to fire regular weapons laser). Cycling the TGP power or laser arm switch does not resolve the laser issue.

TGP.png

Posted

BTW - the above screenshot was taken at 20k ft at 10 NM from the target. There is no reason that the "M" should be showing up on the TGP as if it were masked.
I think this error in "masking" is what's also causing the inability to fire the laser along with the inability to be in point/area track.
After some testing it seems we were only able to get the TGP reliably "unmasked" within ~20 degrees left/right from centerline of the nose OR if you heavily banked the opposite direction so the TGP is pointing almost within ~+/-20 degrees straight down (under the aircraft).

Posted

The FOV limit for the laser and POINT/AREA video tracking is the same in DCS, and the angular limits are significantly smaller than the camera FOV itself.  It's not clear if this is accurate to IRL or not.

 

  • Like 1
Posted

I appreciate the information given here, but I was already aware of the former limitations of the FOV/masking.
What I am posting about is a SIGNIFIGANT change in TGP behavior from before the update to after. This much more restrictive behavior is new. Not only myself, but other members in my squadron have the same issue.

Posted
1 hour ago, Grimm Horizon said:

I appreciate the information given here, but I was already aware of the former limitations of the FOV/masking.
What I am posting about is a SIGNIFIGANT change in TGP behavior from before the update to after. This much more restrictive behavior is new. Not only myself, but other members in my squadron have the same issue.

Ah, ok, haven't flown A-10C since the update.  I wrote down angles there so you can double-check if there's a quantitative change

Posted (edited)
2 hours ago, Grimm Horizon said:

What I am posting about is a SIGNIFIGANT change in TGP behavior from before the update to after.

Track or it didn't happen (a short one, please).

For the time being I still have a 2.9.5 installation available to cross-check.

In your screenshot, the TGP situational awareness cue is on the outside of the display at the 3 o'clock position. As you've obviously read by now in the linked thread, that is where (among others) AIM-9s and ALQ-131 and ALQ-184 pods might block the TGP's line of sight, and as jaylw314 already alluded to, the DCS A-10C TGP masking isn't directly linked to TGP line of sight, as indicated both by the "M" indication and the fact the TGP went to inertial point track, which also coincides with the laser no longer being able to fire. Note, I can't tell if any of this is actually realistic.

From your report, the included screenshot, and anecdotal evidence, it looks like you might simply be misunderstanding how the system has been working for 10+ years.

If you can show that there is a change between the previous DCS 2.9.6 and the current DCS 2.9.7, I'll be more than happy to file a report.

Edited by Yurgon
  • Recently Browsing   0 members

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