Trelane

Just a quick question to see if anyone out there has been able to get the Pro Flight MCP PRO to work well enough to justify it's $500 USD cost, beyond the default panels, that is? I haven't -- that's for sure. I can't even get it to work in the Level D, which they assure me should work. From what I can see they've blocked key mapping of ANY kind with FSUIPC (or even their own software, for that matter) entirely from the Pro unit in favor of their smaller, yet just as pricey MCP unit. This is pretty frustrating -- if I can't find a solution I think I'm going to return it. Thank you for any insight! Chuck B. Pennsauken, NJ

Jeez, Andy! You're everywhere these days. Have you taken over for Pete now -- OK, where'd ya stash the body? :D Hope you're doing well! Chuck B. PFE Beta Tester

Thanks, Pete. At least you've given me a direction in which to look. I'll keep hammering at it, I was just afraid I missed something. Regardless, I'm pretty disappointed and I've a mind to complain to GoFlight in any event that they would charge so much for hardware that's only compatible basically with the default aircraft. Or maybe to PMDG for their part in this rediculous situation. From what I've been reading there cerntainly are quite a large a number of upset GoFlight/PMDG customers . . . If I figure out what's wrong I'll post back with the solution. Thank you again for your time.

Hi, Pete. I'm trying to map some key commands to use with the PMDG 737 which I downloaded from GoFlight's website for their MCP panel, but FSUIPC is not seeing any of the buttons or rotaries on the MCP when I go into the Buttons and Switches or KeyPresses Tab, and I'm wondering if there's some special install instructions I may have missed that pertain to GoFlight equipment in general. I'm using FSUIPC registered version 3.915 and the GF dev.dll downloaded last night from the latest releases page here, installed directly on the FS machine and I've tried the GFdev.dll in both the GoFlight programs folder and, just for jollies, in the Modules folder in FS9 right next to FSUIPC.dll. but still no unique joy stick assignments or button recognition on the MCP in FSUIPC. Of course the MCP works just fine on the default aircraft (I guess) because I'm simply running it through their software. I have WideFS installed with Active Sky 6.5, PFE, and a couple of other addons running on another machine, but this situation occurs whether the WideClient is connected or not. My confusion right now is simply that FSUIPC isn't assigning an independent Joy # to any of my GoFlight equipment such that I'm used to seeing with my CH Yoke and TQ, and my Saitek pedals, (Joy 1, Joy 2 and Joy 3 respectively) although when I press the buttons on my RP-48 or GF-P8, the FSUIPC Keypresses page reports the assigned keystroke commands (i.e. ctrl-sh-3) are being made, albeit under joy #1, my CH Yoke. (I've assigned those keystrokes in the GoFlight software, not FSUIPC.) I've done all the basics, different USB ports, etc., and I've done several searches here and read quite a bit about the travails of GoFlight owners, PMDG, etc., and gathered a lot of information, but if I can't get my FS9 install to recognize the equipment as separate Joysticks, I'm sunk at the very beginning. I just feel like I've just missed something basic here. Thanks for any insight you can provide that might move me forward. Chuck B. Philadelphia, PA

Ah, Jeez, thanks for your quick reply but no sooner did I leave this page but I found that my computer date ont he server read Dec. 12, 2005 instead of 2008. Why that would matter I'm not sure, but as soon as I changed it to '08, all appeared to work ok. How the date change happened today is beyond me, but it obviously did. Thank you again and I'm sorry to have wasted your time. Chuck B.

Hello, Pete. FS9 shows 2 WideCients are being served but none of the programs see FS9 from the Client computers any longer. My setup has worked fine for over 2 years -- I don't even know where to begin diagnosing this one since WideFS and WideClient are such a simple install. There just aren't that many things to tinker with in FSUIPC or WideFS or Wide Client. I'm running FSUIPC v. 3.85 14th November 2008 and WideFS 6.78. Biggest changes since yesterday was the High Priority Microsoft Updates to Internet Explorer 7 and I used the free FS_Registry Repair Tool to change my registry so that program installs would automatically look to my C: drive instead of my E: drive (which is a clone of C:). I also set the scroll lock key to activate PTT in FSUIPC when I was playing the idea of using FightAssistant on one of my WideClients, but immediately Cleared it. Can you give me any idea what to look at? This is so weird. Thank you. Chuck B. MACHINE 1: FS2004/WinXP Pro 64 bit, Intel Core 2 Duo E8500 Clocked to 4.12 GHz, Thermaltake TMG i1, Asus Maximus Formula, 6GB PNY XLR8 DDR2 @1048(!), ATI 4870, WD Raptor 10K RPM 160 GB Hard Drive, Seagate 500 mgb 32mgb cache, Analog 2HTG w/ 3 19" I-INC flat panel monitors 1280x1024x32, PC Silencer 750 Quad, FSNAV, FSPassengers, FSHotSFX, FSUPIC (Payware Version), WideFS MACHINE 2: Dell Dimension E520, ActiveSky v6.5, FDC Live Cockpit, Radar Contact v4.3 or Pro Flight Emulator, WideClient MACHINE 3: Dell Dimension, Ugly Gray Box Butsolidasarock P4, Active Sky v6.5, streaming LiveATC.net, WideClient

