Eihort

Osprey isn't known for publishing garbage. I also wouldn't go quoting parts of Mr. Forczyk's review either. That is probably the most inaccurate review I've ever read, and some of his counterpoints are completely rediculous. True, everything in the book has to be taken with a grain of salt, and the authors are up front about the difficulty in finding any sort of possible confirmation in the reports. However, there is some crediblity in that they go to some lengths to protect the identities of their sources. The only line is supposed to be the party line, and pilots giving interviews about the conflict goes against that. Particularly the parts of Hawk batteries commiting fratricide, and a few pilots that defected with their F-14s for reasons below. Many of these pilots had no love for the Islamic government, only for Iran. After the revolution, and the attempted coup by the Air Force, these guys were locked up, beaten, and worse. Then once the war starts, they're asked to get in their planes and fight. Remember that they were trained by some of the best instructors America had at the time. Pilots and maintainers both. If they were so useless and handicapped, why did the US decide to turn the F-14 fleet once retired into chaff? I knew someone who worked in the USN on them, and some of the things they were doing right at the end-of-life on the airframes to keep them running is barely believable, but certainly acheivable by people with the type of knowledge Iranian personnel would have had at the time. You're never going to find any 100% accurate information about the conflict because of the politics all around. Even in the American report, this is the same thinking that said the MiG-25 was this marvelous supernatural form of flying death and our only hope of surviving the eventual meat grinder of the Fulda Gap was to develop the F-15. Well one defection later that turned out to not be true. I truly believe you are cheating yourself by not reading something that obviously didn't come out of the "Iraninan Military History Ministry".

Red Storm Rising by Tom Clancy Conventional WWIII in the 80s. Runs the gammut of naval and ground pounding. Decent story. Red Phoenix by Larry Bond Helped the above write Hunt For Red October, and father of Harpoon the war game. Hypothetical Korean war. Pretty decent. In a very similar vein to the above.

This report is based on heavily out of date information. The sabotage of the F-14s and their Phoenix missiles did not have nearly as much of an impact on their operations it states. This is a much better read, and was released after this report was written: http://www.amazon.com/Iranian-Tomcat-Units-Combat-Aircraft/dp/1841767875/ref=sr_1_1?s=books&ie=UTF8&qid=1362451129&sr=1-1&keywords=Osprey+Iranian+F-14 I found the picture of a Hawk SAM mounted on an F-14 rather interesting.

Tell it to Bosoff. *badumching!*

Wow. That was a great read!

Assuming you're asking a question, yes. If you play a TRK file in DCS, and TacView is capturing, it will generate an ACMI file.

I see what they did thar....

I believe he's describing a trunking system, and as to whether or not the USAF uses it, I have no idea.

Bah! Us old farts were tooling around in DI's Helo sims in all the polygonal glory with front/back seat on DIAL-UP. This is one of the things modern sims are severely lacking, DCS included.

The other thing to remember is that it's written from an Australian POV, with their defense situation and force deployments in mind.

Netflix is awesome.

Wasn't it not that long ago people were stating that MP was a very small portion of customers? Basically saying us MP people weren't worth the time? Now they're delaying a major patch and apparently dedicating a fair amount of resources to it? Wonder what made them change their minds.

So the client throws out this sudden TSPI data for a missile because it never got the packet it was actually launched? That makes no sense.

Since it's all under DCS world, it will perform the same.

IR missile warnings -sometimes- give you a warning if the guy locked you with his radar first to get a range. But then it might just be a lock or scan warning. However, the 29 and 27 have that IRST system where they don't even need that if they can catch you on it. Your only defense is to be aware of what's behind you. As stated before, if you get close to someone, assume they've got passive IR missiles on you and launch flares, ESPECIALLY at the merge. ECM only seems to serve a use in multiplayer against aircraft. What's modeled in the game is called a 'noise jammer'. Essentially, it generates a lot of noise in different frequencies so that radars can't get an accurate range. Problem is, EVERYONE knows you're doing it, and what direction you are. It is completely possible for someone to see your ECM signal LONG before they would normally detect you otherwise. F-15s see a verical bar with empty squares in it the length of the scope. 27/29 sees a line of static. Some missiles are designed to home in on this signal, but the attacker is guessing if their missile will have enough range. At some point, even the radars realize what's going on, and get "burn through". The other guys will clearly see your dot in the middle of that noise, and can lock/launch weapons with impunity. When you're returning to base, generally turn ECM off as your own guys will not know if you're friendly or enemy right away.

If the bars go to the 12 position, "generally assume" that you've been spotted by aircraft. SAMs are another ball of wax altogether.

Pro Tip: Don't fight the AP. It's trying to use trim to fight you. If you're fighting it and deactivate it, you'll wobble all over the place and be way out of trim. So don't fight it before deactivating it, and/or reset your trim when you turn it off.

I DON'T CARE IF I BRING BACK YOUR JET... CODE 2 OR CODE 3.... I just dump the suckers if they hang like that.

Bah. Confused it with the SA-11.

I'm curious if the SA-6 has similar results.

What's the res on all the monitors?

I have the CH Pedals, and the CH Throttle quad for FSX. The CH Pedals have had both toe-brake pots go out of alignment and need to be replaced. The Throttle quad has had one pot completely die, and replacing it will be a downright pain in the ass requiring de-soldering of all the pots on the board to even see how hard they'll be to replace. I've had three gens of Saitek's HOTAS sticks. No problems on any of them.

I think the short version is you set up the displays side-by-side in the windows control panel. Add the pixels up for total width. Put DCS World in windowed mode, and define the main screen in the configs as the entire thing. So for three screens running 1920x1080 it would be 5760x1080. What I have is a 24" monitor running as main, and a much smaller 1028x960 running my MFDs with the Cougar Frames velcroed to it. The procedure for setting that up is somewhat similar.

I heard a story from a guy that worked on the Nevada range that he was driving down a road, looked in his rear view mirror and saw a BUFF in it....

Flashlight on a stick.