Hi Lefteris

If you help me out with this problem specified below. I would be appreciated.

FSX and device Configuration:

FSX +SP2

HP 6540b probook

windows 7 64bit

MCP PRO firmware:A25

GFconfig version: 1.95 build 4

FSUIPC4 version: 4.7.0.3

I found an opportunity to try gfmcpproxdriver for pmdg 747 in FSX with my goflight mcp pro . I dont see any numbers on the display and leds don't light up when I choose compatible addon on the GFconfig menu. If I choose FS-Default on GFconfig menu, I see numbers on the display but none of them (altimeter,heading and speed) shows correct values. When I turn the knobs up and down numbers increase and decrese on the display. Also, buttons work fine. But in neither fs-default nor compatible addon mode mcp pro works properly. Could you please help me out to get my unit work properly.

By the way, MCP pro works fine with default fsx planes. I can manage the knobs either from the mcp pro or virtual cockpit.I mean when I turn the knobs from the virtual cockpit displays are updated on the mcp pro.

FSlabs Support Response to my question:

Dear Gokhan,

did you go ahead and purchase a driver license before you were able to test and verify that the driver works for you?

You need to use "compatible addon" on the GFConfig menu and then EXIT the GoFlight utility before starting FSX. Then, you need to use our driver interface to connect to the unit via the Addons->FSLabs menu - it should bring up the dialog window where you can connect to the GoFlight MCPPro hardware.

Regards,

FSLabs Support

my response:

I did what I was told. Unfortunately, nothing has changed.When I choose "compatible addon". I see no numbers on the display and no light on the buttons.Only thing I see is dash lines on the display.

Hello to all flight simmers! I have the same problem with my set up. I have Goflight MCP PRO v.A25, with PMDG Interface. Windows 7, 64 bit os. Dashes showing on all the LED indicators. Please, help me. Thank you.

Gents,

when you check the debug box in the dialog window, do you see anything in the output?

Regards,

Gents,

when you check the debug box in the dialog window, do you see anything in the output?

Regards,

Yes, when I rotate the rotaries some numbers show up in the debug box.

That's an almost good answer. A better one would be a copy/paste of the output there...

That's an almost good answer. A better one would be a copy/paste of the output there...

Sir, I tried to copy it and it would not let me. Is there any other method to copy and paste? How would you do it?

Edjet,

Click inside the window, hit Ctrl-A, then Ctrl-C. Then paste here in a reply using Ctrl-V.

Regards,

Here is the copy of the output.Thank you.

This is a fully licensed version.

Thank you for your support!

To GF MCPPro: Dial E:

To GF MCPPro: Dial C:

To GF MCPPro: Dial B:

To GF MCPPro: Dial B:

To GF MCPPro: Dial D:

To GF MCPPro: Dial A:

To GF MCPPro: Dial F:

To GF MCPPro: Indicators: 0

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: 804000

To GF MCPPro: Dial E:

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Indicators: 804000

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: 804010

To GF MCPPro: Indicators: 804010

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: 800010

To GF MCPPro: Indicators: 800010

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: 804010

To GF MCPPro: Indicators: 804010

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: c04010

To GF MCPPro: Indicators: 804010

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: 804010

To GF MCPPro: Indicators: 804010

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: c04010

To GF MCPPro: Indicators: 804010

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Switch State: 804010

To GF MCPPro: Indicators: 804010

To GF MCPPro: Dial C: 360

To GF MCPPro: Dial B: 200

To GF MCPPro: Dial D: 10000

To GF MCPPro: Dial E:

From GF MCPPro: Dial D: -1

To GF MCPPro: Dial D: 09900

From GF MCPPro: Dial D: -1

To GF MCPPro: Dial D: 09800

From GF MCPPro: Dial D: -1

To GF MCPPro: Dial D: 09700

From GF MCPPro: Dial D: -1

To GF MCPPro: Dial D: 09600

From GF MCPPro: Dial D: -1

From GF MCPPro: Dial D: -1

To GF MCPPro: Dial D: 09500

From GF MCPPro: Dial D: -1

To GF MCPPro: Dial D: 09400

