Hi guys...I'm using MCP-PRO with A22 on a Motherboard USB2 single port (Win7 x64) plus Steve's LUA sript and no more loockups.Shipping to US from UE ( Italy ) costs more than 90€, maybe no borders charges ( GoFlight said ) but... 6 weeks waiting is unacceptable!I don't know why GoFlight has not a UE partner to serve their UE customers... ( I bought MCPRO with A22 later 2009 per 600€ in Milan.. )Regards,Francesco

Well I dug out an old powered hub, so old that it 1.1 only, and connected the MCPPRO to it, then directly to an unused 2.0 USB port on the computer. There are no 1.1 only ports on the machine.I crossed my fingers, tapped my head, and rubbed my tummy, loaded up the NGX and then proceeded to give the knobs on the MCPRO a workout, with the default settings in Steve's excellent script. No matter how fast I turned the knobs, didn't get a lockup. The course knobs were always the worst it seems, no hiccups from them.Still early, but this will hopefully be a solution. The 1.1 hub will slow down the to/fro data flow, so maybe that will give time for the MCPPRO/drivers to not get "fire-hosed".One big DISADVANTAGE to getting the A25 update, is that you lose the serial number. Doing so means losing the ability to use the MCPPRO with the payware drivers for the PMDG 747. Of course the other big disadvantage is the down time.* Orest

Edited January 2, 201214 yr by oskrypuch

Well I dug out an old powered hub, so old that it 1.1 only, and connected the MCPPRO to it, then directly to an unused 2.0 USB port on the computer. There are no 1.1 only ports on the machine.I crossed my fingers, tapped my head, and rubbed my tummy, loaded up the NGX and then proceeded to give the knobs on the MCPRO a workout, with the default settings in Steve's excellent script. No matter how fast I turned the knobs, didn't get a lockup. The course knobs were always the worst it seems, no hiccups from them.Still early, but this will hopefully be a solution. The 1.1 hub will slow down the to/fro data flow, so maybe that will give time for the MCPPRO/drivers to not get "fire-hosed".One big DISADVANTAGE to getting the A25 update, is that you lose the serial number. Doing so means losing the ability to use the MCPPRO with the payware drivers for the PMDG 747. Of course the other big disadvantage is the down time.* Orest

Hope it all works out OK. Good Luck!

Steve's script has been flawless for me on the NGX. In fact it works better than the GF stuff driver for Level D and IFLY. I find it curious Steve can do what GF does not.Yes, upgrading would mean loosing the FlightSim Lab 747 driver. I see no reason to upgrade since everything is working. Using quality powered USB hubs is a must for reliable operations. Most of the hubs I have seen include power supplies that will not provide enough power if all USB ports are used on the hub. I found myself purchasing 3rd party power supplies to ensure each port has 500ma so a 4 port hub needs 2 amps.

Steve's script has been flawless for me on the NGX. In fact it works better than the GF stuff driver for Level D and IFLY. I find it curious Steve can do what GF does not.Yes, upgrading would mean loosing the FlightSim Lab 747 driver. I see no reason to upgrade since everything is working. Using quality powered USB hubs is a must for reliable operations. Most of the hubs I have seen include power supplies that will not provide enough power if all USB ports are used on the hub. I found myself purchasing 3rd party power supplies to ensure each port has 500ma so a 4 port hub needs 2 amps.

That a good point about the amperage, the MCP PRO is heavy on the juice.

Steve, et al.NGX SP1b will not load with FSUIPC 4.751a. I have Steve's ver 1.0 and GoFlight's 2.03. Everything was working fine until last week when I updated to 4.751a. After that upgrade, after selecting a NGX aircraft, the GoFlight MCP display goes dark and FSX locks up with a "Fatal Error" message. Every time, without fail. I have even gone so far as to uninstall and reinstall FSX with only NGX and ActiveSky series through 2012 installed (any chance ActiveSky is the culprit?).Up until the upgrade to 4.751a last week on the 27th, everything was working fine. I do not have copy of Pete's older FSUIPC 4.73xx version that was usable with Steve's ver 1.0. I have no idea how to fix this problem.Any suggestions?Thanks,Rich BollWichita KS

