HomeFries

All USN squadrons are done; 5 USMC squadrons to go. Then it will be the A-7 tails for the squadons that transitioned (e.g. VA-203). On a tangent, I think that adding landing lights to the flyable aircraft would be a great addition to the RP, but this is definitely not a "quick" fix. One airframe isn't bad, but all of them (or even just the flyable ones) will be a monster. Any volunteers to take a few aircraft? Honestly, I would be willing to do the data entries if I were just provided with the proper coordinates.

Screenshot of the A-4L with two of the new reserve squadrons.

No problem; 591 and 716 sounds right. Aussies are good.

No problem, DA. Good catch on the ANG squadrons; I didn't even connect the dots. All things being equal, I would like to leave the USN/USMC squadrons from 550 where they are, as each A-6/EA-6B unit has 15 decals at minimum (which will multiply with v2.0 as I go more timeframe specific). Anything I don't have to change there is a good thing. VAQ-33 is one of those with "only" 15 decals, so that would be comparatively painless, but I won't complain if we leave it exactly where it is. I actually thought the same thing you did when I put -33 in; it's not operational, but it flew a number of airframes so there exists the possibility of making multiple sets of decals for different aircraft. The A-4L squadrons can go anywhere. I just know that we had discussed 716-728 previously. I haven't done a full set, so there's no renumbering yet, so put them anywhere you like them. Just let me know the range and set it in stone so that I can make the decals. Here are the squadrons from my original post (to be renumbered as required): [squadron701] Name=VA203 DisplayName=VA-203 Blue Dolphins Nation=USN [squadron702] Name=VA204 DisplayName=VA-204 River Rattlers Nation=USN [squadron703] Name=VA209 DisplayName=VA-209 Air Barons Nation=USN [squadron704] Name=VA303 DisplayName=VA-303 Golden Hawks Nation=USN [squadron705] Name=VA305 DisplayName=VA-305 Lobos Nation=USN [squadron706] Name=VMA124 DisplayName=VMA-124 Bantam Bombers Nation=USMC [squadron707] Name=VMA131 DisplayName=VMA-131 Diamondbacks Nation=USMC [squadron708] Name=VMA133 DisplayName=VMA-133 Dragons Nation=USMC [squadron709] Name=VMA134 DisplayName=VMA-134 Skyhawks Nation=USMC [squadron710] Name=VMA142 DisplayName=VMA-142 Flying Gators Nation=USMC [squadron711] Name=VMA322 DisplayName=VMA-322 Fighting Gamecocks Nation=USMC [squadron712] Name=VMA543 DisplayName=VMA-543 Knight Hawks Nation=USMC and the screenshot. When you say Kiwi squadrons, please confirm that you're only moving RNZAF and not RAAF 1 and 6. I know that 1 and 6 are separated, but I have already released a skinpack that uses those addresses. We should keep them where they are.

Ok, DA, what's going on? Comparing the two files, the 128TFS (Squadron612) has been removed, as has 170TFS (613) and 194TFS (616). We also have 1RAAF at 716, which as I now recall makes sense because I wanted to add 1RAAF and 6RAAF. However, per your own post 716-728 were supposed to be for the USN/USMC reserve A-4 squadrons for the A-4L DLC. They would still fit as 717-728, but it sounds like you want to move them. That's fine; I haven't committed to anything yet with the A-4 squadrons, but I want something in at least quick-setting mud before I get moving on the decals. Finally, what are your intentions regarding VAQ-33? Please let me know what you're going to do before you do it (including what squadrons you want to move around) and I'll let you know if I can support it (the next A-6 superpack has a bunch of different decals by time period, so a major number revision is out of the question).

I'd like to have VAQ-33 in there (I already made decals), but you can renum if need be. As long as I only need to change one set of decals, the pain isn't bad; if you need the space, you can always move it forward to 550. EDIT: I just realized that VAQ-33 is located between other A-6 squadrons; moving that to organize groups may cause a cascade of at least three squadrons to be renumbered. I can do it, but please let me know exactly what you move to where so that I can update my A-6 decals. As far as the reserve A-4 squadrons, you mentioned previously that they were banks 716-728, but I only have 12 squadrons (which takes me up to 727). Please confirm the number range before I start making decals. Finally, I'm finally getting back into the saddle with this. After my vacation, I've been busy with end of fiscal year things, as well as the beginning of the new one. Hopefully things will begin to calm down.

