Swordsman422

Yeah, whoops. My bad.

I think I'll be content with Jul 2012 for a while longer. Doesn't sound like anything has been added that will change my experience for the better. Plus, right now I am 87 missions into a 100-mission Rolling Thunder campaign in the F-105. I am not keen on starting over.

What changes have been made to CampaignV1 and VietnamSEA. Have they been updated to NA campaign standards?

Blackjack and hookers? That sounds like a target rich environment!

But what about feeding the eels?

Hey, guys. I have searched the forum for the topic on how to solve this, but to no avail. I am certain I am not using the correct key words. Anyway, every time I start up my copy of SF2 (full merged install), the stock aircraft.ini files keep getting overwritten. I know this is happening because until the last patch was released I had the A-6A, A-6E, and A-6E_79 all flyable and the F-4B, F-4B_65 and F-4B_67 aircraft names modded in the .inis. However, once I got notification of the new patch, in order to keep any changes I have to set the aircraft.ini files if any stock planes I modify set to read only. I have not installed the May 2013 patch yet. This might make sense if the stock aircraft were absent from the mod folder, but they are not. The game just keeps dumping in new ones every time it starts up. The data, loadout, and other .ini files are unaffected, only the aircraft.ini with the object parameters and .lod and skin lists. This is just a minor annoyance as I have a workaround for it, but I really would like to make it stop. Thanks for any help.

Migbuster, your way worked perfectly. Thanks everyone for the assist!

Tried the new advice. Still nothing.

Thanks both. SW, I'll try it when I get home (and my new wife doesn't see fit to distract me). Wrench, I use a similar method for patching. Thank you all, gents.

ojcar, that is what I've been doing. Weird thing is I wasn't having this issue until I got notification that the new patch was available. Then it started doing it. Thanks, though. Your english reads just fine to me.

With the nose, check your photo. Even if the paint is the same, fiberglass weathers differently than metal. It isn't uncommon for me to use some of the same techniques I use in modeling for photoshopping skins, like preshading and post-shading especially around panel lines. Usually I do a "wash" (<25% opacity) layer of darker grays, either engine gray (fs16440) or euro 1 gray (fs36081) to get a grimy ashen look, or I use aircraft interior black (fs37031) for oily smears. And the smudge tool in photoshop is very useful. But remember, DO THIS ON A NEW LAYER, preferably between the base color and panel line layers if the template has these. Eliminate visibility to all layers except these two and create a new one just below the panel layer. Google these colors and download the color swatches to use in photoshop. Another piece of advise I have is be aware of what is under some of the panels. There may be a faint orange smear near the hydraulic input, and a blue-grey smudge at the lip of the aerial refueling door. Hope this helps. That skins is looking great!

Hey guys, I used to have a list of the squadron color codes used by the USN in the 1950s before the Vietnam squadron shuffle screwed everything up. Namely, I am looking for what colors went with what positions in the air wing. I know a few off hand already. 1xx is red, 2xx is yellow, 5xx is green. But does anyone have or know the full list? Thanks.

Awesome! Thanks guys! I have been trying to refind this information and could not. Xrearl, that is the exact page I had found so long ago and forgotten. Wrench, that sums it up nicely. Thanks for all the help!

I guess the jets were craned off in port?

If I recall correctly the pilot who did this, Tim Dorsey, got nominated for flag rank last year.

Hey, Dave, that is quite a find! What F-14 sheets do you have?

The external carriage will not really pose a problem on the occasions that it is needed. When this jet needs most to be stealthy is in the precision strike role and decapitation roles, which it CAN do vice the F-22 which really cannot. The F-117 carried just 2 bombs internally and did the job very well. When the F-35 is performing the same types of strikes, it will do just fine. Plus it has decent tote in the air-to-air arena without hanging externals. And when it does need to have things on the wings, it won't need to be a VLO platform. Doing CAS, you need to bring all the ords you can so as to tie up as few platforms as possible, and there isn't much hope of being VLO against the good ole eyeball. CAS is where you will be seeing the biggest threat from MANPADS, and I think in most cases this can be managed using stand-off weapons like LGBs and WCMDs. But it will take the guys on the ground popping the bastard with the tube on his shoulder if the F-35 (or any other aircraft) needs to get close and strafe.

As for more F-22s, their role is too limited in this budgetary environment. No self-designation for LGBs, No AGMs, Limited to 2000 Lbs (vs. F/A-18E/F 17,000 Lbs). Currently limited to below 10K feet due to gremlins in the life support system. There isn't a whole lot of room for new single role tactical aircraft and the F-22s reputation isn't good right now. Sad to say that I am certain someone with a microphone (no one here. We are all above that, and this is not sarcasm) will spin this accident into an uninformed criticism of the reality that has been two decades in the making. I am just very happy that the pilot is going to be okay. I hope that this was not his fault and that he can keep doing the job he loves to do and fought hard for.

Just proof that Tomcats aren't all I fly. Stock A-4Cs from VA-144 delivering some pain to Uncle Ho.