Jump to content

Recommended Posts

'What if' KAW Hawker Hunter F.1 with Campiagn


'What if' KAW Hawker Hunter F.1A & F.1B with campiagn 1.0

 

 

The back story:

 

In order to meet the Mig-15 threat over Korea and with no capable fighters currently in the RAF inventory the British Ministry of Supply instructs Hawker Aviation to undertake a crash production program of its P.1067 fighter. Project ‘Huntsman’. In less than a year since the prototype flew and two years ahead of schedule the Hawker Hunter is deployed to the Korean Theatre in early 1952. Since the Hunter F.1 designation was already assigned to the first full production Hunters due into service in 1954, the Hunters produced under program ‘Huntsman’ are (unusually) designated Hunter F.1A

 

These aircraft are basically identical to the future production Hunter F.1 the most obvious difference being that they are finished in High Speed Silver. However the lack of paint means these Hunters are 21 Mph faster and 53Kg lighter than the full production F.1 Hunters.

 

Operations over Korea immediately highlighted the Hunters inherent shortcomings. Of most concern was its lack of fuel and endurance with barely an hour’s flight time. Also of concern was the damage done to the fuselage caused by the ejection of spent cartridge links. These concerns (among others) would be addressed in time by future models of the Hunter, but in the skies of Korea in 1952 the lack of range and endurance had to be immediately mitigated. And thus the Hunter F.1B is born with the addition of wing mounted drop tanks installed in theatre.

 

 

What's in it:

 

 

- Hawker Hunter F.1A

 

- Hawker Hunter F.1B

 

- Various RAF 43 and 222 Squadron Skins in Camo and High Speed Silver.

 

- NOTE: The camo skins are included as a bonus but the aircraft data.ini files are set up to reflect the high speed silver skins as I have included the weight reduction and increased speed that comes without using camo paint. I found the figures I used in an article about the trial OD green Sabres in Korea.

 

- sounds

 

- pilot

 

- Modified Korea Campaign using the Hunters. This will not change the original campaign in any way, you will see an additional campaign called 'Korean War Hunters Over Korea' that you can select. Missions will be similar to the Sabre, No 43 Squadron is based at Suwon AB (K-13) and No. 222 Squadron at Kimpo AB (K-14).

 

- NOTE: this mod can be added to the Wings Over Korea mod without any change what so ever to the original game play. You will never see these Hunters show up over Korea unless you play the above included campaign or start a single mission with a Hunter.

 

 

Operations:

 

 

- canopy open key=10 automatic closing at take off

 

 

To Install:

 

 

- Designed to be used with the Wings Over Korea mod but should work without it.

 

- Put everything in you main StrikeFighters2 KAW mods folder

 

- Get the Wings Over Korea mod here:

 

http://combatace.com/files/file/15221-wings-over-korea-1-of-2/

 

http://combatace.com/files/file/15220-wings-over-korea-2-of-2/

 

 

 

Credits:

 

 

- Third Wire

 

- Paulopanz Hunter F.1 Skins & Edits for SF2

 

- Sundowner Hunter F6 Templates.

 

- Do335 Wings Over Korea

 

- Evryone else in the WOK/ KAW team

 

 

Released under CombatAce Fair-Use terms.

 

 

 

Enjoy!

 

 

Dan

 

(Dtmdragon)


 

  • Like 1

Share this post


Link to post
Share on other sites

very nice! Started new campaign in it and it is a balst! looks great and not that out-of-place in my opinion!

 

good work there dtmdragon :ok:

Share this post


Link to post
Share on other sites

I'm intrigued, because the RAF did not deploy entire units in Korean, only exchange pilots on secondment to the USAF and RAAF. The Fleet Air Airm *did* deploy the Hawker Sea Fury though. The frontline RAF fighters of the time would have been the Meteor F Mk 8 (used by the Aussies), the DH Vampire FB Mk 5 and, from 1952, the Venom FB Mk. 1. At the time of Korea, the RAF were more heavily engaged in their own operations in Malaya, and were stretched my meeting commitments in Europe.