Do you have any Reality XP units installed?* Orest

Steve, et al.NGX SP1b will not load with FSUIPC 4.751a. I have Steve's ver 1.0 and GoFlight's 2.03. Everything was working fine until last week when I updated to 4.751a. After that upgrade, after selecting a NGX aircraft, the GoFlight MCP display goes dark and FSX locks up with a "Fatal Error" message. Every time, without fail. I have even gone so far as to uninstall and reinstall FSX with only NGX and ActiveSky series through 2012 installed (any chance ActiveSky is the culprit?).Up until the upgrade to 4.751a last week on the 27th, everything was working fine. I do not have copy of Pete's older FSUIPC 4.73xx version that was usable with Steve's ver 1.0. I have no idea how to fix this problem.Any suggestions?Thanks,Rich BollWichita KS

Hi Rich,From your email you stated that the displays were out of sync with the default 737? Can you confirm that default aircraft are working OK with the MCP?ThanksSteve

Hi Rich,From your email you stated that the displays were out of sync with the default 737? Can you confirm that default aircraft are working OK with the MCP?ThanksSteve

Hi Steve,First, thanks for the LUA and making GoFlight MCP Pro work with NGX.Allow me to clarify(?) my comments:1. When GFConfig for the MCP Pro is set to the "FS Default", MCP Pro operates normally. All knobs, switches, and displays work and are in sync with what is displayed in the simulator.2. When the NGX configuration is loaded in GFConfig and the MCP Pro is set to "Compatable Add-On", the MCP pro does not function when the FSX B737 default aircraft is loaded (my default flight for FSX uses the default FSX B737 at Wichita KS. When starting FSX, I go straight to this flight). When I move the MCP Pro knobs, the VC cockpit view moves, which is to be expected. The displays values in SPEED, HEADING, and VOR OBS #2 are not agreement with what is shown in the simulator. moving the switches and knobs results in nothing more than movign the cockpit view around Upon further thought, this is probably a correct action since I am do not have the GF Config set to "FS Default". 3. After starting NGX and after the default flight is loaded (FSX B737 at KICT), when I select an NGX aircraft, everything stops. Here's what the screens look like after a few mouse clicks to try and "get things moving" again:Concurrent with selecting the aircraft, GoFlight MCP Pro goes dark. All LED displays extingish. My GoFlight Landing Gear II Quadrant is still lit and appears functional, but there's no way to tell since FSX has crashed. The GoFlight FSX Bridge remains an active program shown in the Taskbar.At the bottom is the event log report on the app crash, should that be of help.The crash is consistent, everytime, all the time.Thanks for your help, Steve!Best regards,Rich BollWichita KSLog Name: ApplicationSource: Application HangDate: 1/4/2012 11:16:59Event ID: 1002Task Category: (101)Level: ErrorKeywords: ClassicUser: N/AComputer: RJB2DesktopDescription:The program fsx.exe version 10.0.61472.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.Process ID: 1bacStart Time: 01cccaffb268efc4Termination Time: 167Application Path: D:FSXfsx.exeReport Id: d01bfae5-36f7-11e1-9991-0026832fb2b1Event Xml:<Event xmlns="http://schemas.micro...08/events/event"> <System> <Provider Name="Application Hang" /> <EventID Qualifiers="0">1002</EventID> <Level>2</Level> <Task>101</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-01-04T17:16:59.000000000Z" /> <EventRecordID>19362</EventRecordID> <Channel>Application</Channel> <Computer>RJB2Desktop</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>1bac</Data> <Data>01cccaffb268efc4</Data> <Data>167</Data> <Data>D:FSXfsx.exe</Data> <Data>d01bfae5-36f7-11e1-9991-0026832fb2b1</Data> <Binary>430072006F00730073002D0074006800720065006100640000000000</Binary> </EventData></Event>

