Hi all,It has been a week since I mapped the MCP and RP48 keys using the latest version of FSUIPC.Everything works fine!! I did the first online flight with this system yesterday and it was a real pleasure!!!Here is how things have been mapped (just an example, personal taste)MCP : all keys and rotary buttons have been mapped to their original function except "B/C" that has been mapped as "Alt/Hold"RP48 : buttons : CMDB, LVL-CH, LNAV, VNAV, TOGA, FD, A/T,Display mode (arc/rose) Knobs : RMI1 (nav1/ADF1), RMI2 (nav2, ADF2 (inop in FS)), Display Range, Display mode (map, vor, ils....)This is great to use the plane that way. A few remarks for those who want to do it :1. The key mapping is for a particular plane. The MCP works fine with the other planes and can be mapped differently for other add-ons.2. The RP48 keys must not be mapped for regular functions with the GoFlight driver (FD and AT work though). For instance, I had mapped the TOGA by default, it resulted in misfunction. Basically, you have to "sacrify" your RP48 module.3. The display on the MCP is not updated. FSUICP does not "talk" to the MCP. This is not a big deal.4. The buttons and switches are very quick. No delay between turning a knob and seeing the result on the screen (and my machine is not top of the art).5. I had a strange behavior from the autopilot. I switch it on, switched it off and could not switch it on again. I fixed it by pulling down the emergency stop of the MPC. It worked and it now works in both ways... it would need more investigation but so far so good.I know lots of GoFLight owners complained about the lack of compatibility. Well, this is solved now even if this is not perfect.You will map a particular plane (ie, a 737 with a particular repaint) but you must be able to copy the whole section in the fsuipc.ini file, just changing the name of the plane. i have not tried it yet but it should work.I also mapped some functions of the JetLine4 RealityXP component on the RP48.Thank you Mr Dawson.Have fun.Olivier

>Hi all,>>It has been a week since I mapped the MCP and RP48 keys using>the latest version of FSUIPC.>Everything works fine!! I did the first online flight with>this system yesterday and it was a real pleasure!!!>Here is how things have been mapped (just an example, personal>taste)>MCP : all keys and rotary buttons have been mapped to their>original function except "B/C" that has been mapped as>"Alt/Hold"If there's already a HOLD button, why did you map the B/C button to ALT HOLD as well? or does the HOLD button not work?You've convinced me that this is worth buying - I've got a fair number of buttons mapped on my sidewinder strategic commander that I'd rather map to GoFlight devices.Any idea if the radio modules would work correctly (including the displays)? I understand the MCP issue since the PMDG autpilot is unique, but I'd guess the radios work using the normal FS systems.Hint/request for PMDG - you would be the ULTIMATE GODS if you added every single function you've got that's not usable via standard FS commands (like the start levers, start switches, other overhead controls like the seatbelt signs) etc.

Hi Oliver,Do your LED`s light up on the RP48 when you press them as mine only light up when i use a stock aircraft, using pmdg 737 thebuttons and rotarys work but dont light up,on the T8 and my P8 the lights work with the 737 but not on the RP48.Tim:"Any idea if the radio modules would work correctly (including the displays)? I understand the MCP issue since the PMDG autpilot is unique, but I'd guess the radios work using the normal FS systems"Yes the Radios work perfectly dipplays and all.I use them for NAV and Com switching between them with a button on my CH Yoke.I use the radio for ATIS to get my runway heading before i program the FMC then when i get near my destination i tune to ATIS on com1 for my landing runway,then i tune Nav 1 and Nav 2 to the ils freq for landing.Its a pity we cannot program the overhead apu etc... but i was thinking of getting a touchscreen monitor as a work aroundToni P......

>Hi Oliver,>>Do your LED`s light up on the RP48 when you press them as mine>only light up when i use a stock aircraft, using pmdg 737>thebuttons and rotarys work but dont light up,on the T8 and>my P8 the lights work with the 737 but not on the RP48.>From what I can tell, on the T9 and P8 the LEDs are wired to the switch itself, and on the RP48 they're driven by the goflight software. That would explain you're behavior.good to hear the radios work. Do you have the throttles by any chance?

Timothy : I mapped the Hold button on the MCP to the VerticalSpeed function on the plane. The reason is that, in the default planes, this Hold button activated the vertical speed mode. This is a Microsoft misfunction (in fact, it makes the MCP simpler). Since I took this habit, I prefered to keep it. You can, off course, map it anyway you want.If you are interested in an MCP, maybe you want to wait for the drivers to be developped for the fancier ones that look and feel like a real 737 MCP. This is especially if you use the 737 a lot. This is a bit more expensive as well but the display will work fine and all the buttons will be the same as the real thing. It is all a matter of personal preference.To answer the RP48 question, the buttons do not lit because no function was defined with the GoFlight driver. So, when I press a button, the green light does not work. It does not really bother me since the functions appear on the screen.Happy flyingOlivier

I have the throttles at home and use it with the PMDG. Although the throttles have an issues with staying stable and steady, the throttles are doing a great job! Only issue I have are the spoilers which stay armed and changes values when you retracted them.I used the CFconfig utility to assignment the keys to buttons. I noticed that the p8 with the knobs is not recognised in FSUIPC. I do not own the MCP, but the radios work OK. Indeed you have to use the shortcut keys from PMDG in stead of the FS Controls.

Hi Ferry,I suppose that what you call P8 with the knobs is the RP48, right ?They do work with the latest version of FSUIPC.Go to the button tab, click on "Airplane specifc", then on the button zone and then turn one of the knobs. you will see that it is recognized and you can map a Key sequence to it. CheersOlivier