Concur, DA. I for one would love to add a boatload of L1 decals, but that may prove to be time consuming. This is one of those things that shouldn't necessarily hold up a release (unless you can burn through a ton of them), but can be released either as incremental patches in the file thread, then integrated with newer releases. I'll still commit to the A-4 reserve units for decals, though I can't do much more than that right now. As for the skins, as long as we have a generic skin like desert or silver, we can always copy it and make it USAF et al in the Textureset.ini. As long as we're not creating new skins, we're still within the intended charter of the RP.

@Spinners, Great work! I'm working on one myself. It really only needs some squadron logos to finish up.

Tangentially on topic, but I add the following lines to the [CockpitSeat001] section of my cockpit.ini files: MinMovementX=-0.16 MaxMovementX=0.18 MinMovementZ=-0.08 MaxMovementZ=0.10 This allows lateral movement in the X/Z (really X/Y) axes with TrackIR. Is there a way to do this in the viewlist so that I don't have to do this for every cockpit I have?

Guys, I'll be away for a week, so don't be alarmed if there are no regular updates for the immediate future. I'll be back with a vengeance at the end of September.

http://www.checksix-fr.com/bibliotheque/index.php?page=detail&ID=5513 2/5 contains the speech pack.

I have a static loop I could insert into the files. I was actually working on a Hawkeye voice mod before SZ beat me to the punch (albeit with better quality).

You're right, and I was lazy. Centurion, the offer extends to you as well.

File Name: RAAF A-6 Intruder Pack File Submitter: HomeFries File Submitted: 10 September 2012 File Category: The Combat Ace What If Hangar This mod adds the Royal Australian Air Force (RAAF) as a user of the A-6 Intruder. It has been tested with Strike Fighters 2 Full 5+2 merged install with the A-6 Superpack 1.51 installed. It should work with less than a full 5+2, but requires the following SF2 versions to take advantage of the respective components: SF2V for the A-6A SF2NA for the A-6E and A-6E_79 The A-6 Superpack 1.51 or later is recommended, but not required in order to use the A-6A, A-6E, and A-6E_79. The A-6 Superpack 1.51 is required in order to use the A-6E_90 Systems and Weapons Improvement Program (SWIP) variant. The included SQUADRONLIST.INI is a part of the file that will be included in the Combat Ace Realism Pack. As a result, it is compatible with DaddyAirplanes' F-4 Post Vietnam skin pack. At the time of this writing, the Combat Ace Realism Pack has not been released. If you have downloaded this pack after installing the Combat Ace Realism Pack, then be sure not to copy over the included SQUADRONLIST.INI, as a more updated one will be included in the Realism Pack. In order to take advantage of the full features of the RAAF Intruder Pack, this readme is intended to be used in conjunction with the Readme for the A-6 Superpack 1.51. Thorough reading of this file and strict adherence to the instructions is highly recommended. As always before making any changes to your SF2 install, back up early and back up often! Introduction As early as 1954, the Australian government first publicly discussed the need for replacing the Canberra. The Canberra lacked radar and electronic countermeasures (ECM), and the RAAF believed that it needed a new strategic bomber to fulfill the nation's obligations to the Commonwealth Strategic Reserve in Malaysia, ANZUS, and SEATO. A requirement mandated an all-weather attack aircraft capable of delivering a variety of bombs and missiles. Air Marshal Valston Hancock, Chief of the Air Staff, stated in April 1960 that Australia needed a replacement for the Canberra, and in 1962 Indonesia's increasingly aggressive statements regarding Malaysia soon caused Australia to seriously consider Hancock’s statement. The Sydney Morning Herald reported in October 1962 that the Indonesian Air Force's Soviet Tupolev Tu-16 bombers could reach Sydney or any other Australian city with a light bomb load, while the Canberras could not fly in all weather and had insufficient range to reach Djakarta. However, available bombers were unsuitable for the RAAF. The American Boeing B-52 Stratofortress and Convair B-58 Hustler, for example, were too large for existing Australian runways. More suitable aircraft such as the British BAC TSR-2 and the American F-111 would soon be available. Candidates for replacing the Canberra included the French Dassault Mirage IV, the TSR-2, and the U.S. North American A-5 Vigilante, Grumman A-6 Intruder, McDonnell Douglas F-4 Phantom II and the General Dynamics F-111 Aardvark. Decision and Alternate History When the RAAF was evaluating the replacement aircraft for the Canberra, they eventually settled on the F-111. The F-111 met the RAAF endurance and all weather attack requirements, as well as being supersonic and having a respectable self-defense capability. The government determined that it did not need to go ahead with an immediate replacement for the Canberra and opted for the F-111 as a long-term solution, leading to the October 1963 announcement that it was ordering 24 F-111s. The development and production lifecycle for the F-111 was complex, lengthy, and troubled on occasion. Additional requests by the Australian government to modify the existing F-111A airframe to what would become the F-111C only lengthened the acquisition process. While the announcement to purchase the F-111 was made in 1963, the first F-111C was not delivered until 1968 . In the interim, the RAAF was using the F-4 Phantom II as a stopgap measure. What if the RAAF decided to forego the troubled (at the time) F-111 and augment its force of F-4 Phantoms with the A-6 Intruder as its all-weather, deep strike platform? This pack is strictly a "What If" set of skins and loadouts that explores what might have happened if Australia purchased the A-6 Intruder from the United States. This pack includes skins for the A-6A, A-6E, A-6E_79 (TRAM), and A-6E_90 (SWIP) in the Southeast Asia (SEA) camouflage pattern, as well as other variants based on the RAAF camouflage schemes of the time. Given that the A-6 Intruder is meant to replace the F-111C Aardvark, this pack features the squadrons, skins, and serial numbers of actual F-111 airframes (though serial numbers of aircraft involved in fatal mishaps have been omitted out of respect for the fallen). Second squadron is represented, as it flew the Canberra in the Vietnam War, and First and Sixth squadrons have been added to SQUADRONLIST.INI as the actual squadrons that flew the F-111 (and therefore the A-6). A-6 specific squadron logos have also been added to the RAAF squadrons included in the Mirage IIIO DLC, though this was done for completeness rather than “alternate historical accuracy.” Limitations This mod enhances default aircraft. If you don't have the default A-6 LODs, then this mod is of limited value to you. Additionally, this pack is unfortunately not flyable without further modification. You will need to provide your own cockpit in order to enable player use of the A-6. Two notable options are extracting the A-6 cockpit from Wings over Vietnam, or by purchasing RAZBAM's excellent A-6 pack for Strike Fighters (recommended). Likewise, plenty of existing SF1 A-6 mods include cockpits that are compatible with this pack. Regardless of which selection you prefer, any cockpit you use for the A-6 Superpack will be compatible with the RAAF A-6 Intruder Pack as well. Installation The RAAF A-6 Intruder Pack is divided into three components: the Primary Component (RAAF A-6 Intruder Skins), a folder for widescreen users that replaces the existing 1024x768 aircraft screens with 1440x900 images, and Section 2 of the Readme file which provides instructions for optional and recommended adjustments to existing INI files. Please see the readme file for further details. Click here to download this file

