gbnavy61

...and skull. "Charlie Foxtrot, Alpha Bravo, adjust fire 50 meters left. Fire for effect!"

Mark, I use the Saitek X52 Joystick/Throttle combo. I've kinda thought about getting some pedals, but never felt like coughing up the change required. I've kinda got my own HOTAS setup with radar, weapons, countermeasure controls on the throttle or stick - the only things I actually have to take a hand off to move are the gear, flaps and hook. To get around the lack of pedals, I've thrown my rudders onto the L/R functions of the lower HAT switch. Honestly, I rarely use rudder. It probably makes a slight impact on some jets, but you can really get away without using any - except maybe a little here or there to aid with gunsight tracking. If you want to turn, just roll and pull - you'll be fine. I think there may be a limited amount of yaw damping in general for jets in the game, though I don't think it's really "auto rudder." I don't really know the answer to any of your other questions, since I don't have pedals and I've only used this setup to play WOV and WOI. So, I will let someone else field those.

I'm looking at moving some jets over from WOV to WOI. I've got the .cat extractor to open up the objectdata.cat, but what I don't know is what are all the files I would need to move a single aircraft over. I'm looking at getting the A-4F and moving it to WOI, but I could also do this for other jets later. Any help would be appreciated. Thanks. (PS - I realize there is an A-4F in WOI already, but I was looking to get some USN skins on them. So far, the addon A-4F skins I've tried to bring over for the stock WOV A-4F work fine on the WOI A-4F except that all the decal coordinates are off. Rather than trying to fix all the decals blindly, I thought this might be the easier route to go. So, if anyone has an alternative suggestion, I'm open to that as well. However, I would still like to know the files needed to move other aircraft over - like the F-4B/J.)

Where are they at TW? I'm not seeing them. I may not be looking in the right place.

I did not know that was an option. Huh. Guess I never noticed that in the d/l section. Thanks.

I sit corrected.

Not to mention that technically, the Gregorian calendar that we use, is off by several years at least. I believe it is already 2012 or later according to historical research. If I remember correctly, I believe the actual year 0 is by our calendar 3 or 4 BC. There may be small elements of truth to those "predictions" but I tend to agree with Silverbolt in general. Anyway, I think Russia's interests/actions merely set the stage for future conflicts, including but not limited to a new (or continued, if you like) Cold War. Russia's ties with Iran as well as its actions in Georgia set the stage for plenty of potential conflicts in the Middle East - mostly related to energy resources, though there are security issues with Israel, even Iraq, that could come into play as well. And that is by no means a comprehensive list. There's security issues between N and S Korea, areas of Africa, etc. I see potential for a lot of wars in the future, but I seriously doubt we will see a Doomsday scenario. I think countries that have many nuclear weapons realize there is little profit in using them. This can be seen in recent history. Although The Bomb was dropped twice in anger in WWII, no one has used it since then. And there certainly hasn't been any shortage of war. The wildcard comes in from small nations without much to lose, or more likely terrorists. Large or established nations would rather fight a conventional war that they have a chance of winning and gaining something from their efforts.

I highly doubt that is accurate. Not trying to start a pissing contest here, just share information. There is one instance I recall reading about from the Iran-Iraq war where an F-14 made a successful landing back at base with most of a wing shot off and the engine on that side out as well. So, an Iranian pilot landed the jet single-engine, single-wing - and those were the less than stellar TF-30 engines. Also, there were plenty of test flights made with the Tomcat in an asymmetrical wing sweep configuration and it still flies just fine. They also proved that it could be landed safely with one wing completely swept and the other unswept. Back to topic. *** I'll amend my first answer to include the F-14. Now that I think of it, I've only been shot down once by a sneaky SAM in the Turkey.

Well, since I've really only dabbled in campaign mode in WOI, I'd have to say the F-4E. Flown several A-A missions always coming away with at least one kill. Flown a few A-G sorties, but I'm not a huge fan of the Rhino for moving mud. However, I was able to dead stick an F-4 into a nice landing after running her out of gas dogfighting a Hunter. Although, in single missions, I've been having a blast lately with the mighty Intruder. I took my A-6E over Egypt just yesterday and completely pasted this runway w/ my Mk 82s. Then, since I still had 6 left, I dropped them all in a cluster of parked MiG-21s. I think 1 MiG was left out of about a dozen. Got a Navy Cross for the effort.

You should call up the AWACS and get a vector out of that weather.

