Fubar512

There is no way to manually "steer" any TV-guided weapons, in this series. TV-Guidance is essentially modeled as fire and forget. Notice that you lose the TV image once the last TV guided weapon is launched or dropped

Add insurance to that. I've got a friend who's an OBGYN. He was literally forced to scale back his practice and give up his O/R privileges, as the malpractice insurance premiums were killing him. He recently admitted that he netted 250K last year, 130 of which was eaten up by his (reduced) insurance premium and income taxes. The latter amounted to almost 80K.

389 lb Bluefin Tuna (as an angler). As a captain, my crew released a 300-400 lb Blue Marlin last Summer. I had one on that may have been a "grander" (1,000 lbs or greater), for a few minutes, back in August of 2006. I derive just as much enjoyment putting others onto fish, as I do from actually fighting them myself. It's the thrill of the hunt, of putting the pieces of the puzzle together. On the freshwater front, there's a reservoir just a few minutes from my home that's home to some large and rather ferocious Tiger Muskies (Pike/Muskellunge hybrids), though I've not really taken advantage of that...stupid me...

You know what's also miraculous, absolutely hilarious, and just about as realistic? Adding a minus sign ( - ) to the gravity value in the environmentsystem.ini. It really perks up missile behavior, not to mention giving every aircraft excellent VTOL capability. Actually, there was a variant of the SA-2E that sported a 15kt warhead. I've modeled it, and then removed it, as it had a nasty habit of appearing at the most inopportune moments....

Do you mean, "vanish" as in no smoke trail? If that's the case, then it's by intent and design.

Actually, there was a B-52 pit, it just never made it past the most rudimentary stages.

You do not have to set up a "dummy" vertical stab, Sparky. You just simply add the necessary anti-yaw parameters and their associated tables to the fuselage section. As for yaw control using the "rudderons", well, that's not hard to do. Again, look at existing rudder entries for guidance.

My apologies, CIACHO, seems that I accidentally edited over your last post while attempting to respond to it. Anyway, Assuming the titles are patched to the same level, the aircraftobject.ini is exactly the same. Only FE & WoI currently have a different one, and that's only true until TK brings the rest of the series up to date. The new parameters in WoI and FE will not work in SF/WoV/WoE, as they are not yet incorporated into the aircraftobject.dll in those earlier titles.

Yeah, right...another 30 day expert making erroneous observations http://forum.combatace.com/index.php?autoc...si&img=3975

First of all, read through a default 'Xterraintargets.ini" file, and see how the SAM launchers and their supporting radar are arranged (offset-wise). Copy those same offsets and locate them on a suitably flat and empty area in your terrain of choice. The trick with Mobile SAM launchers (Chaparral, Sa-7/8/9/Tunguska/Adats/etc), is to redefine their ground object role from "mobile_sam" to "mobile_AAA", which ensures that they'll be placed everywhere, often in the damnedest locations AAA guns will reach up and ruin your day at 30,000 feet, most notably Pasko's 130 mm KS-30, and the 100 mm KS-19 (which is a default Third Wire ground object). 57 & 37 mm are bad just below 10,000 feet, and 23 mm is more of a nuisance than anything else until you get within 2-3000 feet of it (as you've observed). Of course, if you data link (network) the larger AAA weapons as I've done, you're toast Now, you could have found all this information on your own, by searching through the three SF boards as I had suggested.

I believe that's Marcelo's "Ensign Eliminator", or "Gutless Cutlass".

Well, Crusader agrees with you, I just seem to remember reading about that in Belyenko's book (MiG Pilot), some years ago.

Lexx, I believe that you have the firing order backwards.... AFAIK, Soviet doctrine was to fire one radar missile first, and then an IRM, so as to have the IRM follow the radar missile's heat signature (assuming the intended target was beyond the IRM seeker head's detection range, to begin with). This way (at least in theory), the radar missile would be guided to the target by the launch platform, and if that missile happened to be spoofed by the target's ECM, the IRM would by that time be close enough to acquire the primary target's exhaust signature. In which case, it would stand a fair chance of following it home and achieving a kill.

As stated above, there is no salvo mode for AAMs. Fire one missile, keep the target locked, and follow it up with another. I often employ this method, with good results: Lock up a target on radar, launch a SAHM or AHM at it, and then, follow it up with an all-aspect IRM. The key is maintaing radar lock at all times (at least for the SAHM's sake).

The person that might be able to verify, or to dispute those figures, would be Typhoid.

No man. That was not the point of my reply. If anything, we'd rather encourage someone to delve into the dark side (FM creation), than have them turn away in frustration. The issue I have is with the 4Gs at 200 KIAS, Think about that for a second. That literally implies that an F-14A can execute at least a 2.5-3 G maneuver right off the end of the catapult! Another thing, there's a marked difference between an aircraft's limits and performance when it's practically skosh fuel and unarmed, versus carrying a full bag of fuel and loaded for bear. Another issue is one created by the limitations of the game, itself. Ideally, when working with a variable sweep aircraft, you'd have a set of lift and drag tables for each wing sweep setting. Unfortunately, we're stuck with just one set of applicable values. So, we compensate by taking in all the sweep angles, and arriving at an average. We then create Xac tables with values progressing further aft than we otherwise would, had the aircraft been equipped with a conventional wing* (Also, when dealing with the F-14, one must take into consideration the effect of the glove vanes when they deploy). As a result, one is forced to tailor the FM for (accurate) performance within a narrower flight regime, then would otherwise have been possible, had we been able to incorporate tables for multiple sweep angles. So, you can see the dilemma here, at least from the perspective of realism. Hope this helps...it did little more than confuse the crap out of me... *Note: The unwritten rule of thumb is that the Xac table starts 25-30% of the Mac aft of the leading edge of the surface in question, and extends to (and terminates at) about the mid point of the chord.

Caesar, Please do not take offense, but I find those G@speed figures a bit hard to believe. Do you have any vetifiable sources for them, with tables or graphs, (etc)?

This is the second or third time that you've asked this inappropriate question, and you've been warned about it every time.

Someone just made Sparky's day....