Fubar512

EW radars divert, and get destroyed by ARMs meant for SAM radars quite often in my experience. This is especially so in the VietnamSEA terrain.

In the SF1 series, it is, always has been, and always will be, random.

F-15s, MiG-29s, and Su-27s (to name a few) do not have swing wings, and yet are equipped with differential stabs, or elevons. The reason is simple, they augment the normal ailerons on those aircraft at low air speeds. In the case of the Su-27, its ailerons serve a dual purpose, they double as flaps (flaperons), so roll authority is provided by the elevons during takeoff, approach, and landing.

Do you have "threaded oprimaztions" enabled, or disabled, in the Nvidia control panel?

All F-14 variants had differential stabs.

The SA-2 system can only acquire, and guide missiles to, one target at a time. In game (as in and real life), one Fansong radar can provide guidance to the missiles from an adjacent site. The Spoon rest (and other EW radars) really does nothing in game, other than act as a target for ARMs.

SF2 is available only as a digital download from the developer's site: https://store.thirdwire.com/store.htm

A jet-aircraft's engine sound has absolutely nothing to do with "accelerating upward". Its sound (as percieved by someone standing outside) changes in pitch according to turbine RPM, the shape of the inlet and the exhaust, and doppler effect (among many other varibles).

Early development sound fx for KaW, using test models:

There's always been one nagging question: What if Gant (Clint Eastwood) had thought in Latvian, instead?????

That's TKs way of telling us that MTV sucked after 1982

Kevin, you must think in Russian......damnit, do I need to draw you a diagram????

If you hardcode a specific SAM-type and it's supporting radar onto a terrain, you'll never recieve a RHAW warning when it acquires and launches at you. It's a limitation of the series, and no one but the developer can fix that. And don't count on that happening.... SFP1,WoV, and WoE reached their end-of-life update cycle in 2008.

That's the purpose of networking. To ensure that SAM radars and SAM launchers that belong together, show up as a unit.

In my experience, the most likely causes are overly conservative drag values, and drag tables, for all aerodynamic surfaces.

An old test mule...new 3D models are inbound

F-86E by moonlight over the coast

The gaspipe is the ultimate BnZ machine.

I use 4 at 1680x1050 resolution. You can input anything, experiment and see what works best for you. But as Panama Red just stated, SF2 is just soooooo much smoother right out of the box, because of its superior coding and DX10 shaders (in Vista and Windows 7).

I must add that TK's latest FMs (at least for SF2) are quite accurate in their stated limits and values. He states the correct lift and stall values, has accurately calculated the chords for all lift surfaces, and has expanded the various & sundry alpha and mach tables to a higher level of resolution. However, there's still room for improvement in that last area The only issue I have is with changes that were made since the release of SF2I EXP1, to allow all aircraft to depart into spins, has effected the stall modeling of most existing FMs to the point that many behave unrealistically, post-stall.

The card's control panel should have overidden any other settings, but look in the options.ini file, under "graphicsoptions" and set ForceVSyncOff=TRUE

F-86E climbing through the cloud deck MiG-15bis on the prowl over the Yalu East meets West high over North Korea

The FM in question is for an as yet unreleased 3rd party project, so I'm sorry, I cannot share it with anyone at this time. Besides that, it would do you little good, as it's not for a MiG-19. Thirdwire FM "tuning" is a very deep subject, and is somewhat beyond the scope of a simple answer. It would require an entire thread on the knowledge base, one that (other than the basics) is prone to change every time the developer gets it in his mind to do so.

In a perfect Third Wire world, the userlist sets which service an aircraft or ground object may belong to, and the limitednations.ini which nations appear on a given terrainset. However, it's not a perfect TW world, and I've encountered Soviet Meteors and Indian Vampires over North Korea in 1952, limitednation and userlist files notwithstanding...

All one needs to do with a merged install, is to simply run the executables for every title. That creates seperate folders for each and every sim (SF2, SF2V, SF2E, SF2I, EXP1, EXP2, etc etc etc). Then one goes into the desired version's mod folder, and removes whatever models do not belong with a given title/terrainset. One now has separate, and historically accurate titles within a merged install, that can be accessed by simplying clicking on that title's executable. Now, everyone who thinks this is too hard, raise their hands and stand up. Everyone else, hit the floor