Tabs

It's really not that we don't "support" DX10 - if you run a vanilla FSX install with DX10 Preview on, the airplanes should work fine, though Kyle is correct about the shortcomings he mentioned above.
 
The real issue comes from the fact that there are all kinds of third party mods being done to the graphics system at this point. We can't possibly be responsible for supporting things that we have no control over - say a change is made to one of those mods and then suddenly we're inundated with support requests about it. That's not a workable situation for us. To give just one example - back when the 777 was released we had a bunch of tickets come in about the VC becoming partially transparent when in 0 visibility conditions. Vin spent a bunch of time trying to figure out what was wrong with the model and we eventually determined that the entire issue was being caused by a shader mod that the people reporting the issue were using. That's completely wasted time for our team if we have to spend it chasing down things that aren't even our issue.
 
Regarding Nvidia Inspector - I think the old recommendations largely still hold. I have a very old computer actually at this point, I really need to upgrade before doing another guide.

Guys,

This is an attempt to deal with some engine and atmospheric dynamics inconsistencies in the sim. FSX/P3D isn't a perfect simulation and we have to massage it into behaving the way we want it to. The bug was actually that it didn't go to full idle automatically below 30k until you held F1 - that was fixed in the 777, it should go to true idle there unless you have a calibration issue with your stick. The NGX I believe still has the issue where it doesn't automatically reduce without cycling your throttle or using F1 to pull it all the way down.

Avery,
 
I'm running Win10 here and the OC is working fine. What exactly are you seeing happen with it?

It requires creating a custom networking system that can deal with firewalls, router NAT etc. This is just about the furthest thing from trivial that there is - companies like Skype spend millions of dollars on this type of technology. This is not easy stuff to do. We can't just use FSX's shared cockpit thing - it only works with SDK compliant gauges - most of our systems are complete custom, FSX doesn't even know they're there and it has no provisions for becoming aware of them.

Download from your original 300ER purchase email link - there's no patch version, we just updated the main installer. Everyone's link is still active.

This isn't a problem - the FMC doesn't know how long you'll be on that VECTORS course so it draws it out a very long ways on the ND. (I think 650nm is the actual figure it uses) Real airplane does the exact same thing - this has been in there since release last year. NGX does the exact same thing too.

FMC PROG page.

Kyle,
 
I'm pretty sure the switch shouldn't be there if RAAS is disabled - we may have overlooked this in the initial release. I'll put it on the list for SP1.

Try running a registry fix like this:
 
http://tweakfs.com/download/fsx_reg_utility.zip
 
It uses the registry to look up the location of FSX - if it can't find it, that can be the result.

We don't recommend using this - it can result in certain internal FSX variables not initializing properly without the default ultralight having been loaded in the background first. Can cause weird issues or CTDs on load.

Every order from yesterday should have recieved the email now. If you still haven't, submit a ticket at the link in my signature.

No ETA internally - as with the 200LR/F we want to do it right (and we have to fix the issues that have come up with the 200LR/F first anyway). We need to create new performance data for the 115 engine, new FDE stuff for the different airframe and wing, do the cockpit differences, taxi cameras (hopefully) etc.

We know about this - it's minor and we're not holding up the release for it. Will be fixed in SP1.

400 will be done first. Yes, the "NG" FMC will be done, probably as part of the -8 addon and an option will exist to retrofit the 400 with it.
 
And btw 32-bit vs. 64-bit has nothing to do with FPS - it's about addressable memory for the sim. The 64-bit stuff will never suffer from the OOMs that plague FSX. FPS is about the sim's graphics engine, about CPU vs. GPU based rendering etc.

There ended up being a bunch of never before seen things here but yeah, RSR meant the way the ECL works when he mentioned that. Your windows mouse cursor literally just becomes part of the ECL display when you mouse over it. It's not a different windows cursor graphic or some cheesy technique like that either - it actually becomes part of the 3D display. The only other FSX addon that might have done something like this is the VRS Superbug - in that case you can consider us second then on it.

We'll see but it would take a change to the flight model too - the whole point of these things is that they add additional fuel savings over the normal winglets.

Send a ticket with "FWD to Ryan, TeamViewer" in the title. It's pretty late tonight but I should be around tomorrow and we can look at it.

This is correct. You install FSX + Acceleration or FSX + SP1 + SP2.  Those are basically equivalent.