Piecemeal

I've had HUGE problems yesterday trying to reinstall my mods over the new patch. For some reason the game will not recognise the filepath I placed in the Options.INI. All my mods are on an external drive, the filepath was pointing towards it but I could only solve it by placing them back in the C: drive. Also having big problems with anti-ship and CAS missions. CAS has me flying to waypoint 5 but not a tank in sight. Anti-shipping missions consist of flying to an area over land where ships are said to be

I don't suppose anybody with experience in the Fleet Air Arm is willing to back up my claim over at ThirdWire? : http://bbs.thirdwire.com/phpBB3w/viewtopic.php?f=5&t=9035

Thanks for the feedback, guys. I've had the DLC already but I thought that the '75 model was incorrect in that sense since looking at that clip on "Sailor".

Cheers bud.

Death from above

Grrrrrrrrrrrrrrrr!!!!!!

Fantastic work Stary! Tell me again how can I increase the fade distance for the trees. I seem to have forgotten

From personal experience all I can give you is one piece of advice; Practice, Practice, Practice, Practice, Practice, Practice

A hidden bonus in the upcoming patch, maybe?

Getting to really like flying off the Tarawa

I had to look at the title twice - I thought it said "Shi'ite Fighter Pilots Don't Say"

Greased Lightnings

Bugs aside, the new SF2NA game engine that specifically supports carrier ops on other terrains is proving to be a real breakthrough. Very interesting indeed. Using the guidelines from PureBlue's thread in the knowledge base I've been able to add carrier ops to the stock desert terrain: Ironically, some weeks ago I added a friendly segoing oil field in the "Desert3" terrain, complete with third party oil rigs which I obtained from the SFP1 download section : As you can see in the above screenshot, there's part of the CV Battle Group passing closely by one of the rigs. Would any of our terrain gurus know whether a collision between ship and rig be avoided? There doesn't seem to be any collision mesh with Gepard's oil rig model. I suppose some would recommend moving the location of the oil field but I think that with a little editing these models could be set up as very tempting targets for Parani bombing raids. Thoughts, anyone?

Works like a dream in Single Missions. I've got SF2NA, my SF2 install's patched up to March 2012, I've made all the neccessary updates to the terrain INIs, I even created a WATER.BMP. As to whether it requires SF2NA to perform, beats the hell outa me.

Nah. I tried the terrain out with some updated stock campaign files that Shotgun uploaded. Worked out fine. It has to be either something I have put in or left out of the campaign INIs - OR it could be bug related. With regard to the latter we won't know that til the patch is released. It's really weird cos I can fly with an RAF or Mercenary squadron without a hitch. Jeeezus, I mean even if I choose a USAF squadron it crashes; and they're land based with no naval prompts whatsoever in the _DATA.ini!

Enjoy it bud.

[Deck] SystemType=FLIGHT_DECK FlightDeckHeight=20.10 FlightDeckLength=396.0 FlightDeckWidth=84.0 LandDeckAngle=-10.0 LandingAimPoint=-0.35,-57.95 CollisionMesh=CV-63_deck.LOD ParkingChance=100 <- - - - - - - - - - - - - - - - - - - - - raise this to 100 - it'll increase the odds of deck population ParkingMaxSpan=12.0 Parking[01].Heading=270 Parking[01].Offset=27.77,79.19 Parking[02].Heading=270 Parking[02].Offset=27.77,67.58 Parking[03].Heading=270 Parking[03].Offset=27.77,50.94 Parking[04].Heading=270 Parking[04].Offset=27.77,33.68 Parking[05].Heading=270 Parking[05].Offset=27.77,22.07 Parking[06].Heading=329 Parking[06].Offset=7.82,62.03 Parking[07].Heading=350 Parking[07].Offset=15.73,6.12 Parking[08].Heading=270 Parking[08].Offset=29.62,-47.45 Parking[09].Heading=270 Parking[09].Offset=29.62,-59.06

You should install ravenclaw's mini weapons pack which I find to be more realistic (performance-wise) than the stock ones: http://combatace.com...weapons-pack-1/ They also LOOK exactly like they're supposed to in real life as well!

