DCS Hornet – Ground power start

From communications menu, connect ground power:
Main… Ground crew… Ground Electric Power… On…

Wait until Ground Chief inform you: “Ground power is on.”

From GND Power panel…

  1. Reset EXT PWR switch
  2. Set GND PWR switches from 1 to 4 into B position. You have to hold them about 3 second to get them stay on.

Note! Do not do system tests until you have engines running.

Start radio, make align…

When you want to start engines:
1. Battery ON
3. Crank right engine…

DCS Hornet: DDIs, IFEI and RWR to second monitor with Helios

Instead of editing DCS .lua files manually by yourself to get DDIs and IFEI into your second monitor, you can use Helios to add them and much more.

In a picture below, I have 4xCougar MFD’s attached onto a second monitor. One of them is working as a Hornet UFC. Standby indicators and IFEI background comes from Helios Captain Zeen’s Hornet profile http://www.captzeen.com/. Warning lights also comes from Captain Zeen profile (most not visible in pic below, see small SAM text next to right DDI).

Click picture to open it larger:

See Helios from: https://www.digitalcombatsimulator.com/en/files/3302014/
Downloads from: https://github.com/HeliosVirtualCockpit/Helios/releases

For my setup, I installed Helios and used Captain Zeens Hornet profile as a starting point. I ripped off everything I did not need. Then I moved/resized all pictures/gauges what was left to a correct positions and added my own pictures or edited pictures from Hornet profile to get the look what I wanted.

Fourth Cougar MFD was used as Hornets UFC by editing positions of buttons of Captain Zeens Hornet UFC. I added some small own created pics and also added labels for buttons for not need to remember what has been binded and witch button.


Change kneeboard location when Helios is used:

Because Helios creates its own .lua files for setting up views for DCS and monitors, kneeboard position is in DCS default location. And for me it was located in lower right corner of monitors area (in area of right DDI and standby indicators).

To change default kneeboard location I found a workaround from Reddit by user ScopeDopeBC:

Process to do it is copied here below:

  1. Copy
    C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Scripts\Aircrafts_Common\Cockpit\ViewportHandling
  2. Edit file and change line 33 from:
    dedicated_viewport = {default_x,default_y,default_width,default_height}

    into (or use location/size what you prefer):

    dedicated_viewport = {0,640,600,800}
  3. Copy
    C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Scripts\Aircrafts_Common\Cockpit\KNEEBOARD\indicator\init.lua
  4. Change 2nd line:


  5. Copy
    C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Scripts\Aircrafts_Common\Cockpit\KNEEBOARD\declare_kneeboard_device.lua
  6. Change:
    local init_script = LockOn_Options.common_script_path.."KNEEBOARD/indicator/init.lua"


    local init_script = LockOn_Options.common_script_path.."KNEEBOARD/indicator/init2.lua"

    Now kneeboard settings should not get changed on updates and you only need to edit the aircraft settings. For A10 (if you need to do it for F18, just find correct folder and similar files):

  7. Edit
    C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\device_init.lua




DCS Hornet – Stored INS align

DCS Hornet GND align takes about 8 minutes. Stored INS align is faster than normal align.

To make Hornet INS use stored INS align:

  1. Start until right engine runs.
  2. Turn on and see MPCD. INS align is not started (INS knob in OFF position):
  3. Turn INS knob to GND:
  4. From MPCD see that INS align process (that 8 minute version) is started when computer shows quality and is counting time. Stop this and start stored heading align by pressing STD HDG:
  5. STD HDG stays boxed and align process is started again:
    Note! Do not release parking brakes during align!
  6. Wait until time passes and QUAL says OK. Align took about 1:30:
  7. Turn INS knob to IFA position:

DCS Hornet – Litening and GBU bombs

Simple/fast guide for bombing static targets with Litening targeting pod and laser guided bombs…

Fill up tanks and arm your plane with some GBU’s (in this guide I use GBU-12 witch is same as 82LG):

Set FLIR to ON. Wait it to warm up:

    • STBY: Pod is on stand-by mode. It is on (and warming up) but image is not visible. Pod’s turning head is moved into a safe position.
    • ON: Pod is on. If DDI FLIR page show text “NOT TIMED OUT” pod is “warming up”.

Set your master arm switch to ARM and select A/G mode:

DDI to FLIR page: Press menu button until you see a FLIR text in upper left corner and click it:

DDI in FLIR page. If pod is still warming up, you can see RDY text in upper left corner and NOT TIMED OUT text in screen:

