Pete Dowson

Was the FSUIPC Menu still there, and usable? Do you know if FSUIPC was still actualy in contact with FS or ont? It sounds notthe data used by GPSout is merely part of what FSUIPC is getting for any client programs. Have you got any others to check with? If not, try using, for example, the keypress or button assignments, see if they still work. Or the joystick calibrations. It sounds like Smconnect is just breaking when you start multiplayer mode. This is looking very much like yet another FSX bug! :-( Multiplayer mode screwing up data notifications from SimConnect? This needs to be reported to Microsoft with as much detail as you can, please. Best to produce a SimConnect log so I can see what is happening, and I'll report it direct as well. To do this create a file containing these lines: [simConnect] level=Verbose console=No file=\Modules\SimConnect%01u.Log file_max_index=9 and save it as Simconnect.ini in your "My Documents\flight simulator X files" folder. Then, keeping things a short as possible, reproduce the problem. close FSX, Zip up both the Simconnecxt log and the FSUIPC4.LOG and send them to me at petedowson@btconnect.com. Check the settings again please -- it sounds like something go reset. And show me the logs too. If multiplayer mode kills Simconnect then it's going to take a patch for FSXfrom Microsoft. THere a lot of things needing fixing that we know about already. :-( Regards Pete

That should not stop the Installer. What is the install error you are seeing please? There won't be any EXTRA section of FSX. Where are you reading that? I have no contacts for this other than those in the threads here. There is a very long thread down below some place. But the definitive answer, so far, is from Microsoft -- follow the link in the Announcement about FSUIPC and Firewalls above. It will lead you eventually to Microsoft's statement about how to correct the problem. I'm not sure their answer resolves everything yet though. This isn't an FSUIPC problem -- it affect ALL possible add-ons to Flight sim which use Simconnect. If Simconnect is bolocked, denied access, which is what is hapening, then nothing using it will work. Believe me, I'm jumping up and down on the relevant MS folks as hard as I can, but so far that statement is the only response. You have an Add-On menu? What's in it? If FSUIPC installed correctly, which you say it didn't, then when FSX is loaded, FSUIPC will be loaded and run too. It will be running quite happily and it will even make a Log file in the Modules folder. Check. What does it say inside? The problem is that the communication between SimConnect and FSX is blocked. SimConnect talks to FSX using TCP/IP protocols and it is those being interfered with by firewall and privacy settings. Regards Pete

I have a system for making keys and recording the rquests and it is based on emails, so please send the request, with all the details, to me at petedowson@btconnect.com. Anyway, is the person responsible for the log going to send me his FSUIPC.KEY file? It most certainly looks like he is using illegitimate keys. Regards Pete

I don't really know how to answer that. Sorry. I can answer specific questions. If you've got a conflict, tell me about it and we'll sort it out, but you seem to assume there will be some problem when I can't see why there would be. If you've not even tried to do anything yet, then how do you know what is easy, what is difficult and what conflicts, if any, there may be? If we are simply talking about calibrating a few levers to work in FS, then where does "conflict" come in? Just get them working in FS first then refine the calibration in FSUYIPC following the numbered steps in the calibration section. Please do not bother yourself with the Axis Assignments. That's for cockpit builders who know what they want to do. All the thingss you are likely to want to do are (a) dealt with mostly by FS, and (b) refined a little by FSUIPC, if you like, and optionally. You can ghave different arrangements in FSUIPC for different aircraft, but just do one thing at a time. Make a aircraft-spercific arrangements AFTER you have the main setup sorted. Doing what, exactly, quickly? You started off with a book full of wants. Just separate off what you want to do and do one of them first. Why start off making everything so complicated? You are only assigning axes (in FS), testing them and making sure they work there, then optionally calibrating them in FSUIPC. In FSUIPC if you then want to allocate one throttle lever (for engine 1) to Engines 1 & 2 and another lever (engine 2) for engines 3 and 4, there's one button labelled such to press. Same for three engines using two throttle levers. I can answer specific questions, but I am not going to write a manual. Sorry. Regards Pete

Does it run? When you say "a file", what do you mean? It creates several files, not "a file". If it says it installed okay, then Windows has said it copied the DLL into the modules folder correctly. Do you see a Modules folder? The installer creates that too! Are you sure you aren't running with Explorer set to "hide system files" or similar? You don't really need to see it, but if you want to, make sure your Explorer options are correct. Regards, Pete

Sorry, no. If I could do I would have. Terminology? It's in English, using English words relating to flight sim and joysticks. no more. Maybe there are some teachers here who can explain in mono-syllabic words, but I am very sorry, I am not one. The manual has been fully understood by thousands over the past seven years, and is surely far far easier than learning how to fly an aircraft! :-( Anyway, I can certainly try to answer specific questions, but sorry, I really cannot respond positively to blatant accusations of providing unintelligible documentation and being asked to re-write it. If this is all you bought it for why didn't you read it first, then you'd have known to use the CH control manager instead. Regards Pete

Why all the pictures? Please see my reply above. Pete

There is absolutely no connection between FSUIPC4 and FSUIPC3, there is nothing an FSX installation can do to affect an FS9 installation. These log lines 1053734 READ0 [P3820] 3304, 4 bytes: 02 00 00 00 1053734 READ0 [P3820] 3308, 4 bytes: 02 00 00 00 indicate that one or both of your FSUIPC3/WideFS6 keys are not valid, possibly pirated. If you want me to check them please Zip up your FSUIPC.KEY file and send it to me at petedowson@btconnect.com. What line? You seem to have missed something out. Regards Pete

Hmm .. it does sound very much like something isn't performaing fast enough and a queue is building up. If it isn't to do with memory buffers than it just has to be something else en route to the Client PC. Do the Client or Server Logs show any problems at all? What versions of everything are you using? Is there a delay is things happening in the Sim and being reflected in the GC? If so something is queing. If not thenI don't know. Something's going strange in the FS PC. What are the OpenGL graphics frame rates shown by the PM GC on the client? Are you sure you are not trying to drive the client too fast? 40 fps as an average is quite high for a PM networked system, though it should cope okay. As an experiment try limiting the FS frame rate to, say, 25 fps, and see if that makes a difference to how long it goes or whether it starts stuttering at all. What protocol are you using -- TCP, UDP or IPX? It may be worth trying a different one. Regards Pete

In FS9 I think it is something like "HideInfoText=1". There's also "show_brake_message=0" in the [sim] section I think. In FSX there are about half a dozen different parameters for different message types. Regards Pete

Okay, I've experimented and soon found the problem. I don't think you need report it to MS, except maybe to get it clarified in documentation somewhere. I'm not sure where you got the above content for the XML file from, but as far as I can tell, by including that file you are overriding the default setting for how SimConnect uses TCP/IP protocols in the current (FSX) PC. SimConnect is still loading modules according to DLL.XML and programs according to EXE.DLL, but it cannot communicate with them because you have changed the port and IP address. If I change your file to read: Then everything works again. I'm not sure I need the Port number, and probably the Protocol should be Auto in any case to allow it to use IPv6 if installed, but the critical part is the 127.0.0.1 which universally means "this PC". I also set scope as "local" but, again, I'm not sure how necessary that is. Regards Pete

Ah .. so the problem you are saying is that if you set SimConnect to operate on multiple PCs on a Network, it either doesn't service any of the local Simconnect client programs, or perhaps just doesn't obey the DLL.XML and EXE.XML instructions to load them? If this is true it is extremely serious and certainly needs attention. I will try some experiments here. Thank you. Regards Pete

How do I know when it is in mission mode? I think this may first need to be a request to Microsoft, to provide information about FS modes? I can get a notification "Mission Completed" and also another "Custom Mission Action Executed". But I think the latter only refers to missions being controlled by that particular SimConnect client, and maybe the former does too. There's currently no "User has entered mission mode" notification. Oddly, I did get a positive note from one user (Doug Horton no less) who was actually very pleased that the AutoSave not only worked in mission mode, but actually allowed the saved states to appear in the saved missions list. Here is what he said: "Autosave .flt files are visible from the Missions UI if you check the "Show save missions" checkbox. Nice to have, particularly as I try to work through missions, in view of my two persistent crashing scenarios. Of course, they'll disappear from being listed under applicable mission after being overwritten by newer Autosave files that don't pertain to mission." He regards this as a very useful bonus and suggested I mention it in the documentation as such. Curious that you find AutoSaves an actual disadvantage in missions. Why is that? I have two opposite views. I can understand the positive one, but not yours. How do the autosaves detract from flying missions? Care to explain further, please? Regards Pete

You shouldn't do that! An XML file has filetype XML, not DLL. The SimConnect DLL is the compiled program part of FSX which loads and runs all SimConnect client programs! This XML file: should be called Simconnect.XML, and is only needed if you are running SimConnect client EXE programs on a Networked computer other than the FSX PC. Why create the file, then? And odder, why call it SimConnect.dll? If you think you have found a bug in FSX you really need to report it to MS rather than me -- send all the details to tell_fs@microsoft.com. Regards Pete

Sorry, no idea. FSUIPC wouldn't know how to stop those, but there are parameters in your FS CFG file to stop them. Otherwise it sounds likely that you are somehow preventing access to the fonts used. Pete

Thanks! Nice to have some positives here too! It does get depressing sometimes only seeing the problems, especially when nearly all of them are at present outside my control, being to do with SimConnect by the look of it. Regards Pete

Is there an FSUIPC4.LOG file? If so, let's see it please. Are you saying that the 4.026 install (available above) runs through and says "okay" but doesn't actually copy any new files into the Modules folder? I really cannot see how that is possible, as for success Windows must be reporting okay to each operation. Regards Pete

Good. Glad you got it all sorted! Regards Pete

Sorry, no other ideas. This is evidently another SimConnect bug. Please report it to Microsoft via tell_fs@microsoft.com with as much information as possible. Regards Pete

You didn't follow some advice to COPY over the existing DLL.XML file with another, surely? :-( The FSUIPC Install program carefully edits an existing DLL.XML file to insert the correct lines to get it loading by SimConnect. From what I've seen so far precious few other software publishers are bothering to be so considerate. Chaos is inevitable. :-( What is the exact message? In version 4.026 Installer I deliberately make the Modules folder read/write accessible and also unprotect any of the files FSUIPC4 needs to install. I simply cannot understand how any file can become "Access Denied" -- unless FSX is actually still running. Do CTRL_ALT_DEL and see if FSX.EXE is present in the Process list. Maybe one of the add-ins you are using is not terminating. Kill the process (button bottom right). There are never separate "documents". All of the DLLs to be loaded by SimConnect are detailed in DLL.XML and all of the EXEs are detailed in EXE.DLL. There are no other files relevant to this business. Regards Pete

I received your log, by email, and it shows that ASV6 is somehow trying to write to C800 illegally before it has supplied its credentials: 79797 Client Application: "ASv6" (Id=3640) 79797 G:\Flight Simulator 2004\Modules\ASv6\ASv6.exe 79797 Product="ActiveSky 6" 79797 Company="HiFi Simulation Software" 79797 Illegal write attempt: offset C800, size 1024 [P3640] 79797Program or module not accredited for use with this unregistered FSUIPC I assume that its attempts have been thwarted by everything else going on during initialisation. The ActiveRadar DLL muscles in immediately after, and a program called "FSHotSFX" is then so monopolising the interface to FSUIPC for so long that I suspect ASV6 is having problems: Client Application: "FSHotSfx" (Id=3612) 79984 G:\Program Files\FSHotSFX\FSHotSfx.exe 79984 Product="FSHotSFX" 79984 Company="FSHotSeat.com" 79984 READ0 [P3612] 3304, 4 bytes: 00 00 09 37 79984 READ0 [P3612] 3308, 4 bytes: 07 00 DE FA 79984 WRITE0 [P3612] (failed, read-only!) 330A, 2 bytes: 00 00 80094 WRITE0 [P3612] 8001, 12 bytes: 55 39 39 45 5A 59 52 34 50 30 47 50 80094 Program [3612] "FSHotSfx" access registration is okay 80094 ... This above sequence shows a correct startup and registration, unlike the ASV6 one. Somhow ASV6 never gets to send its registration key early enough. Most of the rest of the log is full of so much traffic between FS and FSHotSFX that I'm surprised you manage to fly at all. Every 200 mSecs it does over 200 individual read requests! The next seen of ASV6 is 87187 WRITE0 [P3640] 8001, 14 bytes: 39 47 39 4C 43 4E 54 32 4D 44 55 59 00 00 87187 Program [3640] "ASv6" access registration is okay showing that it finally writes its access Key 8 seconds after it attempts to first write any weather data. Something is wrong with ASV6 as there is no way it should attempt to do one before the other. Please send the Log and my comments to their support. I suspect they have several threads running and there's an interlock mechanism missing. Meanwhile, there are two courses you can take: 1. I don't know how you are starting these programs, but it seems to me you have too much happening immediately after FS is ready. You really need to start up FSHotFSX some time AFTER ASV6 has started, or vice versa. 2. I am looking at removing the access checking in FSUIPC3 in any case in version 3.71, to be released this month. Nothing definite yet, but if I do the this problem will just disappear in any case. Pete

What version are you trying to install? Pete

Did you purchase FSUIPC4 / WideFS7 keys? Check your receipt. 99.9% of all registration problems are caused by incorrect entry of the correct Name, Address and KEY. Use cut-and-paste to be sure. All three fields muct match EXACTLY what it says on your receipt. The newest is 4.026 available above and I am using it all the time with PFC devices. In any case the problem in 4.02 only applied to unregistered users! Please do read the details in the Announcements! Regards Pete

This sounds like it might be related to, or the same in effect, as the problems discussed in thread http://forums.simflight.com/viewtopic.php?t=57105. That has been reported to Microsoft. Which version of FSUIPC4 are you running? If it is down to the same Simconnect bug then I did find a work-around which I've implemented in FSUIPC4 recently. If you are not using 4.026 or later, get it from the FSX downloads announcement above and see if it helps. Let me know please. Possibly the problems you are seeing are completely different. This won't help clashes between other SimConnect clients -- they either all need to take the same steps as I've done, or we need a fix from MS. I'll be releasing 4.03 next week, replacing the 4.02 on the Schiratti page. Regards Pete

First off, the Log shows that you have some Gauge or other DLL trying to use FSUIPC the wrong way. This is shown by these lines: 6016 Client Application: "fs9" (Id=1548) 6016 C:\Program Files\Microsoft Games\Flight Simulator 9\fs9.exe 6016 Product="Microsoft Flight Simulator 2004 - A Century of Flight" I don't know what it is, but it could be interfering. I suspect it to be a gauge in the aircraft loaded by your default flight, "ord.flt". Do you think you could load FS2004, change the default flight to one using a default aircraft, then close FS again please? The log then shows that a program called "MotionDrive302.exe" connected. Unfortunately you did not close FS2004 before zipping the Log. The closing is important too. Also I notice you are using version 3.65 of FSUIPC. The earliest supported version is 3.70. Som please do these things: 1. Download the currently supported latest version of FSUIPC, 3.709, from the Announcements above, and put that into the FS Modules folder. 2. Run FS2004, go to the FSUIPC Options, Logging page, and enable IPC Read and Write logging. Turn ALL other Logging off please. I only want IPC reads and IPC writes. 3. Run your MotionDrive program. See it not working, but don't run it too long in case of a gigantic log file. 4. Close FS2004. Find the FSUIPC.LOG in the Modules folder, ZIP it and send it to petedowson@btconnect.com. Please do not attach it to a reply here. Thanks, Pete