UnitedExpress4180

That's odd. I have a similar problem only my fog is red(!). If I set visibility below a mile, it looks like I'm flying on Mars during a dust storm.

Am I the only one keeping my high expectations for this? I mean, in the past, most people got their expectations stomped on because Microsoft kept releasing a flawed product that was under-tested and poorly developed, but we should keep in mind that P3D is NOT a Microsoft product. It is by a government-contracted company which specializes in aviation and aerospace technology. Not to mention their target market isn't consumers, it's professionals, and that market is far less forgiving when it comes to software such as this. Remember, they are selling this for a lot of money to a lot of different people, all of whom expect it work and to work (very) well, so LM has to raise the bar, whereas Microsoft could release any old crap and be no worse off. LM has more invested in this, so I think this time it's safe to assume that they'll release a superior product. Maybe not in terms of graphics, which for us average Joe's is a shame, but this is supposed to be a training aid, not a game, so even if it doesn't look as nice, at least it'll be more reliable than MSFS was... ...But to cover my behind, I'll add that we'll have to wait and see.

I don't know about the rest of you, but I'm fed up with FSX. Not that I don't like it, it's just that it seems like no matter what I try, I just can NOT get it to run stable. Doesn't matter what plane I fly, what location, weather, addons, utilities, etc, it just loves to crash on me randomly, and only after I've gotten everything set up and ready to go, then it says, "you seem well-prepared for this flight. It would be a shame if something were to...stop working." And I've been dealing with this basically since I started simming almost 7 years ago. So the moment P3D v2 comes out, I'm jumping on it.

The 777 has been engineered to not work in P3D. As for the 747 and 767, as I neither own P3D (for now) or those two aircraft, all I know is that I've heard they work in the new sim. Whether they will for you comes down to trying it out for yourself.

Personally I just wear my headset over my hat when I use TrackIR. Gets the job done, and I can't say it's any less comfortable.

I don't have the iFly model, but I can tell you that PMDG's is lightyears ahead of theirs in terms of functionality and overall quality. I would stick with their model if I were you. As for switching to P3D, I have heard that with some modification it is possible to run the PMDG model in it. Not that I have tried it (or that I intend to), and I certainly don't advise it as it violates their EULA, but it is doable.

I would presume it's because they are not officially licensed by the manufacturers that their aircraft simulate, unlike PMDG, which has been working closely with both Boeing and airlines for years now. If their product was found to be at fault then that could also put Boeing in the hotseat for allowing PMDG to release a training aid that might not meet accuracy standards. It's too big a risk for both companies, whereas most other addon developers are not licensed or endorsed by their respective manufacturers, so there's a lot less red tape.

Unless LM adds a section in the EULA for home users (general consumers), then PMDG isn't likely to support P3D. Which is a shame, honestly, since it's, in my opinion, the next logical step from FSX once version 2 is finished. But since Lockheed is catering primarily to the commercial sector right now, PMDG probably isn't gonna jump on board due to the liability. If a plane were to crash and the NTSB found out the pilot had trained using a P3D-based simulator running a PMDG addon, guess who would be the first one on the chopping block? Yep, PMDG. So it's easy to see why they won't go for it. Not saying I agree with their choice, but the fact is they have to protect their best interests and this is the safest way to do it. But make no mistake, the mouse has to follow the cheese. PMDG is a business, and they're in the business of making money. They're smart guys over there, so you can bet that if the cheese turns out to be P3D, they may well reconsider. And if not, then that's unfortunate, but the community will go on whether they are exclusive to FSX/P3D, X-Plane, or some combination thereof.

What can I say? I'm a child of the '90's. My favorite liveries are now and forever will be relics of the past. :( *cough*United*cough*American*cough*

Well, yeah. The 747 burns a lot more fuel with almost no added gain. Even the 747-8 isn't faring too well with customer adoption. Only 14 airlines have bought any, of them only 5 air passenger airlines, and of those, none are American-operated carriers. Sadly, the age of the 747 (in North America, at least) is coming to a fast-paced end. Even with a new variant out.

They aren't as bright as in DX9, but they are still overblown.

Theoretically it should work, as Windows 7 and 8 are pretty much the same in how they execute code. The only difference is how the system uses available resources. Oh, and also that stupid Metro UI.

The ENB series, sadly, doesn't work in DX10 because it is coded specifically for DX9 only. I wish it weren't the case though, it can still make the graphics look much nicer <_<

No dice. Tried reinstalling the fix and it's just the same as before: it pulls up the splash screen for about 10 seconds then does a faceplant. EDIT: Okay, this is unbelievable, but apparently the cause of the crashing was none other than the good 'ol ENB series mod. As soon as I removed it, the thing ran and just wouldn't stop for anything but the little red 'x' in the corner... Edit #2: Well after about two minutes of looking into this further, I have discovered that I've once again been foiled by the PPIT mod. Apparently the D3D9.dll version it uses doesn't play nice with the new shaders. After switching back to the original one that I was using...it's like there was never anything wrong.

Just saying, if you are using FSX with the Post Process Injection Tool, it can cause FSX to crash when loading in DirectX 10. I was having the same problem as you describe until I removed that mod, and then presto!