Thank you. It must be one of my other addons, then. I will investigate as you advise and if needed, I will post a follow up here tonight (my time, East Coast US) with all of the information you need. Thank you again.

Good morning, Mr. Dowson. I'm in FS2004, using the payware versions of both FSUIPC 3.85 (14th November 2008) and WIDEFS 6.78 (5th November 2007) (My Specs are in my sig. below). After upgrading to these latest releases I've been getting an intermittent FSUIPC pop up error window telling me "Error Opening. Already Open" right after I click on "Fly Now" to start my flight. I can click through it and my flight loads and runs fine, and it only happens say half of the time, but I've never seen it before upgrading to these latest releases. I run FSHotSFX on my WideFS machine, and Active Sky v6.5, Radar Contact or Pro Flight Emulator, and Flight Deck Companion on my other 2 wideclient machines; all of these programs are usually already running, but (obviously) not yet connected. When I get the error, I have closed out each of these addon programs one by one, closing out FS9 as well (but no reboot), and I still get the error upon restart of a flight. I have run FS9 in this way with this type of set up for 2 years and never had this problem before. To make the puzzle even more difficult, I am running XP Pro 64bit and I have a cloned copy of my primary C: Flight Sim Drive as backup on the WideFS computer, and the clone does have the registered copies of FSUIPC and WideFS on them, but is not running, and I have made sure the cloned FS9 and Flight Simulator Files folders are not being shared over the network. I have done a search here but the only reference I see is to some Visual Basic Programming someone was doing a while ago. Thank you very much for your time. Chuck B. MACHINE 1: FS2004/WinXP Pro 64 bit, Intel Core 2 Duo E8500 Clocked to 4.1 GHz, Thermaltake TMG i1 Air Cooler, Asus Maximus Formula MB, 6GB PNY XLR8 DDR2 @1066, ATI 4870, WD Raptor 10K RPM 160 GB Hard Drive, Seagate 500 mgb 32mgb cache, Analog 2HTG w/ 3 19" I-INC flat panel monitors 1280x1024x32, PC Power & Cooling Silencer 750 Quad PSU, FSNAV, FSPassengers, FSHotSFX, FSUPIC (Payware Version), WideFS MACHINE 2: Dell Dimension E520, ActiveSky v6.5, FDC Live Cockpit, Radar Contact v4.3 or Pro Flight Emulator, WideClient MACHINE 3: Dell Dimension, Ugly Gray Box Butsolidasarock P4, Active Sky v6.5, streaming LiveATC.net, WideClient

