Geraki

Dear ED dev's the current slew is not correct as is , please refer into Real manual 1. MLU M_1 Slewable ACM HUD Symbology . . .page.136 2. TO 1F-16CM-34-1-1 block 50 page 1-564 & 1-565 3. Youtube public reference video PM if need it!!! In addition with current elevation numbers position it is too difficult to read actually the numbers. Please re-evaluate your sources

The antenna elevation reference number must be above and below scan centre "small circle" When the scan centre is slewed the number and the scan circle move all together, right now only the small circle moves.

Lock sound specially now in SLEW mode is vital since inform the pilot for radar lock outside HUD FOV

Since PDLT Cues on the HUD is included into M3 older and M4.2 newer tape so MUST include HUD A-A symbology namely the PDLT octagon Has almost the same like A-10 HMD Please search F-16 PDLT octagon on the net regards

i hope to be fixed soon.

it needs to be fixed!!!

Hello does the app is compatible with x32 BIT windows? or only x64 Bit ? If yes can you make the app compatilbe into x32 bit too. Kind Regards

It is the airspeed refresh rate ...HUD Sampling If you study enough HUD videos on Youtube, you'll notice there are small delays in numerical data sampling such as airspeed and altitude (either caused by HUD or CADC processing and/or the 'natural' delays in pitot-static systems) and not an instantaneous display of individual numbers. An example is a quick acceleration in airspeed will 'jump' from value to value...i.e., 102, 105, 109, 113. In DCS the code display every single digit through an acceleration/deceleration or changes in altitude. reference youtube . https://www.youtube.com/watch?v=BHx-OWdHqf8

Soon i hope!!!

Nice tool is this possible with lua editing this one

It is WIP the ACM mode need work like BORE mode MUST automaticaly lock everything it is below 10 miles inside the cross without delay, the same for ACM line 10X60 but...... i hope it is WIP Also we have to see the slew mode also we will se in near feature!!!

Simple code fix in order to be the cursor bulls full visible open MFD_FCR_AA.lua(:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\MFD\indicator\Pages\FCR\MFD_FCR_AA.lua) and change the values from -- bearing and range from steerpoint/bullseye addStrokeText("FCR_Bearing_range", "000 00", STROKE_FNT_DFLT_8_12, "LeftCenter", {-224, -110} , nil, {{"FCR_BearingRangeLabel"}}) *************************************************************************************************************************************** i edit also the :\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\MFD\indicator\Pages\FCR\MFD_FCR_IFF.lua for more realistic representation of IFF SCAN/LOS text Code : \MFD_FCR_IFF.lua dofile(LockOn_Options.script_path.."Displays/MFD/indicator/MFD_Symbology.lua") dofile(LockOn_Options.script_path.."Displays/MFD/indicator/Pages/FCR/MFD_FCR_Defs.lua") IFF addPlaceholder("IFF_ContactsKeeper", nil, nil, {{"MFD_updateMultipleSymbolsBuffer", DYNAMIC_DATA.IFF_CONTACTS}}) local IFF_Show = addPlaceholder("MFD_IFF_Show", nil, nil, {{"MFD_IFF_Show"}}) local IFF_Mode = addStrokeText("IFF_Mode", "", STROKE_FNT_DFLT_10_14, "LeftCenter", {-235, -140}, IFF_Show.name, {{"MFD_IFF_Modes"}}, {"OFF", "M1", "M2", "M3", "M4", "M+"}) addSizeClipMask(IFF_Mode, 2, 20, {{"FCR_ModeMenu", FCR_MODE_MENU_STATE.MAIN}}, {-4, 0}) -- Select label local posY = -160 addStrokeText("IFF_IntgFunc", "", STROKE_FNT_DFLT_8_12, "LeftCenter", {-235, posY}, IFF_Show.name, {{"MFD_IFF_IntgFunc"}}, {"", "SCAN", "LOS"})

i agree for the above but i mention when you do not have bug and you want to change bar scan automatically with cursor movement side to side in MFD. like RWS bar cursor selection.

