Zeus67

RL limitation as in it won't accept more elements. I feel like balancing on a tightrope whenever I am working on it. :smartass:

Better yet, request a power cart from the ground crew.

The RDO button in the PCA does this: The lost track becomes yellow and it remains for a few seconds more. Since I don't know how long I can use the F-15C standard: 8 seconds. Hopefully the radar will reacquire by that time and turn it back to green. But as you said this will be a bit complex to code, and I have another difficulty to deal with: the VTB is very near the system limit of elements it can show.

I'm totally dependent on ED on this. All I do is ask the radar if the target is still there. If it isn't then it is cleared from the target list. I'll see about the time-out, but I need to finish other stuff before i deal with this.

The TWS bug is an antenna recovery bug. The antenna recovers normally when the elevation is above the aircraft's plane. If it is below the aircraft's plane it takes its sweet time returning. The bug is worse when you do a roll. If you do a hard roll the antenna suddenly finds itself below the aircraft's plane and out of position and loses the target due to the long recovery time. In fact tests shows that it does at least two full sweeps before it returns to its position. It manages to keep the target inside the search cone if you do slow and gentle rolls, but then if you are in a combat situation that is not going to happen very often. Since this bug affects basic antenna movements I cannot fix it. ED has to do that. I'll drop a reminder. This bug affects both RWS and TWS. It does not affect STT because it uses a different system to keep a target in sight.

GCI is usually used for intercepts beyond 100 nmiles. Logic dictates that it works this way: 1. The radar network detects and enemy formation a long distance away. 2. The interceptors are alerted, but since it will take some time for the enemy to arrive, they have time to do all ground stuff, including INS alignment. 3. The interceptors take-off and upon contact with ground control set their radar for GCI. This is the TEL option that appears when the system is in AA mode. 4. Ground control vectors individual aircraft to individual targets. 5. The pilot enters target data into the system by using the VTB switches. It took me a long time to know what they were for. 7. The target icon appears in the VTB. This is calculated from the data sent by the GCI network. From time to time data is updated via data link. 8. When the aircraft reaches engagement range it deactivates GCI mode and track with its own radar for weapons guidance. At this point the TEL mode in the HSI is redundant since you are already tracking it in the VTB and HUD.

MARK points cannot be edited. I'll check if they can appear in PREP.

Yes it is. I have the sample code and it still is a bitch to code.

To setup a rendezvous point to form up before flying towards the target or a rendezvous point after an attack. Specially if your flight is using the "spoke wheel" attack (everybody coming from different points of the compass to confuse the anti-air defenses). The advantage of the VAD over the BAD is that you don't need a flight plan.

Just one small correction. It was introduced in the last 2.0.3 update.

This information should appear in the next update: The Horizontal Situation Indicator HSI The Horizontal Situation Indicator, commonly called HSI, is an aircraft flight instrument that combines a Heading Indicator with a VOR-ILS indicator. Unlike standards HSI used in American aircrafts, the M-2000C HSI was designed to require little to no pilot input. It consists of a compass rose to indicate aircraft true or magnetic heading, a selected auto pilot heading indicator, two needles, a four-digit mechanical display, an operational mode indicator and four failure flags. The only pilot required inputs are: Operational Mode and TACAN Offset values. The HSI also controls the type of heading that will be used on all navigation instruments: True or Magnetic. 1. Selected AP Course indicator. 2. DME display 3. Needles *· Needle 1: Wide. *· Needle 2 Thin. 4. VAD (TACAN Offset Point) input knob. 5. Compass Rose. 6. HSI mode selector *· Cv NAV *· Cm NAV *· TAC *· VAD *· ρ *· θ *· TEL Operational Modes The HSI has four operational modes: INS/VOR Navigation (NAV), TACAN/VOR Navigation (TAC), TACAN Offset Point/VOR Navigation (VAD) and Ground Controlled Interception (TEL). *· NAV (main INS/VOR navigation mode): In this mode, the HSI connects with the INS and displays waypoint navigation information along with bearing to selected VOR/ILS station. This is the only mode that allows to select between true or magnetic headings, through its two sub modes: Cv NAV: In this mode the system uses true heading. Cv stands for Cap vrai (French for True heading). Cm NAV: In this mode the system uses magnetic heading. Cm stands for Cap magnétique (French for Magnetic heading). The selection of Cv NAV or Cm NAV also affects the heading indicators in the following instruments: HUD, HDD, ADI. All other following modes are part of the “Cm” category, i.e. they use only magnetic heading indications. *· TACAN/VOR Navigation (TAC): In this mode the HSI connects to the TACAN receiver. *· TACAN Offset Point/VOR navigation (VAD): In this mode the HSI calculates and navigates towards a point offset to the current TACAN station. The offset point location is introduced in polar coordinates, distance and magnetic bearing, by using the VAD (TACAN Offset Point) input knob. This mode has three sub modes: VAD: This is the operational mode. The HSI checks if it a valid TACAN Offset Point exists and calculates distance and bearing from the current aircraft position towards the offset. ρ (Rho): This mode is used to enter the distance in nautical miles from the TACAN station to the offset point. θ (Theta): This mode is used to enter the magnetic bearing from the TACAN station to the offset point. Please refer to the TACAN Offset (VAD) Navigation chapter for more information on this mode. *· Ground Controlled Interception (TEL): In this mode the HSI displays interception information: bearing, distance and interception course, towards a target. This mode is used when the aircraft is under Ground Controlled Interception (GCI). Note: Ground Controlled Interception is not simulated in DCS and thus this mode is not operational. HSI Information provided The HSI needles and indicators show navigation information based on the selected mode. TACAN Offset Point (VAD) Navigation The HSI has a special navigation mode called VAD (Vecteur ADditionel, French for Additional Vector). The VAD is an offset point calculated from the position of the selected TACAN station. The system uses the Needle 1 (Wide) and DME (numeric) indicators. The Needle 1 and DME flags will be shown if it is not possible to engage the VAD mode. For the VAD mode to be operational the following conditions must be met: 1. A TACAN station has been selected and the signal must be received. 2. The polar coordinates from the geographical position of the TACAN station to the offset point have been entered into the system. When all conditions are met the HSI will navigate directly towards the TACAN Offset Point (VAD) from the aircraft position. How to operate the VAD mode: 1. Select a TACAN station in the TACAN receiver. 2. Place the HSI in TACAN mode and check that it is receiving a signal from the TACAN station (the DME and Needle 1 flags should not be shown). 3. Place the HSI in θ (Theta) mode. 4. Enter the magnetic bearing from the TACAN station to the VAD by rotating the VAD input knob. The Needle 1 indicator will rotate towards the selected value, note that the DME window will also show the corresponding numeric value. 5. Place the HSI in ρ (Rho) mode. 6. Enter the distance from the TACAN station to the VAD (offset point) by rotating the VAD input knob. The DME indicator will start showing the selected distance. The valid values are from 001.0 to 999.0 nautical miles. The Needle 1 indicator will show the selected θ (Theta) 7. Place the HSI in VAD mode. The system will calculate the geographical position of the offset point from the current aircraft position: The Needle 1 indicator will show the magnetic bearing to the VAD and the DME indicator will show the distance in nautical miles (see the graphic). HSI Failure Flags The HSI has four failure flags that indicate an error condition in the HSI: 1. DME Failure: It shows a bar across the DME indicator, blocking the value shown. If it is visible there is an error in the DME value. 2. Needle 1 Failure: It shows an orange tab in the right flag window. If it is visible, then it is not possible to show the bearing to the selected navigation point/station. The Needle 1 indicator will park itself to the 135º position. 3. Needle 2 Failure: It shows an orange tab in the left flag window. If it is visible, then it is not possible to show the bearing to the selected VOR/ILS station. The Needle 2 indicator will park itself to the 225º position. 4. Heading Failure: It shows an orange tab in the bottom flag window. If it is visible, then it indicates a problem with the heading gyro and thus the heading value shown in the HSI and other heading indicators is not reliable. If shown it is recommended to use the auxiliary heading gyro.