Good morning, Pete. Back in August you helped CTYankee (Sandy) resolve a conflict whereby FDCLiveCockpit and Radar Contact were stealing focus of the FSUIPC message window from one another. Your rather creative and elegant solution was to invent the "Message Filter" option in the FSUIPC.ini file -- thank you for that, a LOT. (And thank you for the Traffic Zapper option (lord, thank you for traffic zapper!)) There seems to have been a recent mini-resurgence of interest in the program FSHotSFX for use in FS9 (see this thread over at AVSIM, for example: << http://forums.avsim.net/dcboard.php?az=c_id=53380 >> ). As you probably already know, thanks to FSUIPC FSHotSFX allows you to hear all AI aircraft sounds from your cockpit, including engine spool up, take off thrust, tire screech on touch down, reversers, taxi sounds, etc. including all appropriate Doppler effects and ambience. This alleviates for the most part one of the biggest annoyances remaining in Flight Simulator - the "Silent" AI issue. It does this in part by automatically setting the "Set TCAS ID String" drop down under the Miscellaneous Tab of FSUIPC to the "Flight +" option at program start up. I would imagine that this allows it to identify which one of 54 .wav files in it's default database is the correct one to queue up for a particular AI aircraft, depending on the A/Cs size, speed, and relative position. However, it does this at a premium cost: another great program that many of us use, Radar Contact, must have the "Set TCAS ID String" option set to the "Flight" selection, otherwise it verbally identifies all AI aircraft by the bizarre sounding combination of manufacturer, aircraft type, and last 3 numbers of tail number (I think) from both the ATC side and the AI pilot side -- "Embraer . . . ERJ-200 . . . 339, Roger. Line up and wait." or something like that. As you can well imagine, this aircraft identification format is rather distracting and tends to generally detract from the whole flight sim experience. I have tried resetting the option in FSUIPC from "Flight +" to "Flight" after take-off (because FSHotSFX won't be needed again until after landing) -- but this seems to correct the problem only intermittently. RC still seems to call the AI Aircraft in the vicinity by the manufacturer/tail number designation more often than not. The only work around I have been able to devise for this shortcoming is deselecting the "AI Chatter" feature in Radar Contact while at the gate so that RC makes no verbal contact with AI at all for the duration of my entire flight. I then immediately turn on the default Microsoft ATC (ick!) and listen to that for my background AI communications, but as you can imagine this work around is quite clumsy and has it's own drawbacks and shortcomings. However, it's been more or less acceptable for now. I was wondering if there was any way to filter or split the "Set TCAS ID String" selection between multiple programs so that, say, for instance, the program "Radar Contact" is identified as always being assigned the "Flight" option and all other programs being monitored by FSUIPC were assigned "Flight +", or whatever other selection was in the drop down box, or vice versa? Perhaps the FSUIPC.ini file could be hard coded by the user in some way with a few lines of text (a la the "Message Filter" option) which would allow those of us who would like to use both of these programs to do so? Personally, I'm running Radar Contact on a WideClient machine and FSHotSFX must be run on the Flight Sim machine, so perhaps there's something that could be done based on that parameter? Any help or insight you could provide would be greatly appreciated. Thank you so much for your time and consideration with this "issue". Chuck B. Philadelphia, PA/Pennsauken, NJ USA

You seem to have omitted to paste them in! I uploaded them with that post as an attachment in order to keep the board from being clogged with a lot of text. Looks like that feature didn't work. Pete, thank you for your time and help with this. I did post a complete response to your last post yesterday afternoon which included the text of my logs and FSUIPC.ini file, but it didn't go through. (I didn't have much luck with SimFlight's forums this weekend. :-) ) After that, I then saw that there were indeed two "pan view" sections in my .ini file assigned to the hat switch numbers (32-39), one which I had failed to notice at first. The first was assigned to "controller1" and the other right underneath was assigned to "controller2". Since I had already spent some significant time on this issue it was at that point that I simply slapped my forehead, and decided to delete and rebuild my .ini file completely from scratch which is what I should have done in the first place. I then copied and pasted my custom aircraft settings into the new .ini file from the text of my backup .ini and I'll tweak those as needed and as I go along. Again, thank you for your time and help with this, especially on a Sunday. Best regards, Chuck B. KPHL, KVAY

Thank you, Pete. Here are the two logs I created and my .ini file -- I see the Pan View event, but how would I now stop it? My .ini file is assigned to the correct numbered switches on my CH yoke hat switch: 32 - 39. Thanks again for your assistance.

I'm in FS9, using FSUIPC payware version 3.42 -- I've been tweaking my computer tonight, and now my (bl**dy) Saitek pedals are sending a "phantom" command to FSUIPC and the forward view won't stop rolling end over end. This happened to me once before after a reinstall, and I actually wrote the fix down, but that was 2 computers ago and now I can't find my notes or remember how I fixed it. I've done everything my little brain can think of tonight including deleting the FS9.cfg file and let the sim rebuild but no joy. If I delete the FSUIPC.ini file and restart FS9, the rolling stops, of course, but I'm trying to avoid a complete reprogramming of all my planes, buttons, axes, reversers, custom ashtrays, etc. Can anyone tell me what command I should be looking for in the .ini file that I may be able to delete/reprogram to stop the madness? I know it's the Saitek pedals because if I unplug them from the USB port the rolling immediately stops. Thank you very much for your time. Chuck B. MACHINE 1: FS2004/WinXP Pro 64 bit, Intel Core 2 Duo E8500 Clocked to 4.1 GHz, Thermaltake TMG i1 Air Cooler, Asus Maximus Formula MB, 4GB PNY XLR8 DDR2 @1066, ATI 4870, WD Raptor 10K RPM 160 GB Hard Drive, Analog 2HTG w/ 3 19" I-INC flat panel monitors 1280x1024x32, PC Power & Cooling Silencer 750 Quad PSU, FSNAV, FSPassengers, FSUPIC (Payware Version), FSHotSFX, WideFS MACHINE 2: Dell Dimension E520, ActiveSky v6.5, FDC Live Cockpit, Radar Contact v4.3, WideClient MACHINE 3: Dell Dimension, Ugly Gray Box Butsolidasarock P4, FDC LiveCockpit, WideClient