As the title , in TWS when you move the cursor into the left /right MFD gimbals you can change the BAR scan. like RWS. TWS Range Scale. TWS has four range scales: 10, 20, 40, and 80 NM. The 160 NM is not available. The 10 and 20 NM range scales feature a fast antenna scan rate (65 degrees/second) to detect and update targets in closer proximity. The 40 and 80 NM range scales use a slower scan rate (48 degrees/second) to increase detection sensitivity. TWS Scan Coverage. Either a 3 bar ±25 degree or 4 bar ±10 degree scan pattern can be selected by pressing the OSB associated with either the azimuth width or the number of bars. In TWS, scan width and number of bars are not independently selectable. Bump AZ is not available in TWS TWS/Single Target Track (STT) Transitions. Acquisition is initiated by coralling the bugged target with the ACQ cursor, then pressing the TMS FWD and releasing. If the TMS is not released within one second, spotlight search is initiated. STT is only allowed on the bugged target. In TWS when the pilot bug the target ACQ cursor remain stuck in the bugged target, if the pilot move the cursor then the ACQ cursor unstuck from bugged target.

any update off te above?-SLANT RANGE B - TARGET SLANT RANGE F Kind Regards

Please fix the above in upcomming update it is easy text fix. kind Regards

Very nice please keep coming to improve BVR capabilities (Radar and BVR Missiles) - in order to entered into BVR Arena VS F-16/FA-18 ...... Welldone so far!!!

Very important implementation for Block50 if created.

when we have cross cursor for mark point the Ghost cursor must be disappear.

As per title when HSD SOI The Cursor cross + appear in the CENTER of OWN ship , then you can move it up/down into the MFD gimbals and you have the ability to change Range Scale for HSD only using Hotas.

In the last update the Amraam lose easy the lock from target if the target NOTCH the Amraam. in low distance you have to release the Amraam below 5 miles with 1.5 mach in order to hit the target if the target notch aggressively. I think it is need some refinement the Amraam AIM 120C5 to be more aggressive and not lose lock or energy so easy.

There is wrong not to lock targets in low altitude and in low distance . The Radar need recalculation.

in continue from this post In Real when you enter into TWS and move the cursor left/right MFD borders you can change between A6 B4 andA3 B2 bars or change the range in NM when you move up/down borders. From 40 to 20 and vise versa. When you bug a target the cursor stack on target and moves with bugged target until pilot slew the cursor for next bugged target , third, or fourth target ..... and with TMS right can step from each target. On TWS and RWS when you bug a target the Bar scan change automatically into B3 . Also in TWS you can have spotlight search. Depressing and holding TMS Up for longer than 1 second will command the radar to spotlight search like the same is now in RWS mode. kind Regards

Hello my friend As you can see from the picture the cursor bulls are on the last blue line ,this make a conflict and the digits are not clear. This is not normal and not realistic , please view also the videos references too. kind regards

Hello i made some changes into FCR Text in order to be realistic and for players to view clearer the cursor bulls details. Right now the cursor bulls is on the last blue line so it is difficult sometimes to view the numbers there. I change some parts of the code and i make it more realistic as it is in Block 50. As you can see from the image below a move all the left side of FCR distance in miles , blue lines more left in order the cursor bulls to be between the last blue line as per real , now we can read perfectly the cursor bulls. In addition i move up and closer the M symbol and the SCAN/LOS text in order not to conflict with bulls eye ring. the code below is only for M and SCAN/LOS text For miles number and blue lines i have not find the values yet but i provide ans edited FCD symbols that should be changed for RL. kind regards Code: MFD_FCR_IFF.lua ********************************************************************************************* -- IFF addPlaceholder("IFF_ContactsKeeper", nil, nil, {{"MFD_updateMultipleSymbolsBuffer", DYNAMIC_DATA.IFF_CONTACTS}}) local IFF_Show = addPlaceholder("MFD_IFF_Show", nil, nil, {{"MFD_IFF_Show"}}) local IFF_Mode = addStrokeText("IFF_Mode", "", STROKE_FNT_DFLT_10_14, "LeftCenter", {-235, -130}, IFF_Show.name, {{"MFD_IFF_Modes"}}, {"OFF", "M1", "M2", "M3", "M4", "M+"}) addSizeClipMask(IFF_Mode, 2, 20, {{"FCR_ModeMenu", FCR_MODE_MENU_STATE.MAIN}}, {-4, 0}) -- Select label local posY = -150 addStrokeText("IFF_IntgFunc", "", STROKE_FNT_DFLT_8_12, "LeftCenter", {-235, posY}, IFF_Show.name, {{"MFD_IFF_IntgFunc"}}, {"", "SCAN", "LOS"}) **********************************************************************************************