Fubar512

The maneuver's also described in "Scream of Eagles", as is another one, that's also based on an intentional departure with the F-4.

No. Those are leftover entries from SF1.

"The initial colour scheme worn by the AV-MF Yak-38 consisted of dark green anti-corrosion paint on the undersides of the aircraft, with dark blue upper surfaces. This was later replaced by a light grey over dark grey scheme, frequently associated with the Yak-38M. An unusual green-over-silver "tiger" camouflage scheme, reportedly seen on an aircraft onboard Leningrad in 1986, was probably applied for one cruise only. Special camouflage schemes may also have been applied to aircraft involved in the Romb-1 trials in Afghanistan in 1980." Souce: http://en.wikipedia.org/wiki/Yakovlev_Yak-38

Krizis really endowed this model with great damage-modeling....this is but a mere hint of it....

Nvidia produces a recommended reference design, though it's up to the individual hardware vendors to set memory and core clock speeds, as they're the ones that are responsible for any warranty issues. For example, my graphics card is a factory (EVGA) "superclocked" version, that has 20% higher clock speeds than the Nvidia reference design.

From Wikipedia: Armament Guns: GSh-23L 23mm gun pod (GP-9). This gun could be carried in one or two PUK-23-250 pods fixed under the external pylons of wings. Bombs: two FAB-500 or four FAB-250 under pylons, two incendiary ZB-500, or two nuclear tactical RN-28. Rockets: various types of rockets (up to 240 mm). Missiles: two anti-ship or air-to-surface Kh-23. Each missile weighed 285 kg, was radiocontrolled and had 10 kilometres of range. The Kh-23 requires a guidance pod on one of the pylons. R-60 or R-60M air-to-air missiles could be carried under the external pylons. Other: external tanks.

What that tells me, is that your graphics adapter is downclocked from the Nvidia reference design. http://www.nvidia.com/object/geforce_8600M.html

CPU-Z has a graphics tab that provides information about the graphics adapter. Make sure that it reports the following: Core Clock (MHz) 600 Shader Clock (MHz) 1200 Memory Clock (MHz) 700 Memory Size 512MB Memory Interface 128-bit

Yak-38 "Forger" model undergoing carrier qualification tests: Yak_Carqual.wmv Short video on the Forger and the Kiev:

Marcelo & Krizis could well decide to release their works for SF1, though SF2 is currently multi-threaded, and the next expansion pack and subsequent patches will expand on this (it will, according to TK, finally utilize all cores of a quad or hexa-core CPU). The Kiev itself weighs in at over 119,000 ploys, and sports 4096x4096 textures (as does the Yak38). So, they're both best run on a 64-bit operating system (better RAM utilization), and a quad-core processor. Even after reducing the textures to .DDS format, they both still place a significant load on the CPU and graphics system.

I've sent the final data.ini and .DDS-format skins (thank you, Brain32 Lindr, and Krizis) to Marcelo, so it may be out soon. The Yak-38's FM still needs to be tweaked to SF2-standards, and of course, it must be sent back to Krizis for final consideration and release. A short video of the Kiev's layered air defenses in action...gunfire and flak effects by Stary: KievFinal.wmv

PCI latency issues. I once experienced this same issue a few years ago, when I was running SF:P1 on a system based on an N-Force chipset. Adjusting the PCI-latency of my video card down from 256 to 64 helped, as did ensuring that my TB Santa Cruz sound card was set at 32. http://www.soundonsound.com/sos/oct04/articles/pcnotes.htm

Strafing run against a floating buzz-saw: The tracer effects are from Stary's WW1 effects pack.

Previous history indicates that this dearth of newbs is normal with TW sims.....the floodgates will reopen as soon as TK releases a new title (or addon).

An aircraft that can be rather easily purchased (used) on the civilian market? No big deal. It's good business.

Oli was an extremely talanted modeler and a good friend, to boot. I recall asking him to map ground object model for me, when he had some free time. Despite his busy schedule, he sent the completed source and .lod files back to me, a scant few hours later! Here's to you, my friend

Since there's no "FE2 Screenshot Thread" (yet), I'd thought that I'd post this here:

My condolences, Ed. to your brother for his selflessness and bravery.

Krizis's Yak-38, onboard MarcFighter's Kiev:

Gee, I don't an issue with that...oh wait.....I know why.....

The engagement radar (sometimes referred to as the "height finder") is the radar that is used provide direct guidance to the missile. In TW-game parlance, it's the "SAM" radar. The acquisition radar's function in real-life, by definition is (as the name implies) to acquire targets based on the bearing info provided by the search radar, and to hand those targets off to the engagement radar. Though there is no object role so defined in the series, ground objects (namely ships) may be equipped with dedicated search, track, and height finder units. MarcFighter's Kiev is an example of this. Erik Gen's Nike site is equipped with all three of the aforementioned radar types.

Those are executable files, not "game engines". To answer your original question (with another question), did you notice the correlation between name length and the file size?