Sure yeah, a whole lot of editing. That's why over the past few years I've basically selected the flyable squadrons I want to deploy in a campaign, delete all the others from the CAMPAIGN.INI file (example): //----------------------------------------------------------------------------- //---- USN Units [uSNUnit001] AircraftType=F-8E_66 Squadron=VF111 ForceID=1 UnitID=1 StartDate=01/03/1967 DescFile=Campaign3Start.txt StartText=Campaign3Start.txt [uSNUnit002] AircraftType=A-4B_65 Squadron=VA163 ForceID=1 UnitID=2 StartDate=01/03/1967 DescFile=Campaign3Start.txt StartText=Campaign3Start.txt [uSNUnit003] AircraftType=A-4B_65 Squadron=VA164 ForceID=1 UnitID=3 StartDate=01/03/1967 DescFile=Campaign3Start.txt StartText=Campaign3Start.txt //----------------------------------------------------------------------------- //---- USMC Units [uSMCUnit001] AircraftType=A-4E_65 Squadron=VMA121 ForceID=1 UnitID=4 StartDate=12/29/1966 DescFile=Campaign3Start.txt StartText=Campaign3Start.txt [uSMCUnit002] AircraftType=F-8E_66 Squadron=VMF212 ForceID=1 UnitID=5 StartDate=01/03/1967 DescFile=Campaign3Start.txt StartText=Campaign3Start.txt //----------------------------------------------------------------------------- //---- USAF Units [uSAFUnit001] AircraftType=F-100D_64 Squadron=493TFS ForceID=1 UnitID=6 StartDate=12/28/1966 DescFile=Campaign3Start.txt StartText=Campaign3Start493.txt //----------------------------------------------------------------------------- //---- Merc Units [MercUnit001] AircraftType=F-86F-40 UnitName=1st Special Ops Wing ForceID=1 UnitID=7 StartDate=12/25/1966 DescFile=Campaign3Start.txt StartText=Campaign3Start.txt //----------------------------------------------------------------------------- //---- RAF Units [RAFUnit001] AircraftType=Hunter9 UnitName=1417 Flight ForceID=1 UnitID=8 StartDate=12/25/1966 DescFile=Campaign3Start.txt StartText=Campaign3Start1417.txt [RAFUnit002] AircraftType=Lightning6 Squadron=74RAF ForceID=1 UnitID=9 StartDate=12/27/1966 DescFile=Campaign3Start.txt StartText=Campaign3Start74.txt What could possibly cause problems are heavily modded stock aircraft, third party skins on certain a/c, and trying to have altered start dates for certains squadrons so as not to have the USAF, USMC and USN all starting the same day. That makes it a little more interesting. A campaign starts, say on dec 25th, RAF are in the area so kick on straight away. USAF turn up around Dec 29th, and the naval task force arrive on Jan 3rd. My EARLIER enclosed "CAMPAIGN3.RAR" shows this

Well I've narrowed it down a bit in that your campaign INIs worked perfectly, even when I changed it to use "Desert3", and it worked fine with that terrain also. So it's got to be my campaign files. I've been comparing yours with mine and trying it out but still without luck so far. My own _WATER.bmp wasn't far off your own either: By the way, the upper "green area" is supposed to be for a Royal Navy Task Force (whenever I get round to updating the Ark Royal's INI files). I tried out your BMP also without luck so it's definitely my campaign files. EDIT: I forgot to mention that it might be because there's a LOT of prompts I've borrowed from the other SF2 titles' campaign files, such as "RunCampaignBeforePlayerStart", etc. You can see those for yourself anyway. But I don't know if that should matter, since they never caused problems in the past.

No that's not the problem. The campaign was freezing even when I tried to start flying for the USAF, which has no naval mission type prompts in the campaign_data.ini. Even before I added the prompts to the USN squadrons it was freezing. Checking out your INIs now. Actually I just had an idea to try them out in my SF2 install. At least if they work for me then I'll know it'll probably be my campaign files.

Here's my own if anyone wants to check them out as well: CAMPAIGN3.rar Mind you, I'm using my Desert3 terrain and I've added RAF squadrons. It may be a post-release "bug" that could be sorted with the next patch, but in any case if I have missed something, there's the files.

I'm currently trying to revamp my modded Operation QuickSand campaign to March 2012 standard with mixed results. I updated the CAMPAIGN.INI and CAMPAIGN_DATA.INI files by closely comparing them with the SF2NA campaign files. Starting the campaign flying RAF or Mercenary is no problem - if I try to fly for the USN,USMC or USAF the game freezes as soon as I click on the "Accept" tab, meaning I have to shut the game down via the Task Manager. Single missions from the carrier in the Desert - sorted. Created an updated DESERT_WATER.BMP file and all. It's just the campaigns have got me scratching my skull right now