FLIR ready. See OPR text in upper left corner:

Buttons explained:
WIDE / NAR: Changes zoom from wide to to narrow.
ZOOM: changes zoom level from Z0 to Z9.
CCD / FLIR: Changes between visible camera and infrared camera.
UFC: opens UFC menu
VVSLV: Velocity Vector SLaVe button

Note! Set your MFCD to SA page and activate map (top left corner button). Pod targeting location is shown as a square with a dot in it. That way you will see in a map display where your pod is looking:

Activate pod by clicking VVSVL two times (second time clicking takes you back to normal mode). Now you should see camera view that is pointing forward and camera view is moving with your plane:

Click sensor selector switch to right to control that DDI. Then you can slew your pod view around with a TDC. DDI is selected when there is a diamond with a dot on top right corner of DDI:

Change image source FLIR/CCD witch ever is better for you visually to find targets.

If your target has a waypoint added or is near a waypoint, you can use SA pages WPDSG (WayPoint DeSiGnate button) to move pod automatically looking at that location.

Move cursor over target. Note that cursor e.g. over roof of target, seeing from far away, may be actually behind target when your planes location changes. So point cursor to e.g. to wheels or ground below target.

Click TDC to designate target. Your cursor changes into a diamond:

Note: IF you click Sensor Selector hat towards FLIR DDI, it changes FLIR mode to Area Track mode and locks that location (cursor cannot be moved with TDC). If you do it again, it changes to Point Track mode. I don’t use area track. It is easier to move cursor in snowblow mode (diamond). And do not use Point Track unless you especially need to use it for moving targets. You can get away from Area Track and Point Track  with Sensor Selector switch click towards FLIR DDI.

Set LTD/R switch to ARM:

Click UFC button on DDI to show LTDC (Laser Target Designator Code?) option:

Click LTDC and click code into UFC and then press ENT:

Now go to STORES page with left DDI and set up GPU (LG82 in pic below) to use our new laser code:

  • On left DDI stores page:
    • Select 82LG
    • Select MODE -> AUTO
    • EFUZ -> NOSECclick CODE.
  • From UFC:
    • Click CODE
    • And write same code that was written on FLIR page
    • Press ENT


Turn your plane into target and line up for a bomb run. Target can be seen on HUD as a square standing on its corner (flashing if outside of HUD view). Distance to target can be seen in front of TGT text. Time to release is in front of REL text:

Fly towards a target and when release line appears and comes running down on HUD, press and hold pickle button on joystick:

Bomb is released automatically after 0 seconds and HUD starts counting time to auto lasering and then counts “TTI” Time To Target.

Watch for center of pod location from DDI FLIR page and correct it with TDC if necessary.

Ensure hit via FLIR page:

For a new bomb run, set LTD/R switch back to ON (it goes automatically off) and add a new laser code for FLIR and set up a new GPU from STORES page.


DCS Hornet – Altitude indicators and warnings

HUD altitude

In pic below, HUD is showing barometric altitude in right box. In this pic altitude  is 2 730 ft barometric:

HUD can also show radar altitude. When radar altitude is shown, letter R is added right of altitude box:

Barometric altitude can be changed to radar altitude from UFC switch:

If radar altitude cannot be shown (e.g. aircraft upside down), letter B starts blinking next to HUD’s altitude box and barometric altitude is shown. Radar altitude is also shown only to about ~5000 ft and then is changed to show barometric altitude.

Note that you have to also set a warning altitude from radar altitude warning knob. Othervice in ALT RDR selected, radar altitude is not functional and B will flash on HUD.

Standby altimeter

Standby altimeter is in cockpit above pilots right knee:

It has a box for thousands of feet and (almost 3000 feet in pic) and pointer for hundreds (~720 feet). So altitude in this pic is ~2720 feet. Standby altimeter shows only barometric altitude.

Knob in lower left corner of altimeter can be used to change barometric pressure setting. Setting is shown in lower area of gauge (~2990 inHg). To change it, you may you mouse middle button roll or click and hold left mouse button and drag it up/down.

While changing pressure setting from standby altimeter, a pressure is also shown below altitude box in HUD for few seconds:

Altitude warnings

Three altitude warning can be adjusted for Hornet. Radar altitude warning sound from radar altimeter gauge and spoken “altitude, altitude” warning through DDI from HSI’s Data page.

Radar altitude gauge:

Radar altitude gauge has needle for showing altitude (2500 ft in pic). Red arrow in pic is pointing to white triangle that shows witch warning altitude is set (500 ft in pic). Knob on right lower corner can be used to set warning altitude by rotating and test warning with a push.  In middle of gauge an “OFF” text will show up if radar altitude is not on.

