Aintry

I noticed a bit of a performance drop in SFP1, post SP4. But I discovered that the new 3d clouds had nothing to do with it; clear, inclement -- all else being equal, the clouds didn't change performance levels. I'm not surprised, though, that post-SP4 game refinements have, overall, slowed the SFP1 down some. Avionics, smarter AI -- there are a bunch of things that could be affecting post-SP4 game performance.

If that's the same as "Mission: Unarmed Reconnaissance" I'd say yes.

My squadron and I are frequently "SAM lunch" in Gepard's 'Israel' terrain. There's definitely something Freudian going on here.

Hi Allen -- I use a program called '7-Zip' for file extraction. See: http://www.7-zip.org Tristan

Hi, Allen Thanks for hanging in there, and ditto what Fubar said. I'm assuming that what we're discussing here is a problem with an entire airplane, and not just a mod like a cockpit. It's possible that you now have a sub-folder in the Aircraft folder that the game can't read. The only sub-folders that should be in the Aircraft folder are things with aircraft designations -- 'F-4e', 'MiG-17'... things like that. Look for the sub-folder that you installed to the game's Aircraft folder; my guess is that it doesn't have the designation of the aircraft you are trying to run, but instead says something like 'Objects' or 'Aircraft'. Keep clicking on that folder until you get to the folder which has the designation of your plane on it -- 'F-8d', or whatever. Drag and drop *that* folder, the one with the plane designation, into the game's Aircraft folder, where all the other plane subfolders are. Your aircraft should now show up in the game. From now on, you need to make certain that any folders you put in the Aircraft folder have plane designations on them. If it doesn't say something like 'MiG-23', or 'F-14', the game won't be able to "see" the plane. It's the same deal when installing custom cockpits -- all of the pit information has to be installed to the folder of a specific airplane. Otherwise, the game won't 'see' the custom cockpit. As for sources of plane downloads, all I can really say is check the CombatAce download section, and then the community links section. Everybody has his own favorite download site, I think.

Hey, that's good news about the weps! I guess I should add one thing here, in case you don't know already. The way things are set up for the stock weps and for the Bunyap's Weapons Pack, loadouts are now time-dependent. So if you run into another situation where you only seem to have limited options regarding weaponry, constraints imposed by historical realism are probably the reason. I just don't want you to experience this sort of thing again and think that your game isn't running properly. Loadouts are being limited deliberately by the developers as part of gameplay. As for sound... Open the F-14 data.ini file again and scroll down to [sound]. Check out the EngineSoundName entry. If it is anything other than 'JetEngine', delete the entry and insert 'JetEngine' and see what happens (uppercase J, uppercase E, no quotes). If that doesn't work, we'll see if we can try something else.

This looks like a file you would use if you wanted to install your F-14 into a campaign. I don't think this has anything to do with weapons loadout. I'd leave this alone.

There are two different ways to put flyable planes in the game: 1.) Download a complete package -- airframe, cockpit, and all -- and install it. This is what you'll be dealing with most of the time, complete packages. 2.) Download a custom cockpit which will make a plane that is installed in WOV, but not flyable by you -- such as a Russian Mig -- flyable. In either of these two cases, it will just be a matter of dumping folders into your WOV directory. Every plane should be recognized immediately by WOV, and should fly without a hitch, unless the modder has seriously messed up somewhere.

It sounds like there are some mods at cross-purposes here. Something deleted the engine sound file during an installation process, so you'll probably have to load that sound again into the Sounds folder to get the engine sounds back. Check the files that came with your F-14. As for weapons -- weapons are classified differently in the add-on Weapons Pack from the way they are in the stock game. This is causing loadout problems in a lot of third-party aircraft. You're going to have to do what's know as a "data.ini edit" for your F-14 in order to get a full loadout with the Weapons Pack. Inside your F-14 folder you'll see a file called 'F-14_data'. If you open that up and scroll down to the [Weapons] section, you'll see entries called 'AttachmentTypes'. These are hardpoints, and there will be a classification entered next to each one: WP, NATO... something along these lines. Sometimes you'll see multiple entries next to a single 'AttachmentType.' Whatever the case may be, some of the entries at these 'AttachmentTypes' make the F-14 "blind" to a lot of the weapons in the new Weapons Pack, so you're going to have to do some editing. If you open up Bunyap's Weapons Pack manual, you'll see a table entitled 'Nation Name and Attachment Type Table.' This tells you what entries need to be made next to the 'AttachmentTypes' to allow your plane to "read" the new Weapons Pack files. I see an entry for 'United States Navy' -- USN. Assuming that the loadout scheme for the F-14 is USN, that is the *only* entry you should have at the F-14's ATs. Anything *other* than USN, such as WP or NATO, will have to be deleted to get the F-14 to read the Weapons Pack USN weapons. Multiple entries are no longer supported when using the Weapons Pack. You might have to go through this process with every third-party plane in your stable, unfortunately

A loadout problem, that is, a problem getting weapons loaded onto a plane, is a separate problem from setting up custom planes so that you can fly them. Are you having problems doing both things?

That's OK. If you're having loadout problems with any of the planes, post back. There's a very good chance I'll be able to help you. Tristan

Hi, Allen. It sounds like what you are trying to do is use the Weapons *Editor*, which is in the main WOV directory. You don't have to use the Weapons Editor to load the planes. The weapons themselves are installed in their own sub-folder within the Objects folder. In order to use the weapons, you'll have to load them through the loadout GUI of the plane you want to fly. Give me an example of a problem you're trying to solve. Tristan

You don't need to install a patch for pit upgrades, unless by "patch" you mean an official game patch. There should be read-mes that come with the pit files; the installation instructions are usually pretty simple. BTW, how did you manage to get inside the cockpit of your simulated jet? Is this a Tron thing going on here or something? If you want to find out where to download things like mission editors, you'll have to do a little homework. Start by perusing the community links section on this site.

I fly the MiG-21MF in 'Strike Fighters'. Unlike the stock pits for all of the other aircraft, Mago & Co.'s MiG-21MF pit has moveable stick and pedals. It also has functional RWR. You can download that pit right from this site.

Ah, good. Thanks, bud. :)

USAFMTL -- Forgive what might sound like an utterly stupid newb question, but do people ever do sound-effects mod work for SF or WOV? Just wondering. Tristan

testing, testing....