Jump to content

Search the Community

Showing results for tags 'f-86'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CombatACE General Forums
    • The Pub
    • CombatACE News
    • Military and General Aviation
    • Digital Recon
    • Virtual Squadron Chat
    • Site Support / Bug Reports / Suggestions
  • Editorial Reviews and Interviews
    • Hardware Reviews
    • Game Reviews
    • Interviews
    • Mission Reports
  • Modding and Developer Forums
    • Razbam
    • Mod Mafia
    • CAF Development
  • Eagle Dynamics Digital Combat Simulator Series
    • Digital Combat Simulator News
    • Digital Combat Simulator Series File Announcements
    • Digital Combat Simulator Series General Discussion
    • Digital Combat Simulator Series Modding/Skinning Chat
    • Digital Combat Simulator Series Mission/Campaign Building
  • Thirdwire: Strike Fighters 2 Series
    • Thirdwire: Strike Fighters Series News
    • Thirdwire: Strike Fighters 2 Series - File Announcements
    • Thirdwire: Strike Fighters 2 Series - Knowledge Base
    • Thirdwire: Strike Fighters 2 Series - General Discussion
    • Thirdwire: Strike Fighters 2 Series - Screen Shots
    • Thirdwire: Strike Fighters 2 Series - Mods & Skinning Discussion
    • Thirdwire: Strike Fighters 2 Series - Mission & Campaign Building Discussion
    • Thirdwire: Strike Fighters 2 Series - Sci-Fi/Anime/What If Forum
    • Thirdwire: Strike Fighters 2 Series - World War II Forum
  • Thirdwire: Strike Fighters 1 Series
    • Thirdwire: Strike Fighters 1 Series - File Announcements
    • Thirdwire: Strike Fighters - Knowledge Base
    • Thirdwire: Strike Fighters 1 Series - General Discussion
    • Thirdwire: Strike Fighters 1 Series - Mods/Skinning Discussion
    • Thirdwire: Strike Fighters 1 Series - Mission/Campaign Building Discussion
    • Thirdwire: Strike Fighters 1 Series - Sci-Fi/Anime/What If Forum
    • Thirdwire: Strike Fighters 1 Series - Prop Heads Forum
  • Over Flanders Fields
    • OFF / WOFF 1 2 3 / UE - General Discussion
    • OFF / WOFF 1 2 3 / UE - Knowledge Base
    • OFF / WOFF 1 2 3 / UE - File Announcements
    • OFF - Retired Threads
  • WW1 Flight Simulation
    • WWI Flight Sim Discussion
    • Thirdwire - First Eagles 1&2
    • Rise of Flight
  • IL-2 Series / Pacific Fighters / Cliffs of Dover
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: News
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: File Announcements
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: General Discussion
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: Mods & Skinning Chat
    • IL-2 Series / Pacific Fighters / Cliffs of Dover: Mission & Campaign Building
  • Canvas Knights WW1 Game
    • Canvas Knights WW1 Game - Official News Releases
    • Canvas Knights WW1 Game - General Discussions
    • Canvas Knights WW1 Game - Works In Progress (WIP)
    • Canvas Knights WW1 Game - Other Mods
    • Canvas Knights WW1 Game - Videos and Screenshots
    • Canvas Knights WW1 Game - File Announcements
  • EAW - European Air War
    • EAWPRO - New Location Redirect
    • EAW - File Announcements
    • EAW - General Discussions
    • EAW - Support and Help
    • EAW - Skinning, Modding, Add-ons
    • EAW - Online Multiplay
    • EAW - Knowledge Base
  • Flight Simulation
    • General Flight Sim News
    • General Flight Sim Discussion
    • Microsoft Flight Simulator
    • Jet Thunder
    • Falcon 4 Series
    • Combat Pilot Series
  • Helo Simulation
    • The Hover Pad
  • World Language Forums
    • Español
    • Português
    • Deutsch
    • Polski
    • עִבְרִית
    • Italiano
    • 한국어
    • 中文 (正、简)
    • 日本語
    • Русский
    • Français
    • Česky
  • West Coast ATC / PROPS Racing
    • West Coast ATC General Topics
    • PROPS Racing General Topics
  • Racing Sims
    • Racing Simulations General Discussions
  • Tactical Sims/FPS
    • The Bunker
    • Americas Army
    • Armed Assault Series
    • Call of Duty
    • BattleField
  • Naval Simulation
    • Naval Combat Information Center
    • Killerfish Games - Cold Waters, Atlantic & Pacific Fleet
    • Silent Hunter Series
    • Dangerous Waters
  • Space Simulations
    • Sci-Fi Simulations
    • Star Trek Legacy
    • Star Wars
    • Battlestar Galactica
  • Hardware/Tech/Gadgets
    • Hardware/Software Chat
    • Game Controllers
    • Case Modding
  • Odds & Ends
    • Strategy Simulations
    • Game Console Corner
    • Buy/Sell/Trade Corner
  • EAWPRO's Discussions