From GF MCPPro: Dial D: -1

To GF MCPPro: Dial D: 09300

From GF MCPPro: Dial D: 1

To GF MCPPro: Dial D: 09400

From GF MCPPro: Dial D: 1

To GF MCPPro: Dial D: 09500

From GF MCPPro: Dial D: 1

To GF MCPPro: Dial D: 09600

From GF MCPPro: Dial D: 2

To GF MCPPro: Dial D: 09800

From GF MCPPro: Dial D: 1

To GF MCPPro: Dial D: 09900

From GF MCPPro: Dial D: 1

To GF MCPPro: Dial D: 10000

From GF MCPPro: Dial D: 1

To GF MCPPro: Dial D: 10100

From GF MCPPro: Dial D: 1

To GF MCPPro: Dial D: 10200

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 359

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 358

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 356

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 355

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 354

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 353

From GF MCPPro: Dial C: 1

To GF MCPPro: Dial C: 354

From GF MCPPro: Dial C: 2

To GF MCPPro: Dial C: 356

From GF MCPPro: Dial C: 1

To GF MCPPro: Dial C: 357

From GF MCPPro: Dial C: 2

To GF MCPPro: Dial C: 359

From GF MCPPro: Dial C: 1

To GF MCPPro: Dial C: 000

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 358

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 356

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 355

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 354

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 353

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 352

From GF MCPPro: Dial C: -3

To GF MCPPro: Dial C: 349

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 348

From GF MCPPro: Dial B: -1

To GF MCPPro: Dial B: 199

From GF MCPPro: Dial B: -1

To GF MCPPro: Dial B: 198

From GF MCPPro: Dial B: -2

To GF MCPPro: Dial B: 196

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 346

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 344

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 342

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 341

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 339

From GF MCPPro: Dial C: -3

To GF MCPPro: Dial C: 336

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 334

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 332

From GF MCPPro: Dial C: -3

To GF MCPPro: Dial C: 329

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 327

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 326

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 324

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 322

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 321

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 319

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 317

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 315

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 313

From GF MCPPro: Dial C: -3

To GF MCPPro: Dial C: 310

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 308

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 307

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 306

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 305

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 304

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 303

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 302

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 301

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 300

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 299

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 298

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 297

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 295

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 293

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 292

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 290

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 289

From GF MCPPro: Dial C: -2

To GF MCPPro: Dial C: 287

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 286

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 285

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 284

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 283

From GF MCPPro: Dial C: -1

To GF MCPPro: Dial C: 282

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 197

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 198

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 199

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 200

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 201

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 202

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 203

From GF MCPPro: Dial B: 2

To GF MCPPro: Dial B: 205

From GF MCPPro: Dial B: 2

To GF MCPPro: Dial B: 207

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 208

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 209

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 210

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 211

From GF MCPPro: Dial B: 2

To GF MCPPro: Dial B: 213

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 214

From GF MCPPro: Dial B: 2

To GF MCPPro: Dial B: 216

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 217

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 218

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 219

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 220

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 221

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 222

From GF MCPPro: Dial B: 1

To GF MCPPro: Dial B: 223

Hi Lefteris,

when I run the game in debug mode. I see the same output as Edjet's. I have been doing research about this problem since I opened this topic here. However, I couldnt come to a result. Please help us out, lefteris.

Hi lefteris,

Have you ever tested the driver for pmdg in fsx before Its been released. Because the buttons dont light up and no numbers on the display. If you get it work on any platform, please let us know how you did it. If not, would you do something to fix it. Many people who experince this problem have been waiting for a solution. when you consider how much I paid for the driver ,the mcp unit and the pmdg software. I think I have a right to request for a solution.

gokhan.

Please, let us see some solution ASAP. Thanks.

I have the same problem as well.

I think it has to do with A25 goflight firmware, previous people with earlier A22 firmware never had this issue I guess.

I think Mr kalamaras needs to update his driver to make it work with goflight A25 goflight firmware.

By the way A25 new goflight firmware supposed to help the freezing issue on the mcp pro panel, that I was told by the tech support from goflight.

