Fubar512

You do realize, that there is no way to accurately model FBW (fly by wire) aircraft in this series, right? What we've done in the past, is to limit the model's maneuverability at a given Mach level, by adjusting the center of lift for all aerodynamic surfaces, so that it's impossible to pull past a given value. Even though that FM's getting a bit long in tooth by now, the F-117 in the ODS package is a perfect example of this.

Keep in mind that the AI may attempt to roll at whatever rate you hardcode, even when it's inadvisable (or impossible) for it to do so. For example, the flight manual of any given combat aircraft will advise againt performing a hard rolling manuever when carrying drop tanks or bombs. Some of the FMs we've been penning up recently are hitting the threshold of realism, where you will overstress and possibly tear wings off a model if you attempted such a manuever, on a heavily laden aircraft.

Degrees per second, of course.

I would not mess with those values if I were you...they are global and effect all aircraft. Besides, they can be added directly to the individual data.ini files, and edited there.

Wipe your glasses and look again.....It's not only in the particlesystem.ini, it's the very first entry in that file.

I'm sure many (if not most) of you have seen some of the footage shown here before. However, trust me, it's still worth taking the time to watch this video:

Am I the only one visualizing a scenario, where said video card will be sent aloft trailing from a balloon by a long steel cable, and then recovered by an airbus equipped with a bizarre apparatus attached to its nose (ala the "Thunderball" finale)?

Looks like a "Work of Ant" to me....

Have had it out for a couple of years or so....just place it in your sounds file, and perform the necessary edits to the desired aircraft's avionics.ini file, like so: Under the RWR section, edit the folowing [RWR] LockSound=FanSongLock.wav FansongLock.wav

In real life, RWRs on NATO aircraft identified emitters (and their various modes) by individual sounds. We don't have that option in any flavor of Strike Fighters. Just one track and one lock sound, per aircraft.

If you mean WoI (and not SF2I), that's a DX9 title. Perhaps your graphics adapter cannot handle ThirdWire's implementation of DX10.

What are your system specs? In particular, what garphics card are you running?

Did you try new drivers, and or making adjustments within your graphic adapter's 3D settings?

SFP1E is not for SF2. You need to use Gerwin's CatPack, instead.

Well, that's the correct path. However, even if one makes an error editing the F-104.ini files, the game shouldn't crash...the F-104 variants would simply not show as one of the player's aircraft choices.

I meant, what directory did you install the modded F-104 files into?

You are installing them into the proper folders, right?

Are you running it under DX9, or under DX10?

Helios and why don't they fly correctly in the game engine.....? Perhaps it's because you're not from Heliopolis?

That's a MiG-15 cockpit, BTW, not a MiG-17's. Also, the MiG-19 is a twin-engined aircraft.

Well, considering that I'm less than 7 miles (as the crow flies) from the Atlantic, and some 300+ road miles south of you, our 62+ inch total snowfall (so far this season) ain't too shabby

As I was once a network administrator for the NJ subsidiary of a major insurance company, there's probably NOTHING NEW that you can tell me in regards to that subject (nor of the diificulties one might experience while attempting to navigate Microsoft's virtual quagmire). Worst case scenario; Simply download and install the latest DirectX User runtime for your OS. http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3b170b25-abab-4bc3-ae91-50ceb6d8fa8d

What OS? Simply updating the DirectX 9 on your system will fix the issue.

http://www.thirdwire.net/files/dl/WeaponEditor_042406.zip

Then OBVIOUSLY you're not running at the '08 level, so try the '06 weapons editor. Now, that wan't so hard, was it?