Aintry

Hi, Maico. I'll paraphrase the Weapons Pack instructions. Basically, you have to update the data.ini and loadout.ini files of each aircraft to allow them to "read" the weapons in Bunyap's Weapons Pack. I'll give you a fer instance. Under the stock weps classification, Soviet aircraft loadup weapons under the classification 'WP'; you'll see that if you look in the data.ini files of the Soviet aircraft. 'WP' weps are what you see listed in the loadout screen for Soviet aircraft with a stock setup. Bunyap's Weapons Pack changes all of that. Soviet weapons in the Weapons Pack are categorized under the designation 'Soviet', not 'WP.' So if you don't change the data.ini and loadout.ini files of Soviet aircraft to reflect the changes in weapons classification, you could very well end up with no weps as a loadout option for your Soviet planes. People have found ways to get around this new classification system by using the Weapons Editor, so if you want to go that route, that is certainly available to you. I'm not advocating one method over another. I just happen to prefer the route of updating the data.ini and loadout.ini files.

Yeah, like capun said, you have some file editing to do.

Hi f.t.a.-- You could be having a file extension problem for any number of reasons. I think you should post the exact error message to give potential helpers a foothold. BTW, I haven't had any problems with the latest Weapons Pack in either SFP1 or WoE, so I suspect your problem isn't weps-related. Tristan

Two questions: 1.) Are the planes you transferred to WoV third-party aircraft or stock aircraft from SFP1? 2.) Are you using stock weapons or are you using Bunyap's Weapons Pack in WoV?

Yeah, the MinBase thing solved the problem for me, also. The Foxbat flies fine in WoE now.

Still, I wish I knew why the add-on A-10 started self-destructing in WoE, since all of my other add-on planes have always worked fine. I once thought it was the infamous MinBaseSize issue at work, but the MBS value is identical in the both the stock and the add-on A-10 data.ini files. If there's a file conflict somewhere, I sure don't know what the offending file is. It's a bit irritating.

The first time I tried the mod A-10 in WoE, it worked fine. Then, after I patched WoE for the first time, the mod A-10 behaved exactly as you described -- it blew up. It has always worked fine in SFP1, despite the fact that SFP1 has been patched as well. I wish I knew what the problem was; I haven't had time to look into it.

I get the jibberish letters sometimes when I left-click on a file to download. I solve that by right-clicking and choosing the download command from the list, then things download just fine (at least for me). I don't know what to say about missing configuration files; there has to be at least a TextureSet.ini file in the package or the skin won't load. Might be a download thing, or a decompression thing; it's hard to tell from this end. Perhaps we need a talk-through to solve this problem. SP4 is the latest service pack for the SF-series games; WoE already has SP4 incorporated into it out-of-the-box. The place to check for the latest upgrades/patches is either here in the downloads section, or at: http://www.thirdwire.com Make sure you download *all* the updates from Thirdwire, not just the SP4. And get the June 2006 build of Direct X 9.0 from Microsoft if you haven't already installed it or the April 2006 build. As for a decompression program, the one I recommend is a program called 7-zip. It's freeware, and you can probably download it from a number of different places. I downloaded my copy from: http://www.tucows.com Sorry about giving you all of that jazz about manual configuration file editing. It's good that capun stepped up with his info. Modding should not be made more complicated than necessary. I know I already have enough to do with weps and flight model editing. Incidentally, I've been setting skin defaults by labeling my favorite skin [TextureSet001] and literally erasing the other [TextureSet] entries in the aircraft configuration file. The entries for the other skins will eventually reappear in the configuration file automatically, but with the favorite [TextureSet] at the top of the list. Wonderful.

OK, capun, since you've picked up the ball here, maybe you ought to tell Sora how you designate a skin as a default skin, since he's probably wondering.