Delays to getting the Avon running with adequate surge margin in the Hunter meant buying in interim solutions, including the Venom, and the Canadair Sabre IV, which was deployed almost entirely with 2ATAF in West Germany. The SF2 version of the Venom FB4 is *interesting*, it has lower wing loading than the MiG-17, and, at low level, is more than capable of out-turning it. Performance in the vertical plane isn't great though. Venom vs. MiG-15 is an interesting one. The two major shortcomings of the J-47 powered Sabres were a lack of firepower (and why the USAF never fitted them with cannon is a mystery to me) and too low power/weight ratio at altitude. The Venom has the same kind of power limitations, but has a much better offensive kick with 20mm Hispanos.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By ironroad

      By the end of March 2019, one of the world’s most successful, combat-proven, fast jets will have been retired.
      https://combataircraft.keypublishing.com/2018/01/25/last-year-of-the-tornado-gr4/
    • By HomeFries


      View File M-2000C: US Marine Corps Adversary Squadron VMFT-401 "Snipers"
      M-2000C: US Marine Corps Adversary Squadron VMFT-401 "Snipers"
      for DCS World 1.5.6 and later
       
      VMFT-401 was commissioned in 1986 and in 1987 received the IAI Kfir (designated F-21A) under lease from the Israeli government. The "Snipers" flew the Kfir until 1989, when it transitioned to the F-5E Tiger II. This skin is inspired by the 1987-89 timeframe in which USN and USMC flew the Kfir, a delta-wing aircraft of French origin.
       
      The Kfir was built by IAI based on the Mirage V airframe. The closest flyable substitute to the Kfir in DCS is the M-200C, so this is a fictional skin that paints the M-2000C as a USMC adversary. This skins uses the traditional Israeli Air Force desert pattern that was used on some of the VMFT-401 adversary aircraft. Since the original aircraft were leased and kept much of their original markings, so is the case with the M-2000C skins. No original markings (e.g. rescue arrows and safety markings) were subdued to match US paint schemes. However, minor liberties were taken with the pilot skins in order to make the pilots look more American.
       

      For Compact Installations - A Note About Autoexec.cfg:
      Rather than copying texture files to their respective livery folders, I prefer to use a series of common texture folders along with unique filenames. This allows a single instance of many of my common textures, and keeps the hard drive footprint to a minimum (especially nice if you run a SSD for your system drive).
       
      The installer will add a series of folders to the DCS Texture path; if you do not have these folders created, then it is no problem. The autoexec.cfg included will automatically point to the Texture folder in your Saved Games\DCS folder, and regardless of whether you run the Open Alpha, Open Beta, or Release version of DCS, the path will always point to your Saved Games\DCS\Texture folder. Again, this saves space on your hard drive.
       
      If you use your own Autoexec.cfg, then when prompted to overwrite you can click "no". This will create a file called autoexec.new, and you can manually make the updates as you like. Just don't modify the top line with the file date; this is used by the installer for version control. However, feel free to include it in your existing autoexec.cfg, so you don't get prompted to overwrite until there's another update to the autoexec.cfg.
       
      If you inadvertently overwrite your autoexec.cfg, it is actually backed up as autoexec.old. Just open it and copy the appropriate information to the new file.
       

      For Traditional Installations or JSGME Compatible Extractions:
      If you don't wish to use the shared texture folder and custom autoexec.cfg, you have a couple of other options available. Selecting the Traditional Install copies all textures to each livery folder, then copies each livery to each version of DCS detected (up to three versions, including release, open alpha and open beta). As a result, the listed hard disk space requirement assumes all three DCS versions are installled. Each skin is independent and portable.
       
      If you wish to install to a location other than your Saved Games folder, you must select the Single JSGME Extraction, or else the installation will fail for not detecting existing Saved Games\DCS folders. Selecting this option will create a JSGME compatible install that can be dropped directly into your JSGME _MODS folder for installation. Each skin is independent and portable.
       
      For either of these installation options, if there is an issue with textures not displaying, then it is likely a problem with the installer. Please let me know what textures are missing so that I can troubleshoot the issue.
       
       
       
      If you have any squadron requests, please PM me. If possible, provide top and profile views of the aircraft, preferably line art (much easier to extract color), and for CAG/CO birds, a close up of the tail fin is greatly appreciated.
      You are free to use any of these skins in other projects as long as proper credit is provided in the readme file.
      Fly Navy!
      -Home Fries
      Submitter HomeFries Submitted 03/08/2017 Category Misc/AI Aircraft Skins  
    • By HomeFries


      View File P-51D Colombian Air Force Skin Pack (Fictional)
      This is a package of two P-51D skins using the current Fuerza Aérea Colombiana grey paint scheme used for the Super Tucano. One version of the skin has a "shark mouth" on the nose. Nationalities are USA and Spain.
       
       
      Installation Instructions:
      Copy the folders to your Saved Games\DCS\Liveries\P-51D folder.
       
      Optional:
      The release of DCS World 1.2.4 added the ability to add texture paths using the file "autoexec.cfg" in your Saved Games\DCS\Config folder. This will allow you to save hard drive space as long as the skin filenames are unique. My skins support this, so any DDS file with the same name will be identical.
       
      In order to enable this feature, add the following line to autoexec.cfg (be sure to create the file if it doesn't exist):
      table.insert(options.graphics.VFSTexturePaths, "C:/Users/<username>/Saved Games/DCS/Textures")
      You can use any path (even a different drive), but you must use forward slashes for your path. Backslashes won't work here.
       
      Then, you can move all of the DDS files from each of the skin folders to this new folder you've added to your path. Allowing overwrites is not a problem, as I use unique names for each file. Finally, be sure to go into each description.lua file and change all "false" entries to "true."
       
       
      You are free to use any of these skins in other projects as long as proper credit is provided in the readme file.
       
       
      -Home Fries
      Submitter HomeFries Submitted 06/28/2014 Category Misc/AI Aircraft Skins  
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..