GHD

Hi Alan, In your introduction you stated that you had no programming skills. I hope you realise that FSUIPC is a programming interface to FSX. George

I have had the same experience when following AI, there were instantaneous jumps to 102, 86, 2, 220, 94, 2 with it returning at one second intervals back to 294, the setting in World/Weather. George

SP1 for Vista64 slipped out in Windows Update on Feb 21: I think it was withdrawn almost immediately. George

It's a Xeon Pete and it FSX works very well on it. I use it for development and usually have at least one of VC++, ADE, Fugawi etc. open on my second monitor. It is quite a beast, a Q6600 at 2.87GHz, but it has only one monitor so is not suited to development. Why don't I switch the monitors you may ask? It is running under Vista64 and I cannot install all of my legacy software. George

It seems totally screwed Pete. I have only a single core, 3.06GHz hyperthreading Xeon with 3GB ram and a 512MB 7900GS so I limited FSX to 12FPS, set its affinity to CPU1 and reduced its priority to Low. Started Fugawi, set its affinity to CPU0 and its priority to Realtime and still no connection: I guess I shall have to forego GPSout. George

Thanks for the response Pete, I am sure you are very busy at the present. On this machine using XP, I can still run FS9 with GPSout V2.57 with no problems whatsoever. Again, on this machine, with FSX SP1 I had no problems with GPSout. I installed Acceleration (SP2) and since then, the connection is flaky, sometimes Fugawi shows a GPS connection, but more often it doesn't. As I said, if I look at FSUIPC.INI, the [GPSOUT] section frequently changes to either Com1 or without me changing anything in FSX. The FSUIPC drop-down shows Com1, Com2 and the two MixW ports: Fugawi is using Com6: The only difference is that FSX now has Acceletation installed. The other machine is stand-alone running Vista64, a separate installation of FSX/Acceleration is installed so I would still need to use virtual ports, unfortunately, there are no free versions. I think some vendors provide a trial version so I could try that. Regards, George

Hi Pete, I'm sorry to spring this on you immediately following your holiday, but I am having dreadful problems with GPSOUT post SP2 I use Fugawi Maps interfaced via GPSOUT using virtual com ports 5&6. With FS9 I have no problems at all, but in FSX, post SP2, each time I run FSX I get different ports set for GPSOUT and even after re-setting them, it doesn't always connect to Fugawi Maps. Here is a typical sequence: Started FSX and set Com5/RMC etc Ran Fugawi Maps and GPS is connected: Re-ran FSX and opened FSUIPC, port has been changed to COM1: Opened FSUIPC.INI and port is still COM5: Re-ran FSX and opened FSUIPC.INI, port is Changed back to Port5 but no connection to Fugawi: Re-ran FSX, FSUIPC.INI has Port COM5 but FSUIPC dialog has COM1: Re-started FSX and FSUIPC.INI has port At no time did I set the port to other than COM5, I may have clicked "Cancel" on finding that it was set correctly in the FSUIPC dialog. I am using FSUIPC V4.205. If I can resolve this problem, I will purchase virtual com ports for my Vista64 machine, but it doesn't seem worth it if GPSOUT refuses to work. Regards, George PS. I hope you had a relaxing break.

Thanks for the reply Pete. FSInterrogate confirms the program findings, offset 0x20 is being returned as zero. However, the program positions the aircraft before interrogating the height. I was running FSX in paused, slew mode and I could see that the position was being changed but the altitude remained the same. I then "unpaused" FSX and it worked correctly. I am sure I have run it previously with FSX paused but perhaps I hadn't :? Sorry to have troubled you. George

I am running a program which used to work but now gives all ground altitudes as zero. The code is: double dLat, dLong; double dLat1, dLong1, dHeight; long long Lat; long long Lat1; long long Long; long long Long1; long GroundAlt; FSConnection.Read(0x560, 8, &Lat1); FSConnection.Read(0x568, 8, &Long1); if (FSConnection.ReadAndProcess(0x20, 4, &GroundAlt)) { dLat1 = Lat1; dLat1 = dLat1*90.0/(10001750.0 * 65536.0 * 65536.0); dLong1 = Long1; dLong1 = dLong1*360.0/(65536.0*65536.0*65536.0*65536.0); dHeight = GroundAlt; dHeight = dHeight/256.0; } The latitide and longitude are correct but the altitude is always returned as zero. Any ideas? George Edit. I've just tried with V4.203 with exactly the same result.

No wonder you are smiling in your avatar :D It was quite an epic hunt :P George

I certainly will and thanks again for your attention. Regards, George

Thanks again Pete, I didn't appreciate that FSUIPC reads every simvar and every event for each frame, I thought it read only the values I was requesting :oops: I do appreciate your concern, my only perceived problem is the size of the log file, all of my programs work fine despite the re-connections. Regards, George

Well, I am unable to determine a serious problem in my two systems. I have written a tiny C++ program which does a SimConnect_SubscribeToSystemEvent(hSimConnect, EVENT_ID, "6Hz") and it successfully receives data every 1/6 of a second with no apparent timeouts. Regards, George