Small bug when you start in the air. The DA (RWR) switch is in the M position but the RWR is still OFF. Please cycle the switch back to A then M in order to turn it on. It is fixed for next release.

This is how it is behaving right now. https://forums.eagle.ru/showpost.php?p=2919817&postcount=80 There is not much to go. Most of the functionality is an educated guess. Aircraft defenses are among the most heavily classified items there are and nobody, not matter how willing, is authorized to speak about them. Not even for a simulator.

If you are inTWS then it is a known.bug that must be fixed by ED..

Unfortunately it is very hard to finetune low speeds in DCS. Sometimes it is better to leave things as they are because changing them can and will alter other settings.

Anybody has a HOTAS Thrustmaster mapping that want to share?

I mapped all of them to the PCA and PPA. So I can change weapons/modes without having to use the keyboard.

I will appreciate that. So far what I've seen is that the Saitek software, or should I say Logitech now :), only creates keyboard macros. So I wondered if I had to do keyboard bindings and then map them to the throttle/stick.

I know that I am new to the DCS environment and all. In fact, before DCS, the last combat flight simulator I flew was Microprose's F-117 Nighthawk. At the time it was top of the line in combat flight simulators. It even had the Desert Storm campaign!! :D Anyway, a few months ago I bought a Saitek X-55 Rhino system and after many trials and errors I think I have the best mapping, so far, for the M-2000C. I am using DCS control mapping instead of Saitek's system. I still don't know how to configure this thing. :helpsmilie: But I wanted to share this with you and hope it may be useful to somebody. I want see your mappings, perhaps yours are better than mine,

What do you mean?

I suggest that you contact Customer Support.

No, there isn't. But a quick glance can tell you the switch position.

The system only uses one method: TAS or RS. When you select both TAS and RS the system will use TAS but if for any reason the radar is not working, it will use the radalt (RS) as a backup.

These are the final changes made to the CMD: DRM (marked LL) is the system master switch. DRP only controls the decoy release program. If DRM is in A (Off) you cannot release chaff nor flares. If DRM is in SA or AU but DRP is in A: you cannot use the decoy release program but PANIC release is now available. If DRM is in SA or AU and DRP is between 1 to 10: you can use the selected decoy release program and PANIC release. Button 5 = Decoy Release Mode (DRM). Knob 6 = Decoy Release Program (DRP). The Keyboard bindings are now these: FLARE release is now Decoy Program Release. CHAFF release is now Decoy PANIC Release. There are new keyboard bindings for the DRM switch and DRP knob so you can map them to the keyboard and/or joystick. Default Decoy Release Program is the following: Also we have included the éclair pod release position. Now when you use the éclair pod, the chaff and flares will be released from the pod position instead of the internal containers position. The following are not available at this time: 1. Automatic decoy release (AU). 2. Ability to modify decoy release program. We will provide them as soon as we can.

The N.DEG bug has been fixed in development.