Thanks.

Gents,

can you ask GoFlight to send you A22 firmware for testing, so you can confirm? It will be impossible to test new firmware until the middle of next month as we're working on the A320 in the meantime.

I did ask for it but I didn't get any respond so far.

I talked with Mitch from Goflight but the only way to change theFirmware is by sending the MCP to them but I can't do it. I hope that Mr Kalamaras will find a way to test and fix the problem.

Thanks again.

Evan B.

Hi dear pilots,

Neither flightsimlabs nor pmdg cares about our problem here although gents, we have sent many e-mails to both companies so far, .What I did yesterday was I changed my add-on plane to ifly 737 ngx. Its %100 compatible with goflight mcp pro. Every display and buttons light up and work. I enyoy it tremendously. I recommend it to everyone.I dont want to revile against pmdg products.But, they don't have sufficient support at all. I also dont wanna pay extra money for the interface drivers anymore to get the add-on planes work with panels such as mcp pro and efis so on. PMDG might be producing good add-ons. However, they dont care about their customers at all.

gokhan.

Hi,

I am back with an answer from GoFlight for MCP pro firmware version compatibility.

To check the firmware version on your MCP-Pro all you need to do is

unplug the USB cable from the back and plug it back in in the left

course window you will see the firmware version A25 is the current

version.A25 firmware fixed the freezing problems that the MCP-Pro was

haveing.

If your are going back to firmware A22 you will get some freezing issue as mentionned by Goflight tech support but the FLIGHTSIMLABS interface will work and you will fly the Queen PMDG. It's an individual choice. Freezing and/or an interface for now.

When GF fixed the firmware in the last version A25 the serial # was removed because

there was no memory left on the processor in the MCP-Pro. That's why

if you upgrade to A25 FLIGHTSIM LABS will not have the serial # to

license your interface software.This was unavoidable to fix the

firmware for the freezing problem the MCP-Pro was having with some

add-on's.

I hope that Flightsim Labs will find a solution to produce an interface who will work with the A25 firmware and without the needed of serial number on your MCP pro.

I am asking the developer if you have any suggestion to avoid and produce an interface who will work.

No problem to pay for it.

Keep going your excellent work.

Cheers

Dear Polar,

we're sorry, but without a hardware serial number, our driver will not work, as it cannot authenticate a legal purchase. It seems GoFlight's choice is quite unfortunate.

Hi Lefteris,

I just talked to GoFlight Tech support this morning to ask about the A25 firmware update. According to John (GoFlight), this iteration completely fixes the freezing issue some of us are experiencing. As John explained it, they were almost completely out of memory with the current chipset that has to be at least almost 5 years old (I've had mine for about that length of time). So GoFlight probably has a large installed base of MCP Pro's that can only be updated via firmware flashing. To fix the serial number problem long term, they would have to unsolder the old chipset (or replace the circuit board) to completely fix existing users units. This would be expensive for customers as GoFlight couldn't afford to competely absorb the replacement costs, so the firmware fix seems to do the job more cost effectively. Possibly this issue could be fixed in the future with a new processor/memory chip, so we will have to see what happens.

However, this puts me, and others in a hard spot, as I have the freeze problem. If I get the firmware fix, then my current license for the PMDG 747-400 (FSX) will no longer work with your driver (I purchased a while back). If I don't fix, then I have to continue to dealing with freeze ups and lagging digits.

I'm assuming that all new MCP Pro hardware will ship with the new firmware, which means new potential Flightsimlabs customers will not be able to use your drivers for either the FS9 PMDG 737 or the FSX PMDG 747. Also, your existing base of Flightsimlabs users can't update their firmware to fix this issue (those who are experiencing this freezing issue) as it will prevent their updated units from working.

So we, your current customers, are between a rock and a hard place!!!

Bill Clark

Hi Bill,

thanks for the detailed description! In fact, I am a bit surprised that it has to come from you, rather than GoFlight themselves - I would have appreciated some indication that they were going to make such a change, as they were the ones who first requested that we create the drivers for their product, to make them compatible with the 737NG and 747 series.

I would like to invite you to understand our position here: This is a change made by the hardware manufacturer, quite outside our control, removing a vital piece of information that allows our product to validate itself against piracy. Without this information, there can be no authentication as it's almost trivial to simply bypass any software solution (for any hacker worth their salt). This removal comes completely by surprise to us, without any prior notice and without any collaborative efforts to work a possible solution out that would benefit you, the customer. We didn't make the change, it was done via a firmware update. This update caused several irate customers to come back to us asking why we are suddenly breaking their product - but we didn't! We didn't even touch the software - it's been the same all along!

With this information at hand, I'd invite you to write back to GoFlight to ask that they try to find a solution for this issue. We will be happy to accommodate any further firmware changes, provided they find enough (a few bytes worth) storage space to put their hardware serial number. I am sure they will have a much better idea how to do so than us! (We don't have the slightest clue how their firmware is written). We will be happy to change our code to use new commands in their SDK, if that's what it would take. We cannot, however, be expected to simply give up on our license protection mechanism simply because they decided to stop providing a serial number - I would have to draw the line right there.

