Jump to content
HomeFries

An idea: Making USN NationName a level 1 decal

Recommended Posts

While it makes perfect sense to keep the default NationName as a level 0 decal (i.e. taking its entries from NATIONS.INI), when it comes to the US Navy I would like to be able to have the name of the carrier on the side of the aircraft. Since USN Aircraft generally already have four decals on the fuselage (NationName, InsigniaFuseL, InsigniaFuseR, SQName), there is no room for an additonal decal for the aircraft carrier.

 

So how was I able to do this?

img00532.jpg

 

Quite simply, I took the USN decals.ini files and changed the NationName decal to level 1, then created a series of decals each pertaining to the squadron. In this case, I named the files Navy.tga and Navyxxx.tga where xxx is the entry number in squadronlist.ini.

 

MeshName=fuselage_rear
DecalLevel=1
DecalFacing=RIGHT
FilenameFormat=A6SP1979\NAVY
Position=-5.92,0.55
Scale=1.1
DecalMaxLOD=2

 

This can be done for any USN aircraft; the supercarriers have been done. All you need to do to make this work for another squadron is find the appropriate TGA and rename it to the number of the squadron in SquadronList.ini.

 

There is one potential downside to this workaround: since it is a workaround, this only works for USN squadrons. If you select a USN aircraft with this tweak and select a different nation, you will still get "NAVY" on the fuselage. There are two ways to address this:

  • Since most USN aircraft are also flown by the USMC, just put the USMC aircraft entry first in the aircraft.ini file. Then when you select a different nation, you can still use the level 0 NationName in the USMC decals.ini.
  • This can work for absolutely everybody so long as every entry in the squadronlist.ini has a level 1 decal. In other words, for non-USN squadrons you would need to duplicate the corresponding NationName decal as a level 1. As you can imagine, this could get unwieldy rather quickly, especially if you want to allow for different carriers over different periods of time (e.g. the picture above is 1979; for 1976 VA-52 was on the Coral Sea).

I realize that this isn't rocket science, but I figured it was worth bringing up as a brainstorming/discussion point.

Edited by HomeFries

Share this post


Link to post
Share on other sites

yours is an interesting idea at the moment but i think to easily affected by future patches. the only thing i can think of is that it would no longer be a part of the nationname grouping but rather purely tied in to the appropriate skin (NAVYxxx for USNGrey, USMCxxx for USMCGrey etc). no reason that shouldnt work, have it going on one of my skins with the insignia(though named star) to make a couple of squadrons insignia smaller as IRL.

Share this post


Link to post
Share on other sites

You don't need to tie to the skin; you could have a global entry (though it makes sense to tie it to a timeframe). If you take a look at my example above, you'll see that the files are called NAVYxxx.tga, and are located in Decals\A6SP1979. This is only because it is for the superpack; this could just as easily read Nationxxx.tga and be located in Decals\1979. You can also add USMC et al to the same naming convention since it is level 1; you don't have to worry about overlap.

 

For my experiment, I actually created entries for the USMC squadrons by just duplicating NationName004.tga ("MARINES") to the appropriate NAVYxxx.tga entries. This could actually be useful for USMC squadrons that deployed with carrier air wings; they would need a separate skin anyway to allow for USN modexes, so the default USMC skins with the 2 digit numbers could still use NationName.

 

EDIT: As far as patches go, they will be affected only if the decals.ini file is patched. With the exception of the F-14, this sort of patching appears to have stabilized.

Edited by HomeFries

Share this post


Link to post
Share on other sites

looks good for A-6 and prob Hornet as i think they had most of their carrier names near the service name. Phantoms and i believe Tomcats are a bit more problematic as they can be all over the airframe. i've got Forrestal on the tail, on the spine, back by the NAVY etc. Toms had the same variations esp earlier on. so for it to work it would have to be one huge decal and alot of testing to verify location on skin. that or place it above the NAVY anyhow and suffer the wrath of the rivetcounters........

Share this post


Link to post
Share on other sites

Wait, does the 4 decals limit still apply ? I thought it went away some time ago...

Share this post


Link to post
Share on other sites

Wait, does the 4 decals limit still apply ?

 

I assumed so that why I did this with my KC-130's.

 

Dels

Share this post


Link to post
Share on other sites

