Steve,

 

Is this lag issue due to the firmware of the MCP Pro not being updated to A25?

 

Bill Clark

 

PS - Great job on this driver, I will install after I send my MCP gack to GoFlight to update the firmware.

Steve,

 

Is this lag issue due to the firmware of the MCP Pro not being updated to A25?

 

Bill Clark

 

PS - Great job on this driver, I will install after I send my MCP gack to GoFlight to update the firmware.

 

As far as I can tell and what was reported during the Alpha testing, but the jury is still out because the testing sample is so small. To be clear its not a lag issue, its a freeze issue which may be temporary or permenant. The sliders on the MCP PRO settings tab enable you to slow things down so the MCP PRO doesn't get overwhelmed and freeze and thus you don't need to upgrade your firmware.

 

I'm not aware of anyone running A25 which has the problem, BUT that doesn't necessarly mean I'm right, it could be that no-one has shouted about it who runs A25!!

 

Be aware though that upgrading to A25 wipes out your serial number and there is a payware driver for the PMDG 747 that will not work without the serial number being in the MCP PRO.

Steve,

 

As I understand it, the A25 update was done primarily to address the lag and the freeze issue of the MCP Pro, at the expense of eliminating the serial number (due to the limited space available for the FW code update). This has caused some issues as the drivers produced by Flight Sim Labs for the PMDG 747 and the PMDG 737 (FS9) version require the serial number, or else the MCP PRO wouldn't work. There have been a number of posts on the GoFlight forum (some have dissappeared) that discussed this. I believe all production units shipping from GoFlight now have this A25 code.

 

Also, apparently GoFlight will update devices with the older FW versions, but you have to sent your unit back to them for the FW update.

 

My particular version is A22, and seemed to work well with your LUA file, but there have been digit lags. I actually got, maybe one freeze up with your LUA driver over a number of months. However, I would get a freeze up at least 1 out 5 flights with the Flight Sim Labs driver. Because I'm no longer flying the PMDG 747, I don't care about the old driver anymore as I'm now flying the PMDG 737 NGX, and presumably the PMDG 747 V2 and the PMDG 777 later when they are eventually released.

 

So you may want to ask those experiencing freeze issues what version of FW they have?

 

Thanks,

Bill Clark

 

PS - have you ever approached GoFlight to see if they will compensate you for your work if they will incorporate your code into their software? Of course, neither you nor Goflight can charge for the HW drivers due to the PMDG policy inplace for their new generation of aircraft? I can't tell you how much we all appreciate the level of effort, you and others, have put into improving the enjoyment of this hobby. It is truly a joy to find out someone is fixing these issues, one by one.

Steve,

Results of changing the Write and CMD delay sliders:

• Increase Write Delay from 50 to 55 (CMD at default 60): Unable to induce the lag and/or temporary freeze.
  
• Increase CMD Delay from 60 to 65 (Write at default 50): Unable to induce the lag and/or temporary freeze.
  
• Increase Both Delays (CMD=65 and Write=55): Unable to induce the lag and/or temporary freeze.
  
• Reset the Delays at defaults (CMD=60 and Write=50): Induced lag/freeze in Heading, Altitude, and both Courses.
  

Testing sequence: Intialize FSX-SP2, start the PMDG interface, change the delay setting, load a saved 737-800 situation (at gate, KIAD, VC panel on ground power), test the MCPPro's controls.

 

