samainville

FS9 is running, on the title bar it does not say "waiting for client" consequently the other 2 machines running Radar Contact and FS Commander don't connect. My FSUIPC install is the latest from your site 3.99 I registered both at the same time. No Wideserver.dll found, I installed twice so far.

Installed FSUIPC for FS9, registered both FSUIPC and Wideserver succesfully and it says so in the modules section of FS9, but it's not waiting for clients and the other 2 PC's won't connect.

Thanks, that was to easy!!

Starting with the yoke, I assign aileron to the axis and then in calibration I click set then proceed to turn left, click set, return to center and click set, turn right and click set but now it goes "ding" and nothing happens unless I select "rev" checkbox and start over. But I have to uncheck or else it turns the wrong way. As for the TQ6 throttle control I assign my axis to throttle 1 & 2 but get lost of engine power when I push all the way up, I have to pull back but it does not feel like full power. All this is happening on my iFly 737 in FSX. Thanks

Got to love Wilco, From their site: Microsoft Flight Simulator X (Windows XP/Vista/Seven) / Flight Simulator 2004 (Windows XP) - Windows XP/Vista 32bits - Windows 7 32/64 bits - Microsoft FSX Service Packs 1 & 2 (or Acceleration Pack) - Pentium IV - 1.4 GHz - 256MB RAM - 32Mb Graphics. The answer: Sir, If it was running before, we assume the problem doesn't come from our 737PIC. Please note that there is no version supported for 737PIC FS2004 under Vista. Best Regards, Well unchecking "Yoke can overforce AP" fixed it for me and it's running fine;) On a different note, I cannot get this aircraft to run smoothly on Windows 7/64 with 4g of ram and installed in it's own directory and that for FS9 or FSX. I won't bother to ask them, should have never bought the necessary upgrade.

Ok, as for buttons, I was using the ones on my new MCP from GoFlight. When I suspected that maybe the MCP was the source of the problem I disconnected it and used the buttons in the game on the MCP of the Wilco 737, same results. The FSUIPC I'm using is the one posted here on June 1.

Has anyone experienced this, where when I engage the AP(cmd A) on this aircraft, anything else such lvl chg, spd, v/s, hdg, vnav, lnav will disengage it!! This model was working flawless for me. I thought maybe it had to do with my new goflight MCP-PRO, but I disconected it(usb only) and same thing. I am baffled as to what could have taken place, I'm running the latest fsuipc and nothing else has changed being that I took a break at playing the game for a while. I did do the iris alignment.

It's unfortunate, such a nice aircraft and such a nice mcp but incompatible :x So for me it's all level D and Wilco from now on. If anyone knows other products that are fully compatible please let me know as I'm looking for a 757, greatly appreciated. Thanks

From what I understand FlightSimLabs did have it at one time but no more.

Is there a way to make the PMDG737 on FS9 work with the GoFlight MCP-PRO. I'm looking for a complete solutions not something that gives me half functionality. I find the stories are varied and confusing throughout the web. Thanks

Who here might have experience with the uiautomationcore.dll problem that causes fsx to crash, and what they did to resolve it? The reason for my post is that since the error occurs after having made 20 selection from the fsx menus the crash may occur, if your last selection was fsuipc, one could end up blaming it. After numerous searches on the net, it would appear that placing a copy of the dll in the fsx directory will solve it.

Well things are coming along, will give it a test tonight with my Level D and see what happens.

Well considering I'm not that far ahead with FSX and want to put all the chance on my side, I will follow your recommendation for choice of directory. So re-install here we come, might as well try FS9 again. The button activations were intentional, I was testing that everything was working before starting to assign, when I noticed the freeze it is then I decided to investigate and avoid frustrations down the road. Thanks

Strange. Why not just change to Win7 for both? Eventually I will, I have a huge investment both time and money in FS9 on Vista and it works very well. I'm not sure if I will have to pay something to re-activate my Ariane 738, one of my favorites. Of course by moving over I would overcome the memory limitation of a 32 bit OS and that is attractive. In time I guess. As I said I will report back after making these few changes in Win 7. FSX is perfectly happy as it is, as a normal Vista or Win7 application Would the same apply to FS9 for Vista or Win 7? So we don't know if it would have recovered if one or other of the 4 (?) devices were to be removed? Hum.......... never taught of trying that.......I imagine that would point to the culprit?

Compatibility mode and admin seems to be the unwritten rule on all forums from what I gather, therefore you disagree with this practice? I have in fact pressed many buttons, with the goal of verifying that all my controllers are working, I use these various modules from desktop aviator. To date they have worked very well in Vista for FS9. I use 2 seperate drives and boot to Vista when I want to play FS9 or boot Win 7 for FSX. Yes I had to force quit (end process in task manager)because it was frozen. Let me give this another try and will see what happens. Thanks