Crptalk

Are you sure it's actually drifting and not because you're flying toward the point the cursor is stabilized on the terrain at?

Yeah not sure why this was moved from the F-16 forums, customized cockpits work fine with every other aircraft.

Care to share one that does work? I've tested a few mods and none overwrite the default cockpit textures unless placed in the default folder.

Still unable to use Customized Cockpit

People are trying really hard to gatekeep A-G radar and its kind of cringe. Spoilers: not everyone plays the game to min-max.

The thing that looks like a line cutter is a line cutter https://en.wikipedia.org/wiki/Wire_strike_protection_system

Probably the main reason boresighting is implemented for the f16 and not the f18 or a10 yet is the procedure is more documented in the f16.

lmao op really took smudge tool to a f18 and made it fatter then called it better looking

ego yikes

Seems like Israel has no problem doing it with their Apaches to much smaller aircraft.

Link 16 should still allow for transmission and reception of SPI, Steerpoint, surface tracks, SEAD threats and the 5 closest ground PPLI's to SPI; among other things.

You should be able to tms up on any steerpoint 1-127 including datalinked steerpoints.

Except there's not even a WIP page for the DTS page and no mention of DTS in the roadmap Which is why this is a whishlist thread.

If it was modeled we would have terrain referenced navigation, predictive ground collision avoidance system, database terrain cueing, and obstacle warning and cueing. ICP 3 would open the DTS page.

tracks for the last 2 posts were broken so i reuploaded them

Another track. This time I pushed the plane nose down until lock was broken. Picture is with the antenna elevation at the lowest it will go. rws_radar_elevation_keyboard3.trk

I unbound antenna elevation and just used the default keybinding (- and =). Steps to reproduce: Switch to missile override Lock a target Pull up until the lock is broken by going past radar gimbal limits Where the radar was gimbled when lock is broken is the new "center" of antenna elevation In this track I used 1 bar radar scan to better show antenna elevation. In the picture is the antenna elevation at maximum. rws_radar_elevation_keyboard2.trk

Developed in the late 90s, the DTS stored the Digital Terrain Elevation Data and had the following features: terrain referenced navigation (TRN) predictive ground collision avoidance system (PGCAS) (Not to be confused with AGCAS) database terrain cueing (DBTC) obstacle warning and cueing (OW/C) passive ranging (PR) In addition to being a digital terrain height map, it also contained vertical (towers) and horizontal (wires) obstacle data for OW/C. There is a publicly available paper titled "Developmental flight testing of a digital terrain system for the USAF F-16" published by the IEEE which describes in detail the development and different functions of the DTS and has figures showing HUD symbology. A certain MLU M2 pilot's guide available online goes into further detail and shows more HUD symbology.

2.7.6.13133 Open Beta I have antenna elevation on an axis with center detent. Even when in the detent you can see the antenna elevation is much different from being horizon centered. Image attached with antenna elevation centered. rws_radar_elevation.trk

dcsPLEASSE.trk

Here's a trackfile. Unable to unlock someone in RWS closer than 3nm. Also bugged TWS radar contact disappears after you tms up on it again. dcsPLEASSE.trk

Radar and AIM9 symbols are both off dcsPLEASSE.trk

I'm ok with this, as long as ED sticks with this philosophy and removes all the non "operationally valid" loadouts for other planes for their time period, including 3rd party. They can start with cancelling the BS3 module. Can't have KA-50's flying around breaking my immersion in 2021.

That's the whole point of R7.

When you're in for example A-G mastermode and switch to NAV mastermode should it auto stow the TGP if STBY was already selected in NAV?