dseagrav

To quote xkcd, "F--k Cancer"

FBW is for hippies and communists! Every airplane should have a FBW disconnect button and every pilot should use it. If it crashes the airplane then the airplane deserved to be crashed for depending on SATAN'S HANDS. Everyone who dies as a result of such a crash should feel proud that their deaths contributed to the extermination of FBW aircraft! "I used to be WITH IT, but then they changed what IT was! Now what I'm with isn't IT, and what is IT seems weird and scary to me! IT'LL HAPPEN TO YOOOOOOOOU!"

The update page at http://www.fs2crew.com/cart/pages/FS2Crew%3A-PMDG-737-NGX-Edition.html links to here, which is probably the source of the confusion.

Awesome. Thanks a million.

I have a tablet and I like having manuals and checklists for reference on the tablet so I don't have to continually jump in and out of FS.

I fixed it. In \AppData\Roaming\Microsoft\FSX\SimObjects there's two folders, PMDG_MD11 and PMDG_MD11FDelete those. They will be recreated when the MD11 is loaded, and all is right with the world. As for the other problems I was having, it turns out that when Flight1 products tell you to back up the extracted data, I somehow misinterpreted this to mean that you were to back up the key and exe.I thought they were a pair. This is not true. The exe is specific to the computer it was extracted on, and is useless after the install completes. You're only supposed to back up the key file.Copying the extracted installer is interpreted as violation of the copy protection and is intended to cause problems. You're supposed to use the key file to run the Flight1 wrapper again.

I tried this and it didn't work. I uninstalled and reinstalled the MD11 and that didn't help either.FSX did ask me to re-authorize the DLLs, so they are being loaded, it's just locking me out.I also noticed that the PMDG menu is not showing in the menu bar.

I built a new computer. I reinstalled FSX from the DVDs, reinstalled all my addons from their original installers.BUTI didn't want to go to the hassle of recreating my key maps and tweaks and everything else, that would take days, assuming I can even remember it all. So I copied the stuff in Users\dseagrav\AppData\Roaming\Microsoft\FSX (fsx.cfg and so on) from my other computer. That was all I copied, nothing else.Apparently, if you do this, most addons think you're a filthy pirate and disable themselves in strange ways designed to foil pirates.The MD-11 was installed from the original download and did its verification with the PMDG server, so I wasn't expecting anything from it. But when I try to load it, all functions are disabled and the initialization never happens.Is this a real bug or is this just the pirate protection?If it is the pirate protection, do I have any hope of convincing it that I actually paid for the software WITHOUT having to delete my FSX config or reinstall FSX yet again?

Yep. It confirms that not only are you a valid address, but you actually read spam and click links in said spam. It makes your address very valuable to the spammers, and they will immediately sell it to other spammers. The problem with this is that the vast majority of sending addresses are innocent people whose addresses are being forged by the spammers. All you do is grow your block list. The spammers almost never use the same sender address twice.Email filtering technology is the best option.

Some of those had radio altimeters toward the end of the war - Maybe it's the antenna.

I'm sorry, I didn't mean to imply that the impact on pilots is worth more than a little girl's life. That is TOTALLY not what I feel. I meant that this action is so patently evil and vile that you cannot possibly have done worse with an airplane. This is the worst anyone could do.Edit: Additionally, and reluctantly, were a ban on general aviation proposed in response to this action, I do not feel I could oppose the ban and remain on sound moral footing. My hobby is dear to me, but not worth trying to justify the actions of this evil being.

http://www.indystar.com/apps/pbcs.dll/arti...D=2007703060397Geez, the anti-aviation lobby couldn't have asked for any more.

Your link, not your article. I should have worded that better.

