grajay

Top job there Pete - I reset the local to global then reinstalled FSUIPC and the following secion was added to my SimConnect.xml: Starting up FSX and the Add ons menu is present and FSX is communicating with my Client OK. I should add that running the file as it was with local (apart from killing FSUIPC) I was able to connect over the network OK. As you say - the documentation needs to be a bit more explicit. Thank you again.

Thanks Pete - at least I now know (sort of :shock: ) how to get myself sorted out. Much appreciated.

Having said all of the above - clearly this is NOT a problem with FSUIPC - so I'm sorry (again) to have troubled you about it Pete. I've got myself sorted out by installing 3rd party program on my Vista machine and removing the offending SimConnect.xml file - now of course EVERYTHING works. Still strange though :roll:

Hi Pete - I MUST apologise for yesterday - trying to sort out my problem whilst suffering a migraine is not recommended. When EVERYTHING I wrote became unitelligible I realised I'd best just delete everything and retire hurt to my bed. :shock: Anyway I started today early (having slept most of yesterday afternoon and evening) on the quest to sort my FSX out. This is my installation - running FSX on Vista business 32 bit (server) networked to a WInXP (Client) machine using a Netgear DG834 Firewall router. I can confirm that SimConnect is working correctly as the 3rd party program I'm testing is connected and fully functional over the network with FSX. Here's what I have done so far: 1. Re-installed SimConnect & run the repair utility in FSX. 2. Switched off my anti-virus program 3. Installed FSUIPC 4.1.0.3 Sadly still no Add ons menu. Here's my FSUIPC install log: Here's my FSUIPC log: My SimConnect Log: As I tried rather badly to explain yesterday - if I remove the SimConnect.xml file needed to make SimConnect over my network then FSUIPC is connected without a problem: My Simconnect.xml file contains this: The only modifications I made to this file are the 192.168.0.3 500 Any advice you can offer would be much appreciated. Many thanks.

Just forget it Pete - sorry to have bothered you.

Thanks anyway Pete - I'll just keep going along as I am.

double posted - sorry

deleted

Thanks Pete - just by way of an update, I've found that I can make the OSP work together with FSX now by changing when I start it up. I've advised the dep CEO of BAV about this problem and of this thread so now it's up to them. I know I am not the only person with this problem. Again thanks for your time.

Well - perhaps 'chuck it back' was a bit on the loose side - suffice it to say that I've placed the ball back in their court :) When you say is FSUIPC running - I have to say yes it is - it is selectable from the Add-ons menu and I was able to register it without a problem. I registered FSX successfully without any issues at all. As I said, when I got my new machine (you may recall we touched on it on the RC5 group) I just installed FSX and the BAV OSP to eliminate any extraneous programs, but still it wouldn't play. The log file is attached which I believe indicates there's not a problem (I hope). I appreciate your time, but as you suspect it's something to do with the OSP itself. Thanks again. FSUIPC4.zip

Thanks Pete - fyi OSP is Offline Schedules Program - and having seen mention of it before on this forum I rather thought you'd had some dealings with it seeing as how it 'uses' FSUIPC - not to worry - I've chucked the ball back to BA Virtual.

Thanks for that Pete.

This problem has been asked about on the BAV forum and there doesn't appear to be a resolution other than to suggest that FSUIPC may have the answer. I can happily run the BAV OSP with FS9 - when it starts up the information in the Flight Monitor Window shows [FS2004 FSUIPC3.719]. When I run the OSP in FSX I get the information in the Flight Monitor Window [unknown2 FSUIPC4.07]. Shortly thereafter the message: "Another Flight Monitoring is already collecting your flight data, aborting" - clicking OK leaves me with a warning message "Unable to load flight plan". When I first ran FSX in early December the OSP worked fine - the ONLY change I had made was to change my anti-virus software (from AVG to Avast) - so when I reinstalled FSX on my brand new machine I was anxious to try the OSP and FSX in it's 'raw' state - but got the same error message. I've been told that I had to delete my fsuipc.ini file after updating FSUIPC which I've also done. So can you tell me if this problem is an OSP one or an FSUIPC one please? I suspect the OSP as afa I know nothing has been done to it to account for FSX, but a lot of people seem to be using it without any problem. Thanks.

Thanks Pete - I guess I'll not be the only one to be in this kind of situaltion.

Hi Pete I'm just a little confused (nothing new there I hear you say) but I'm sure you'll square me away. My WideFS was purchased in August this year but FSUIPC is a lot older - do I buy an upgrade for WideFS and a new FSUIPC please? My confusion is that the Bundle cost for a new WideFS and FSUIPC would appear to be the same as the method I outlined above, unless I'd qualify for an upgrade for both? Thanks. There's always one isn't there?