PFunk

LOL. I wonder what THAT does. I'm working on converting the J-31 Chinese stealth fighter that's in the SFP1 section to SF2 use and I was just curious about how they worked. It's just going to take some testing to make it a little more accurate because SF2 radar AI wasn't really built to handle 'stealth'. I'd like for SAM's to at least give it a look. Right now, when I fly over a target area, I'm invisible to radar and I don't think that's an entirely accurate picture of how it works. Furthermore, the F-22 and F-35 aren't really 'stealth' as much as they are 'low-observable', meaning radars can picket them up eventually. And, now that I have actually discovered how the engine populates air defenses in the game (thanks to an entirely different thread), that's going to affect how I view terrains and target areas.

I cannot wait to fly this beast.

Some of those values seem....optimistic. Wasn't one of the Nighthawks shot down over Serbia with a Vietnam-era SA-3?

I know in the data.ini files of all "stealth" aircraft, there is an RCS and IR entry that I presume reduces the radar and heat signatures of the plane. I presume, the smaller the number the greater the "stealth"? I.e. 0.1 means 10% of the radar cross section?

That would be awesome if we got a Viggen here.

Both of you have a point, good and bad for both. I do love the high resolution decals, though.

Wasn't being a smart guy, I actually do appreciate the guys who put one together with insignia decals and not applying them directly to the skin. Just want them to know that extra mile is appreciated.

You know who you are. You're the guys who, when you make an airplane, you include skins with the mesh details and proper decaling. This means I can fly anything for any air force and the insignia show up. Now, I understand why some folks directly apply insignia to the skins. It often looks more realistic and YOU KNOW IT WILL WORK. It's just a pain for those of us who want to fly an airplane for one military and someone's else's insignia are on the wings. Thanks for going the extra mile for us 'what-if' guys.

Yeah. That's one way to go about it.

I never knew the hard number until just now. Thanks. This is going to definitely affect how I look at terrains from here on.

Wow. File that one next to "spotted a leprechaun".

EDIT: Never mind. Read the answer in the 2nd post. By the way, thank you all for the advice, and keeping the community well-informed on how to get the most out of this sim.

It's well-known that the #4 aircraft in formation doesn't engage with air to air targets. If you are tasked with an air to air mission, is it advisable to leave him at home or has anyone altered the AI to get him to fire on something?

What does the Redux Pack do, increase detection range?

It would cost more to restart a production line in the F-22. Not only that, the hardware that goes into the F-35 is far more advanced than even the Raptor.

Any carrier action in that map?

Those exhaust tail pieces don't look that stealthy.

Boeing really hit one out of the park.

Happy Christmas and Chag Sameach!

The X-32 was less capable. Looking at that Advanced Hornet...going into a knife fight with the induced drag and weight of a giant external pod seems like a really bad idea.

To be fair, we were getting an idiot either way.

Comparable?

Pretty much. The F-14 avionics .dll file was built to mimic the "track 24, engage 6" ability of the AWG-9 radar. It also took away the A2G radar. TW assumed the only people shooting AHM missiles would be the player and friendly AI, not the enemy. You can fly modern scenarios, but your opponents are going to blow you out of the sky with AHM missiles and you will never know what happened. Force opponents to use only SAHM missiles. Which isn't whollyy inaccurate.

Ah, you've fallen victim to the "AHM cheat". The SF2 avionics .dll file was never updated to include AHM functionality. It will only warn you if an SAHM has been fired at you. There are a couple of things you can do to fix this. 1. Change all Red-side AHM-guided missiles to SAHM guidance. (A pain to do...) 2. Don't fly any scenarios past 1992. (Easier, but restrictive)

It's getting harder and harder to even create new places to fly. As Wrench pointed out, even finding the .DEM files for the Terrain Editor to read is getting to be a chore. Then you have to contend with the Terrain Editor itself, which is hardly the easiest thing in the world to do. Target population takes forever in order to make a halfway decent place to fly. I just recently got my Alienware back from Dell and they replaced the mainboard and reinstalled my OS. I'm actually contemplating not reinstalling SF2 at all and focusing on DCS. Even with its limitations, it has the advantage of still being supported. CB