FOD

Pete, Many thanks for your prompt help as always. Ports were all correct with no conflicts. I eventually went for any changes I had made over the last few weeks and un-installed a couple of programmes I had tried. I then un-installed MSE from both systems (which I had swopped for AVG Free as the latter seemed to be growing with every update) - no change. I then reinstalled MSE to search on line for solutions but carefully made sure that both firewalls were off. The first option I tried after this - "voila" Wide FS connected immediately and after a couple of tweaks simconnect was also back on line. In the end, I suspect that somehow a firewall had still been active on one of the systems - although I don't understand why it only affected FSX and not FS9? An interesting 24 hours but we got there. Best Wishes John R

For well over a year, I have been running FS9 and FSX {on 2 separate partitions} networked to a second computer via an ethernet connection as an FS Support system with Wide FS to run programmes such as Squawkbox, FlightSim Commander etc etc. During the last month I flew FS9 exclusively but today tried FSX. It ran correctly except that Wide FS would not connect. Fsx showed Wide Server waiting for clients and Wide Client showed waiting for a connection. A copy of the wide client log is as follows: Date (dmy): 13/01/11, Time 17:40:06.640: Client name is JER 94 Attempting to connect now 110 Trying TCP/IP host "JER1" port 8002 ... 110 ... Okay, IP Address = 169.254.208.49 21172 Error on client pre-Connection Select() [Error=10060] Connection timed out 21172 Ready to try connection again Repeated until I close dowm - note, the IP Address identified by the log is correct So far I have checked the installation on both computers against the Wide FS manual, ensured all firewalls etc are turned off, reinstalled my windows network, and checked that all necessary files are shared and can be seen and opened in Network Places. All to no avail. But Wide FS/FS9 still works perfectly! On the other hand, I have also lost the FSX Simconnect connection between the two computers! So it seems to be something blocking the client computer seeing FSX - with either Wide FS or SimConnect - but nothing else! Not sure where to look next so v grateful for any suggestions John R

Pete, Thanks for the response. I wasn't criticising but had discussed this problem on two other forums with guys who had the same problem with a lot better hardware than I have. Hence I came here to see if there was anything else I might try. By the way, it occurs using Alt-enter as well as the menu. However, I have found that if you switch off AA in FS9, the dialogue box comes up and can be accessed ok but with a black screen behind it. This is even if you are using AA through the graphics card control panel. In addition, there are other odd graphics issues with Win7/FS9 in full screen mode [eg right click over scenery area and cursor changes from white arrow to solid black arrow} so I guess it goes back to my original conclusion that I have a Win7/FS9 problem which could be graphics card and/or drivers or perhaps DX11 incompatibilty etc etc . Best Wishes and, as always, many thanks for all your efforts in keeping FSUIPC etc available to us. John R

Unfortunately, I have the same problem with Win 7 and have tried: 1. Two separate computer systems {one AMD, One Intel C2D} 2. Two different graphics cards {NVidia + ATI} 3. Several different drivers from original win7 drivers to latest from the card manufacturer. All with no effect - select FSUIPC in full screen and FS9 goes black screen. Odd that FSUIPC in Win 7/FSX is ok. Suspect that perhaps its a Win7/FS9 problem but to date no other add-ons have any problems. Grateful for any other options I might try. Many thanks John R

Thanks Pete. "Interpretation" was the wrong word. Particularly as I am English and not many miles away from you. I don't pretend to understand the intricacies of FSUIPC but when I read that the "client part is the same as before" etc, I am afraid that the wish was master of the thought and I jumped to the wrong conclusion. Ah well, off to SimMarket for Wide FS {and I have missed out on the bundle - that'll teach me}. Best Wishes John

Firstly my apologies - I have searched but could not find the answer. I have a fully registered copy Wide FS for FS9. Today I have purchased a license for FSUIPC for FSX and I interpreted the web site as not requiring me to purchase a new Wide FS license {as the FSX server is already in FSUIPC4}. However, while I can immediately register FSUIPC4 in FSX, I cannot remove the "register Wide FS" box. Grateful for advice. John Rooum

Interesting - I have spent the last few days trying to use this axis of my X52 as the steering tiller using the new Beta version. To add to Francois' comments - both rotary axes on the X52 throttle [the other is below the highlighted control in the screenshot] can in fact be assigned directly in FS9. I have used the highlighted one for several months as a tiller by assigning it to rudder control in the FS9 assignments dialogue. FS9 also seems to retain the twist grip stick as a rudder control by default. However, when using FSUIPC control, the highlighted rotary control is not recognised either in "assignment" or "calibration". Occasionally, when the control is first moved FSUIPC will assign a letter but that is all - the numbers do not change as the control is moved. But of note, the other rotary axis control can be assigned using FSUIPC and works perfectly as a tiller. Not as easy to use but still effective. I have no idea why the highlighted control cannot be assigned in FSUIPC - a quirk in the X52 software perhaps?? John Rooum