Geraki

Steps Select instant action -> Fighter Intercept 1.When MIDS is on in TWS when you STT the target the target box disappear from theFCR- MFD. 2. MIDS off the target box in STT stays in FCR- MFD. 3. TWS below 5 NM MIDS ON again the STT target appear correctly in FCR TWS BUG-MIDS ON.trk

Hi about Cursor bulleye

Not realistic!! DED in HMCS Wait for more symbols and data in HMCS -LINK 16 ------

Correct in emergency Jettison both fuel tanks and pylons should jettison , as per real . https://docs.google.com/viewer?url=http%3A%2F%2Fcsef.ru%2Fmedia%2Farticles%2F4361%2F4361.pdf The issue occurred in the last update , DCS 2.7.6.13436 Open Beta Simple select instant action , takeoff , and emergency jettison the payload , only the fuel tanks from station 4&6 are jettison not the TER too. When you push emergency jettion button.

CRUS page (5) The Cruise page provides access to 4 submodes: TOS, RNG, HOME and EDR and gives relevant information for navigation, time and fuel while cruising. All time references are ZULU (UTC) Each submode must be mode selected to become active and supply accurate information and cues. Mode-selecting is done with the M-SEL 0 button and when active highlights the area The submodes of the CRUS page are accessed sequentially with DCS SEQ or by pressing any secondary ICP button. When first entering the CRUS page it defaults to the first subpage: TOS (Time Over Steerpoint).

CAT III limitation , warnings and damage avionics if the pilot exceed the stores limit tolerance.

After last update general difficulty for radar to recognize and lock targets Hi to low even with cursor antenna on it with same target alt and bar scan in targets.

Data Link Mode (OSB 6). IDM Data Link Mode rotary IDM Data Link Mode rotary: • ASGN • CONT • DMD Data Link Assignment Transmit Status (OSB 7-10) Depression of OSB 7-10 (representing flight member numbers 1-4) transmits an IDM Assignment to that flight member and causes “XMT” to be displayed for 2 seconds Air-to-ground data link information consists of the selected steerpoint which may be a markpoint, a navigation steerpoint, or the FCR air-to-ground cursor position. Air-to-air and air-to-ground data link information may be selected for display on the HSD MFD format by selecting ADLINK (OSB 16) and/or GDLINK (OSB 17) on the HSD Control page (both are on by default). When ADLINK is selected, intraflight member’s ownship positions and the locations of their bugged targets are displayed on the HSD. This same symbology is also displayed on the FCR, provided the FCR is in one of the air-to-air radar modes. When GDLINK is selected, data linked steerpoint (or markpoint) and FCR air-to-ground cursor positions will be displayed on the HSD

HAF F-16CJ Block 50

Also i tried to upload into jet and i get this exception See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:43001 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at DTC.Models.F16Upload.Load(Boolean waypoints, Int32 wptStart, Int32 wptEnd, Boolean radios, Boolean cms, Boolean mfds) at DTC.UI.F16.UploadToJetPage.btnUpload_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- DTC Assembly Version: 1.2.0.0 Win32 Version: 1.2.0.0 CodeBase: file:///C:/Program%20Files/Eagle%20Dynamics/DCS-DTC-1.2.0/DTC.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Newtonsoft.Json Assembly Version: 13.0.0.0 Win32 Version: 13.0.1.25517 CodeBase: file:///C:/Program%20Files/Eagle%20Dynamics/DCS-DTC-1.2.0/Newtonsoft.Json.DLL ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- System.Runtime.Serialization Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

any instructions please?

Tracks Multiplayer.rar

Could be a feature option in loadout menu like right now we have restrictions for weapons in specific pylons . We can have the option for Variant 3d F-16 selection ,avionics and weapons.

As per title when we switch on the FCR it takes some countdown BIT time.

After last update F-16 radar redesign there is a difficulty to find and lock targets closer than 15 miles , it is suppose to be that in specific distances all aircrafts with high aspect could be viewable in FCR and could be locked! like previously open beta patches.

DTS is another method of telemetry and use another F-16 avionics-than TGP like DTC and more other sys..

Please change the notice - need track replay- i think it is a feature for W.I.P - in comparison with topic radar loose lock when switching from deferent A-A modes e.g locked in dogf and then switch into NAV mode. e.t.c ******When we are in NAV master mode we have Streer- point Slant range B, But in NAV mode if we have Radar A-A contact "bugged" the Slant Range B must be changed to F which become the TARGET SLANT RANGE.***** Associated with topics

Digital Terrain System (DTS) The DTS is a digital representation of 480 NM^2 of terrain loaded into the data tape cartridge (DTC). The F-16 uses this digital terrain for a number of different things: Database terrain cueing (DBTC): With the radar altimeter on, the actual terrain the F-16 is flying over is compared against the database to determine position on the digital terrain. This information is combined with the INS and GPS and used in position fixing. When flying in an area without DTS coverage, the words "OFF MAP" appear below the ASI on the HUD. Proximity to ground collision avoidance system (PGCAS): Without the DTS, the airplane assumes a "flat earth" for the PULL-UP cues (in other words; it's only effective if flying over the ocean or perfectly flat land). With the DTS, the jet can give accurate PULL-UP cues over mountainous terrain. To differentiate between cues given by the existing ground-proximity warning system and PGCAS, a separate terrain-proximity warning (along with the break-X on the HUD) will appear below the ASI. If PGCAS is not available, a "NO GPW" warning is displayed on the HUD. Obstacle warning/clearance (OW/C): Along with a terrain database, the DTS includes information on man-made obstacles (height and position). The HUD will display "OBSTACLE" when nearing an obstacle, and "<- OBSTACLE" or "OBSTACLE ->" when one is to the left or right of the aircraft. The DTS is configured from the DTS page on the DED, ICP button 3. From this page you can turn on and off different DTC features and configure minimum altitudes. some more DATA for PGCAS .. http://www.f-16.net/f-16_versions_article8.html http://www.youtube.com/watch?v=XgJB9PBnKGw http://www.youtube.com/watch?v=577Lh7cEq80

When we have radar lock the radar locator line and the target designation box MUST be visible in NAV mode too it is normal since we have RADAR LOCK. And the B-Steer point distance symbol become F - target reference distance unless the pilot make's brake lock the target from FCR. Same sources. Kind Regards

Please put the above topic into Wishlist!!

The video shows possibly a block40 F-16 But....i have seen that in Block 50 too. It is normal since we have Radar lock -> when we switch into the NAV mod without to drop the target in FCR, the target designator box schould be remain when we switch form A-A /Dogft into NAV mode. If the pilot drop's the FCR target then the target designator box disapper from the NAV HYD mode.

Same here ... TMS long right does not switch into TWS mode from RWS and vise versa .

As title says to view the Bullseye blue cyrcle into A-A FCR mode like the same bullseye appraring into HSD.

When we are in NAV master mode we have Streer- point Slant range , But in NAV mode if we have Radar A-A contact "bugged" the Slant Range B must be changed to F which become the TARGET SLANT RANGE.