FastCargo

I thought the sim can only handle a max of 28 weapons in a single bay? FC

AGOSTINO and others, SF2/V/E are recent releases...MANY models have not been updated to SF2 standard. Posting threads about something not working in an aircraft for an aircraft NOT designed for SF2 just makes you sound like you aren't paying attention. If you are going to post about something like this, it would help if you posted a possible solution. FC

Rock on! It's actually simpler to make weapons now...the HARD part is migrating the old ones over. I just decided to download and install KBs weapons pack instead...then migrate any weapons he missed. FC

Eric, Are you still using a weapondata.ini and dat file? I've dumped that entirely. FC

Frankly, I'm glad TK hasn't spent the time or money upgrading the avionics just so I can have a countdown timer to a release point. BTDT in real life for level bombing. It's dull, it's boring, it's not satisfying, and it's relatively inaccurate (for level bombing). Nope, you can quote all you want from whatever sources you want. I've done it for real. Sure, in real life, there are many things to consider to get the aircraft to the computed release point...striking a balance between the demands of self defense, and the demands of the release parameters (when you're dropping a stick, that's real important). But this ain't real life. Far more interesting to practice trying to do a manual pickle, to get the aircraft in the exact parameters for a release without getting killed. Or as you get in later years, CCIP which allows you to still do a visual release. Or trying to get in LGB parameters (newest patches have done a better job in simulating the tolerances of the release basket). I don't want to be the monkey looking at the timer (no offense to my WSO bretheren). Now, this might be different if you could simulate a 2 person cockpit (multiplayer) with a dedicated WSO...THEN things would get interesting because CRM becomes a whole other issue... As our favorite friend sparky likes to say...if you want reality, start by filling out the paperwork. I'd rather have fun. FC

The topic is starting to drift again. Answer the basic question...single aircraft (or aircraft packs)...yes or no...why or why not. No 'would rather have' wishes here. FC

During testing of an 'all in one' terrain mod for SF2V...(unfortunately the testing is not going well)... FC

Got a few friends like that...makes me feel smarter... FC

x2. And I used to be a gun enthusiast back in the day. FC

Yea, the cirrus mod works just fine on terrains that aren't too 'lumpy'. However, I haven't found a way to prevent them cirrus from showing through the far mountains if you're low level. Not a factor when you're at 60k feet at Mach 2+...but down low... FC

The release tolerances for LGBs have become tighter...that's why you have problems using them on mobile targets. They still will kill tanks just fine. FC

Also, if those features are there (HUD in lower right corner, radar in upper right corner, etc) you definitely aren't on hard settings for everything. FC

No, no, it's not that the terrains aren't working...it's that the mapping on the runways are different. Trust me, look at a numbered runway tile for the stock SF2V install, then look at a numbered runway tile of JSF_Aggie's enhanced runway textures and you'll see what I mean. FC

I couldn't get past the opening sequence with the BFM against a SAM...just way, WAAAY too Hollywood. Too bad, because I like Owen Wilson and Gene Hackman. FC

You're name had better not be panchobel... FC

Currently, most aircraft projects on temporary hold while I adjust to the SF2/SF2V/SF2E/SF2I standard. Already have most of my enviromentals setup, the cirrus mod working, and working on terrains...including adjusting JSF_Aggies' high res runway tiles to fit on the SF2 runways...the mapping seems to be slightly different with the new runways. Basically, I want my enviroments working right before I start porting my aircraft into them. But I still have a few surprises in store... FC

That's not the newest gun editor. FC

You cannot shoot down missiles in this game. FC

Nope, doesn't affect the sim or downloading at all. Like MigBuster said, all it does is tell the computer to try to open the LOD file with Microsoft Word if you double click on the file. Since there is almost no reason to try to open a LOD file except for very advanced modding issues, you will never encounter an issue. FC

One more thing: The Gen 2 TW sims can still run self contained and do not need to be 'installed' except in the case of a merged install. With each sim, I've installed, then copied the stock directory, then uninstalled the sim and backed up the directory. Even with my merged install, I've done the same thing. FC

It doesn't matter...it doesn't affect using the sim in anyway. FC

Also folks, for those who don't like the idea of going through a bunch of nestled directories to get to stuff, even if it's just the options.ini file, you don't have to. As K and K first mentioned eariler, you can set the options.ini file to refer to a mods folder that is somewhere other than the default Vista "C:\Users\<username>\Saved Games\ThirdWire\StrikeFighters2\blah blah blah...". However, you still have to go there just to get to the options.ini to edit it. However, there are 2 ways to get around this: 1) Simply create a shortcut to the options.ini and place it anywhere or 2) Go into the StrikeFighter2.ini and edit the location of where to look for the options.ini file. The nice thing about this setup is that now my SF2/V/E install is totally self contained. I actually have my universal mods folder inside my SF2 install. So i can copy the SF2 folder to a stick and run it off the stick with just a few edits of the StrikeFighter2.ini and options.ini files. No having to go everywhere if I want a portable copy of SF2. Also, K and K alluded to the idea of only having one core install and run all the mods you want with just dragging and dropping mods into your mods folder. A more elegant solution is running a BAT file. Remember those? I used to run a BAT file for all my sims back in the day so that it would automatically load my TQS/FLCS/RCS profiles for the particular sim I was going to fly...no muss, no fuss. To the end user, it was transparent. It would load the profile, then run the sim, then once I exited the sim, it unloaded the profile. The only problems I would ever have is if the sim did a CTD. Anyway, instead of dragging and dropping your whole mods everytime you want fly a different one, make several option.ini files, each with different names (say optionsOTC.ini, optionsODS.ini, etc). Then create a BAT file which simply has the programming (be advised I haven't created a BAT file in a while, so the terminology is wrong) of 3 lines like: Rename optionsOTC.ini options.ini Run SF2.EXE Rename options.ini optionsOTC.ini Have a shortcut to that BAT file, and there you go. One click shopping...no copying mods, no fiddling with swapping around options.ini everytime you want to play a different mod. FC

Wrench, The, Yep, it pretty much is THAT easy. I have to say, I like the updated arrangements of weapons, guns, and pilots (separate folders). It'll make aircraft mods MUCH easier to add in the future. The hardest part of the whole thing is the initial conversion, especially for weapons. But once you get past that... FC

Yep. FC

I'd say go with the head as the name of the 'head' as a child mesh of the body. That's what I noticed in the stock pilot.LOD files. I suspect the engine automatically animates anything designated as the 'head' of a 'pilot' object. FC