Paulo, Feel free to use my RAAF A-6. Since we're both doing What-If, this might work.

I know the Reloaded mod uses the speech pack for SF1 by Renegade and Retrograde. Additionally, Skatezilla and Spectre have released improved Hawkeye comms, and Romflyer posted a link to his own approach/departure controller speech pack.

My prayers for the Mrs.

Look on CheckSix; it's part of a WoV mod. Some of the links are broken, but at least the part with the speech pack isn't. I'm looking at putting the VPAF speech pack in the CA Realism Pack. Since the guy who did the Charlie mod isn't part of the CA licensing agreement, I need to get the guy's contact info and ask for permission.

NATIONS.INI includes Army. I'll upload it when I get a chance; I've already incorporated the speech packs I have as well (German, British, VPAF, Russian). What we can do with the red is as soon as we get level 1 decals, we can pull those particular squadrons into the sub-1000 range. I have them starting at 1000 because they are UnitNames in the campaigns, which means TK didn't make level 1 decals for them in the first place. If we have unit-specific skins, we can leave them where they are and just reference the squadron in the TextureSet.ini. We should only need to pull them sub-1000 if level 1 decals are made, at which point it won't matter anyway since the only thing that use the entry numbers are level 1 decals.

Thanks, Piecemeal, That one's on my list, but since it's historical I may need to tweak the camo pattern. That's the tough part: getting the lines to match up.

Just found the Canadian/Italian medals and French ranks in NF5 last night; will be pulling those into the RP as well (along with my USN medals). I'll tweak the commendation write-ups so that they're not theater specific. NATIONS.INI has also been updated accordingly.