Not sure I understand the debate. I have been using all PMDG planes with (14) GoFlight modules programmed through the registered version of FSUIPC, why would the NGX be different?

well not that good to explane but mainly already done. But the main difference is the SDK which could be used by hardware programes, to program the Goflight software to comunicate whit the pmdg plane and the goflight hardware. as then you only need the goflight software provided whit the hardware which makes it very easy to use, whit out additional programs like FSUIPC. and in most cases would give the best resault. best exsample is the flight 1 767-300ER as you can chose the level-d i mean it is named in the goflight software (where you set it up what the displays should show and that). thats because the level-d 767-300ER was made whit an SDK and then programed by goflight to use the info from the SDK.Best regards Lars N.

Steve you beat me to it. Well I think that's a very good indication that the hardware industry will back the NGX by PMDG 100% with driver software as it's in their best interests and bottom-line to make sure hardware works with the plane. If go flight is doing it for ifly then they will definetly do it for PMDG as will open cockpits, vrinsight, flight deck solutions, etc etc. It's exciting times for fsx as up til now alot of hardcore sim pilots with massive amounts of hardware have not had any incentive to switch to fsx because of no decent NGX. Ian Sissons springs to mind straight away. Heaps of people will change to fsx because of it. Some may even wait til msflight comes out and skip fsx altogether but why wait? Msflight might take years to get the kind of addon software and hardware that now works with fsx. Hopefully most are compatible with both fsx and msflight but I don't think so as msflight will be a build from the ground up and completely different architecture so why wait for something that could take years to be right?Mike Kendall

Speculation is not my thing, but I'd find it hard to fathom that GoFlight (or any other of the high end hardware makers) would not support the NGX in some shape or form with a driver update. It's understandable if they didn't make the investment of writing drivers for other add on aircraft, but we're talking about the PMDG NGX people!!The hardware folks are not fools, they know the NGX is the most anticipated add-on aircraft of all time, will be the highest selling addon, and will jump over backwards to accommodate people who request NGX specific drivers for their home cockpit setups, especially since PMDG is making their work so much easier by providing an SDK. And as mentioned before, if the iFLY has support, it's a no-brainer that the PMDG NGX will as well.

yep all know it would sell well, but why diden´t they support other PMDG projects like the MD11 or 747 ? The only 1 is the 747 where you could buy a 3rd part driver to get it working not nice for PMDG right as they get money for just creating a driver. About why Goflight support the iFly i think it is because the developers worked to get it work whit hardware, like they did for other mcp as an extra service, as they have a hardware section on the forum where you can also se from the beta testing and so on. but no more of this non PMDG businessBut i stil hope there is the lvars for mcp displays, and mabee the buttons of the mcp in the 737NG as that would in some way make it possible for all i think, to create the lua that can update the displays like the J41.Even if there would be released a driver by goflight to support the 737 it isen´t sure it would run as well as the Lua for all. And now i would tell why as said ifly is supported, but it have some very iritating lag on the displays of the hardware, and seems to have different influence depending on when you buy your hardware, but hard to say for sure and i must say a device that is under 1 week old have the lag and some whit a older 1 dosent, more of that on the goflight / iFly forums. Hope that gives an explanation why i like to go throu fsuipc and lua files or macro files insted.so the Speculation is just as when released it might be to late to whish for and mabee already :-)Best regards Lars N. and have a nice day

Ugh, does no one read. An SDK will be released for the NGX. This is what level D did with their 767 and enables full interfacing with almost any hardware. PMDG will provide the SDK, end users and hardware companies can then use that to write a driver for product x. As for the fslabs 747 fiasco it probably has something with the fact that the lead dev over there used to be part of the PMDG team, he left, driver went with him. As for GoFlight, I believe they would support as many aircraft as possible IF the devs would release an SDK for their aircraft. Level D, Ifly, and the PMDG J41 (Limited, not publically available i believe) are the only ones to do this so far (correct me if i'm wrong). An SDK with the NGX is going to be brilliant for Hardware devs, PMDG, and us end users. Opens a whole world of possibilities and i surely hope they continue to do it for future products.

well i just wounder about why you are sayeing: Ugh, does no one read, An SDK will be released for the NGX. As a few post above there was talked about the SDK so yes we know and haven´t forgot. I just say it mabee isen´t the best possible way. The LEVEL - D as i read on the net also have some lag on the displays like the iFly, but i havent tryeid it myself as i haven´t instaled it at the moment. and to go 1 step closer i think it might be as i say on the goflight forum as i see it not much into the codes goflight use but, if i should do as the Lua file, it seems it only read it dosent write back to the plane mcp, or some thing between the to displays dosen´t communicate right. so what happens well it reads the curent HDG as an EX. then you adjust so the reading is 145 inside the plane then the Goflight mcp might show 165 what happen then well now the dokument starts again and read the current reading inside the plane which is 145 now the goflight unit reads that and it jumps back. that way it keeps running you see it is very laggy and would take much longer time to reach the number you want as it is like 1 step farward and a half back.Best regards Lars N.

No lag for me with the level D. An SDK will prevent those issues from happening as it will allow direct interface and you wont be using some third party program to provide that link.

No lag for me with the level D. An SDK will prevent those issues from happening as it will allow direct interface and you wont be using some third party program to provide that link.

You are lucky as my does lag whit the LEVEL-D to as i have just tested it. But what is you firmware ? (shown on the unit in the CRS 1 display, when you start the pc or insert the usb stick it would show right after) as an code that stars whit A and then 2 numbers)also what version of the driver do you use the latest which i do 2.01 released this weekendbut yes i also like if the goflight driver was enough and worked for all which dosent seem to be the case .Lars N.

I guess the NGX SDK will consist of a set of C functions. Maybe someone from PMDG can confirm that?If that's the case, there's a C API in Lua to acccess those C functions.

I guess the NGX SDK will consist of a set of C functions. Maybe someone from PMDG can confirm that?If that's the case, there's a C API in Lua to acccess those C functions.

To access C-functions from the Lua, these functions need to be declared in a special way and the library need to be compiled with several Lua sources included. Not so simple. Doubt if devs decide to support Lua access to it.I'm praying for SDK is not based on a C-library or at least all the major functions and controls are still accessible through the LVars.

Firmware is A22, software is 1.93 build 20

I have had communications with the GoFlight gentleman about payware interfaces. I get the impression they are commited to Ifly. They never mentioned the NGX and my confidence GoFlight will build a NGX interaface is not high.

Only the time can show, but if i can, i would support the goflight MCP-PRO whit lua fiels if posible or the way i can get it working best posible. but we know when it is relesed if there is anything we do to get it supported that way, which i realy hope i / we can.

My MCP-PRO Firmware is A25 and software is the latest 2.00, I can't wait to see it working with my NGX, thats the main reason why I bought it in the first place. Evan Banalian.

It makes commercial sense for goflight to support the NGX directly, so I'm not worried so long as the sdk provides the required autopilot interfaces.However if Goflight don't, I will write something in C since lua is a little too slow for quality autopilot use. I already have 50 percent of the code written to interface the NGX to the engravity CDU. I want the hardware support to match that of the Level D, whether that's from suppliers or I develop it myself. I will freely share any interfaces.