There's basically 4 A-A radar modes - Search, Track While Scan (TWS), Acquisition, and Boresight. Generally, when you use the radar you'll step the modes down in that order as you close with the bandits. Search - gives you the longest range, allows you to see the "big picture" and is limited to something like 30 degrees either side of the nose and about 10 degrees above and below the nose. Selecting and locking a contact activates Acquisition mode. TWS - This mode allows you to start tracking a single target, giving you info on that specific target, while still presenting the contact echoes from Search mode. Acquisition - Once you've selected a contact, this mode engages automatically when you try to lock that contact. Now the info that is displayed changes. Your radar doesn't care about anything else except that one contact. A wide vertical line appears over the contact's position that gives angle off the nose (L or R from centerline) and range info to the contact (based on what range you have selected, the target blip will appear at a proportional location - for example, if your range is set to 50nm, when the target blip is halfway down the scope it will be at 25nm). A thin horizontal line will appear on the vertical line and will give weapon's max range (so, when the target is above this line, it will be out of range, at or below = in range). There may be a min range tick, but I don't remember for certain. In any case, when you have gone inside your weapon's min range with a radar lock, you will get a big X across the scope indicating you can't fire because your weapon will not have time to arm, etc. before reaching the target. A little dot also appears on the scope which gives the target's position relative to the nose (i.e. when the dot is near the bottom of the scope, you have your nose above the target, center of the scope = nose on the target). Two circles also appear on the scope. The larger, outer circle has a break in it and, based on the clock position of the break, tells you if you are opening, maintaining, or closing distance with your target. 12 o'clock is maintaining distance, clockwise from there is closing, counterclockwise is opening. The inner circle gives you the limits of the seeker head for the missile you are using, I believe. The moral of the story there is to put the little dot as close to the middle of the circle as possible when shooting. Boresight - Limited to 10nm range, this mode is best used in close-range combat (also why this mode may be referred to as ACM or Dogfight mode). Basically, the antenna is pointed forward scanning a thin horizontal slice (3 degrees L and R) but a larger vertical slice. As soon as a contact comes within the envelope of the scan, the radar kicks to Acquisition mode. Some general radar takeaways: - Depending on your settings, you can't always tell if you've locked a bandit or a friendly, so be sure you're not about to ruin your buddy's day. - The longer the range setting, the bigger chunk of sky you're scanning. For example, scanning 30 degrees L/R at 10nm range covers roughly 5nm wide, whereas at 20nm you cover 10nm. Same for the vertical chunk. - Chaff, ground clutter, and in WOI beaming, can break a lock by your radar. Be prepared to recaquire. If possible, engage a BVR target co-altitude or slightly below to avoid a look-down situation where ground clutter (radar returns from the ground) can interfere. - Flying around with your radar on makes you more visible, so use it judiciously. As the others have said, the basic answer to your question is: radar on, search, select contact with brackets, lock, when in range - shoot, make bandit go away.

ALF - He has the experience. Plus, we can finally get rid of all the cats - tasty cats.

That's a nice looking Goshawk. But, it should say TW-2 on the side instead of USS Forrestal.

I am wondering how EO guided missiles (like AGM-65s) and LGBs are used in the confines of the game. I have all my gameplay settings to 'Hard' and find that when I take the aforementioned weapons on a mission, they are pretty much useless because I can't seem to lock onto a target to fire them. I recall reading somewhere a while back that the game engine allows you to take guided bombs and AGMs without pods and you can still hit the primary target. If you take a pod, you can hit multiple targets. What I'm wondering is, because of the 'Hard' settings, is this preventing me from using these weapons at all? (Flying WOI using the May 08 MFWP and a bunch of addon jets.)

Thanks gents.

Do you need to have the visual targeting off of hard for these to work properly?

Check your first post, for starters.

I understand what you're saying. My little blurb there comes from something I read (in a book) that said the Tomcat was more accurate because the RIO's display was larger and allowed him better resolution than a Strike Eagle WSO to pick out targets. Not that a bomb being put into a specific window would make much of a difference, but the fact that a high level of accuracy was available wasn't a shortcoming. Also, I read in the same book, at least one event where a Tomcat was able to hit a target that likely couldn't have been identified from another platform. Literally, the ground controllers were describing a building's exterior details (like number of windows) to help the Tomcats find the specific building to hit amid the others. Regardless, I definitely see that as a ground-pounder, one wouldn't care who delivers the bombs or how, he'd just want them on target in a timely manner. I also think that you're right - for a 2000lb bomb versus building, it doesn't matter what window it goes into, the building loses. *** I had to watch The Great Santini for a class once. It had about 4 milliseconds of F-4 footage in it. From what I remember those were the better parts of the movie. The story was somewhat engrossing, but I felt let down in the end. It was just kind of a weird movie. Then again, I haven't watched it in a while.

I see that little has changed in the last few days. Russia is still carving up and enveloping what's left of Georgia.

Ditto to the above two. What's your deal, Streak?

My feeling is that there won't be peace until Russia has what it wants. Or, by some remote chance, Western Europe grows a pair and tells Russia to stop.

I think it's about time for Grumman to crank out the next Cat.

That freakin' rocks! Look out, Red Baron.

First, while I know the AIM-54 was an expensive missile, I got the impression that not using them was in the long run more expensive than firing them off. So, that arguement in and of itself, doesn't seem to hold up very well. As to the increased likelihood of a blue on blue kill, I'm not sure how the Phoenix increased that risk. One also has to consider how politics played into Desert Storm. Perhaps you weren't aware, but the USAF was managing the overall air-to-air mission tasking. I don't think it's too far a stretch to think that F-15's got the lion's share of the kills becase they were the only ones providing CAPs in the likely engagement areas. In total, the Navy only got 2 air-to-air kills during Desert Storm, both by F/A-18s, on a single mission. Apart from that, have you heard of the term "MiG repellant?" That is what the AWG-9 was to Iraqi aircraft during Desert Storm. They had learned the hard way throughout the 1980's what a Tomcat could do if you didn't just run away from it. So, I guess we also have to thank Iran for spoiling the Tomcat's chances for kills. But, in spite of the Israelis successes and the F-15's combat record, it doesn't seem like the Iraqi pilots were loathe to engage them. Perhaps they learned that later, though. For OEF and OIF, the Tomcat was by no means "benched." During OEF, due to the long flights into Afghanistan and lack of Air Force bases in close proximity, the Tomcat was practically the only tactical jet flying up there for a good while. Not only could it bomb accurately, but it could bomb more accurately than F-15Es - which is why for delicate targets in populated areas, FACs called for Tomcats. The analogy I've heard is: the Strike Eagle could put a bomb into a building; the Tomcat could put a bomb in the 3rd floor window, second from the left. --- I'm sure I don't have to say this, but given the choice, I'd go Super Tomcat all day, every day.

Walsh - "No, Mr. President. You want your palm turned outward. And you're hitting much too high." Actually, it just looks like he's reading notes off his hand. Like cheating for a high school math test.