Edited January 4, 201214 yr by richjb2

Do you have any Reality XP units installed?* Orest

No, nothing installed from Reality XP. In fact, I have ActiveSky 2012 (and earlier), GoFlight, and PMDG NGX installed on my just clean, re-installed version of FSX. I did follow PMDG's instructions on their website for removing and reinstalling FSX.Rich

Hi Steve,First, thanks for the LUA and making GoFlight MCP Pro work with NGX.Allow me to clarify(?) my comments:1. When GFConfig for the MCP Pro is set to the "FS Default", MCP Pro operates normally. All knobs, switches, and displays work and are in sync with what is displayed in the simulator.

OK, good that means the hardware and goflight drivers are OK.

2. When the NGX configuration is loaded in GFConfig and the MCP Pro is set to "Compatable Add-On", the MCP pro does not function when the FSX B737 default aircraft is loaded (my default flight for FSX uses the default FSX B737 at Wichita KS. When starting FSX, I go straight to this flight). When I move the MCP Pro knobs, the VC cockpit view moves, which is to be expected. The displays values in SPEED, HEADING, and VOR OBS #2 are not agreement with what is shown in the simulator. moving the switches and knobs results in nothing more than movign the cockpit view around Upon further thought, this is probably a correct action since I am do not have the GF Config set to "FS Default".

Thats OK, the mouse look command is sent to cancel the mouse cursor hence why you see this odd behaviour. You are correct GFConfig must be set to FS Default for default aircraft to use the MCP. So no problem there either.

3. After starting NGX and after the default flight is loaded (FSX B737 at KICT), when I select an NGX aircraft, everything stops. Here's what the screens look like after a few mouse clicks to try and "get things moving" again:Concurrent with selecting the aircraft, GoFlight MCP Pro goes dark. All LED displays extingish. My GoFlight Landing Gear II Quadrant is still lit and appears functional, but there's no way to tell since FSX has crashed. The GoFlight FSX Bridge remains an active program shown in the Taskbar.

Have you tried loading the NGX from the FSX main menu instead of using a default saved flight?So, to be clear you were using the LUA script OK until you installed a new version of FSUIPC and Active Sky 2012?Best wishesSteveEDIT: You have disabled the closure routine as discussed in the previous few posts?

Edited January 4, 201214 yr by Steveo38

Have you tried loading the NGX from the FSX main menu instead of using a default saved flight?

No, but will attempt to do so.

So, to be clear you were using the LUA script OK until you installed a new version of FSUIPC and Active Sky 2012?

Yes. And, I was using the LUA ver 1.0 script with Active Sync 2012 without issue. On December 27th, I updated to the latest FSUIPC from Pete's Updated Modules page. That's when this issue began.Rich

No, but will attempt to do so.Yes. And, I was using the LUA ver 1.0 script with Active Sync 2012 without issue. On December 27th, I updated to the latest FSUIPC from Pete's Updated Modules page. That's when this issue began.Rich

I'll do a test with that version of FSUIPC. I guess you have tried installing the full version of that FSUIPC release and not just the update? Can you also confirm you have disabled the closure routine in the LUA script as per the discussion a few posts back?ThanksSteve

Hi Rich,Just tested with your version of FSUIPC and its OK, apart from the known closure routine issue that needs to be disabled. I need you to confirm that you have done this because it is a known cause of a lockup and crash.I would also recommend downloading the LUA file again in case it is corrupted (remembering to do the above point before using).Best wishesSteve

Edited January 4, 201214 yr by Steveo38

I guess you have tried installing the full version of that FSUIPC release and not just the update?

Yes, everything works with FSUIPC versions up to but not including 4.751a.

Can you also confirm you have disabled the closure routine in the LUA script as per the discussion a few posts back?

Errrrrrrrrrr...... No, I have not! :) That might be (likely is?) my bad. Let me find that and test it out.Rich