Piecemeal

I've been using the third party HGU26_8 model in Soviet fighter aircraft for a while now which I think makes a passable Soviet flight helmet: But yeah, I agree. A proper Soviet model has been a long time forthcoming. If I was any good at modelling I'd have tried it myself

Tried that already. No Joy. First I added it to the end of the list: [squadron262] Name=254IDF DisplayName=No. 254 Midland Squadron Nation=ISRAEL [squadron263] Name=436TFS DisplayName=436th TFS Nation=USAF [squadron264] Name=VF43 DisplayName=VF-43 Challengers (Aggressor) Nation=USN Result: FAIL I then started from scratch and tried adding it to the list in the order that the squadrons would appear: [squadron108] Name=VF41 DisplayName=VF-41 Black Aces Nation=USN [squadron109] Name=VF43 DisplayName=VF-43 Challengers (Aggressor) Nation=USN [squadron110] Name=VA46 DisplayName=VA-46 Clansmen Nation=USN Result: FAIL I've been thinking that maybe I'm putting the edited squadronlist into the wrong folder; or maybe as one member said here recently; there's still so much that we don't know about the new SF2 file setup and there's so many people going round like headless chickens. In otherwords, it's still early days

I just thought I'd give a quick update before I head for the bunk. I've been able to add the VF-43 F-21 Lion Aggressor squadron to the campaign, but only by assigning a different squadron to the campaign ini files. Obviously I was correct in my suspicions that the game would only accept default squadrons on the squadronlist.ini. Which brings me to my next idea. 1. I extracted the squadronlist.ini from C:/Program Files/ThirdWire/StrikeFighters 2/Flight/MissionData001 and found the squadronlist.ini in it. 2. I then picked the squadron VA-152, which I would never use, from the list and edited the display name: [squadron149] Name=VA152 DisplayName=VF-43 Challengers (Aggressor) <-------------- Nation=USN 3. I then copied the above mentioned amended squadronlist to My Name/Saved Games/ThirdWire/StrikeFighters2/Flight (just to be sure). I then edited the campaign ini files to include the F-21 and squadron VA-152, which should display the above display name. Unfortunately the squadron was still displayed as 'VA-152 Friendlies' I've been thinking of adding a new subfolder in the Flight folder mentioned in part three above anf throwing the squadronlist.ini into it, but I'm just too tired to experiment any more tonight. Thoughts or recommendations anyone? Ciao for now....

No joy. It looks like aircraft will only fly if the squadron assigned to the aircraft are on the SquadronList.ini file. I also tried to add the VF-43 squadron to the squadronlist but it didn't recognise it. What a bummer.

The calm before the storm.

Will check it out in the campaign now to see if it works

Jesus, CL; you've just given me another idea! I might actually put on an USN F-5E Aggressor squadron since I've successfully tested the F-5E in SF2. An add-on aggressor shouldn't be too hard to get my hands on either. It seems (and I could be wrong here) that SF2 will only recognise default squadrons on the SquadronList.ini, so I've attached a list of the default USN Fighter squadrons. Maybe yourself or somebody might be able to recognise if one of them is an Aggressor squadron: SF2_USN_FighterSquadrons.txt Thanks for keeping the interest up lads.

No joy I'm afraid bud. Tried both 1 and 0 and the carrier squadrons started either on the day the campaign started (07/09/1986) or within one day of it. I brought the number back to 14 and discovered that when flying with the USN/USMC it's within a couple of days of whenever they're supposed to start. I still have that problem though when flying with the USAF or Mercs of seeing the carrier squadrons flying long before they're due to appear

Watch this space Dave. Will get back to you ASAP

Great idea, TC! You've just given me an idea for a noughties SF2 campaign. I might try to put one together as soon as I can sort out some minor teething problems with an eighties campaign I'm putting together

Thanks for your help Dave. Much appreciated. Just checked out your suggestion. Changed that said entry to 'Historical: TRUE'. Nochange I'm afraid. Before you take a lookat the ini's I just want to give you the reasons for a late USN/USMC start; I want to give the idea of the Midway arriving in the conflict area much like the 'cavalry coming to the rescue' when Dhimar's 'posterior' is against the wall after over a week of fighting with reduced squadron numbers. Anyway, here's the inis. Once again thanks for your time in assisting me on this. CAMPAIGN6.txt CAMPAIGN6_DATA.txt

