Hi all,I am sorry if this question has been asked previously. Will the NGX be compatible with the GoFLight MCP Pro module? Thanks. P.S. Keep up the great works, you guys are awesome.William Campbell

HI,PMDG said that they'll make an SDK for the developers and so they can make their hardware compatible. But it depends on the developer if they use it.So basicly without a patch I think it won't run.

HI,PMDG said that they'll make an SDK for the developers and so they can make their hardware compatible. But it depends on the developer if they use it.So basicly without a patch I think it won't run.

OK. Thanks for the reply.

Hope they are goeing to do goflight, but dont think its much fun for all as it seems they havent given some feautures to us whit the previus version of the mcp. We could hope PMDG use lvars we could program into LUA files that can run whit FSUIPC like other add-ons, (other pmdg prodcts) to correct displays and program buttons on the hardware. but i think the last part would be avaible first, if posible as i know i would try LUA programing when i get it, if i have the money. But ofcause it would be more fun to have on release but not posible.Best regards Lars N.

We're not "doing" anything as far as hardware - we have an SDK that the hardware makers will be able to use to make their driver compatible with the plane - that's literally all we can do, we aren't going to write drivers for a ton of different hardware.

well we all know. i am just sayeing that if there is lvars like other of your planes, we can use them to program LUA like this for the PMDG j41:prevHDG = -1prevSPD = -1prevALT = -1while 1 doHDG = ipc.readLvar ("L:HDGBug") if HDG ~= prevHDG then stringHDG = string.format("%03d", HDG) gfd.setDisplay(GFMCP,0,1,stringHDG) prevHDG = HDG endSPD = ipc.readLvar ("L:IASBug") if SPD ~= prevSPD then stringSPD = string.format("%03d", SPD) gfd.setDisplay(GFMCP,0,2,stringSPD) prevSPD = SPD endALT = ipc.readLvar ("L:AltSelAlt") if ALT ~= prevALT then stringALT = string.format("%05d", ALT) gfd.setDisplay(GFMCP,0,4,stringALT) prevALT = ALT end ipc.sleep(50)end

well we all know. i am just sayeing that if there is lvars like other of your planes, we can use them to program LUA like this for the PMDG j41:prevHDG = -1prevSPD = -1prevALT = -1while 1 doHDG = ipc.readLvar ("L:HDGBug") if HDG ~= prevHDG then stringHDG = string.format("%03d", HDG) gfd.setDisplay(GFMCP,0,1,stringHDG) prevHDG = HDG endSPD = ipc.readLvar ("L:IASBug") if SPD ~= prevSPD then stringSPD = string.format("%03d", SPD) gfd.setDisplay(GFMCP,0,2,stringSPD) prevSPD = SPD endALT = ipc.readLvar ("L:AltSelAlt") if ALT ~= prevALT then stringALT = string.format("%05d", ALT) gfd.setDisplay(GFMCP,0,4,stringALT) prevALT = ALT end ipc.sleep(50)end

That's what the SDK is for, you won't need Lvars anymore

No you would for displays as the LUA file was fore, if the hardware company don´t want to do it. how often isent it the hardware is suported by the buttons but doesen´t update the displays as there is no comunication as they say (vrinsight), goflight use the combability mode some times but isent supported on the MCP (advanced version) . Thats a thing i have been so angry on the hardware companies for, as ho wants to pay for some thing that cant communicate, then there is no need for hardware. As using an sdk you have to be in most cases a more hard core programer to use.so yes Lvars is needed. Best regards Lars N.

No you would for displays as the LUA file was fore, if the hardware company don´t want to do it. how often isent it the hardware is suported by the buttons but doesen´t update the displays as there is no comunication as they say (vrinsight), goflight use the combability mode some times but isent supported on the MCP (advanced version) . Thats a thing i have been so angry on the hardware companies for, as ho wants to pay for some thing that cant communicate, then there is no need for hardware. As using an sdk you have to be in most cases a more hard core programer to use.so yes Lvars is needed. Best regards Lars N.

No, you are talking about the displays in the VRInsight panels, that have nothing to do with Lua vars (and with PMDG by the way). That is done via the serial port "COM" library in Lua. Lua Vars read/write from the plane, not the panel, and that's replaced by the SDK. I guess what you need to know is if the PMDG SDK will include Lua libs to interface with it, so you can use your Lua code to comunicate with the VRInsight panels and everything else (replacing ipc.readLvar / ipc.writeLvar with calls to the NGX SDK). Here's hoping that's the case as a Lua aficionado myself

I dont know what you are talking about, the LUA files are usefull more then only for VRINSIGHT. as said not all goflight hardware support the updated displays on fx. mcp-pro. so stop i have programed this for goflight and more lua files on the fsuipc forum from others.i realy dont know what you mean, i know how the vrinsight works in a diferent way from goflight and other hardware: " not the panel" what panel? i know it reads all its info from the pmdg lvar. EX. L:HDGBug and write it directly to the display as we have told it to do whit the programing.like it would do if i wanted to program it to another display in the pmdg planeBest regards Lars N.

I dont know what you are talking about, the LUA files are usefull more then only for VRINSIGHT. as said not all goflight hardware support the updated displays on fx. mcp-pro. so stop i have programed this for goflight and more lua files on the fsuipc forum from others.i realy dont know what you mean, i know how the vrinsight works in a diferent way from goflight and other hardware: " not the panel" what panel? it reads all its info from the pmdg lvar. EX. L:HDGBug and write it directly to the display as we have told it to do whit the programing.Best regards Lars N.

Lua in FSUIPC has the com library added by Pete that you use to interface with VRInsightLua in FSUIPC has the event.gfd functions in the event library to interface with Go Flight, also added by PeteBoth have ABSOLUTELY NOTHING TO DO WITH PMDG or any other addon A/C, but...The ipc lib added by Pete includes the Lvar functions to read/write from a number of planes, including PMDG, and that's what the PMDG SDK is replacing, so you won't need that FSUIPC feature anymore with the NGX (LVars)So what we need is a Lua lib to access the PMDG SDK like we did with Lvars until now, because an SDK is much better for us Lars :(: you won't need to log Lvars to figure out what's the name for each function, you will have a nice document explaining what's the landing lights function, and the APU master switch... and they're all guaranteed to work (not all functions work with a Lua var), and you won't miss the click sound in the buttons and all that stuffI don't know if PMDG will include support for Lua or we'll need Pete Dowson to add it in the FSUIPC Lua interpreter to interface with the NGX (so we'll be able to use those scripts with VRInsight and GoFlight panels), but I certainly hope soI really don't know how to explain it any better, or maybe I'm missing something

GoFlight have just annouced full support for the iFly with MCP Pro and EFIS so I would guess they will support the NGX after a few weeks from its release.Steve Munn

GoFlight have just annouced full support for the iFly with MCP Pro and EFIS so I would guess they will support the NGX after a few weeks from its release.Steve Munn

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

But still 1 thing, they don´t support all the hardware/software, as the GF-MCP Advanced Autopilot which is stil on the market, dosen´t have the same options as the pro version, i know they looks a bit diferent but isent imposible to let you chose what you want it to handel of the pro options.Best regards Lars N.

I'm not going to buy the NGX if I have to resort to mouse clicks and mouse wheels for things like autopilot ( I have the MCP pro amongst other hardware panels ) - I have spent a fortune £,£££ on hardware so I'm not going to let them go redundant for an unsupported add-on.If go-flight make a patch, then fine. But I'm going to wait. The NGX is not that much of a big deal to me.Chris Farrell