JSF_Aggie

The production versions do not have a unique surface for a speed break, like the two CDA aircraft. It's done with a combination of the rudders and flaps.

I believe that is the case. A year or so ago, when the Mirage Factory released a large pack for use in online play, I believe they included some modified dogfight.ini's for a couple terrains. I think it's used as XY locations to spawn the different players.

Kevin, Sorry, I've missed this thread somehow. If you still have some questions, let me know and I'll do my best to answer.

In SP4, TK changed the code defining how the front line behaves. If you define more than 2 Forces in a campaign, several things go screwy, including ground units disappearing after they capture a StrategicNode.

The 3rd of the Harrier FOB's...

Moses, did this fix your problem???

Moses, I got it working. I did the following: 1. Installed the Hornet 2. Corrected two capitalization errors, but I doubt this is what fixed it: [USMCUnit001] UnitName=VMFA-122 Crusaders ForceID=1 UnitID=45 StartDate=1983 DescFile=woe2Start.txt StartText=woe2Start1.txt 3. Removed a 2nd entry from the loadout section for the AGM-45B, I bet this is causing your CTD. Supply[001].WeaponType=Mk82 Supply[001].Quantity=2880 Supply[002].WeaponType=Mk84 Supply[002].Quantity=480 Supply[003].WeaponType=Tank300_F18 Supply[003].Quantity=480 Supply[004].WeaponType=AIM-7M Supply[004].Quantity=240 Supply[005].WeaponType=AIM-9F Supply[005].Quantity=480 Supply[006].WeaponType=Mk83 Supply[006].Quantity=1560 Supply[007].WeaponType=AGM-45B Supply[007].Quantity=480 Supply[008].WeaponType=Rockeye Supply[008].Quantity=1480 Supply[009].WeaponType=AIM-9L Supply[009].Quantity=480 Supply[010].WeaponType=AGM-45B Supply[010].Quantity=480 These are the only changes I made, and it's working for me. There are a total of 93 AirUnit's. Let me know if you still have issues, and I can send you these files and/or look at it some more.

Moses, The most I've done, or seen done is around 90, but I would be surprised if that's the limit. If you want, PM me your email, or a link to your campaign files and I'll look. Hopefully it's just a typo or something along those lines.

If you guys want help with any skins, I would be more than happy to. When my dad was flying, we were stationed at Minot, Dyess, and Carswell. I was real young, but I still remember going to the Minot alert pad and watching the Airman standing guard with their parkas in the minus whatever temps. 1 week on, 2 weeks off.

This is not true, just forward looking.

I don't know that this has anything that you don't already have access to, but I have my dad's H model self-training handbook. It has some good diagrams of all the cockpit instrumentation. Were you going to do with, or without the tail gun? Thanks.

Are you talking this one here? http://forum.combatace.com/index.php?autom...p;showfile=1772 If so, it's older than what you get with the update file above. It's still using avioncs60.dll, with the above update, it switches to using avioncs70.dll with a real hud. Also, I diff'ed the _data.ini's and the flight models are significantly different. Kreelin posted this June, 24 2006. By the way, my Pax trip went down the toliet. All flights into the area were canceled until Tuesday cause of weather, and the guys running the class said that would be missing to much time. There's another in July, so hopefully I'll get to go to it.

USAFMTL, I don't think the AV-8C here, has Kreelin's last update. Kreelin did an update after SP4, in which he updated the flight model, and Kess added the HUD symbology. MoonJumper and Deacon tested the flight model. The update is here, but requires that it be installed ON TOP OF the AV-8C here. http://tiana.andriam.free.fr/av8csp4udp.exe

Thanks man, those are great. Much appreciated.

The .bmp's in the file should go into the folder for each terrain you want them for, i.e. desert, GermanyCE, VietnamSEA, etc... I don't believe it's possible for .bmp's to remove your runways. This is usually because your terrain isn't finding a .cat file. For example, in the bombing range's range.ini: [Terrain] TerrainFullName=Range DataFile=Range_data.INI TargetFile=Range_targets.INI TargetTypeFile=Range_types.INI MovementFile=Range_MOVEMENT.INI NationsFile=Range_NATIONS.INI BriefingText=Range_Briefing.INI DogfightFile=Range_dogfight.INI DogfightOnly=FALSE CatFile=..\GermanyCE\GermanyCE.cat <--------This needs to point to a cat file that exists.

The Huey was made by KillerBee, specifically for use as a ground object. The Cobra is Capun's, used as a ground object.

Another AV-8C base:

Thank you

I haven't tested it, but I assume MissionRate works as a multiple of NormalMissionRate. For example: NormalMissionRate=1.0 will give you 1 mission per day. In that case, MissionRate=0.5 would give 1 mission every 2 days & MissionRate=1.0 would give 1 mission per day & MissionRate=2.0 would give 2 missions per day

Johan, You may want to play around with adding the "MissionRate" variable to each of your squadrons. TK uses it in the stock SF campaign (per the example below), but not in any of the WOV or WOE campaigns. I assume it works as a multiple of the MissionRate variables defined at the top of the _data.ini. TK has it in there even for squadrons that are not playable, so hopefully it effects AI squadrons as well. It was something I'm going to experiment with eventually. [AirUnit001] AircraftType=F-100D Squadron=436TFS StartDate=9/25/1959 ForceID=1 Nation=USAF DefaultTexture=USAFSilver1 BaseArea=D3 Airfield RandomChance=100 MissionRate=0.9 <<<<------------------------------------ MaxAircraft=16 StartAircraft=16 MaxPilots=16 StartPilots=16 Experience=100 Morale=100 Supply=50

Nothing that I'm aware of. I've only completed 2 campaigns since SP4, OTC and DBS '72. Both had the problem you mention, and both were fixed by having just two "forces" defined. The only other thing I can suggest is to show TK your two campaign .ini files, either via email or post them at his site. Good luck

Check this... http://bbs.thirdwire.com/phpBB/viewtopic.php?p=19576 What's defined as the base needs to be a strategic node, so the ground forces have a "road map" to get there.

This is a fictional campaign I'm working on for Strike Fighters. It's set in 1978, on a heavily modified version of the stock SFP1 desert terrain. It will be Paran vs. Dhimar, with help from the US Navy and Marines. Dhimar's air force will consist of F-4D's, F-5E's, and A-4F's. The USMC will be the VMFA-542 Tigers, split up among 3 different forward operations bases. One of which is pictured below. The USN will be represented by the USS Nimitz, and the squadrons that sailed with her on her '78 cruise: VF-84 Jolly Rogers - F-14A VF-41 Black Aces - F-14A VA-82 Marauders - A-7E VA-86 Sidewinders - A-7E VA-35 Black Panthers - A-6E With the exception of the AV-8C, and the F-14, the skins below are done new for this campaign.

How many "Forces" do you have defined? TK changed the front line code with SP4, and it does a few squirly things if you have more than 2 "Forces" defined (one friendly, one enemy). I had the same problem you described in DBS '72 & OTC, when I had 3 "Forces" defined, and TK told me that was the reason. Problem went away when I changed it to just 2.