SupGen

Jesus, this guy needs to get a job...making movies!

Hear, hear...well said that man.

paulo, let me just start by saying THANK YOU for the 102nd FIS NYANG Skin; anybody who's paid any attention to my obsessions knows I'm a Long Island boy; born there, grew up there, had uncles and cousins who worked for both Grumman and Republic. For those who may have wondered about my little obsession with the Deuce, both the Air Force and the ANG flew it from Suffolk AFB,about 40-50 miles from my house as the crow (or Deuce) flies, the Air Force's 2nd and 5th FIS from 1956 (the year I was born) to 1960, and the NYANG's 102nd FIS from 1972 to 1975 (I graduated High school in 1974; sort of ), Convair, although a west coast company was a part of my youth as much as Grumman and Republic were. That being said, paulo your data ini.s are missing the SpecificStationCode=RAZ, that allows all kinda funny things to go on with the loadouts. The other thing (and this is my fault, I should have gotten in touch with you when I first read you were going to update this pack), I was working on one, final update to this magnificent aircraft; unfortunately it required renaming and consolidating the types of aircraft. It turns out that the Case XX Wing aircraft were the tail end of the late 50's production run, the (69) thing is totally wrong, not only that, but it was the most important modification made to the plane after the Area Rule. Nearly 350 aircraft (from October 1957) were produced to this standard and could fly higher, faster than the previous Case X Wing aircraft. paulo, I'm attaching my latest update; maybe you could integrate it with your beautiful skin-pack? (Also, the edit to Rocket Tray3 leaves a rocket hanging outside of the aircraft.)

Can we like, hire a bodyguard or somethin' for Ravenclaw...I mean if anything happens to him before he uploads this stuff there's gonna be no one left here...we'll all have killed ourselves.

Just upgraded to Platinum, dude.

Stipe, you have to open the "common files" folder and copy/paste the contents to each of the aircraft folders.

This is from NeverEnough's post on the previous page. Read it!: http://www.mca-marines.org/gazette/article/get-over-it-we-are-not-all-created-equal

Yeah, using this tool (I think correctly), the R-37 tops out at Mach 7.54. I think things would be starting to melt, there. The third-party AIM-54s hit almost Mach 6, so far it seems like I can get realistic speeds/ranges by balancing the Booster and Sustainer entries. For the AIM-54 it isn't necessary for the tool to show full maximum range as it doesn't model loft profiles. Using Booster G/Duration of 16.85/6 and Sustainer G/Duration of 4.0/50 for the AIM-54CE gave me a top speed of 1139.44 M/S, or Mach 3.44. The range given by the tool was only 75277.88 Meters-BUT I was able to fire at 99+ miles with a 60% kill ratio. That seems pretty "realistic"-or at least pretty much in the ballpark of what we've been led to expect. Try this thing out, it's one cool tool.

Back in the 70's I served in the Army Infantry in Alaska in a straight-leg unit. No tracks, no trucks, you walked in the summer and skied in the winter. Mortar platoon, A Co, 1st Bn 60th Inf Regt. As a member of a Mortar unit, I, and everybody else had to carry an M-16, Load Bearing Equipment w/ ammo etc., large Alice pack, AND at least one part of the broken-down gun. Every piece of that f****n thing weighed 50-60 Lbs, and then of course there was also ammo for the gun; no point in humpin' that f***er if you didn't hump some rounds for it too. This was up and down the mountainous terrain of Alaska. At the time, I was 185 Lbs of hard-core and there were times I thought it was going to kill me. Thank god we didn't have combat to deal with as well. I hate to be the one to tell ya all this, but if there is a woman on this planet who can do what we did, I certainly haven't met her yet. Frankly, I don't think she exists. If someone can't hump their gear plus a base plate, or a gun tube, or a bipod; if they can't carry their share of ammo, somebody else has to do it. It's not only not fair to those who can, but it can be dangerous. When everyone is already stretched to the limit, asking people to pick up someone else's slack is just plain stupid. For this reason, if no other, no one has a "right" to serve in the front lines. To do what they can, yes. But not if they are going to be a burden in any way, in any measure, to anyone. Our military, for the most part, has not engaged in large scale, desperate, the issue-is-in-doubt combat since Vietnam, and before that Korea and WWII. And before you jump on me about that, read up on the Ia Drang, A Shau, the Frozen Chosin, the Bulge and don't leave out the Russian Front. Guy Sajer's The Forgotten Soldier will give you an interesting Frenchman-in-the-Wermacht perspective on desperation, for sure. In that kind of combat, any weakness, any distraction, any chink in your armor can spell the difference between victory and defeat, and more to the point, survival or death. The men at the tip of the spear have it hard enough without us making it harder on them so we can stroke ourselves and tell each other how enlightened we are. Fire away.

Well, I did a little mooching around and found myself here: http://search.yahoo....avebooks.co.uk/ . Cleave Books. Conversions for just about anything. Turns out the Gravity entry is the value for 1g in Meters/Second/2. The Sonic entry I think is the value for Mach 1; it's 343 M/S, Wiki gives Mach 1 at Sea Level as 340.3. I think the IAS/TAS is a ratio. This thing is actualy kinda cool, I'm gonna take EricJ's advice and go shoot some stuff up and see how well it really works.

Here: http://combatace.com...ange-simulator/ To be honest, I don't really see how this thing works; what is sonic speed? What does the gravity entry signify? There are separate entries for Gs of acceleration. What about the IAS/TAS entry; is that a ratio or a constant? Some pointers would be appreciated.

Yeah, Mac, you're absolutely right; slick cowboy add this to the Fuselage Systems entries: SystemName[014]=ALQ51 SystemName[015]=ChaffDispenser1