Since I was getting the Data Stalled messages at approximately 5 second intervals, I set SimConnectStallTime=6. This appears to have solved the problem. Running FSX with two of my programs and Afcad2 produced only two occurrences during a run time of about 18 minutes: ********* FSUIPC4, Version 4.09 by Pete Dowson ********* User Name="George Davison" User Addr="XXX" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX Module base=61000000 DebugStatus=15 156 System time = 16:44:53 156 FLT UNC path = "C:\Documents and Settings\Davison\My Documents\Flight Simulator X Files\" 172 FS UNC path = "\\DAVISON-9C66B69\Xeon D\FSX Programs\Microsoft Flight Simulator X\" 2891 LogOptions=00000001 2906 SimConnect_Open succeeded: proceeding to initialise interface! 42781 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0) 50516 SimStart Event: Initialising SimConnect data requests 50516 FSUIPC Menu entry added 50547 C:\Documents and Settings\Davison\Application Data\Microsoft\FSX\Previous flight.FLT 50547 D:\FSX Programs\Microsoft Flight Simulator X\SimObjects\Rotorcraft\Bell206B\Bell_206B_JetRanger.AIR 115297 **** No SimConnect events or states being received! Re-connecting now**** 115313 SimConnect_Open succeeded: proceeding to initialise interface! 115313 Initialising SimConnect data requests now 115313 FSUIPC Menu entry added 115344 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0) 279703 System time = 16:49:32, FSX time = 16:45:30 (15:45Z) 280063 Aircraft="Bell 206B JetRanger Paint10" 288000 Advanced Weather Interface Enabled 295047 **** Simconnect Data Stalled! Re-connecting now**** 295141 SimConnect_Open succeeded: proceeding to initialise interface! 295141 Initialising SimConnect data requests now 295141 FSUIPC Menu entry added 295156 Failed on SimConnect_CallDispatch for Message, return = 0xC0000120 295156 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0) 295922 System time = 16:49:49, FSX time = 16:45:30 (15:45Z) 304016 **** Simconnect Data Stalled! Re-connecting now**** 304016 SimConnect_Open succeeded: proceeding to initialise interface! 304016 Initialising SimConnect data requests now 304016 FSUIPC Menu entry added 304016 Failed on SimConnect_CallDispatch for Message, return = 0xC0000120 304016 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0) 304938 System time = 16:49:58, FSX time = 16:45:30 (15:45Z) 1077828 System time = 17:02:51, FSX time = 16:57:51 (15:57Z) 1077844 *** FSUIPC log file being closed Memory managed: 740 Allocs, 740 Freed ********* FSUIPC Log file closed *********** Thanks again, George

Yes, it is weird. I use AVG 7.5 Pro but only on the XP systems, on Vista I don't run any firewall or AV, but it is always connected to the Xeon via a router. Apart from the visibility settings (which are considered doubtful) I use FSUIPC only when I run my own programs to interrogate the position of the user aircraft. In the particular case quoted, none of these were running yet I still got a 14Mb simconnect log for the 10 minute run. I will try upping SimConnectStallTime but I never have single figure frame rates on either system. Thanks again, George

Hi Pete, I did a repair after renaming x86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.60905.0_x-ww_429211e9 and it duly created a new one. However, it did not fix the **** Simconnect Data Stalled! Re-connecting now**** which occurs approximately every 3 seconds. The only other program I have running is AVG antivirus. George

Thanks for the reply Pete. I've been running FSX since its initial release but I have just noticed the large size of the FSUIPC log. On my Xeon system (XP) I get an average FPS of about 20, on the AMD (XP/Vista) it is about 40+ (I fly mainly in the UK using the Horizon Photographic Scenery). I have just run FSX on the Xeon, it takes about 7 minutes to load to the point where the aircraft is on the runway. I then let it run for another 3 minutes. The resulting simconnect000.log was 14.3Mb and the FSUIPC4.log 21Kb. All entries were to do with: **** Simconnect Data Stalled! Re-connecting now**** Are you suggesting that SimConnect may have been wrongly installed four times? I have separate FSX DVD's for each system and when I installed Vista about a week ago I needed to do two further installs to ensure that the registry entries were made into each OS. I will try the repair option on the Xeon and report back. George

Er, could you just amend the documentation? I have a dual boot XP/Vista setup, FSX is installed on the same drive for both systems. It's bad enough that there are two registries and that FSX saves files in Documents and Settings/Roaming. I can live with the different FSX ini/log file names. Re the stalling, even if I have no other Simconnect clients I see the same problem running on two separate machines, one is XP only and the other is XP/Vista. George

Hi Pete, I seem to remember that this has been mentioned before. I keep getting this entry in the log about every 5 seconds both on XP and Vista (FSUIPC 4.09). Has anything been done in FSX SP1 to alleviate the problem? Incidentally, I notice that the log is called FSUIPC4.log in XP and FSUIPC.log in Vista. George

I think you should also be aware that Generation X will take about 90Gb of storage. Currently I have all of my scenery on 74Gb Raptors so I have ordered two 320Gb drives to replace the Raptors, one for each of my systems :roll: George

It was "User defined" with one layer of cumulus 2/8 between 6000 and 7000 but with unlimited visibility. The FSUIPC vis settings were 1000/500/300/300. Yes, I'm using the VFR Photographic Scenery and VFR Terrain in FSX. It works very well. I also installed the Horizon Generation X Demo and that is incredible. Here is a top-down shot showing that it has exactly the same registration as the original (left side of shot) but the increase in detail is amazing. I've also pre-ordered Generation X and I believe it should be out next month. George ps. I would request a refund of your "Next day delivery" charge :wink:

Thanks Pete for the very complete and informative answer. In fact I hadn't enabled "Allow changes to FS own weather" on the Miscellaneous tab :oops: Enabling this immediately altered the visibility. This is just what I need when using photographic scenery. I do have Active Sky 6.5 but if the weather is lousey I tend to use the FSUIPC visibility settings. Thanks again, George

I see the warning that the Visibility tab is "For testing only! These facilities still need more FSX changes". The General limits seem to have no affect in FSX. What changes to FSX are necessary and will these be forthcoming? George

Can I echo those sentiments and also thank Pete for his patience in answering my stupid queries in this and other forums. George

:oops: Sorry Pete, I read it as Name or E-mail address. Having said that, I didn't notice the key information on the order receipt. My eyes are dim, I cannot see :wink: George