Good. File no. 1 is the configuration file. You can forget about the other files. Now, the [TextureSet]s listed in the configuration file correspond to the aircraft skins that are already inside your airplane folder. [TextureSet]s also have sequential numbers associated with them: 001, 002, etc. Now, here's the clincher. Every skin folder that you download for your airplane will have a [TextureSet] "ini" file inside of it. So here's how you get your plane to recognize the new skin: 1.) Put the new skin folder inside the aircraft folder, right alongside the other skin folders. 2.) Copy the data from the new skin's [TextureSet] file and paste it into the plane's configuration file, making sure that you assign the correct sequential number to the new skin (if, for example, this is your third skin, it should be listed as [TextureSet003]). Believe it or not, that's it. This is literally a copy-and-paste text job. When you open the loadout screen before a mission, the new skin should be listed as an option.

OK, I'm going to be a little meanie and give you an assignment, heh-heh. I want you to open the folder of one of your installed aircraft and locate the configuration file for me. You'll know it's the configuration file when, after you've scrolled to the bottom of it, you see a list of [TextureSet]s. Hint: this is a text file with a gear attached to it, a/k/a an "ini" file. Post back when you're done.

Are you talking about simply adding pre-made skins to your aircraft or are you talking about making skins from scratch yourself?

No, if you download MiG pits, you won't need to use the A-4 pit to make the MiGs flyable. The A-4 option is for when you *don't* have custom pits to download. Addenda: I think I should add something here, just to be on the safe side. These are the options for realizing flyable aircraft in SF-series games: 1.) The "A-4 pit" option. For stock non-flyables. 2.) The downloadable-custom-pit option. For stock non-flyables. 3.) The whole-aircraft option. This applies to aircraft that aren't part of the stock lineup but which will appear in your game and fly after they are installed. Pits are part of the download package. The MiG-21F-13 is one such example of a "whole aircraft". Hope this helps. Tristan

The Su-27 is being worked on, but there's no word about a possible release date.

#1 There is a Configuration "ini" file inside the directory of each aircraft. To get a skin to show up on an aircraft, you need a skin folder with the skin set inside of it, and the name and configuration of the skin set, aka "TextureSet", in the Configuration ini file. Example: You download a skin set for a MiG-29 and load the skin folder inside your MiG-29 aircraft directory. Then, you look inside the MiG-29 skin folder for the TextureSet file. You copy the text data from the TextureSet file and paste it into the the aircraft's Configuration file (minding the TextureSet number sequence). The skin should then show up as an option in the airplane loadout screen when you start a mission. #2 Yes, you can download other aircraft, and it should be, for the most part, simply a drag-and-drop op to install the aircraft into WoE.

You'll have to hunt around for flyable MiGs or cockpits that will make MiGs flyable. Check the downloads section here first, then go to the link index for a list of other download sites. Cockpits almost always come with a set of installation instructions. Just to let you know, once you patch your game, the A-4 cockpit for the MiG-27 will disappear and the MiG-27 will no longer be flyable in single-player mode.

Ever heard of an Easter Egg? The MiG-27 had a functional cockpit out-of-the-box, just not a MiG-27 pit.

Hi Rob: I think you might be mistaking the MiG-27 for the MiG-29. Yes, the unpatched WoE had the MiG-27 as flyable in single missions, but the first patch made it unflyable in single missions. You aren't going mad. I don't know why the change was made. Tristan

Has anyone bought the first installment of 'Yankee Air Pirate' yet and, if so, what do you think of it?

Is there any chance we could get a shot of the helo in a mid-air refuel?

Hmmm. I just right-clicked on a mod compressed to .rar format, selected 7-zip from the menu options, chose 'Extract Here', and 7-zip opened the file just fine.

Try: http://www.tucows.com/Windows/IS-IT/FileMa...ssionUtilities/ I recommend 7-zip.

Would this be of any help? http://bunyap2w1.com/SFP1_Wiki/index.php?title=Aircraft_Data

The image you've posted is taking forever to load. Is there some way to scale it down?