Will check that out Dave . I don't suppose you'd fancy looking over the ini files if I attached them to my next message here? (Just so you'd be able to see the full picture as I created it)

Does anyone know which website I can download the add-on deck crew for the WOV carriers? I was told before some time back but I can't remember the name

Mirage IIICD - Royal Dhimari Air Force, 1969 A little experiment I took on by importing the stock Mirage IIICJ and cockpit from WOI. Adds a little spice (or should I say garlic) to the stock campaigns.

Hi guys. Don't know why but the IAI F-21 Lion Aggressor Kfir won't appear on the campaign, even as an AI squadron, so I've struck it off the project. Pity really. To make up for things I've added two squadrons; one USN attack squadron and one USMC fighter squadron (both also on Midway). Here's the list on the new CAMPAIGN.INI : [CampaignData] CampaignName=Operation Desert Shepherd DataFile=Campaign6_Data.ini CampaignMap=DESERT Historical=FALSE Service001=USAF Service002=USN Service003=USMC Service004=Merc [uSAFUnit001] Squadron=104TFS ForceID=1 UnitID=1 StartDate=07/11/1986 DescFile=Campaign6Start.txt StartText=Campaign6Start.txt AircraftType=F-4E_75 [uSNUnit001] Squadron=VF151 ForceID=1 UnitID=2 StartDate=07/21/1986 DescFile=Campaign6Start.txt StartText=Campaign6Start.txt AircraftType=F-4SL [uSNUnit002] Squadron=VA66 ForceID=1 UnitID=3 StartDate=07/21/1986 DescFile=Campaign6Start.txt StartText=Campaign6Start.txt AircraftType=A-7E_Late_MF [uSMCUnit001] Squadron=VMFA333 ForceID=1 UnitID=4 StartDate=07/21/1986 DescFile=Campaign6Start.txt StartText=Campaign6Start.txt AircraftType=F-4SL [MercUnit001] UnitName=1st Special Ops Wing ForceID=1 UnitID=5 StartDate=07/09/1986 DescFile=Campaign6StartMerc.txt StartText=Campaign6Start.txt AircraftType=Mirage5D I've chosen the A-7E because there were two A-7E squadrons aboard the Midway, namely VA-56 and VA-93 aboard from the early 70s. I've chosen the MF A-7E as the aircraft platform but unfortunately there aren't any skins for that squadron available with the MF A-7E. While looking into the Midway's career (acting also on charlielima's info - cheers bud ) it transpires that VMFA-333's F-4S squadron have been aboard from time to time so I thought it would be a good idea to add 'the boys': BTW has anyone been able to think about my little problem regarding the carrier squadrons' start dates? For example: The carrier start date is 07/21/1986. Obviously I've edited the carrierborne squadrons to start on the same date. But when, for example, I start a Merc campaign (which starts on 07/09/1986 - the same date as the campaign) there's carrier squadrons flying in the area. I can upload the campagn.ini and campaigndata.ini if anyone's interested in looking through that issue. I'd really appreciate it :yes: . I may seem like a pain in the a**e on this issue but I guess I'm just ine of those guys who likes everything just right

Sounds like something worth looking forward to :yes:

Cheers for the info bud. It must've been Jet Thunder or one of the other sims I was thinking of

Thanks for the info CL. Looks like my information on the Midway was wrong. Dont know where I got my info on her being decommisioned in '86. I took the liberty of checking it out on Wikipedia. Check it out for yourself: http://en.wikipedia.org/wiki/USS_Midway_(C...ife_as_a_museum Looks like I might also have to take you up on your info on USN squadrons. I did a test run about 30 minutes ago on 'Op Desert Shepherd'. I had assigned the Aggressor squadron VF-43 as one of the active USN squadrons and had them based in D6 Airfield. With each air arm I tested (USAF, USN, Merc) there was no sign of them being active. Maybe I'll put an A-7 and/or an A-6 squadron alongside VF-151's F-4S squadron. There wasn't even any sign of VF-43 in the drop-down menu at the start when you have to select what air arm you have to fly for. Maybe it's because VF-43 isn't in the default SF2 squadronlist. Can anyone give advice on how to solve this? Two more small snags that someone might be able to help with: 1. When I tested out flying the F-4S from Midway, the 1st campaign mission starts no problem on the deck of Midway. The only problem is in the main Campaign ini I put this entry in: [uSNUnit002] Squadron=VF151 ForceID=1 UnitID=3 StartDate=07/21/1986<--------------- DescFile=Campaign6Start.txt StartText=Campaign6Start.txt AircraftType=F-4SL VF-151 were supposed to start 12 days after the out break of hostilities, not on the startdate. All the other player squadrons have been designed to start on the day war breaks out - as it states in the CampaignData.ini: [CampaignData] StartDate=07/09/1986 StartDateDeviation=0 ForceWithInitiative=2 MaxMissions=35 I wanted to give the idea of the US Navy playing the part of the Cavalry coming to the rescue. 2. Playing the campaign with the Mercs is no problem, apart from the fact that the game engine ignores the MIRAGE5DLOADOUT.INI. When I go to 'loadout' on the campaign mission menu, nothing is selected. I have to select weapons myself from the list (which even includes Soviet weapons!) and the default Mirage drop tanks aren't available. Ideas on these niggly problems anyone?

