Connect failure

[philabos]

I am running FSUIPC 4.60a which appears not to connect to add ons. Also running FSX SP2. Windows 7 64 bit.

Flight Sim Commander cannot connect through FSUIPC and shows location at 0X0 in Gulf of Guinea.

At first I thought this was an FSC problem, but also tested G-Plan which connects successfully through Simconnect. It has an option to connect through FSUIPC - and results in the same problem - locates aircraft at 0X0.

When I did a fresh install of the latest FSUIPC version, the connection actually worked and FSC functioned. When I rebooted and started a new FSX session, I was back to the same problem. This has been the pattern even for

the 4.5.7 installation. Never had this issue until W7 but apparently some others running into the same issue.

Any thoughts appreciated.

[Pete Dowson]

I am running FSUIPC 4.60a which appears not to connect to add ons.

It surely does, as I'm using in here with many addons, both locally and on WideFS.

Also running FSX SP2. Windows 7 64 bit.

Flight Sim Commander cannot connect through FSUIPC and shows location at 0X0 in Gulf of Guinea.

It sounds very much like you are running FS and the add-ons at different privilege levels. I use W7 64-bit but I have FSX installed on a separate hard disk and don't need to run anything "as administrator", but I notice a lot of add-on suppliers are advising folks to use "run as administrator" as an easy way out when folks have FS installed into the Program Files (or Program Files (x86)) folder, which is protected otherwise.

If you run FS "as administrator" you must run all FSUIPC add-ons the same way, or, vice versa, they must all be run at normal priority. Win7, like Vista before it, prevents programs of different privilege levels exchanging data the way FSUIPC and add-ons are setup to do.

It doesn't affect SimConnect as that can use Internet type messaging or named pipes.

Regards

Pete

[philabos]

I run both programs as admin - FSX is in D:Program Files (x86) FSC is in D:\.

Same result.

[Pete Dowson]

I run both programs as admin - FSX is in D:Program Files (x86) FSC is in D:\.

Same result.

Well a difference in privilege levels is the only cause I know of for the problem you are seeing. No connection at all simply means that the code in your applications cannot get a message to FSUIPC, that the shared memory cannot be established. By all means check the FSUIPC log file to make sure there's nothing odd reported there, but otherwise i really have no other suggestions. It just has got to be a privilege problem. As a test try running FSX normally (not as administrator) and running one of the standard FSUIPC client programs I provide, like WeatherSet2 or TrafficLook, also normally, no privilege.

BTW you say on the one hand there's no connection, but on the other hand that the location derived from FSUIPC is zero. Those two things are actually contradictory. If the programs cannot connect they will say so -- they'll simply timeout trying to connect and never get any data whatsoever. That is what "no connection" means. They'll come up with an error message.

If you don't really mean that, if they are connecting but getting zero data, then that's an entirely different matter. That's a sign normally of a signature or key problem. Maybe your key is not valid. Try temporarily removing your FSUIPC4.KEY file from the FSX Modules folder. If that fixes it you either have a bad key (maybe pirated), or your Windows system date is incorrect, before the date of purchase of your key and so making it look invalid.

I'm away from now till Monday, but if you'd like to paste a copy of your FSUIPC4 log file in a message here I'll look at it then. Make sure you close FSX first.

Regards

Pete

[philabos]

Thanks Pete. I had tried that one earlier - but I think the problem is now resolved.

You were right - it was in the priviledge area. Based on a tip I saw on another site, it was a Windows firewall issue.

Maybe everyone else already knew this - I did not.

Thanks for the help.

[Pete Dowson]

Thanks Pete. I had tried that one earlier - but I think the problem is now resolved.

You were right - it was in the priviledge area. Based on a tip I saw on another site, it was a Windows firewall issue.

Maybe everyone else already knew this - I did not.

Unless you are using an out-of-date install of FSX (i.e. one not up tp SP2 or Acceleration levels), the state of the Windows firewall cannot affect the local connection between FSUIPC applications and FSUIPC. It only ever affected the earlier SimConnect implementations which used TCP/IP for the connection.

Regards

Pete