Difference between revisions of "F/A-18C"
(→Planned Weapons) |
(Manual countermeasures lua editing) |
||
| Line 105: | Line 105: | ||
[https://www.youtube.com/watch?v=FAKuuaemFUs& DCS F/A-18C Hornet Countermeasures Tutorial by RedKite] | [https://www.youtube.com/watch?v=FAKuuaemFUs& DCS F/A-18C Hornet Countermeasures Tutorial by RedKite] | ||
| + | |||
| + | === Editing our default F18 countermeasure setup === | ||
| + | |||
| + | Please note that you can also edit your countermeasures outside of the game; normally if you close the game down you lose the editing to your countermeasure profiles that you have done in game. If you find you have a particular setup that you would like to keep (forever), rather than the default setup that comes in the F18, you can edit the .lua file and change the defaults to suit your preference. For example, we can tone down the amount of countermeasures used, so that we have more time we can use the countermeasure profile before you run out of flares / chaff (but it could make the profile overall less useful). | ||
| + | |||
| + | |||
| + | To edit a .lua file we are first going to need an adequate text editor; although you may be familiar with using notepad, I would instead recommend installing and using notepad++. The reason for using notepad++ is that the normal notepad does not respect the original file structure (so basically, newlines / enters as well as spacing) in some cases, and as such the file may become unusable if you try to edit and save the file this way. Notepad++ instead keeps the original file structure intact. | ||
| + | |||
| + | The file we wish to edit is the '''CMDS_ALE47.lua''' file; but before you start editing it please make a backup of it first. This file can be found in the path | ||
| + | (\Eagle Dynamics\DCS World OpenBeta ) \Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device | ||
| + | |||
| + | |||
| + | Once you have made a backup file of the original .lua file, we can start editing it as we see fit. Please note that we '''do not want to edit anything besides the numbers''', as editing anything else the file unusable. Technically, you should be able to rename the comments (ie the text following the double hyphens ''-- Default manual presets''), but I would simply refrain from doing so and only edit the actual profile. | ||
| + | |||
| + | The profiles we are interested in (potentially) editing are manual profiles 1 through 6 (you could edit the auto presets as well, but I find it less useful). Please note that the following profiles can be accessed directly in the cockpit correspond to the following: | ||
| + | (manual) Program 1 is CMS aft (Countermeasures aft). | ||
| + | (manual) Program 5 is CMS forward (Countermeasures forward). | ||
| + | (manual) Program 6 is DISP button (Big Friendly Dispenser button on the left side of the cockpit). | ||
| + | |||
| + | |||
| + | Now onto the actual formatting of a countermeasure profile; note that they all function the same, but they all work for different profile. Let's take manual profile 1 as an example: | ||
| + | -- MAN 1 | ||
| + | programs[ProgramNames.MAN_1] = {} | ||
| + | programs[ProgramNames.MAN_1]["chaff"] = 1 | ||
| + | programs[ProgramNames.MAN_1]["flare"] = 1 | ||
| + | programs[ProgramNames.MAN_1]["intv"] = 1.0 | ||
| + | programs[ProgramNames.MAN_1]["cycle"] = 10 | ||
| + | The ProgramNames.MAN_1 refers to the fact this is the first manual profile (ProgramNames.MAN_2 being the second manual profile, and ProgramNames.AUTO_1 being the first auto profile; though again we probably do not want to edit those). | ||
| + | |||
| + | The chaff and flare values refer to how much flare and chaff is dispensed, but this is the amount dispensed per cycle and not the total amount dispensed. For our example (manual profile 1) we have 1 flare and 1 chaff dispensed per cycle, but we have a total of 10 cycles (cycle = 10). This means that the profile runs for 10 cycles total, during each cycle dispensing 1 chaff and 1 flare (thus expending a grand total of 10 chaff and 10 flares). The interval (intv) value is the time delay in seconds between each cycle; as in our example profile it is set to 1 (1.0), we have a profile that runs for 10 seconds, each second expending a chaff and a flare. | ||
| + | |||
| + | Overall that seems rather wasteful to me, so lets come up with a more sensible and conservative profile (but perhaps less effective) so that we can enjoy our countermeasures a bit longer: | ||
| + | -- MAN 1 | ||
| + | programs[ProgramNames.MAN_1] = {} | ||
| + | programs[ProgramNames.MAN_1]["chaff"] = 0 | ||
| + | programs[ProgramNames.MAN_1]["flare"] = 1 | ||
| + | programs[ProgramNames.MAN_1]["intv"] = 0.8 | ||
| + | programs[ProgramNames.MAN_1]["cycle"] = 5 | ||
| + | As you may have noticed nearly all manual profiles expend both chaff and flare at the same time, which I absolutely hate: you are almost never in the situation where you are being engaged by both radar guided missiles and infrared seeking missiles, so I prefer to split my countermeasure profiles accordingly. In my revised profile I run the profile for 4 seconds total: each cycle lasts 0.8 seconds, and during a cycle I only dispense a singular flare. | ||
| + | |||
| + | === Saving our edited countermeasure profile from DCS updates === | ||
| + | |||
| + | Now, our last thing we have to realise is that although this profile is saved from deletion if we open and close our game (or hop into a brand new F-18), it will be deleted once DCS updates. However, we can save it from being deleted, by making it into a mod (modification)! To do this we will need yet another tool, called OVGME: this is a tool that many people who wish to mod their game use to, well, mod their game. | ||
| + | |||
| + | The installation of OVGME is largely self-guiding (but there will be tutorials for it), but the gist is that we end up with a profile folder and a mod folder for DCS. The profile tells OVGME which game we wish to mod, where to find this game and where the folder is that we are going to store our mods in. The mod folder is where we store our mods that we wish to use. | ||
| + | |||
| + | So if we wish to save our edited countermeasures profile, all we have to do is make a new mod for it! In the OVGME DCS mods folder you have made, we wish to recreate the folder structure pointing to our CMDS_ALE47.lua file. This has to be done with the DCS World (Openbeta) folder as our begin folder (or root); all these folders will be empty, except for the last folder, as in there we will place our edited CMDS_ALE47.lua file. | ||
| + | |||
| + | The first folder we will make in the DCS mod folder is the mod folder itself, so I recommend naming it something like "''Nanne118's totally awesome countermeasure mod for the F18''" or something equally easy to remember. Now all we do is replicate the folder structure until we get to the CMDS_ALE47.lua file location: we do not have to copy in every file, as OVGME is smart enough to only replace the actual files in the mod. Equally you do not want to just copy over the existing folder structure from the DCS World install location, as you will be copying over all the files as well. You could delete all the files, but that would be a whole lot more work. | ||
| + | |||
| + | The folder structure we want to make, with all empty folders, is: | ||
| + | \Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device | ||
| + | In the device folder we then paste our modified CMDS_ALE47.lua folder, so that we can get OVGME to overwrite it. The only thing we then have to change is that we have to enable our mod within OVGME itself, so start up the OVMGE.EXE, click the mod, and enable the selected mod. | ||
==Ground Radar== | ==Ground Radar== | ||
Revision as of 19:17, 11 October 2018
Contents
The F/A-18C Hornet is a twin-engine, multi-role, carrier-capable combat jet. It was designed by McDonnell Douglas (now Boeing) and Northrop in the 1970's, and is the only jet in the US inventory to carry both the Fight and Attack designation (the "F/A" part of the name). The Hornet is a supersonic capable jet, able to reach speeds of Mach 1.8. The Hornet modeled in DCS represents an "off-the-line" US Navy Lot 20 jet, with the OFP-13C software upgrades. It is equipped with the F404-GE-402 enhanced performance engines (which is the more powerful engine that replaced the original F404-GE-400's). The F/A-18C/D served as the baseline for the Boeing F/A-18E/F/G Super Hornets. The Hornet is capable of carrying a wide array of both precision and dumb bombs, A/G and A/A Missiles, rockets, and is supplemented with a 20-mm cannon mounted in the nose.
The Hornet entered service in 1978, and first saw combat in 1986 over the skies of Libia with numerous Hornets preforming SEAD strikes and strike missions. The Hornet again saw action during the Gulf War of 1991, as there were 106 in theater with the Navy, along with a further 84 USMC that were shore-based. It was during the Gulf War that the Hornet was credited with it's first Air-to-Air kills (both aircraft were MiG-21's, shot-down by AIM-9's and AIM-7's). Notably, the aircraft credited with the kills went on to resume their strike mission and dropped their 4 Mk-84's (2,000lb bombs), living up to their multi-role moniker. The Hornet took it's first combat losses in the Gulf War as well, in total 10 Hornets received battle damage, which included 3 losses (2 to ground fire, and one very likely to an Iraqi MiG-25). All told, Hornets flew a total of 4,551 sorties during the Gulf War.
Since the Gulf War, the Hornet has been a vital piece of the Navy/USMC inventory, and has seen action in every conflict or operation since then. While it is still in active service with the USMC (and will remain until the early 2030s), in April 2018 the US Navy retired the F/A-18C from combat roles.
Required DCS World Version
Please note that you need to be on the open beta version of the game to fly the Hornet.
If you don't have the game installed already you can get the open beta from here
If you already have the release version installed, it's much faster to switch to the open beta using the DCS World updater as it will only change the files needed, keeping all the ones that don't need to change.
Switching to the Open Beta
- Open File Explorer and navigate to your DCS World install
- Hold LShift + Right click on bin folder and press "Open command prompt here"
- Type or paste
DCS_updater.exe update @openbeta
Switching to Open Beta on Steam
- Open steam and navigate your DCS in your library
- Right click DCS and pick Properties
- Click the betas tab and then from the drop down select Open Beta
- Steam will now patch your game once you close the dialog box
Once the update is finished, you should be able to install the Hornet via the Module Manager in game.
SimpleRadio Update
The latest version of SimpleRadio has been updated to work with the Hornet.
DCS F/A-18C Manual Waypoints Quick Guide by RedKite
Weapons
Implemented
Mk-82 series Mk-83 series Mk-84 series CBU-99 and Mk-20 Cluster Bombs BDU-33 Training Bomb BDU-45 Training Bomb 2.75 inch rockets 5 inch rockets 20mm cannon AIM-9L/M/X and CATM Sidewinder AIM-7F/M Sparrow AIM-120 B/C AMRAAM
Planned Weapons
AGM-88C HARM AGM-45A/B Shrike AGM-84D Block 1C Harpoon AGM-84E SLAM AGM-84H/K SLAM-ER AGM-65E Maverick AGM-65F/G Maverick AGM-154A JSOW AGM-154C JSOW Walleye I ER/DL Walleye II ER/DL GBU-10 Paveway II GBU-12 Paveway II GBU-16 Paveway II GBU-24B/B Paveway III GBU-38 JDAM GBU-31 JDAM GBU-32 JDAM AIM-7P Sparrow Mk-40 Destructor Sea Mine Mk-63 Quickstrike Sea Mine Mk-77 Fire Bomb
Countermeasures
DCS F/A-18C Hornet Countermeasures Tutorial by RedKite
Editing our default F18 countermeasure setup
Please note that you can also edit your countermeasures outside of the game; normally if you close the game down you lose the editing to your countermeasure profiles that you have done in game. If you find you have a particular setup that you would like to keep (forever), rather than the default setup that comes in the F18, you can edit the .lua file and change the defaults to suit your preference. For example, we can tone down the amount of countermeasures used, so that we have more time we can use the countermeasure profile before you run out of flares / chaff (but it could make the profile overall less useful).
To edit a .lua file we are first going to need an adequate text editor; although you may be familiar with using notepad, I would instead recommend installing and using notepad++. The reason for using notepad++ is that the normal notepad does not respect the original file structure (so basically, newlines / enters as well as spacing) in some cases, and as such the file may become unusable if you try to edit and save the file this way. Notepad++ instead keeps the original file structure intact.
The file we wish to edit is the CMDS_ALE47.lua file; but before you start editing it please make a backup of it first. This file can be found in the path
(\Eagle Dynamics\DCS World OpenBeta ) \Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device
Once you have made a backup file of the original .lua file, we can start editing it as we see fit. Please note that we do not want to edit anything besides the numbers, as editing anything else the file unusable. Technically, you should be able to rename the comments (ie the text following the double hyphens -- Default manual presets), but I would simply refrain from doing so and only edit the actual profile.
The profiles we are interested in (potentially) editing are manual profiles 1 through 6 (you could edit the auto presets as well, but I find it less useful). Please note that the following profiles can be accessed directly in the cockpit correspond to the following:
(manual) Program 1 is CMS aft (Countermeasures aft). (manual) Program 5 is CMS forward (Countermeasures forward). (manual) Program 6 is DISP button (Big Friendly Dispenser button on the left side of the cockpit).
Now onto the actual formatting of a countermeasure profile; note that they all function the same, but they all work for different profile. Let's take manual profile 1 as an example:
-- MAN 1
programs[ProgramNames.MAN_1] = {}
programs[ProgramNames.MAN_1]["chaff"] = 1
programs[ProgramNames.MAN_1]["flare"] = 1
programs[ProgramNames.MAN_1]["intv"] = 1.0
programs[ProgramNames.MAN_1]["cycle"] = 10
The ProgramNames.MAN_1 refers to the fact this is the first manual profile (ProgramNames.MAN_2 being the second manual profile, and ProgramNames.AUTO_1 being the first auto profile; though again we probably do not want to edit those).
The chaff and flare values refer to how much flare and chaff is dispensed, but this is the amount dispensed per cycle and not the total amount dispensed. For our example (manual profile 1) we have 1 flare and 1 chaff dispensed per cycle, but we have a total of 10 cycles (cycle = 10). This means that the profile runs for 10 cycles total, during each cycle dispensing 1 chaff and 1 flare (thus expending a grand total of 10 chaff and 10 flares). The interval (intv) value is the time delay in seconds between each cycle; as in our example profile it is set to 1 (1.0), we have a profile that runs for 10 seconds, each second expending a chaff and a flare.
Overall that seems rather wasteful to me, so lets come up with a more sensible and conservative profile (but perhaps less effective) so that we can enjoy our countermeasures a bit longer:
-- MAN 1
programs[ProgramNames.MAN_1] = {}
programs[ProgramNames.MAN_1]["chaff"] = 0
programs[ProgramNames.MAN_1]["flare"] = 1
programs[ProgramNames.MAN_1]["intv"] = 0.8
programs[ProgramNames.MAN_1]["cycle"] = 5
As you may have noticed nearly all manual profiles expend both chaff and flare at the same time, which I absolutely hate: you are almost never in the situation where you are being engaged by both radar guided missiles and infrared seeking missiles, so I prefer to split my countermeasure profiles accordingly. In my revised profile I run the profile for 4 seconds total: each cycle lasts 0.8 seconds, and during a cycle I only dispense a singular flare.
Saving our edited countermeasure profile from DCS updates
Now, our last thing we have to realise is that although this profile is saved from deletion if we open and close our game (or hop into a brand new F-18), it will be deleted once DCS updates. However, we can save it from being deleted, by making it into a mod (modification)! To do this we will need yet another tool, called OVGME: this is a tool that many people who wish to mod their game use to, well, mod their game.
The installation of OVGME is largely self-guiding (but there will be tutorials for it), but the gist is that we end up with a profile folder and a mod folder for DCS. The profile tells OVGME which game we wish to mod, where to find this game and where the folder is that we are going to store our mods in. The mod folder is where we store our mods that we wish to use.
So if we wish to save our edited countermeasures profile, all we have to do is make a new mod for it! In the OVGME DCS mods folder you have made, we wish to recreate the folder structure pointing to our CMDS_ALE47.lua file. This has to be done with the DCS World (Openbeta) folder as our begin folder (or root); all these folders will be empty, except for the last folder, as in there we will place our edited CMDS_ALE47.lua file.
The first folder we will make in the DCS mod folder is the mod folder itself, so I recommend naming it something like "Nanne118's totally awesome countermeasure mod for the F18" or something equally easy to remember. Now all we do is replicate the folder structure until we get to the CMDS_ALE47.lua file location: we do not have to copy in every file, as OVGME is smart enough to only replace the actual files in the mod. Equally you do not want to just copy over the existing folder structure from the DCS World install location, as you will be copying over all the files as well. You could delete all the files, but that would be a whole lot more work.
The folder structure we want to make, with all empty folders, is:
\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device
In the device folder we then paste our modified CMDS_ALE47.lua folder, so that we can get OVGME to overwrite it. The only thing we then have to change is that we have to enable our mod within OVGME itself, so start up the OVMGE.EXE, click the mod, and enable the selected mod.
Ground Radar
Not yet implemented
IFF (Identification Friend or Foe)
A basic version of IFF currently exists within the hornet module. At this time it will only let you know if your target is friendly or not by placing them in the center of your hud. If a valid IFF response is received you will get a square marker, where as an invalid response is currently represented by a diamond.
Manuals
I Read the Manual So You Don't Have To By MustardCosaNostra
F/A-18C Hornet | Armament Matrix by Twisted-Biscuit
Wags' Tutorial Videos
Preflight, Startup, Taxi, and Takeoff
AIM-7 Sparrow Air-to-Air Missile
Feature List
https://forums.eagle.ru/showthread.php?t=194412&page=2
HOTAS Configs
SkillSawTheSecond's HOTAS setup
Carrier Lights Tutorial
FAQ
Click to expand ->
Q: I cant use Afterburners when taking off
A:The Hornet uses WOW (Weight on Wheels) to prevent unintentional use of the afterburners. You can manually override this system by pulling the finger lifts on the HOTAS and advancing the throttle.
Q: How does IFF work?!
A:Currently only a basic version for the hornet is implimented. After locking your target, putting them in the center of the HUD will give you either a diamond or a square. Square targets are friendly, and diamond targets are not responding to IFF.