HSI… DATA… A/C page radar warnigns

From HSI and DATA page a altitude warnings can be seen in lower left area of DDI (text WARN ALT in pic). These setting set altitudes for spoken warning sounds (5000 for barometric and 0 for radar). To set altitudes press DDI Option Select Buttons and look UFC:

From UFC, you can click wanted warning altitude with number buttons and press enter to set it.

SRS Transponder – Squawk code

Bind some key or joystick button for SRS Overlay Toggle -control to show/hide it while playing DCS:

…or use SRS program toggle -button:

SRS Transponder in overlay:

Mission code (Mode 1 or M1):
In military use: Role, mission or aircraft type.

Aircraft identification code (M3):
Add squawk code here.

Toggle transponder on/off:
Button for toggling transponder on and off.

Ident button:
Makes your aircraft to “blossom” on the controllers radar scope. Controller asks you to use this if needed. Text “IDENT” will appear after text “TRANS” in DCS if Ident is on.

3-pulse reply (M4):
Mode 4 on/off button. Encryption or something…

Emergency squawk codes to use:
7700: General emergency
7600: Lost communications

Settings for SimpleRadioStandalone with Hornet

If you intent to fly with others in DCS, SRS (Simple Radio Standalone) is a must. So get familiar with it and see download and installation information from:

To make it work best with Hornet, I suggest to use one hat for both radios 1 and 2. I use Thrustmaster Warthog, so I have plenty of buttons/hats to use.

I have selected “Coolie switch” from throttle to be as a radio selector. Hat left click for radio select 1 and hat right click for radio select 2 (radio 1 is left radio on hornet and right is number 2):

To set Radio 1 and 2 select buttons in SRS, go to Controls tab and with set button you can select them:

To make same Radio select buttons work as an radio PTT (Pust To Talk) button, go to Settings tab and set it on:

Now you have a radio selector switches that also work as an PTT switches.

OvGME and DCS Hornet view settings

If you edit files inside of a DCS game program folder (usually C:\Program Files\Eagle Dynamics\DCS…), files edited will be overwritten on DCS update. It might be frustrating, if you have to edit .lua files back to your settings after every update.

For this problem, you can use OvGME to add edited files as “mods” into a game. You can familiarize and download OvGME e.g. from https://wiki.hoggitworld.com/view/OVGME

You can use OvGME with my IFEI, UFC and kneeboard view settings .lua file edits. See posts:
DCS Hornet – IFEI and UFC to external monitor
DCS kneeboard position in multimonitor setup

First create a folder for mods. I have used Windows normal \Documents folder under my user profile and created there an OVGME Mods folder:
C:\Users\USERNAME\Documents\OVGME Mods

Install OvGME and check correct settings. Title is just a name for used configuration. Root folder is a DCS game folder. Mods folder is folder for mods that we just created:

Then see for where your edited .lua files are in DCS game folder and create the same structure into your OvGME Mods folder.

For IFEI and UFC edited .lua files, create folder and add .lua files to:

…and for kneeboard position .lua file, create folder structure and add file to:

Restart OvGME and you should see in OvGME a “Hornet View lua edits” folder mod that you can select and enable:

You can quit OvGME and your mods are still enabled. To disable them, you have to start OvGME and disable them.


Remember to disable and enable your mods after update (or better disable before update). They will not work after update.

DCS kneeboard position in multimonitor setup

Note! Not needed anymore: Update on Open Beta DCS
“Upgrade cockpit kneeboard. Mouse drag and resize. Added clickable buttons for navigation and making bookmarks. Each new bookmark – new color. Route UI buttons callbacks to track.”


Note: You can use OvGME with this setup. 

Annoyed by a kneeboard position in a multimonitor setup?

DCS seems to locate kneeboard to a lower right corner of a monitor area by default (my monitors are set up side by side in settings, while in cockpit they are on top of each other):

To change DCS a kneeboard position in a multimonitor setup, edit viewporthandling.lua file in C:\Program Files\Eagle Dynamics\DCS World\Scripts\Aircrafts\_Common\Cockpit\ folder.

Comment out old line with — and add a new one:
dedicated_viewport = [0,0,562,750}

Check that you are inside of a correct function:

Numbers inside of [x,y,w,h] are:
x = x position in monitor of kneeboard top left corner,
y = y position in monitor of kneeboard top left corner,
w = kneeboard width and
h = kneeboard height.