looks good for A-6 and prob Hornet as i think they had most of their carrier names near the service name. Phantoms and i believe Tomcats are a bit more problematic as they can be all over the airframe. i've got Forrestal on the tail, on the spine, back by the NAVY etc. Toms had the same variations esp earlier on. so for it to work it would have to be one huge decal and alot of testing to verify location on skin. that or place it above the NAVY anyhow and suffer the wrath of the rivetcounters........

Can't suffer the wrath of the rivetcounters! That's a good point in that you are obviously limited to the immediate area of the decal; huge decals wouldn't be worth the payoff IMHO.

 

Of course, if the CV/CVW names are all over the place, then you may not have to sweat the 4 decal limit. I started this because there are already 4 decals on the rear fuselage of the A-6/EA-6B. If it exists on another mesh, then we might be in business with the CV/CVW alone as a level 1, and without having to mess with NationName.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

  • Similar Content

    • By Menrva


      View File Operation Desert Storm: 30th Anniversary Edition
      Welcome To Duty
      Built with the extraordinary expertise and dedication of modders from CombatACE.com, Operation Desert Storm – 30th Anniversary Edition promises to be the most complete total conversion ever made for Strike Fighters 2 by ThirdWire.
      Fly with more than 50 aircraft ranging from Cold War relics to the most advanced platforms. Gain air superiority in the mighty F-15C Eagle or challenge the Coalition with the agile Fulcrum. Support troops with the A-10A Thunderbolt II, bomb strategic targets with the stealthy F-117A Nighthawk, lead airfield denial operations in the iconic Tornado.
      Enjoy a beautifully rendered scenario on a scaled and accurate terrain. Fly over the lakes and rivers of Mesopotamia, the oil-rich fields of Kuwait, the mountains of Iran and Turkey. Take-off from aircraft carriers stationed in the Persian Gulf to watch over Kuwaiti oil rigs. Perform landings and patrols in more than 90 airports and air bases in the Middle East.
      Take part in different campaigns including the Iraqi blitzkrieg on Kuwait and the US-led liberation of the Kuwaiti Emirate. Discover how the Iraqi Army was one of the biggest in the world, through the eyes of American, British, Canadian, French, Italian and Arab pilots. Test your skills and abilities flying for the Iraqi Air Force during all stages of the conflict.
      Thirty years after, Operation Desert Storm still remains the largest air operation of modern warfare to date. Modders and flight sim enthusiasts at CombatACE teamed up to bring you a unique product in the lite flight sim world. Exquisitely detailed aircraft and paint schemes are delivered in a well-researched and thorough order of battle.
      The ODS 30th AE Development team would like to thank CombatACE.com, its admins, moderators and contributors.
      We are sure you will enjoy and appreciate this high-quality freeware product. From the aviation enthusiasts, to the aviation enthusiasts... and for the pilots of tomorrow.
       
      Minimum Requirements
      Required products from ThirdWire:
      Strike Fighters 2, July 2013 patch Strike Fighters 2: Israel, July 2013 patch Strike Fighters 2: North Atlantic, July 2013 patch Full support for:
      Mission Editor DLC Campaign Customizer DLC System specs:
      OS: Windows 7 x86 Processor: Dual Core 2.7 GHz Memory: 4.0 GB RAM Hard Drive: 17.0 GB Free Space Video Card: 1024 MB DirectX 10  
      Sneak Peek
       
      Disclaimer
      CombatACE.com shall at all times retain ownership of the Software as originally downloaded by you and all subsequent downloads of the Software by you. The Software (and the copyright, and other intellectual property rights of whatever nature in the Software, including any modifications made thereto) are and shall remain the property of CombatACE.com and of the respective developers/modders.
      In no event, unless required by applicable law or agreed to in writing, shall CombatACE.com, or any person be liable for any loss, expense or damage, of any type or nature arising out of the use of, or inability to use this installer or program, including, but not limited to, claims, suits or causes of action involving alleged infringement of copyrights, patents, trademarks, trade secrets, or unfair competition.
      The Operation Desert Storm: 30th Anniversary Edition modification does NOT comply with CombatACE's Freeware Licensing. Various contents of this modification are exclusive, as such you are NOT allowed to share, redistribute and/or make use of the mod and/or its contents for other purposes, without the consent of the mod's developers. Contents of the modification are the copyright of their respective authors.
       
      Notes about the installer
      Beware, the mod is available only in the ISO format. You can either mount it on a virtual drive, burn it on a DVD like in the good old days, or unzip it with 7-Zip or equivalent software.
      The installer will automatically detect your installation of the required Strike Fighters 2 games by reading through the registry keys. Game folders that are copied from or manually moved from where they were originally installed are not supported. You need all three aforementioned Strike Fighters 2 games and they must be installed with ThirdWire's original installers, not manually copied from other sources nor moved elsewhere after installation to other folders or drives. If you do not meet any of these requirements, installation cannot proceed and you are on your own. If you install all required games properly, the installation of the mod will proceed correctly as intended. The installer then lets you choose where to install the mod folder; you can even install the mod on a different drive or partition than the one where Strike Fighters 2 is installed. No further user input nor manual edits after installation are ever required; the installer takes care of creating all proper links to your desired path for the mod folder. After installation is over, simply run the mod by using the created Desktop and/or Start Menu links.
      If you have a previous version of the mod installed, please use the uninstaller to remove it completely. Clean installation is mandatory. You might want to make a backup of the Controls folder, so that you can easily restore your controller settings afterwards.
       
      Suggestions on common issues
      Make sure that you are using your dedicated GPU. By default, Strike Fighters 2 usually selects the integrated GPU you may have on your CPU, which is much weaker in terms of VRAM. In case you have frequent crashes or black/missing textures, I highly suggest you download and install the DXVK graphics wrapper (x86 DLLs) into your Strike Fighters 2 game folder: https://github.com/doitsujin/dxvk. You need a Vulkan-compatible GPU. The wrapper can greatly improve the experience with the mod. With DXVK I can play the mod on a mere Intel UHD 710, whereas without it the mod would always crash to desktop. Go to Sound and set Sound Channels to 32. We got reports that 16 is not enough and will cause crashes on some systems, due to the higher quality sounds included within the mod. The mod is pretty heavy for the game engine despite huge optimizations. Strike Fighters 2's engine is 32bit only and apparently does not manage VRAM properly; consecutive campaign missions might show black/missing textures on objects or cause crashes to desktop because the game does not release the occupied VRAM from the previous mission you played, thus the more missions are loaded consecutively, the more easily you may run out of memory. Set Ground Objects to Medium or Low, Horizon Distance to Near, and Shadows to Medium or Low. These are the most troubling settings. Avoid Unlimited settings as much as possible. If the mod used to work and suddenly crashes to desktop, updating or reinstalling video drivers should help. Make sure that DirectX June 2010 Redistributables are also installed, they are included inside the ISO disk image of the mod. Inside the mod folder, you'll find some extra text files. "(Coalition Order of Battle)" should be of your interest; the mod's terrain covers the entirety of Iraq, at the cost of not having all of Saudi Arabia; this means that a number of important units are based on airbases that are beyond the in-game playable area. With those units you always spawn near the target area, you'll never get to start from a runway nor to land on the assigned runway beyond the invisible wall. You have an entire list of the affected units in the aforementioned text file. By pressing ALT+N, the plane returns to base automatically. The mod is fully compatible with the Campaign Customizer and Mission Editor DLCs by ThirdWire. The Campaign Customizer might be an alternative way to experience those off map units I mentioned previously, since it assigns you to a random airbase of the in-game flyable area. Escort missions are often broken, this is not an issue of the mod, but a bug of the stock game; sometimes the AI flight you escort does not engage its target and keeps flying in a straight line instead of following waypoints, thus the trigger for mission success will never happen. Abandon the mission or retry it if the issue happens, sometimes it works. Pray for ThirdWire AKA Tsuyoshi Kawahito to work on a 64bit version of Strike Fighters 2, maybe even with support for DirectX 12. With that done, any out of memory issues should become an old memory. Submitter Menrva Submitted 01/16/2021 Category User Made Campaigns  
    • By Spinners


      View File [Fictional] McDonnell Douglas Phantom F-4L (USMC)
      McDonnell Douglas F-4L (USMC/USN) Phantom for STRIKE FIGHTERS 2
      This is a simple mod of the stock Third Wire F-4M_75 to give a fictional USMC Phantom F-4L with markings for VMFA-333 'Shamrocks'. Also included is a USN VF-111 scheme that generally uses stock decals but is included here to give a blank F-4L tail for you to do other squadrons by using stock decals. It goes without saying that you will need to have the F-4M_75 from SF2:Europe.

      BACKSTORY
      With all the considerable design effort being put into the marriage of the Phantom airframe and the Rolls-Royce Spey turbofan engine McDonnell Douglas thought it might be a good idea to propose a version to the US Navy to allow the Phantom to operate from the smaller carriers that were limited to F-8E Crusaders. In June 1966 the designation F-4L was given to the proposed Spey-powered Phantom and in October 1966 an initial order for 130 F-4L's (USN/USMC) was made, followed by an unexpected export order of 30 F-4L's for the Royal Australian Navy.
      Deliveries to the US Navy commenced in February 1969 with VF-24 becoming the first operational squadron followed by VMFA-333. By this time the wisdom of operating such a relatively large aircraft on the older, smaller carriers was being questioned and most F-4L's served aboard the larger carriers or with land-based units. 
      When the decision was made not to re-equip the USMC 'fighter-attack' Phantom squadrons with the hugely expensive Grumman F-14A Tomcat, McDonnell Douglas pushed hard for low-rate production of the F-4L to continue specifically for USMC use and they were eventually successful meaning that production continued until 1976 with an eventual total of 306 F-4L's being built. Apart from Australia, F-4L's also served with the Royal Air Force where 15 ex-USN F-4L's were sold to the UK Government to allow the formation of an additional home-based Phantom squadron to release a squadron for the defence of the Falkand Isles. 

      INSTRUCTIONS
      1. From the AIRCRAFT folder drag and drop the F-4L_75 folder into your Aircraft folder.
      2. From the DECALS folder drag and drop the F-4L_75 folder into your Decals folder.
      That's it!

      CREDITS
      As always, thanks to Third Wire for a great little game/sim.
      And, finally, thanks to everyone in the wider Third Wire community.
      Regards 
      Spinners
      Version 2 - February 17th, 2024.
       
      Submitter Spinners Submitted 01/24/2010 Category What If Hangar  
    • By Spinners
      McDonnell Douglas F-4L (USMC/USN) Phantom for STRIKE FIGHTERS 2
      This is a simple mod of the stock Third Wire F-4M_75 to give a fictional USMC Phantom F-4L with markings for VMFA-333 'Shamrocks'. Also included is a USN VF-111 scheme that generally uses stock decals but is included here to give a blank F-4L tail for you to do other squadrons by using stock decals. It goes without saying that you will need to have the F-4M_75 from SF2:Europe.

      BACKSTORY
      With all the considerable design effort being put into the marriage of the Phantom airframe and the Rolls-Royce Spey turbofan engine McDonnell Douglas thought it might be a good idea to propose a version to the US Navy to allow the Phantom to operate from the smaller carriers that were limited to F-8E Crusaders. In June 1966 the designation F-4L was given to the proposed Spey-powered Phantom and in October 1966 an initial order for 130 F-4L's (USN/USMC) was made, followed by an unexpected export order of 30 F-4L's for the Royal Australian Navy.
      Deliveries to the US Navy commenced in February 1969 with VF-24 becoming the first operational squadron followed by VMFA-333. By this time the wisdom of operating such a relatively large aircraft on the older, smaller carriers was being questioned and most F-4L's served aboard the larger carriers or with land-based units. 
      When the decision was made not to re-equip the USMC 'fighter-attack' Phantom squadrons with the hugely expensive Grumman F-14A Tomcat, McDonnell Douglas pushed hard for low-rate production of the F-4L to continue specifically for USMC use and they were eventually successful meaning that production continued until 1976 with an eventual total of 306 F-4L's being built. Apart from Australia, F-4L's also served with the Royal Air Force where 15 ex-USN F-4L's were sold to the UK Government to allow the formation of an additional home-based Phantom squadron to release a squadron for the defence of the Falkand Isles. 

      INSTRUCTIONS
      1. From the AIRCRAFT folder drag and drop the F-4L_75 folder into your Aircraft folder.
      2. From the DECALS folder drag and drop the F-4L_75 folder into your Decals folder.
      That's it!

      CREDITS
      As always, thanks to Third Wire for a great little game/sim.
      And, finally, thanks to everyone in the wider Third Wire community.
      Regards 
      Spinners
      Version 2 - February 17th, 2024.
       
    • By Menrva
      Welcome To Duty
      Built with the extraordinary expertise and dedication of modders from CombatACE.com, Operation Desert Storm – 30th Anniversary Edition promises to be the most complete total conversion ever made for Strike Fighters 2 by ThirdWire.
      Fly with more than 50 aircraft ranging from Cold War relics to the most advanced platforms. Gain air superiority in the mighty F-15C Eagle or challenge the Coalition with the agile Fulcrum. Support troops with the A-10A Thunderbolt II, bomb strategic targets with the stealthy F-117A Nighthawk, lead airfield denial operations in the iconic Tornado.
      Enjoy a beautifully rendered scenario on a scaled and accurate terrain. Fly over the lakes and rivers of Mesopotamia, the oil-rich fields of Kuwait, the mountains of Iran and Turkey. Take-off from aircraft carriers stationed in the Persian Gulf to watch over Kuwaiti oil rigs. Perform landings and patrols in more than 90 airports and air bases in the Middle East.
      Take part in different campaigns including the Iraqi blitzkrieg on Kuwait and the US-led liberation of the Kuwaiti Emirate. Discover how the Iraqi Army was one of the biggest in the world, through the eyes of American, British, Canadian, French, Italian and Arab pilots. Test your skills and abilities flying for the Iraqi Air Force during all stages of the conflict.
      Thirty years after, Operation Desert Storm still remains the largest air operation of modern warfare to date. Modders and flight sim enthusiasts at CombatACE teamed up to bring you a unique product in the lite flight sim world. Exquisitely detailed aircraft and paint schemes are delivered in a well-researched and thorough order of battle.
      The ODS 30th AE Development team would like to thank CombatACE.com, its admins, moderators and contributors.
      We are sure you will enjoy and appreciate this high-quality freeware product. From the aviation enthusiasts, to the aviation enthusiasts... and for the pilots of tomorrow.
       
      Minimum Requirements
      Required products from ThirdWire:
      Strike Fighters 2, July 2013 patch Strike Fighters 2: Israel, July 2013 patch Strike Fighters 2: North Atlantic, July 2013 patch Full support for:
      Mission Editor DLC Campaign Customizer DLC System specs:
      OS: Windows 7 x86 Processor: Dual Core 2.7 GHz Memory: 4.0 GB RAM Hard Drive: 17.0 GB Free Space Video Card: 1024 MB DirectX 10  
      Sneak Peek
       
      Disclaimer
      CombatACE.com shall at all times retain ownership of the Software as originally downloaded by you and all subsequent downloads of the Software by you. The Software (and the copyright, and other intellectual property rights of whatever nature in the Software, including any modifications made thereto) are and shall remain the property of CombatACE.com and of the respective developers/modders.
      In no event, unless required by applicable law or agreed to in writing, shall CombatACE.com, or any person be liable for any loss, expense or damage, of any type or nature arising out of the use of, or inability to use this installer or program, including, but not limited to, claims, suits or causes of action involving alleged infringement of copyrights, patents, trademarks, trade secrets, or unfair competition.
      The Operation Desert Storm: 30th Anniversary Edition modification does NOT comply with CombatACE's Freeware Licensing. Various contents of this modification are exclusive, as such you are NOT allowed to share, redistribute and/or make use of the mod and/or its contents for other purposes, without the consent of the mod's developers. Contents of the modification are the copyright of their respective authors.
       
      Notes about the installer
      Beware, the mod is available only in the ISO format. You can either mount it on a virtual drive, burn it on a DVD like in the good old days, or unzip it with 7-Zip or equivalent software.
      The installer will automatically detect your installation of the required Strike Fighters 2 games by reading through the registry keys. Game folders that are copied from or manually moved from where they were originally installed are not supported. You need all three aforementioned Strike Fighters 2 games and they must be installed with ThirdWire's original installers, not manually copied from other sources nor moved elsewhere after installation to other folders or drives. If you do not meet any of these requirements, installation cannot proceed and you are on your own. If you install all required games properly, the installation of the mod will proceed correctly as intended. The installer then lets you choose where to install the mod folder; you can even install the mod on a different drive or partition than the one where Strike Fighters 2 is installed. No further user input nor manual edits after installation are ever required; the installer takes care of creating all proper links to your desired path for the mod folder. After installation is over, simply run the mod by using the created Desktop and/or Start Menu links.
      If you have a previous version of the mod installed, please use the uninstaller to remove it completely. Clean installation is mandatory. You might want to make a backup of the Controls folder, so that you can easily restore your controller settings afterwards.
       
      Suggestions on common issues
      Make sure that you are using your dedicated GPU. By default, Strike Fighters 2 usually selects the integrated GPU you may have on your CPU, which is much weaker in terms of VRAM. In case you have frequent crashes or black/missing textures, I highly suggest you download and install the DXVK graphics wrapper (x86 DLLs) into your Strike Fighters 2 game folder: https://github.com/doitsujin/dxvk. You need a Vulkan-compatible GPU. The wrapper can greatly improve the experience with the mod. With DXVK I can play the mod on a mere Intel UHD 710, whereas without it the mod would always crash to desktop. Go to Sound and set Sound Channels to 32. We got reports that 16 is not enough and will cause crashes on some systems, due to the higher quality sounds included within the mod. The mod is pretty heavy for the game engine despite huge optimizations. Strike Fighters 2's engine is 32bit only and apparently does not manage VRAM properly; consecutive campaign missions might show black/missing textures on objects or cause crashes to desktop because the game does not release the occupied VRAM from the previous mission you played, thus the more missions are loaded consecutively, the more easily you may run out of memory. Set Ground Objects to Medium or Low, Horizon Distance to Near, and Shadows to Medium or Low. These are the most troubling settings. Avoid Unlimited settings as much as possible. If the mod used to work and suddenly crashes to desktop, updating or reinstalling video drivers should help. Make sure that DirectX June 2010 Redistributables are also installed, they are included inside the ISO disk image of the mod. Inside the mod folder, you'll find some extra text files. "(Coalition Order of Battle)" should be of your interest; the mod's terrain covers the entirety of Iraq, at the cost of not having all of Saudi Arabia; this means that a number of important units are based on airbases that are beyond the in-game playable area. With those units you always spawn near the target area, you'll never get to start from a runway nor to land on the assigned runway beyond the invisible wall. You have an entire list of the affected units in the aforementioned text file. By pressing ALT+N, the plane returns to base automatically. The mod is fully compatible with the Campaign Customizer and Mission Editor DLCs by ThirdWire. The Campaign Customizer might be an alternative way to experience those off map units I mentioned previously, since it assigns you to a random airbase of the in-game flyable area. Escort missions are often broken, this is not an issue of the mod, but a bug of the stock game; sometimes the AI flight you escort does not engage its target and keeps flying in a straight line instead of following waypoints, thus the trigger for mission success will never happen. Abandon the mission or retry it if the issue happens, sometimes it works. Pray for ThirdWire AKA Tsuyoshi Kawahito to work on a 64bit version of Strike Fighters 2, maybe even with support for DirectX 12. With that done, any out of memory issues should become an old memory.
    • By Menrva
      Fans of ThirdWire's Strike Fighters, I'm glad to announce the Christmas release of Operation Desert Storm: 30th Anniversary Edition. This huge and quality total conversion has seen two Early Access releases this year, one back in January 16th and the other on August 2nd.
      Once available to site subscribers only, now we offer an updated version of the package to all CombatACE users as our Christmas gift, regardless of a subscription.
      There have been usual bug fixes and important improvements since the last release. Make sure to read the change log and all the details in the mod's download page once it's approved.
      You are not required to own a subscription, but keep in mind that the mod is distributed in a hefty, yet highly compressed 3GB installer which contains 15GB of contents. You will need a stable internet connection in order to download it. The mod cannot and will not be offered in a different form. A subscription grants you unlimited number of downloads for its duration and will support the site's hosting costs.
      The Operation Desert Storm: 30th Anniversary Edition modification does NOT comply with CombatACE's Freeware Licensing. Various contents of this modification are exclusive, as such you are NOT allowed to share, redistribute and/or make use of the mod and/or its contents for other purposes, without the consent of the mod's developers. Contents of the modification are the copyright of their respective authors.
      My personal thanks to the ODS 30AE Development Team, you guys keep inspiring me with your great works and continuous support! And special thanks to @Erik and to all admins and moderators of this great place that is CombatACE.
      Happy Holidays, pilots of the virtual skies! 

×

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