{Sorry; First paragraph redacted... that's going too far. My sincerest apologies to anyone who read that and was offended by it. I am not racist or anti-semetic, and I do not intend to devalue the sacrifices of the holocaust.}I would have no problem giving consideration to the other side of this argument if it weren't a series of misrepresentations and biased half-truths designed to mislead the public and ensure that I can't fly anymore. This won't "force corporate jets from the runway" like the commenter in your linked article wishes, and it won't prevent the rich from jetting wherever they wish - They can afford to pay. It won't make ticket prices substantially cheaper - The airlines will lower prices by some token amount and pocket the remainder. It won't remove any tax burden from the public - The government will put that tax money to other uses, or in their own pockets. The only thing this does is ensure that myself and people like me can't fly.

Also, we pay a higher tax than the airlines do. For private use, avgas is taxed at 19.4

This whole thing is just to benefit the airlines anyway. I would have much less of a problem paying for satellite-based ATC if I had the ability to use it, but the features they want to add have nothing to do with a 152. They aren't adding any significant new functionality, no better weather or better coverage, they just want to have computer-controlled dispatching so they can stop paying dispatchers, and they want to use more regional jets so they can pay pilots less. The whole thing is just the airline management trying to fleece everyone from the top down.

If you were ever planning to fly in real life, or want to see general aviation continue in the real world, you really should consider joining the AOPA -RIGHT NOW- or you may lose the chance forever.The white house has submitted its budget for the 2007 fiscal year, and the new FAA budget, which is required to be decided by September, includes a 400% increase in fuel taxes and substantial user fees. The total cost of private flying is expected to increase over 500%.The reason for the increases and funding changes is that the government no longer wants the FAA to be tax-supported and wishes to move the costs of operation to pilots. We're being forced to foot the bill for a system designed to put us out of business. The airlines want a next-generation satellite-based surveillance system to replace the existing radar system, which would allow them to fly more smaller jets and replace dispatchers with computers. They try to justify this by pointing out that Europe has this system already - and in Europe, there is no general aviation. Private airplanes are almost exclusively business jets owned by the very wealthy. The rank and file take the airlines; the private skies are reserved for their masters.I am not exaggerating in the least - I have no political agenda and represent no group, except that I am an AOPA member. But I am not typing for the AOPA. I'm typing for pilots. Our fellow pilot in the white house has sold us out. The implementation of these fees will END GENERAL AVIATION AS WE KNOW IT. And that's what they want. The airline lobby and their backers want the common rank and file chained to the ground where they "belong".The news will try to spin this in their favor - Talking about how this will make ticket prices cheaper, and about how rich corporate fatcats and their private jets should pay a "fair share" - But don't be fooled. The goal of these fees is to make sure that a general-aviation "flying car" like the ones envisioned in the past will never exist; and those that do exist will be the privilege of the wealthy. Your children will never fly. Never again will someone look up in the sky and see a Cessna or a Piper and dream.Please, for the sake of pilots present, past, and future; FIGHT THIS.Join the AOPA. Write your congresscritters. MAKE NOISE. We cannot allow this to succeed.

Sounds a lot like Wilco and Anticyclone with A320PIC...

I can confirm this is an nvidia bug and not an FSX bug because FS9 does the same thing for me. It does it when ANY window overlays the FS window, be it a tooltip, a subwindow, a dialog box, the alt-tab box, instant messenger, whatever. I got around it by disabling tooltips and avoiding overlaying the FS window.I haven't reported it to nvidia because both times I've reported a driver bug to nvidia they just tell me to uninstall the driver and buy another video card or go back to some ancient version of the driver and "wait for the next release". In fact, this started happening to me when nvidia tech support had me uninstall and reinstall their driver three times because the new nvidia control application guesses the wrong language for my computer.

gb2/b

How'd you do that?

No, not even a scratch! I sure felt stupid though. My instructor wasn't pleased either.We were on a paved runway (3MY), and she was explaining "All you have to do is hold some back pressure while you take off..." and demonstrated as she was speaking, except for pushing the power in. She pulled the yoke almost to the stop, so I assumed that was what I was supposed to do. I took the yoke where she had it, added a bit more back pressure, then pushed the power in before she had a chance to do much about it. The nose came up before I could react to it, because I didn't know the prop wash was strong enough to have any effect with no airspeed. (I was expecting to hold the pressure until the wheel started to lift and then back off) The instructor already knew what was coming and was pushing the nose back down as soon as it lifted. It hit the tail but not very hard. Just enough to get a nice, loud "BANG!" out of it and scare the wits out of me. It didn't even set off the ELT (which is in the tail.) There is a small skid attached to the tail tiedown loop, and that's what hit pavement. I assume it bent a little, but I couldn't tell. We decided since it didn't hit very hard and there was no visible damage it was best to vacate the area before anyone saw us. :( I got a "Don't ever do that again!" type speech afterward. It was funny afterward but I wouldn't advise anyone else do this.In my defense, (to date) that is the only part of the airplane I have allowed to touch the ground, other than the tires.

I'm not dumping on FSX, I like my copy. Calm down.I tested as follows: I loaded a Piper Cub under default weather, set the parking brake, advanced the throttle, and tried to raise the tail. I couldn't. Then I loaded a C172 and tried to raise the nose with the parking brake set. I couldn't. I've seen the Cub lift its tail in real life (Well, a video of it), and I've also personally banged the tailskid of a 152 on the runway (at zero airspeed) by pulling far too hard while attempting my first soft-field takeoff. I can't do either in FSX, so I think it doesn't simulate prop wash over the elevator, or at least not at zero airspeed.

I just tested, and it does not appear so.

I dunno about that; Flying helicopters at full realism in FS9 was mostly an exercise in futility, and it's a lot better in FSX. I haven't tried to stall or spin any of the default airplanes yet, though. Someone would have to do some side-to-side comparisons with the same airfile in both sims to see what the differences are.