PC: i7-2600K (not OC'd), Asus P8Z58-V Pro/Gen3, 8MB memory, Win 7 (64bit). The MCPPro is connected to a powered USB PCI card containing a NEC controller chip providing both USB 1.0 and 2.0 ports as needed. The MCPPro gets its full 500ma at 5V.

 

One other observation fyi:

While testing I also tried changing the delay settings and hitting the interface restart button. First try no problems. Second try the interface module crashed (FSX did not). Attempts to reload/restart the interface were unsuccessful including a try at unpluging/re-pluging the MCPPro.

The Win7 Events Viewer noted an error 1-2 seconds before the module faulted to be

• .NET Runtime
  
• Application: GoFlight PMDG Interface.exe
  
• Framework Version: v4.0.30319
  
• Description: The process was terminated due to an unhandled exception.
  
• Exception Info: System.NullReferenceException
  
• Stack:
  
• at GoFlight.GoFlightP8.ProcessInputs(GFP8INPUTREPORT, UInt16)
  
• at GoFlight.GFDevApi.GFInputCallBack(GoFlight.GFDEV_HW_TYPE, UInt16, IntPtr)
  

 

Later today I'll try to test in flight.

 

Hope this helps.

 

Claude

One other observation fyi:

While testing I also tried changing the delay settings and hitting the interface restart button. First try no problems. Second try the interface module crashed (FSX did not). Attempts to reload/restart the interface were unsuccessful including a try at unpluging/re-pluging the MCPPro

 

This error is because I accidently left some of the GFP8 support in place before I published the beta. Its fixed now so don't worry. Thanks for the MCP PRO info. I'll include those settings as defaults.

 

Best wishes

Steve

Is that "fixed" BETA posted now?

 

* Orest

Is that "fixed" BETA posted now?

 

* Orest

 

No, but I've just sent out a new Alpha version that has P8,T8 and RP48 support. It should be in your email right now! :Big Grin:

Rog.

Update 4: 27/4/2012

 

I've just uploaded the 2nd Beta release that contains full support for GFT8's, GFP8's and RP48's. It may take some hours before the new release is shown in the library so make sure you do get the BETA version 2.

 

One of the key features of this release is that it allows you to control light states on GoFlight devices based on actual NGX states/data. So, not only can you use this interface to configure the buttons, toggles and switches as other tools allow but you can get a valid light indication too.

 

You do not have to re-program all the devices if you currently have things setup using other tools. You can just use the Interface for the light states if you wish. Please read the user guide for details.

 

It allows full access to the PMDG SDK in a very user friendly and accessible way.

 

Please feedback and raise any issue you may have.

 

Best wishes

Steve

OK.. Please don't be hard on me for asking this Q.

 

My PC is a dog so don't have the 737NG as yet. But I do have the PMDG 747. Can I use this driver for the Go flight GF-WP-6 to work with the 747? I already have the payware driver for the MCP Pro and EFIS.

 

:)

 

Manny

Can I use this driver for the Go flight GF-WP-6 to work with the 747?

 

Hi Manny,

 

In short, No. It uses the NGX SDK and there isn't one for the 747. I have written the interface it so that the new 747 will plug into it but thats not going to help you if your PC is a dog. LOL.

 

Best wishes

Steve

Hi Manny,

 

In short, No. It uses the NGX SDK and there isn't one for the 747. I have written the interface it so that the new 747 will plug into it but thats not going to help you if your PC is a dog. LOL.

 

Best wishes

Steve

 

Its allright Steve.. this is just a tempeory issue. I am going to be building a new PC Soon once the IB fiasco gets resolved... I came looking for a small solution and in the process I found a bigger solution for a bigger issue.

 

I am glad we have a solution for the new 747 and the 737NG. Thanks to you where we could use the GF MCP Pro and EFIS.. NOW THATS BIG!

 

Thank you.

 

:)

 

Manny

Hi Steve, I have tested your interface today, and the window of the interface doesnt show up. I have installed .net 4 as requested the first time I have lauch the interface, I have then accepted the PMDG End User Licence Agreement, and since then nothing happend when I lauch the interface.

How can I help you to solve this ?

I am under Win7 64bits Ultimate.

 

Thank you for your work.

 

Franck

Hi Steve, I have tested your interface today, and the window of the interface doesnt show up. I have installed .net 4 as requested the first time I have lauch the interface, I have then accepted the PMDG End User Licence Agreement, and since then nothing happend when I lauch the interface.

How can I help you to solve this ?

I am under Win7 64bits Ultimate.

 

Thank you for your work.

 

Franck

 

Did you run Windows Update to get the latested updates for the framework?

Did you run Windows Update to get the latested updates for the framework?

 

yep, but windows update always offer me 2 ujpdates for a total of 41 Mo, even if I have just did it.