Crptalk

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

It's not just look down. The radar is sometimes just completely borked in ACM.

Not appropriate for the timeline of our Viper. However, Predictive Ground Collision Avoidance System(PGCAS) should be appropriate for a 2007 block 50.

Which is still jittery to the point it's nearly unusable. The DCS TGP A-A functionality is limited compared to what is demonstrated in this video. Notice how the TGP can also be slewed and commanded to track other objects in A-A. As well as what looks like black outline around the text and symbols to aid in legibility, also not present in DCS.

In my case, I have had this issue happen for a while. It's just now that I happen to have track recording turned on and decided to make a bug report. Personally, I don't see how the radar losing lock in a close range, clutter free, look-up environment isn't a bug.

I see this issue now and then playing pvp, finally reproduced it in singleplayer. Multiplayer example- https://gfycat.com/veneratedunitedconch Singleplayer example- https://gfycat.com/alertwavygoldenretriever radar lookup losing lock.trk

Trolling again?

Problem with that is most (all?) TGP lasers can't go beyond 8 miles in dcs

When (if?) it gets NCTR that should change.

Only AGM-88's. It's an anti compromise feature. The F18 does it too I believe.

Coordinates are displayed on the FCR when you have a target track or in FRZ. With SOI on the FCR press 7 on the ICP to bring up the markpoint page on the DED and TMS up to create a markpoint at the current FCR cursor position then press "0" to make it the active steerpoint. Remember to CZ to remove any slews afterwards. SPI is displayed on the HSI so you can slew the FCR to move SPI to where you want it on the HSI then make a markpoint there.

The latter.

With HUD markpoint selected, TMS up >0.5sec slaves the markpoint cue to the HMD. Or when they're implemented, slave the DTOS or EO-VIS designator to the HMD and designate the target that way.

It should be a procedure required for any aircraft that wants to cue the Maverick LOS to a SPI/TGT Designation/TGP LOS/HUD Cue/etc with any accuracy. My guess is there is a certain expectation when it comes to the DCS F-16 because of the "other game" and that if the "other game" didn't exist then boresighting might also not exist. Also the boresighting procedure is well documented for the F-16, not sure about other planes. Though after a bit of searching I did find this video of an A-10A pilot boresighting his mavericks on another aircraft.

If it isn't clear, DTS is a collection of systems to store digital terrain data and obstacle data for 5 primary functions: Terrain Referenced Navigation(TRN): Compares radar altimeter readings to the digital terrain database to calculate aircraft location within the digital terrain map and estimate INS drift. Predictive Ground Collision Avoidance System(PGCAS): Uses 3d terrain elevation and obstacle data for pullup calculations instead of 2d radar altimeter readings. Obstacle Warning and Cueing (OW/C): Provides HUD advisories of man-made obstacles along the flight path. Database Terrain Cueing (DBTC): Displays a vertical steering cue on the HUD to maintain a specified AGL altitude during low level flight. Similar to LANTIRN's manual terrain following hud cue. Passive Ranging(PR): Backup target ranging method for when the FCR is inoperative and TGP lasing is unavailable. The DTC of Block 50 aircraft have expanded storage to store the digital terrain and obstacle data and has a dedicated DTS processor. The DTS Priority Page can be accessed by pressing the number "3" button on the ICP. This page allows the pilot to select different DBTC, OW/C, and PGCAS options and to view the current TRN confidence level. Feel free to educate yourself on the basics and development of DTS with this open source paper titled "Developmental flight testing of a digital terrain system for the USAF F-16" presented at the 1999 IEEE Aerospace conference. Other references sent to the mods in dm's.

Makes me wish they would just overhaul the mfd's completely to improve readability. Trying to read the mfds through the fake screen door effect while wearing a vr headset with real screen door effect is terrible.

2.7.7.15038 In this test the steerpoint is on one end of a runway and I slew the radar cursor to the middle of the runway and SPI is moved twice as far, to the other end of the runway. agfrzslew.trk

I've wanted to say something on this subject but just assumed it was very WIP. It's my understanding from the (admittingly old) "publicly available" pilots guides that because of the F-16's single LOS concept, in A-G when FCR is SOI and a slew is commanded then the TGP will break lock to follow the SPI. Likewise when TGP is SOI and in a track mode then FCR will break lock to follow SPI.

While we're on the subject, will we be getting covert IR external lighting for the DCS F-16? AFAIK it's not implemented yet in DCS.

It's almost like it's meant to simulate night flying using pnvs/tads. Someone should tell the Army it's useless then because they've been using it for simulated night flying since the beginning.

lol I know this technically works, it just seems odd that the F-16 is the only plane (that I know of) where you can only use the default folder.

You're using the default folder. Try using a new folder. Expected behavior with other modules is using separate folders and not overwriting the default folder. For example the SU33