Geraki

As a new DCS user BUT old F-16 hardcore simmer and lover, I will post some vital updates that should be made from early days and then can add avionics and functions which I am sure will help in the development of other like AGM-65 so on...... 1. FCR A-A cursor bullseye position MUST!!!! 2. Spotlight search provides hands-on temporary switching to a 4 bar ±10° scan pattern, increasing opportunity for target detection in RWS and TWS.-possibly later 3. TWS scan bars and cursor like RWS 4. ACM modes NO RAD, There are four scan patterns or submodes available in ACM: 30° x 20°, 10° x 60°, Boresight and Slewable, represented on the MFD below OSB 2 by the mnemonics: 20, 60, BORE and SLEW respectively. They all have in common: • ACM automatically acquires and tracks the first target detected within submode search range. • Holding the TMS forward commands BORE and inhibits auto-acquisition until TMS is released. • ACQ cursor and search target symbols are not displayed. • While in ACM STT: TMS up, TMS right or CURSOR/ENABLE slew will not cause a radar break lock nor command a new scan pattern. 5. HSD Ghost A-A cursor bullseye position righthand side HSD Ghost A-G Cross HSD Cursor bullseye position lefthand side HSD 6. TD box in NAV -FCR lock F target range distance correction than B slat range which is now even with FCR locked target. 7. HUD AIM 120 Symbology: The Dynamic Launch Zone (DLZ)-Raero,Rpi,Ropt,M-pole ,F-pole FCR A-A RWS/TWS AIM 120 Symbology: The Dynamic Launch Zone (DLZ) 8. Steerpoint path creation -now when you add STPT via DED the previous paths deleted.- FIXED 9. A-G weapons bomb page: when you change bomb distance or separation feet e.g for MK82 the system keeps the same data for another loaded weapon e.g LGB -the correct is every weapon page has it's own data loaded. Then we can have AGM-65 avionics page .... kind regards

correct Falconeer

Three scan patterns are available in TWS and must controlled by cursor like in RWS They are: ± 60, 2 bar ± 25, 3 bar ± 10, 4 bar Without a bugged target, the azimuth scan centers on the cursors and elevation is controlled manually. When a target is bugged, the azimuth is biased to keep the bugged target in the scan and the elevation is centered on the bugged target. If the antenna elevation is tilted while the pilot has a bugged target, upon dropping the bug, the elevation scan will move according to what the pilot commanded to reflect the position set by the antenna elevation controls. in addition Spotlight Scan must occured Depressing and holding the TMS to the designate (up or forward) position for longer than 1 second will command the radar to spotlight scan (±10 degrees azimuth by 4 bars elevation). Spotlight scan is initially centered about the acquisition cursor and antenna elevation knob setting and can be slewed. The radar attempts to acquire and track the target within the acquisition cursor at release of the designate position of the TMS.

i do not think so , please review you documents and resources In TWS you can change bar scan the same like RWS with the cursor Three scan patterns are available in TWS. They are: ± 60, 2 bar ± 25, 3 bar ± 10, 4 bar AND Spotlight Scan the same like RWS Depressing and holding the TMS to the designate (up or forward) position for longer than 1 second will command the radar to spotlight scan (±10 degrees azimuth by 4 bars elevation). Spotlight scan is initially centered about the acquisition cursor and antenna elevation knob setting and can be slewed. The radar attempts to acquire and track the target within the acquisition cursor at release of the designate position of the TMS. kind regards

As you can see from video when the pilot selects Radar altimeter the R-value is the same even sometimes higher than the altimeter in the altitude bar. is it WIP ? kind regards

hope to be fixed in next update too about F distance of the RDR lock target ...now show the only B in NAV master mode which is wrong when you LOCK with FCR target

Correct we need a DTC ....

I prefer to wait and get an accurate and complete AGM-65 MFD page and avionics than an incomplete and the user can not even use it properly, like CCRP solution cue circle missing e.t.c let's wait and see......2-3 weeks :)

will be also the above in the next update? Kind Regards

Will be the Cursor bulls and in MFD -HSD in the next update?

Very nice work keep walking... and update it ...... Best Regards

Different but could be the same realistic ..... https://www.facebook.com/171823043426849/videos/652487598934974/

F-16 DTC Data Transfer Cartridge ability to load threat rings, Pre plants threats, areas, Countermeasure profile e.t.c kind regards

barrel roll

you are correct about 2 issues reported i am sorry !!!! The bug is when we have TD box in HUD even in NAV mode we must have F distance in the righthand side of HUD.

@BIGNEWY I speak about TD box and F target distance this is not correct as it is ....when pilot locks target in FCR the F details MUST show in the right-hand side of the HUD even in NAV mode. watch the RL video above. about TA altitude YES this is correct as it is .

Bouli306 my friend i am sorry .... :) lets hope to be fixed in new update like some other like AIM 120 DLZ ,and ASEC circle in HUD and MFD, ACM slew mode .... e.t.c kind Regards

Correct for TA altitude for DCS F-16 sim tape, wrong of DLZ you said I am in NAV mode, BUT in NAV mode you can have TD box and F target distance ... view the video end of discussion.

you are wrong mate ..... Watch the video below ..and again the target lock is FCR dependent in RL the pilot locks the target even in ACM or FCR the TD box remains in NAV mode until brake lock from the pilot that why the purpose of TD box in HUD.

Since your RADAR FCR locks the target the details from radar must display in the HUD, if not then you could have a reason for the TD box in the hud. The lock is Radar associated and not missile associated.

Make and Greece campaign too, please

A quick practice to calculate is add 4 kts per 1000 pounds of fuel and stores to the basic speeds. 143 knots for F-16C

stay at sustaining G's and in a lead pursuit .....do not be anxious to put the gun dot in the aircraft always try to put the gun dot in front of the nose of targeted aircraft ...for practice just pull more G' so the gun cross to be far enough in front of the bandit then pull sustain G's in order to have the same flight path with the bandit , the same turn, do that without to push the trigger when becoming comfortable with turn , then push the trigger. I hope the ED creates the simulated bullet trajectory with scor on in MFD.

I try the instant action take off without A-A weapons, I locked an A-A target in FCR but the F target range and letter TA target altitude never appear in the right side of the HUD I only have the B letter for RNG to STRP, even with target locked in FCR But in the same mission ( and it is not mission issue this happened also generaly if A-A weapons not loadout ) with A-A (CATM or AIM ) weapons loadout, the locked target gives in HUD the F target range but not TA altitude details. The bug is -===when we lock in FCR we must get data F and TA in right handside of HUD even we have or have not A-A weapons. The FCR lock's the target not the A-A weapon. Screenshot without A-A weapons Screenshot with A-A weapons

When we probably saying that RWS could be stronger, is the ability to show target's little bit quicker (stronger radar power)than TWS in addition in RWS the max scan area is 160 NM on the other hand in TWS 80 NM is the max scan range Generally, we use RWS in BVR for a quick target scan for distances over 40 NM under 40NM we can switch into TWS for sorting and multitargeting over 6 bogeys. SAM mode is even stronger, SAM provides tactical advantages over STT. First, SAM track updates are short (less than 1 sec) versus STT, increasing situational awareness on other targets.