JSF_Aggie

Those are the only two we found talked about in liturature, I think Crusader found that piece of documentation. There may have been more, but I just went with those two. They made sense just based on the fact that they were close to were the USMC ground forces were at the start of the war. Skins are included for all the AV-8B units in DS, but I only have three in the campaign. Two on the Expeditionary Airfields, and one coming off the LHA. I found a lot of conflicting documents as far as were each was actually stationed. Some operated from standard airfields and/or moved around. I'm ok with making the harrier airfields a stand alone download, but let me ask the guys whose objects I used: FastCargo, KillerBee, and Kesselbrut.

We know about #1. They're target areas that were added for single missions, but are on in Kuwait, and therefore behind the front line for the camapaign. A simple fix is to change the start/end dates for these target areas in the terrain's ds_targets.ini. comrpnt's posted the exact lines to add in the big ODS thread. We've seen #2 as well, but don't know the cause of it yet.

Just to add a little to what Dave said, no one is saying you can't point out an issue with a mod just because it is free. We tested the hell out of ODS, but I knew we would miss little things here and there. The campaign files were over 5,000 lines long, so I knew there would be a few errors and typos, no matter how many times I looked them over. Some of you have posted mistakes in the forums, others have PM'ed me. Thanks, we appreciate the input, and we'll get them fixed. It's obvious to just about everyone if someone is trying to be contructive, or if their sole purpose in life is to be an ass.

Thanks

Which aircraft are you seeing this with? I have occasionally seen with all SF/WO? versions, if you give the "return to base" command after you've reached the last three waypoints (approach, lineup, touchdown), the AI will sometimes get confused and fly around in circles. This is not specific to the DS addon, we didn't change anything with the stock airfields, or the AI landing behavior. Either give the "return to base" command prior to reaching the 3rd to last waypoint, or just fly the last three, let your flight follow you, and they will land. If it's a specific aircraft, it may be a FM issue. For example with the AV-8B, I had to specify an approach speed in the AIData section, or it would not get slow enough to land. It would flare, and overshoot the runway/carrier.

Man, those are awesome. He must be be working on a whole new set of menu, hangar, and loading screens for us.

I did the following yesterday, on a clean install, with no problems VietnamSEA_Tile_Repaint_v1.0.zip Green_Hell_2.ZIP (high detail .tod's) Shimmering_buildings_fix.zip The modifed VietnamSEA_data.ini that's attached here, which is just CA_Stary's, with the couple of new entries added in the Oct 08 patch. VIETNAMSEA_data.zip

Yes, you do need all three. http://forum.combatace.com/index.php?autoc...amp;showcat=339 EDIT: Dave beat me to it.

Updating the Harrier Campaign is one of the next things on my list. If you just want the README for the F-14 HUD documentation I can post it when I get home. It'll tell you what works, and what Crusader and I couldn't get working due to game limitations.

What squadron were you flying? Can you repeat it, or was it a one time thing? Did you happen to catch the date the campaign ended? Have you made any other mods to your ODS install? Thanks

Go with the starting number, specific for each squadron. The resupply time was set to 80, based on the logic that the campaign should be over in less than 80 days, and I just wanted each squadron to start out with enough to get them through the campaign. I'll deffinately check each unit as part of the first update.

It's set to resupply every 80 days. This can be tweaked at the top of the DesertStorm_Data.ini campaign file. In the same file, is the starting number of stores for each squadron. This is also something I'm probably going to tweak in the future. If you change these values, you'll have to restart your current campaign to see the changes.

In the terrain's DS_TYPES.ini, every target type has a repair rate variable. I don't know the units, I assume days. The values are still at the stock values, but I might look at tweaking them in future updates. For most aircraft types, you should be flying close to once a day, if not more. [TargetType027] Name=Runway1 FullName=Runway ModelName=airfield1.lod TargetType=MEDIUM_RUNWAY ActiveYear=0 TargetValue=1000 UseGroundObject=FALSE DamagePoint=140.0 ArmorValue=0.0 ArmorType=0 RepairRate=10.0 <<<<<<<<<<<<<<<<<<<<<<<<<<

Cool, I was just looking to see if anyone else had made one.

Man, what a great simulator.

If required, please tattoo the following on your butt: http://forum.combatace.com/index.php?showt...mp;#entry240900 Also, unless someone else has made one, we do not have a CF-18 skin. saguanay pulled the skin he made, and asked that it not be used.

Yeah, with part one being the largest part, I wonder how many with dial-up didn't get the complete download, and had to start it a second time.

Thanks. You may want to watch making them to fancy. I turned my EFFECTS down to MEDIUM, because the B-52's flattening an airfield with 51 M117's a piece, killed my frame rate for a short time. Crashed my GFX drivers once, when EFFECTS were on HIGH.

Thanks. There will be updates for bug fixes. There will also be updates to add new content, and to improve existing content. Some countries and/or squadrons are missing, some aircraft are missing, etc.... Some of this was due to time constraints, and some because we're just waiting for the 3d model or skin to be completed.

Your key settings sound be in /Controls/default.ini. You should be able to copy that file over with no problem at all. Your gamesettings are in the options.ini file at the top level. However, if you copy your options.ini file directly over, you'll break Instant Action and Multiplayer. This will probably result in a CTD if you try to do either.

Keep in mind we're limited to what we can do as far as the campaign engine. We don't have source code. I can specify A target area to be focused on for the entire force, but I can't keep certain squadrons from being assigned certain target areas/cities. You may want to try tweaking the NormalMissionRadius and MaxMissionRadius in the AV-8B's data file. If you make it small enough, it may keep the game engine from sending you up to Bagdad. You can change what mission types you're assigned in the DesertStorm_Data.ini campaign file, per squadron: MissionChance[sWEEP]=0 MissionChance[CAP]=0 MissionChance[iNTERCEPT]=0 MissionChance[ESCORT]=0 MissionChance=50 MissionChance[CAS]=90 MissionChance[sEAD]=40 <<<<<<<<<<<Set this to something smaller MissionChance[ARMED_RECON]=50 MissionChance[ANTI_SHIP]=0 MissionChance[RECON]=20

In addition to what comrpnt said, I'll look at moving the front line to get those target areas he added onto the Coalition side of the FEBA. That way the game engine won't turn them RED.

Thank you sir.

Crusader has done avionics upgrades to almost every flyable aircraft. Some minor, some major, and everything in between.

This doesn't last very long. After the first 6-7 campaign missions, there isn't much of an enemy air threat. Watch out for the SAMS though.