Thanks for listening, I hope this makes things clearer, tho I understand the frustration fully!

Regards,

Hi Bill,

thanks for the detailed description! In fact, I am a bit surprised that it has to come from you, rather than GoFlight themselves - I would have appreciated some indication that they were going to make such a change, as they were the ones who first requested that we create the drivers for their product, to make them compatible with the 737NG and 747 series.

I would like to invite you to understand our position here: This is a change made by the hardware manufacturer, quite outside our control, removing a vital piece of information that allows our product to validate itself against piracy. Without this information, there can be no authentication as it's almost trivial to simply bypass any software solution (for any hacker worth their salt). This removal comes completely by surprise to us, without any prior notice and without any collaborative efforts to work a possible solution out that would benefit you, the customer. We didn't make the change, it was done via a firmware update. This update caused several irate customers to come back to us asking why we are suddenly breaking their product - but we didn't! We didn't even touch the software - it's been the same all along!

With this information at hand, I'd invite you to write back to GoFlight to ask that they try to find a solution for this issue. We will be happy to accommodate any further firmware changes, provided they find enough (a few bytes worth) storage space to put their hardware serial number. I am sure they will have a much better idea how to do so than us! (We don't have the slightest clue how their firmware is written). We will be happy to change our code to use new commands in their SDK, if that's what it would take. We cannot, however, be expected to simply give up on our license protection mechanism simply because they decided to stop providing a serial number - I would have to draw the line right there.

Thanks for listening, I hope this makes things clearer, tho I understand the frustration fully!

Regards,

Lefteris,

I've been following your websiste for a long time, and it appears to be unavailable most of the time. By this, I mean, your web page shows up partially, but you can't access the forums, or click on anything. This has been going on for me the past year or so....maybe I'm the only one, but I've tried with several PC's and my IPad 2.....no luck....but today it is available!

My response to you:

When I communicated with GoFlight a week or so ago, before I posted my original comments to this thread, I talked directly to John on the phone, their Tech support guy. Mitch is no longer with GoFlight as I believe he was the Marketing guy and has moved on.

John basically told me that there was very little space left to initiate a fix to the freezing the digit's or the lagging digits problems many users were experiencing, me included. He made it clear to me that the amount of firmware space left to place this fix was minimal, and the only way they could implement this fix, was to sacrifice the serial number. He said they would have kept the serial number if they could have. I pointed out to him the issue we are now discussing and he said it was up to me to chose between A22 (my current version of FW), or send my unit in and he would flash it to A25 (version that fixes the freezing problem). He also said he felt the change from Windows XP to Win 7 contributed to this freezing issue. I take him at his word on this.

GoFlight's decision, certainly affects your future business opportunities, and any current users like me. If I, or they do elect to update their MCP Pro units to firmware version A25 to fix this issue, then they are locked out of using the PMDG 737 or PMDG 747 software. This is a Sophie's choice decision for me and other registered users of your driver.

