Search the Community

Dev Blog №1 Well — here it is, this moment. We announce to you, dear friends, our new project and our new game world — "Korea. IL-2 Series." From now on and until the release of the game, we plan to publish developer diaries regularly and quite often, in which we will tell you in detail about most aspects of the new flight simulator. In this, the first, introductory entry, we will "go over the top" and outline the main features of the new project. What is it about? "Korea. IL-2" immerses the player in a virtual world that recreates the air battles in the skies over the Korean Peninsula from April 1951 to July 1953. Military operations during this time were concentrated in the northern part of the peninsula, and much was decided in the air. These events became a landmark in the history of aviation and military affairs: it was the swan song of propeller aviation (which played a very important role in the Korean War) and the rise of jet aviation. By the time of release, it is planned to recreate no less than 8 player-controlled aircraft — half of them will be jets and the other half will be piston-engined aircraft. The jets will be represented not only by the first "pioneers" of the new era, in which designers and pilots for the first time faced unknown challenges to their skills, but also by the powerful and efficient second-generation F-86A Sabre and MiG-15bis. Piston-engined aircraft will be the quintessence of the era — in the skies of Korea piston aviation enthusiasts will be able to fly the most powerful and efficient machines of this type in history: the F-51D Mustang and F4U Corsair and their Soviet opponents. One of them will be the Il-10 attack plane — where else but in a flight simulator about the Korean War could we pay tribute to the last attack plane of the famous Il-2 series? With improved aerodynamic contours, a more powerful engine, improved flight characteristics, still powerfully armed, and having an armored fuselage — in the hands of an experienced pilot it was a powerful machine. Who is it about? In the new project we are recreating the air forces of those countries whose pilots were most involved in the aerial battles: the USA, North Korea, the USSR and China. It is interesting that both the Soviet pilots and the Chinese People’s Volunteers participated under the legend that they were all flying North Korean planes — the identification marks of the USSR and China were painted over by the marks of the North Korean Air Force. In fact, there were air regiments in the command structure of the Soviet and Chinese armies, which will be reflected in the uniforms and equipment of the pilots and the language of radio communication. In the main game mode, the player will no longer be an ordinary pilot, concerned only with individual success in a series of combat missions — now the player will be a commander of an entire unit, and on his shoulders will rest not only the management of personnel, but also the planning of combat missions based on the situation and the management of the unit’s resources — the personnel and aircraft. What's new? The new game engine is even more different from Great Battles than Great Battles was from Rise of Flight. DirectX 12, Physically Based Rendering (PBR) technologies, new visualization systems for atmosphere, vegetation, graphical effects, integration of a new version of the sound API, a new GUI engine and design, an evolution of the aircraft simulation physics engine, including a new aerodynamics, systems operation and damage model, a new damage model for ground objects and ships, a new system of decision making and giving orders to AI pilots, a new radio communication system, and, of course, a new qualitative evolution of the main game mode — all this together makes a qualitative leap, not just an evolutionary step. It required a huge investment of effort and resources from us, because for the new technologies all models, effects, sounds, graphical interface — all this had to be created from scratch. In other words — this is not just "a new version of IL-2," no. "Korea. IL-2 Series" is a completely new version of the engine and has completely new content. What's next? Actually, we started the development of "Korea" in parallel with the development of "Great Battles" back in the summer of 2022, and most of the work has already been done. Now we are actively developing the graphical interface and game modes: the development of aircraft has already moved to the stage of creating cockpit models, while the map of Korea is in its final shape and we are already filling it with cities and airfields. The development of dozens of types of ground and sea objects is nearing completion, and the new technological base — engine and tools — is already ready. Most of the development path has been completed, all the parameters of the new project have been defined, and that’s why we can finally announce it with peace of mind and tell you about its features without making promises we weren’t sure we could keep. Thanks for your patience! We will try to keep you updated on what we have already created and how we are progressing during the development cycle until the release. Dev Blog №1 (il2-korea.com)

