Fubar512

Too late, the SF2I patch was uploaded at Third Wire's site earlier this evening.

Find in this image: Spanish Cat Class Two dogs "Never get outta the boat" An angry bronze Titan (from "Jason and the Argonauts') Alpha Leonis and a few others.....

That's fine, as long as you're happy with being limited to only two wingsweep angles.

There's no provision for manual control of wing sweep angle in this series.

Technically, all the 2 gen models will work in any 2 gen title (SF2,2V,2E,2I), but a model may require title-specific files such as entire cockpits, or specific cockpit gages, that are only contained within the catalog files of that specific game.

The series 2 sims (SF2, SF2V, etc.) were written with Vista and Windows 7 in mind. They can make use of DX10 (advanced shaders), and they take advantge of the "saved games" folder path, that was intro'd with Vista.

Only those structures which are terrain objects (those that have their own .lod and .ini files, and are therefore handled as solid objects), can cast shadows. Quite a few structures are alpha objects (similar to trees) and are defined within the various .tod files. In a nutshell, because alpha objects do not have .lods and .ini files associated with them (which would in turn define their shapes and dimensions), there's nothing "there" to tell the game engine when, where, and how to cast shadows.

In a word, no. Only one missile launcher pitch and yaw axis allowed per model. Now, on that model, you're in luck, as its SAM launchers utilize a VLS system (pitch=90.0,Yaw=0.0 Yawlimited=true, Pitchlimited=true, etc.). But, you cannot use the ASM launcher and the SAM launcher positions on the same model, you'd need to create two separate models, one tasked for an antiship mission, and another for airdefense.

Are you implying that the F-15C FM might be somewhat unrealistic?

It was a pleasure knowing Oli and working with him. He was a true gentleman.

None of Third Wire's core files are contained within any ODS distribution. The .ini files, and .bitmaps that are used with existing TW models, are all either, modded or unique to ODS.

The pilot in the image must be thinking "Oy vey, I must have made a wrong turn at Galilee!"

190.38 Drivers, and FSAA works fine for me.

Please tell me that you took a few images, while you were refueling them, with the Giza Plateau as a backdrop....

At the height of the stock market meltdown during the Autumn of 2008, an executive at a large trading firm kept receiving text messages and emails from an irate client. They were all the same, nothing more than a cryptic, and seemingly undecipherable alpha-numeric sequence: 370HSSV 0773H The executive kept pondering the meaning of this. He checked through thousands of transactions and account numbers, and could not find a match. Finally, during a board meeting, his cell phone buzzed with an incoming text message, and again, he saw the strange message: 370HSSV 0773H. Baffled and upset, the exec showed the message to his colleagues, who were just as perplexed. One of them jotted down the sequence, and handed the slip to a young intern, who deciphered it instantly. "You've been reading it upside down", he proclaimed. : )

Judging by the behavior of enemy AI, I'd say that they only switch on their jammers when they're targeted (locked on).

Mach 2 is glacially slow, compared to 186,262 miles per second.

A real Cat.

LightSrcOffset=0.00,0.00,0.00 I believe that this 0,0,0 value means that the light appears "centered" from every viewing angle, in other words, it's a point source. LightSrcRange=0.5 Distance light casts its light on the model's airframe or surrounding objects (0.5 meters in this case).

You need to extract the airfield lods, bitmaps, and .ini files from the series 1 terrain(s) that you wish to use, and move them to the terrain folder.

The .ini and .lod files in SF2x are in unicode, and as such, will not work in series 1. While you can recompile the .ini files from unicode to ANSI, you cannot do the same for the .lod files. The forest and tree mod will work in SF2x.

That appears to be an issue from a mod, and is not issue from a default install. You'll need to adjust the clipping distance in your flightengine.ini to compensate.

Typical MiG-29A loadout, through the early 1990's was 4 x AA-8 (R-60), and 2 x AA-10 (R-27). To the best of my knowledge, AA-11 Archer was carried sometime after 1991-92. The MiG-29 never carried the Atoll (AA-2), as it was all but obsolete by the time the Fulcrum entered service.

Please stop posting game-related questions in the pub. We have game related (including ThirdWire-specific) forums just for that purpose....post your questions there.

Someone posted this site on another forum that I'm a member of. It's aerial views of sea life, etc, along the New England and Northeast coasts. Some of the shots are flat out amazing, including the attached image, of Bluefin Tuna swimming in "hunting" formation. Sights such as these, is the reason that I keep going back out "there": http://www.oceanaerials.com/index.html