Fubar512

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?

Then obviously, you need the '08 editor.

You asked someone to send you a .lod file, belonging to someone who specifically asked that their work not be distributed by any means, other than by direct download from their site (which requires membership). What part of that statement don't you understand?

The ceiling value can likewise be a limitation, as it imposes a set value based on an agreed upon rate-of-climb minimum, and it's implemented in-game by zeroing thrust above that value.

I see that TK replied to you Here's something that may help illustrate the point both of us are trying to make. Granted, both the mass and thrust involved in the example are way out there compared to what we're dealing with, but it should help hammer home why the sim uses an acceleration curve based on an average value: Now, imagine trying write a dynamics model that allows for that level of complexity

There is no way to accurately calculate it, short of having precise aerodynamic, weight, and thrust data. And, there are always other factors at play, too (such as atmospheric density, attitude and initial velocity when launched, etc). The game engine is not sophisticated enough to model it to that level of fidelity, and I strongly suspect that it simply uses an average, anyway. TK's the person you need to verify that last bit...

Possibly overly conservative drag tables, or even a matter of simply not defining a sufficiant number of data points in said tables. I once used NASA data while penning up a modified flight model for the F-104G (TKs CD0 values for that bird were a bit off, which was unusual), as well as expanded drag tables, and voila... The resulting model matched published time-to-speed acceleration tables and low-altitude Vmax figures for an F-104 with the same powerplant. Wrench can attest to that one...