Amokfloo my friend; with these skins you are reeeeally spoiling us! Only problem is the campaign timeframe is before the ADF upgrades were delivered: http://www.sirviper.com/index.php?page=fig.../f-16/adf/index But of course campaign timeframes are something that can be easily rectified

This is just a personal opinion but I've used the various MF F-16 models before I purchased WOI and was blown away when I saw and used the F-16 Netz. The stock WOI F-16 cockpit is far better and more detailed than the MF cockpit, as is the WOI F-16 model and Israeli skin itself. But as I said already, for me it's just a personal preferance. I suppose you could use the Venezuelan F-16A Block 15 and put Dhimari decals on the skin, which has a desert-type colour scheme also. Another option, if you have WOI would be to extract the stock WOI F-16 cockpit and place it in the MF F-16 model of your choice. I did that with the SF2 Mirage 5D. To make the plane flyable I extracted the Nesher cokpit from WOI and placed it in the Mirage 5D folder. On the subject of F-5s, I've been toying with the idea of throwing a 'good will gesture' squadron of Saudi F-5Es into the campaign on the Dhimari side. The only problem there is until a Weapon Editor can be released for SF2 I can't put any default drop tanks on it

Are these new skins for SF2? I'm not sure if the original add-on skins for SFP1/SFG will work on the models for SF2. I don't know if the models have been re-designed for the -23. But if they work, cheers bud. Will check them out shortly. In the meantime; watch this space. Will keep you updated on how I get on with them

Contrary to what the medical experts say, I really must eat Doritos (potato chips) more often: I was on the forum here about an hour and a half ago discussing the creation of an 80s campaign for SF2 when ... .... the mains power went in the whole neighbourhood and surrounding areas. My laptop went onto battery power but my broadband receiver unit in the hall is connected to the mains so, yes you've guessed it, no broadband. "F**k this anyway", I said to myself as I closed my laptop. For the next 45 minutes I tried to entertain myself my watching the flames dance in the hearth and wondering what the hell to do with myself for entertainment when suddenly my stomach started telling me it needed a snack. I wandered out the kitchen using my mobile phone as a makeshift torch. Sandwich? Nahhhh..... I'd probably cut one of my fingers off in the process. Instant noodles? Nahhhh.... no power for the kettle. But then I thought of that big packet of Doritos I didn't finish the other night when I was washing them down with (more than) a few beers while watching DVDs. Why not. So in I plodded to the living room with the remains of a pack of 'chilli heatwave' flavour Doritos and sat myself down next to the candles and munched away. Two minutes later....... ...... the electricity company said "let there be power", and there was power. And yes, it was GOOOOOOOD! I must put a couple of packs of those tasty snacks on this week's shopping list for my Mrs.

I've been making an attempt to simulate the scarcity of weapons stocks for this campaign. Here's an example of one active squadron: [AirUnit003] AircraftType=F-4SL Squadron=VF151 ForceID=1 Nation=USN DefaultTexture=USNGreyLate BaseArea=Echo Station CarrierBased=TRUE CarrierNumber=41 RandomChance=100 MaxAircraft=16 StartAircraft=16 MaxPilots=16 StartPilots=16 Experience=100 Morale=100 Supply=25 <------------------------ is this the right adjustment? MissionChance[sWEEP]=90 MissionChance[CAP]=90 MissionChance[iNTERCEPT]=90 MissionChance[ESCORT]=70 MissionChance=25 MissionChance[CAS]=50 MissionChance[sEAD]=50 MissionChance[ARMED_RECON]=25 MissionChance[ANTI_SHIP]=10 MissionChance[RECON]=50 UpgradeType=NEVER

This has happened me a couple of times before but only when there's been a huge amount of activity in the target area and my FPS goes below 5fps. How much RAM have you? I've got 2gb but am planning to up that to at least 3gb; depending on what I can afford when I order it