Presently, I have migrated to the new PMDG 737 NGX which currently has no driver support. However, there is someone developing an FSUIPC driver, but they apparently can't finish it until the PMDG SDK is released....once again, this is my understanding. BTW - GoFlight software does not yet support the MCP Pro for the PMDG 737 NGX at the present time. I'm sure eventually someone will develope drivers for this A/C and future ones coming down the pike (at least that is my hope)?

So, there you have it, you, me, and other FlightSimLabs installed base users are SOL. I will have to make my own decision as to how I go forward. I understand the situation, but it is what it is!

Best Regards,

Bill Clark

Lefteris

Brought the Goflight MCP-Pro myself and uploaded your driver but also having the same issue as the previous post. I spent over £60 on a driver that really does not do what it is meant too and there is no mention that it may not work on later versions of the MCP pro.

Are you in the process or will you in the near future address this issue by releasing an updated driver for the current frameware version of the MCP pro?

Dear ?

the driver is "try-before-you-buy", meaning you download it - for free, install it - for free, try it - for free, make sure it works (around LGAV) - for free, and ONLY THEN, if it satisfies your needs, you can - at your option - purchase a license to use it world-wide.

If you tried it and it did not work for you (for whatever reason), why would you pay for a license?

In terms of "releasing an updated driver" - there is no new functionality that requires an updated driver. In fact, all that GoFlight did was *remove* the serial number. That automatically invalidates your hardware against verification. You need to request that they restore this serial number, in order for "things to work properly" - nothing FSLabs did caused this problem.

In terms of "releasing an updated driver" - there is no new functionality that requires an updated driver. In fact, all that GoFlight did was *remove* the serial number. That automatically invalidates your hardware against verification. You need to request that they restore this serial number, in order for "things to work properly" - nothing FSLabs did caused this problem.

If that is the case, then how did I manage to get my MCP-pro verified for the driver when I purchased it. The MCP-pro I have is brand new and I had no problems buying your driver and going through the verification process.

What about those that have brought the driver from you, I am sure you can get verification of who they are for a more up to date driver. I am sure updating the driver would take very little time in programming terms.

I have e-mailed Goflight also regarding this and have told them to get in contact with you and find away round this and find a solution.

First of all-

it's considered bad etiquette not to sign with your name. Please start doing so, I don't know who I am responding to otherwise.

Secondly - evading the first part of my response is curious - why would you purchase a driver if after you tried it (for free) it didn't satisfy your needs? Why didn't you suggest there is an issue then?

The reason I brought the driver is becouse of the following:

Without the driver I cannot use the MCP-pro at all on the PMDG 747, non of the function work at all. But with the driver some of the buttons work and I can still use the knobs to change the speed, heading, and altitude on the autopilot. Having some of the function working it better than nothing working at all,that is why I brought the driver. But there is still the case of some of the buttons not working and the displays on the MCP-pro not working also. That is why I was asking about a possible update.

You did fail to answer a couple of the questions in my last post.

Regards

Marcus

Marcus-

you are once again evading my question.

The driver is FULLY testable in all its functionality WITHOUT purchasing a license. All you need is to place your aircraft at LGAV airport. Then you can test it to its full capabilities without a need for a license.

Once satisfied that it works well *for you*, you can purchase it to enable its functioning in other areas globally.

This is all explained BEFORE you purchase.

Regards,

I did answer your question . I did test it before hand at LGAV, and like I said in my previous post `some of the buttons work and I can still use the knobs to change the speed, heading, and altitude on the autopilot. Having some of the function working it better than nothing working at all,that is why I brought the driver. But there is still the case of some of the buttons not working and the displays on the MCP-pro not working also. That is why I was asking about a possible update.`

But you have not answered the question if you would be looking at updating the driver for people that will buy the more up to date frameware of the MCP-pro?

Regards

Marcus

Marcus-

up-to-date firmware on the MCP Pro has *no* serial number, unless there have been developments that we're not privy to. As such, the driver does not link with the hardware properly.

GoFlight have our contact information - if they have (yet again) changed their stuff to allow a serial number to be visible (and you can show this to me), we'll gladly support this process and take a look to fix. Last word we had from GoFlight, though, was that they "did not have space to put the serial number anymore".