Okay so hear me out. I finally plated the NATO fighter campaign in 1953. Guess I just got tired with the short and sharp dogfights of the Radar missile era of the late cold war so I decided to jump to the 1953 campaign on the MiG-15bis cockpit. Well, I have experience with supersonic jet gunfights (MiG-19 is my all-time favorite) but riding the MiG-15bis with a vastly inferior engine is something I am not prepared for. Sure, I could chase turboprop attack aircraft (A-26 Invaders are my favorite prey!) but I kind of struggle catching with jet engine ones without getting too distracted by my fuel reserves. Once I managed to trash F-84S (they were on a strike configuration and were running away) when I happened to chance upon two Canadair Sabres. They tried to run-away as well but I was too determined to catch them and I eventually did but then they dropped their tanks and turned around and an ensuing dogfight erupted between me and my wingman. Suffice to say, in my opinion, MiG-15bis guns were horrible. The entire aircraft had the tendency to lose alignment when firing and the bullet ballistics is crap owing to the heavier caliber. The turn radius seems to be terrible as well, as the Canadair Sabre effortlessly managed to outturn me. Then I found myself being chased, completely at their mercy. A Sabre fired a 50 caliber salvo and grazed my wing, clipping my aileron (thank god the tank didn't explode) and I managed to emergency land to a nearby airfield while my wingman managed to shoot one of the Sabre who tried to finish me on my landing approach. In my opinion, MiG-15bis is a terrifying interceptor and absolutely crap dogfighter, but still, I want to hear your side and opinions on this. Is the MiG-15bis inferior at dogfighting or am I just a crap dogfighter (lol)? (screenshots of my MiG-15bis barely managing to escape from the two Murderous Canadair Sabre on my tail lol)

File Name: DHIMAR SABRE PACK File Submitter: trotski00 File Submitted: 03 April 2016 File Category: What If Hangar After seeing the effectiveness of the F-86F Sabres in the hands of the USAF over Korea, the Dhimaris made overtures to the Americans to buy F-86's, however as the Dhimaris had close ties with the UK, they eventually settled on buying the licence built Mk-4 which was in use at the time by the Canadian and British Air forces, they eventually purchased MK-4 airframes for the Ground attack/interdiction role, and later on the MK-6 for a pure fighter /interceptor . They foung the engine and avionics fits , were more suitable for Dhimari needs, and used these aircraft until the early 60's with great success. Click here to download this file

File Name: FJ-3M VF-211 Red Checkertails Skin for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 211 (the Red Checkertails which were later redesignated the VF-24 Renegades, not to be confused with the VF-211 Checkmates designated in 1959) flew the FJ-3M Fury from 1956-1957 before transitioning to the F8U-1 Crusader. This skin pack features skins from the 1956-57 deployment aboard the USS Bon Homme Richard (CVA-31) as part of Carrier Air Group 21 (CVG-21, Tailcode G). Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. You are free to use any of the textures in other skins or projects as long as proper credit is provided in the readme file. -Home Fries Click here to download this file

File Name: FJ-3 VF-191 Satan's Kittens Skin for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 191 flew the FJ-3 Fury from 1956-1957 before transitioning to the F11F-1 Tiger. This skin pack features skins from the 1957 deployment aboard the USS Yorktown (CVA-10) as part of Carrier Air Group 19 (CVG-19, Tailcode B). Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. You are free to use any of the textures in other skins or projects as long as proper credit is provided in the readme file. -Home Fries Click here to download this file

File Name: FJ-3M VF-142 Fighting Falcons Skin Pack for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is the first in a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). The idea of this series is to have a single skin for each squadron, and separate decals for each side number (Modex). The last 4 digits of the serial number (BuNo) use the USAF serial number to allow for dynamic BuNos, though the side number must be selected by choosing the skin itself. This will allow a common Modex pool and a single texture for each squadron, thereby allowing you to employ an entire squadron in a mission while keeping the hard drive and in-mission RAM footprint to a minimum. Fighter Squadron 142 (the Fighting Falcons, not to be confused with the VF-142 Ghostriders that was designated in 1963) flew the FJ-3M Fury for a short time (1956-1958), including a deployment on the USS Hornet (CVA-12) as part of Carrier Air Group 14 (CVG-14) before returning to NAS Miramar and transitioning to the F8L1-1 Crusader. This skin pack features skins from the 1957 Hornet deployment (CVG-14 Tailcode A) and the return to Miramar (1958) prior to transitioning to the Crusader. The 1958 skin displays the CVG-14 Tailcode NK, which replaced A once the US Navy went to 2 letter tailcodes. Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. You are free to use any of the textures in other skins or projects as long as proper credit is provided in the readme file. -Home Fries Click here to download this file

File Name: FJ-3M VF-121 Pacemakers Skin for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 121 flew the FJ-3M Fury operationally in 1957 before being redesignated as a Replacement Air Group (RAG). Of note, it was VF-121's status as a F-4 Phantom RAG at NAS Miramar that helped provide the squadron's reknown as the original host unit for the US Navy Fighter Weapons School ("Top Gun"). This skin pack features skins from the 1957 deployment aboard the USS Lexington (CV-16) as part of Carrier Air Group 12 (CVG-12, Tailcode D). Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. You are free to use any of the textures in other skins or projects as long as proper credit is provided in the readme file. -Home Fries Click here to download this file