Well, they were fitted with RWRs during the 1990 update, but I couldn't find any reference to Chaff/Flare dispensers. However, the ThirdWire F-8E_66 does have dispensers and a jammer. Add this after the Weapons Station entries in the Data ini.: [ALQ51] SystemType=ECM_JAMMER JammerType=DECEPTIVE_JAMMER JammerStrength=25.0 MinFreq=2.8 MaxFreq=3.2 CanJamCW=FALSE [ChaffDispenser1] SystemType=DECOY_DISPENSER EjectPosition=0.00,-3.21,-0.88 EjectVelocity=0.00,0.00,-10.00 NumChaff=60 NumFlare=0 The dispenser only has Chaff, but Flares are easily added.

HAH!!! Beautiful.

Always a plus.

Thanks, FC.

I never said it wasn't bigger....

Crusader wins the kewpie doll! The version does matter; Brain32's has the correct DetectSystem entries in the Data ini., all the earlier versions had this: RadarType=S-800Zaslon. That might be the RadarName but RadarType=AIR_INTERCEPT; just tested it and got locked up at around 50 miles (90KM); Foxhounds were making a beeline for me from all over the map!

Sorry, I screwed up on the NodeNames; this should work. [ClockHour] Type=CLOCK_HOUR NodeName=needle_clock_hr MovementType=ROTATION_Z Set[01].Position=-100.0 Set[01].Value=0.0 Set[02].Position=-99.0 Set[02].Value=1.0 [ClockMinute] Type=CLOCK_MINUTE NodeName=needle_clock_min MovementType=ROTATION_Z Set[01].Position=-100.0 Set[01].Value=0.0 Set[02].Position=-99.0 Set[02].Value=1.0 [ClockSecond] Type=CLOCK_SECOND NodeName=needle_clock_sec MovementType=ROTATION_Z Set[01].Position=-100.0 Set[01].Value=0.0 Set[02].Position=-99.0 Set[02].Value=1.0

Put ClockHour, Minute, and Second back in the Instrument list. Instrument[021]=TurnIndicator Instrument[022]=ClockHour Instrument[023]=ClockMinute Instrument[024]=ClockSecond Instrument[025]=CautionLight Add this: Instrument[055]=RadarScope Then, use these entries. [ClockHour] Type=CLOCK_HOUR NodeName=needle_clock_hour MovementType=ROTATION_Z Set[01].Position=-100.0 Set[01].Value=0.0 Set[02].Position=-99.0 Set[02].Value=1.0 [ClockMinute] Type=CLOCK_MINUTE NodeName=needle_clock_minute MovementType=ROTATION_Z Set[01].Position=-100.0 Set[01].Value=0.0 Set[02].Position=-99.0 Set[02].Value=1.0 [ClockSecond] Type=CLOCK_SECOND NodeName=needle_clock_second MovementType=ROTATION_Z Set[01].Position=-100.0 Set[01].Value=0.0 Set[02].Position=-99.0 Set[02].Value=1.0 [RadarScope] Type=RADAR_SCOPE NodeName=Clock See if that works.

Which version are you using? Updated SF1 or Brain32's SF2 version? Edit: I don't think the version matters. Try adding this line under RadarData: StartRangeSetting=5. Neither has it; without it the Radar turns on at RangeSetting[1]=10 (KMs), this would explain why it waits so long to react.

ummm...That was actualy pretty sucessful; the number of real life pilots that got four kills in a single mission was pretty small. That being said, from the looks of things, you spent most of that fight going dangerously slow, well below the Hun's corner speed. In large part, this is because you were fighting the AI's fight; you were letting them lead you around by the nose, so to speak. You were flying pure pursuit. This isn't the most efficient way to do it in any aircraft; in the Hun it's the worst. The SuperSabre doesn't benefit from much in the way of Area Ruling, that's why it "bleeds speed in the turns and takes forever to accelerate". You need to get outside of the Mig's plane of Motion, get your speed back up, and come back for another pass. In other words, Boom and Zoom rather than Yank and Bank. If you want a real pro's input on all this, go here: http://simhq.com/_air/acc_library.html#briefing and read at least all four parts of "It's All A Matter Of Perspective". You won't regret it.

Roger, I think you can cycle thru ground objects and target the one you want by pressing the E key.

Oh man, Padlock!? I'm sorry, I just didn't follow you there. Roger, do me a favor, click that link and read those articles yourself, the info there is timeless, and applys if you use TrackIR or not. I quote " Efficient BFM takes full advantage of the effect of gravity as it affects turn radius and turn rate. Efficient BFM almost always involves split-plane maneuvering. Split-plane maneuvers are those flown out of the opponent's plane of motion...i.e. three-dimensional maneuvers. Efficient BFM is almost always lead or lag pursuit, and seldom is pure pursuit. As with most things in life, there is good news and bad news in using padlock. As good as padlock views are, there still remain some shortcomings. Two are significant...the tendency to use the view to fly in-plane with the opponent, and the amount of time needed to interpret the view. When padlock is used to orient the lift vector at the opponent, the end result is a pure pursuit course that is nothing more than a sophisticated form of using the "pointed x"." Let me first say that I suck at this...and yet, using this I suck less than the other guy. When I first started playing StrikeFighters a couple of years ago, I was pretty much at the mercy of the AI...not that it has any. Believe me, after attempting to implement the techniques and procedures outlined here, my sucess ratio went through the roof. Almost every one of the R/L techniques Col. Bush refers to applys to Air Combat in StrikeFighters...utilizing this stuff can't help but make you a better Sim pilot. Read these articles, if you think it was pointless, you can throw tomatoes at me and I won't say a word.

Understood, however there ain't much difference between 12.7 and 14.5MM rounds, ballisticly, and the guy referred to at the beginning of this thread was probably not killed by either; the Gazelle is basicly unarmored.