Calendars

  • Community Calendar

Categories

  • Strike Fighters by Thirdwire
    • Strike Fighters 1 Series by Thirdwire
    • Strike Fighters 2 Series by Thirdwire
  • First Eagles by Thirdwire
    • First Eagles - General Files
    • First Eagles - WWI and Early Years 1914 - 1920
    • First Eagles - Golden Era 1920 to 1940
  • Digital Combat Simulator Series
    • DCS Aircraft Skins
    • DCS Aircraft Mods
    • DCS Singleplayer Missions
    • DCS Multiplayer Missions
    • DCS Campaigns
    • DCS Object Mods
    • DCS Sound Mods
    • DCS Tracks / Videos / Tutorials
    • DCS Utilities
    • DCS Joystick Config Files
    • DCS Misc. Files
    • DCS Patches
  • OFF/WOFF - Over Flanders Fields by OBD Software
    • Aircraft Skins
    • Aircraft Models
    • Scenery and Ground Objects
    • Maps, Missions, and Campaigns
    • Modding Tools and Add-on Software
    • OFFice / OFFbase / OFFworld
  • Canvas Knights WW1
  • EAW - Europen Air War
  • IL2: Forgotten Battles / Pacific Fighters by Ubisoft
    • IL2 Series Aircraft Skins
    • IL2 Series Campaigns & Missions
    • IL2 Series Game Mods
    • IL2 Series Utilities/ Editors
  • Rise Of Flight
    • ROF - Aircraft Skins
    • ROF - Missions and Campaigns
    • ROF - Miscellaneous Files
  • FALCON 4.0: Allied Force by MicroProse
  • Flight Simulator by Microsoft & PROPS Racing Files
    • FSX by Microsoft
    • FS9 and Pre-FS9 by Microsoft
    • PROPS Racing Files
  • Racing Simulations
    • rFactor
    • Main Game Files and Updates
    • GTR/GTR2
    • Aircraft
    • Aircraft Skins
    • Ground and Sea Vehicles
    • Scenery, Maps, and Objects
    • Missions
    • Miscellaneous
    • Mods
    • Tools
  • Sci-Fi Simulations
    • Star Trek Legacy
    • Star Wars Games
    • Misc - Other
  • First Person Simulations
    • Armed Assault
    • America's Army
  • Naval Simulations
    • Cold Waters
    • Silent Hunter Series
    • Dangerous Waters

Group


AIM


MSN


ICQ


Yahoo


Jabber


Skype


Location


Interests


Website


Twitter


Facebook

Found 19 results

  1. 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
  2. DHIMAR SABRE PACK

    Version SF2 Merged

    163 downloads

    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.
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. Version 2.0

    16 downloads

    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
  9. Version 2.0

    9 downloads

    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
  10. Version 2.0

    8 downloads

    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
  11. Version 2.0

    7 downloads

    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
  12. Version 2.0

    5 downloads

    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
  13. 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
  14. Version 2.0

    7 downloads

    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
  15. 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  
  16. Version Version 7

    157 downloads

    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 Win10 64-bit was..(yours may be different)... C:\Users\<your_id>\Saved Games\ThirdWire\Strikefighter2 Korea\ Enjoy!
  17. Screen 140726 021935

    From the album Ironroad

    DACT with a Korean War-era F-86 Saber Jet. Not sure how an F-86 fits into the Black Sea, Final Countdown Maybe?
  18. 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
  19. Sabres HAF cl-13

    Version

    52 downloads

    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.
×

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..