eburger68

Dedalus: It was as I suspected: the lack of shipping routes on the blue side. Attached is an updated MOVEMENT.INI that will allow you to fly anti-shipping missions for the Iraqi side. You'll need to get past the USN destroyers and cruisers to get a shot at the cargo ships, though. The new MOVEMENT.INI should be dropped in \Terrains\DS, overwriting the old MOVEMENT.INI. Eric Howes DS_MOVEMENT.zip

Dedalus: Quick followup: to answer my own question, it appears that all Iraqi aircraft that are configured for anti_ship missions suffer from this problem. From what I can tell, the game engine is simply not allowing Red side anti_shipping missions. If you select anti_shipping, it actually generates a recon mission. The loadout you're seeing is actually the recon loadout for whatever aircraft you've selected. This behavior happens on both the NavalMap enabled DS terrain and the older/standard version of the terrain. It happens even when I explicitly specify the Allowed Mission Types in the terrain's main INI file. I do notice that the terrain Movement.INI does not have any shipping routes that are in Blue side territory, so that may be playing a role here. I'll have to generate some new shipping routes and see if that changes the behavior. Eric Howes

Dedalus: Which aircraft? Eric Howes

fenbeiduo: Please don't post the same question in multiple threads. I already responded to your earlier post elsewhere. The modded carriers work fine. If they didn't, we'd be getting flooded with complaints about them. We aren't. I have tested the carriers again on my own system to verify that they work fine. Make sure that you're installing all the bits to the correct places properly -- including the SF2NA versions of the files, which are delivered in a separate folder. Eric Howes

fenbeiduo: The modded carriers work fine. If they didn't, we'd be getting flooded with complaints about them. We aren't. And i just tested the carriers again on my own system to verify that they work fine. Make sure that you're installing all the bits to the correct places properly -- including the SF2NA versions of the files, which are delivered in a separate folder. Eric Howes

Al: I have never seen that error. Perhaps someone else has. The best I can offer is that something in your SF2 install is porked (or the underlying OS config on which you're running), or something in your install of the mod was not done correctly. As to what specifically is causing that error, I have no idea. Someone else who has encountered that error might have some additional insight. Eric Howes

plug_nickel: I don't understand what "unavailable" means. Is that the text that you're actually seeing in the campaign screen? Also, do you have SF2I, Expansion Pack 1, and Expansion Pack 2 installed? Eric Howes

captainschwarz: None of the F-16s in NF4+ (which are the early blocks) can carry LGBs. That's why you're not seeing LGBs in the Loadout screen for those aircraft. If you want to change that, I would suggest that you consult the Knowledge Base here at CombatAce. Eric Howes

Spiff: Try bumping LandingSpeed value down -- say, by 0.5 increments. Eric Howes

Allen: Well, the last update for the Expansion Pack was in January of this year. As we discussed in a thread earlier this past Spring, a lot of the new SF2NA features (at least the ones pertaining to carrier battle groups) are of limited use in SF2V because of the nature of the carrier tours in the campaigns, esp. Rolling Thunder. Carrier battle groups and carrier-based naval aircraft could be implemented for Single Missions, but carrier battle groups are impractical for campaigns. The new aircraft probably will be enabled as optional installs for those that have SF2NA as part of their install base. As for Homefries' A-6 and EA-6 projects, those are fine mods. They are also large, and I'm not sure it's the job of the Expansion Pack to simply redistribute such mods when users can easily download and install them on their own. Remember: the Expansion Pack is already very large, and I am loath to turn it something even larger -- another comprehensive mod, heaven forbid, on the scale of NF5. I only need one of those in my life to maintain. So, yes, there will be an update. Can't say when, as I have several other things on my plate right now. Eric Howes

AleTB: The second file is configured for use with SF2NA. If it works, great. But I don't understand why it would work if you don't have SF2NA. Eric Howes

AleTB: Attached is a ZIP with two different versions of the CVN68_DATA.INI, which should be dropped in \Objects\GroundObject\CVN68 in your Mods folder. Try each of them in order, then tell me which one works. Also, what patch level are you on? Eric Howes cvn68_data.zip

Toro: I think what you're seeing is the product of coincidence. It's not anything that we configured to happen. Op Darius has naval aircraft from only two carriers; Op Desert Storm has naval aircraft from five carriers. In other words, you're more likely to get aircraft from the same carrier wing in Op Darius because there are fewer carriers to begin with. Eric Howes

AleTB: Is SF2NA part of your install? Eric Howes

Arthur66: OK, I took your changes to the flaps, tweaked that data just bit, then worked with the stall speed and landing speed until I got AI behavior that was reasonable. Normally the landing speed would be just above the stall speed, but with this flight model the aircraft doesn't seem to be getting enough lift in landing configuration. So, the specified landing speed is considerably above the stall speed -- about 154-155 knots, which I suspect is probably closer to the real thing than 105 knots (what it was doing previously). And even though the specified landing speed is 155 knots, AI actually comes in around 140-145 knots. Whatever the case, AI does a lot better with these numbers. Eric Howes F-22A_DATA.zip

Arthur66: I should have specified that I was more interested in AI landing behavior. Eric Howes

Arthur66: Have you tested the landing behavior? Very important, because this version drops the lift on the flaps and drops the flap deployment angle. The original flaps were manually deployed to allow the landing flap angle to be double the takeoff angle. Eric Howes

arthur66: Attached is another version of the DATA.INI, tweaked a bit more. Still not where it needs to be, but improved over the previous version. Eric Howes

Arthur66: The flight model probably does need to be revamped. I'm not the guy to do it, though. EricHowes

Folks: This mod package was refreshed today (12 Sep 2012). The only change of note is that it now includes the fixed main INI for the SF2V version of the South Atlantic (Falklands) terrain, which I originally posted a few days ago (see above). Eric Howes

arthur66: The F-22 (at least with the current flight model) has a rather high takeoff speed. If you pull back on the stick too early, you may crash. Notice that AI is usually above 200 knots before rotating and taking off. I've attached a tweaked DATA.INI for the F-22, which should allow you to rotate and take to the air at around 175-180 knots. Let me know how this works for you. Eric Howes

Stary: I'd be interested in taking a look at the 1024x1024 version of the terrain, as would plenty of others, I'm sure. Why not upload it to the Downloads section? Eric Howes

Do335: I've never encountered that problem. The only thing I can think is the Super Etendards somehow got their Exocets off and sank their own primary target. Eric Howes

Stary: You mean these? http://combatace.com/files/file/12852-mig-17-pfpfu-cockpit/ http://combatace.com/files/file/12684-mig-15-mig-15-bis-mig-17-simplified-cockpit/ Honestly, I overlooked them. So many updates and fixes in this mod. I'll pick them up in an update at some point. Thanks, Eric Howes

Stary: You mean the Su-15-based cockpits that you did? Those are nice cockpits. We're using them for the MiG-19s. Eric Howes