File Name: FJ-3 VF-73 Jesters Skin Pack for DCS F-86F File Submitter: HomeFries File Submitted: 30 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 73 flew the FJ-3 Fury from 1956 until its decommissioning in 1958. Originally part of Carrier Air Group 7 (CVG-7, Tailcode L), VF-73 was transferred to CVG-4 (Tailcode AD) for its 1957 deployment on the USS Randolph (CVA-15). This skin pack features skins from CVG-7 and the 1957 Randolph deployment with CVG-4. Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. You are free to use any of the textures in other skins or projects as long as proper credit is provided in the readme file. -Home Fries Click here to download this file

File Name: FJ-3 VF-24 Corsairs Skin for DCS F-86F File Submitter: HomeFries File Submitted: 29 June 2015 File Category: Misc/AI Aircraft Skins This is part of a series of US Navy and Marine Corps skin packs for the FJ-3/FJ-3M Fury, the navalized variant of the F-86 Sabre (the M version being Sidewinder capable). Fighter Squadron 24 (the Corsairs which were later redesignated the VF-211 Checkmates, not to be confused with the VF-24 Renegades designated in 1959) flew the FJ-3 Fury for a short time (1956-1957) before transitioning to the F3H Demon. This skin pack features skins from the 1956-57 deployment aboard the USS Shangri-La (CVA 38) as part of Carrier Air Group 2 (CVG-2, Tailcode M). Note: this skin pack uses an EXE installer that creates common texture folders and an autoexec.cfg (if you already have one, you can make manual changes). I would like your feedback on this system; if it works I intend to apply it to my other skin packs. If you have a 1.x version of this skin installed, then the installer will remove the old 1.x liveries and obsolete texture folders. Be sure to update any missions that used 1.x series skins. 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. Updating from the 1.x series of FJ-3 Skins: With the release of DCS World 1.5.4 and 2.0.3, the decal layer that once covered the entire model has been removed by Belsimtek. As such, organizational specific modex placement as well as modex placement on the wing is no longer possible. The modex (1xx-3xx) is now selected in the Mission Editor rather than by skin selection. For skins that have the BuNo on the tail, the last two digits of the modex are also used for the BuNo (this is not accurate, but just to allow a dynamic number on the tail). Detail placement in textures based on USN skins by Crazyeddie. Special thanks to SkateZilla for the awesome Photoshop template. You are free to use any of the textures in other skins or projects as long as proper credit is provided in the readme file. -Home Fries Click here to download this file

View File SF2 "MiG Alley" Wings Over Korea (KAW v1.1) Hi-Res 1920X1080 Menu Screens and Music! SF2 "MiG Alley" Wings Over Korea (KAW v1.2) Hi-Res 1920X1080 Menu Screens and Music v7 By Viper 04/26/2020 Note: I removed all the nation sounds from this Menu packs for size reasons. If you intend to install the "VIPER63A HQ Menu Sounds" pack, please install that pack first. Installing the HQ Sound pack over the Menu pack may overwrite some of the menu specific music files. You can always re-install this menu pack to get the menu specific theme music back. I made these upgraded alternate "Korean Air War" themed Menu screens to go with Do335's "SF2 Wings Over Korea" package! Pleae unzip the compressed file and preview the new screens before installing them. I recommend doing this as there are some alternate screens I have in there that you might like better. If you choose to install these screens, I recommend that you back up your FLIGHT and MENU folders in the SF2 Mod folder you're installing this mod into. Just in case you want to go back to your original setup. To install, simply unzip and copy the uncompressed FLIGHT and MENU folders to your StrikeFighter2 mod folder. My StrikeFighter2 mod on Win97 64-bit was..(yours may be different)... C:\Users\<your_id>\Saved Games\ThirdWire\Strikefighter2 Korea\ Enjoy! Submitter viper63a Submitted 03/15/2015 Category Menus  

File Name: Sabres HAF cl-13 File Submitter: acesfakia File Submitted: 14 January 2013 File Category: SF2 Series Add On Skins Cl-13mk Canadair F-86 sabre HAF Hi this is a skin for the greek F-86 sabre... Was a canadair cl-13....and upgrade to f-86e/m this is for the aerobatic team named Hellenic Flame,colors plane... ..and more skins are coming....this week... it can be use it in all f-86....with the same skin...just make changes the pixels..resolution... be attention in that...and don't forget the texture....ini. Click here to download this file