Burnspot

Pilot version, the base model...that's all you really need unless you're into 2D panels and circuit breakers.

Yea, it was patched for FSX:SE in early January with 1.012 (Pilot Edition). I've had no issues with it. For awhile, I was blaming it for some BSODs I was getting, but those turned out to be related to my system's overclock settings and were rectified.

Yep. It's working great and doing all my regional stuff...along with a QW RJ85. BTW, the Q400 is running with the 1.013 patch.

Not to veer too far off topic, but FSX:SE is no different than boxed...except for the updates that DTG has made to it within the limits of their contract. Far from being "crappy", I find it performs better than boxed FOR ME, not too mention it makes re-installations childs play. The PMDG 777, A2A aircraft, QW's Avros, and the Q400 work marvelously in it, along with a slew of "advanced" addons. FSX:SE does not equal "dumbing down" things...it is a new avenue, a new lease on life for the "entertainment" version of FSX and will certainly introduce more folks to flight simming. That's a good thing for PMDG and all the other developers; P3D simply isn't the best option for everyone. I'm looking forward to getting the NGX back into my virtual fleet...it's been in the FSX:SE hangar far too long. The Q400's been getting a workout in the meantime....

If I had to guess based on the "time off" you talk about, I bet it was just downloading an update. To reduce the PITA factor for me, I uninstalled the "legacy" FSX entirely and went FSX:SE all the way. All of my installed A2A planes work fine (Piper, Mustang, Cub, and 172), as does my Orbx scenery (since they've patched the libraries), QW's 146 package, Q400, Ideal Flight 10, FSCaptain, Air Hauler, ASN, Aivlasoft EFB, FSBuild, PMDG 777 (and 737 shortly), Milviz 737, GEX, FSGlobal, and Aerosoft's Twotter all work fine for me. Don't care about the politics of Steam; been a member for 10 years and have a ton of games in my library...I've never had any problems with the service...at all. The overlay is pretty handy on long cross country flights...

I moved my FSX platform over to FSX:SE this past weekend and uninstalled my original FSX. The MOST important aspect of FSX:SE to me is that it's now getting updates...something it obviously hasn't had for years (not sure how much they can play with, but it's good nonetheless). Anyway, I'm still moving stuff over, but so far, in FSX:SE I've installed FSCaptain, FSUIPC/WideFS, AS2012 (pending ASN's update), GEX NA & Australia, Aivlasoft's EFB, all of PMDG's 777 stuff, A2A's C172 & C182, Air Hauler, and some Scenery Tech stuff. I've done two 773 flights via FSCaptain, each over 2k miles and used 8x auto cruise here and there - zero problems. I've also done probably 6 100 mile flights with the A2A Cessna's with no problems. Things seem more fluid (i.e. smooth) in FSX:SE and seemingly less problematic (I don't FPS track). I'm use Win 8.1. While I'm sure I'll have a lockup/crash at some point, it seems pretty nice right now.

Map the PMDG key assignment for the disconnect. Press disconnect once, wait at least 1.5 seconds (IIRC) and press again...it will stop.

What Willywonka said; there's a flow you need to go through in order to properly configure the NGX for flight. Weight, flap settings, trim, etc. Unless you have an issue with FSX in general, a properly configured NGX will have no trouble getting airborne.

Guess we'll find out today since 8.1's been released. I have zero problems now with 8.0 and hopefully, 8.1 continues that trend....though I'll wait a few days and see what others find before taking that chance.

At work, so I can't do anything at the moment, but yes, I'd give manual loading a shot (simulate load also, just for realism's sake). Bear in mind that it's looking at the payload weight in total (PAX/Cargo) and not individual PAX numbers. I haven't tried any of the more advanced loading stuff FSC now offers. I might be doing it weird, but I typically do "off the cuff" FSC flights mostly, i.e. no ahead of time setup in the FSC Administrator. I'll load into an airport, call up the FCDU, pop in my time limit, and see what flights, if any, are available. Most of the time, they're charters, but for those airports where I generated an FSC schedule at some point, I'll come across scheduled flights. The charters often go to places I've never been...part of the reason I like the off-the-cuff method. Anyway, I'll find the flight I want, go to my second PC and check out the destination in EFB and then put together a flight plan in FSBuild...which gets exported to the FSX machine, then I select the flight and start the FSC flow. The FCDU will show the estimated fuel needed, PAX count, and payload. At that point, I'll set the T7's fuel to the estimated amount (it's usually in the ballpark), then begin the boarding process in the FCDU. During the boarding process, the FCDU displays the payload information - current T7 load and load called for by the manifest. I'll bring up the T7's CDU and adjust the payload using the % entry method until it's pretty close to what the manifest calls for and do finer adjustments using the T7's PAX/Cargo entries (remember, load is manual, but simulated). If you nail the weight, the current T7 and manifest payload numbers will be green. If not, after loading, the FCDU will bring up a page that allows you to reconcile the load...per the manifest or per the current load on the T7. That's it, loading done. From there, I proceed in FSC up to the point where it's waiting for Pushback. THEN I start working on the T7's flows. When GSX initiates the pushback, FSC senses it and goes on with it's flow and the flight's underway. I do a similar process with flights I setup in the FSC Administrator prior to starting FSX and it works fine. I seem to recall reading somewhere that for some flights (not scheduled), FSC will use the payload currently on the AC for the required payload...maybe that has something to do with your trouble? I've never see a 0/0 problem like you're talking about, but I don't think I'd totally trust the auto-payload method...it's always been tricky with advanced FSX add-on aircraft. I've tested out auto-payload twice on the T7 and it's been fine so far, but I prefer manual and NEVER auto-fuel. I suspect things will improve once Dutch and Travis sort out the T7 and what it calls for.

Been an FSCaptain user for a few years now and use it all the time with the T7. I did the usual thing for getting a CFG for the T7 in FSCaptain...launch the FCDU in the T7 for the first time and it creates a CFG for FSC use. It may be awhile before Dutch puts out an internal interface for it as it looks like a number of common FS signals are not getting passed in the usual way that FSC can pick up on (e.g. the belt signal)...maybe with the coming SDK? I've found it works fine using manual payload/simulate load and manual fueling. This past weekend, I tried out auto payload to see what would happen and it appeared to work fine, though the PAX count and cargo weights didn't update themselves until after the load was complete (the gross weight climbed steadily while loading was underway however). I never use the auto fueling feature of FSC with any PMDG aircraft. Anyway, I always see PAX/Fuel/Payload figures in the FCDU (and see the red/green weight disparity/match figures). Might want to check the load map for the CFG in FSCaptain and make sure the key fields are populated. Can't wait for things to get completely sorted with it...had a bird strike/engine failure occur shortly after takeoff from NZAA; however, with the present state of T7 & FSCaptain interaction, there was no actual effect on the aircraft. FSCaptain is the ideal tool for this aircraft.

The T7 performs wonderfully for me and none of the reported bugs are showstoppers in any way...I'd say you're missing out. Performance between the T7 and NGX are not noticeable to me, but then again, I don't chase FPS and only look for smooth, stutter-free operation, which both aircraft provide gobs of.

Windows 8, FSX, and all PMDG aircraft work harmoniously together here...

Updated my 4S and iPad 3 yesterday. The process took a bit of time because of everyone rushing to download, but it eventually finished up painlessly. I like the new look...very sharp, snappy, and smooth, no lag whatsoever (I know one of the beta versions had lag). A few things are done differently now, flinging cards up to close apps being one, but overall, I think they're moving in the right direction with iOS 7. I like the call block feature...added my very long list of "spam callers" to it. :Applause:

Yea, that's what I was talking about....moving them. I move them around when using FSCaptain's FCDU.

Smaller frame to grab onto with those windows...it's there, just much thinner.

Whatever the case and regardless of what PMDG does, ASN certainly sounds enchanting... (reading Damian's full post).

This. I've never had to shuffle FSBuild routes around or rename them to get them to load in any PMDG aircraft. With my current setup, I use FSBuild on another computer, export the route to my FSX rig, and immediately call up the exported route in the FMC for use. It's rather painless actually.

Yea, the settings don't seem to stick around unless you save and shutdown/restart it. Also, there should be no need to rename the files after export...forgot to mention that. It's a bit of a PITA to get setup right, but once you have it, you're set. I just re-installed FSBuild on my external laptop, feeding into my FSX rig, the other day and went through this process. I like the look of PFPX, but the $$ is best spent on other addons when FSBuild still does a good job.

IIRC, it just exports to the PMDG/FLIGHTPLANS folder...been using FSBuild for years with PMDG aircraft, including the T7 now. Make sure you have the correct export option set (I think one setting is for PMDG iFly or something like that...which you don't want) and that you have set the right FSX root directory. FSBuild should take care of the rest automatically. You can then call up the routes from the T7's FMC using any of the various methods it provides (CO ROUTE, route request, etc.). I'd recommend having FSBuild export without the SID/STARs (an option that doesn't seem to stick in FSBuild)...that's a PMDG recommendation I believe. Side note: Make sure that if you change a setting in FSBuild, that you save it and then restart FSBuild...so the setting sticks.

Might as well toss my experiences in this Win 8 thread as well. The PDMG 777 performs beautifully in Windows 8; zero crashes, zero OOM's. The only issue I was experiencing, was the freeze thing (it always recovered), but for me, that turned out to be a SimConnect issue that was solved by correcting my SimConnect configuration (I hadn't set it up properly on my new FSX rig when trying to link in my laptop). All other PDMG aircraft perform normally (NGX, MD11, 747, and J41) as do all of the other addons I've used (Coolsky's MD-80's required minor tweaking IIRC). I've run into the FSX joystick drop issue, but that can be dealt with in a couple of ways. Win 8 performance has been better than Win 7 in my experience (based off my previous FSX rig). I DO use the UIautomationcore.dll file...the same version I used in Vista & Win 7.

Are you running anything linked to FSX from another computer? I had a few pauses here or there and it turned out to be my SimConnect config between my FSX rig and the laptop I use to run FSX-related stuff...I hadn't set it up properly. Another fella found that SimConnect itself was trying to load stuff in FSX's DLL and EXE xml files that was no longer installed...creating freezes. Might be worth checking out.

Dunno, I've been happily flying the 777 in Win 8 since release...as well as the NGX, MD-11, etc. The only big issue in Win 8 seems to be that FSX MAY forget that a joystick is connected if you alt-tab out of FSX and once you lose it, it's gone until an FSX restart (not a 777-exclusive problem). If you don't alt-tab, you're generally good to go. There's a mega-thread here in Avsim about this. I've run into this issue once or twice, but have since gotten my external laptop setup with everything so that alt-tabbing on my FSX rig is never needed.

I use NavDataPro with no issues in the T7.

It's looking like a mis-configured SimConnect was at the root of my freeze (but no crash) problem. My FSX rig is new (received same day as 777 came out) and in the crush of everything FSX-related that I needed to re-install, it looks like I overlooked my SimConnect config. I had the SDK and SP1A installed, but apparently never went back and set it up. After posting here, I cracked open the SimConnect setup bible (aka HiFi's AS2012's instructions) and got everything squared away on my FSX rig and laptop. No issues with my existing EXE or DLL XML files in FSX....pretty clean actually. Since then, the T7's been running smoothly, with all my ancillary stuff operating, without so much as a micro stutter. So I'd say SimConnect could be a freeze culprit worth looking into if you operate external stuff (EFB, Air Hauler, etc.) and get the freeze.