Pete Dowson

Something is blocking SimConnect then. It sounds EXACTLY like a firewall type access problem. You said you uninstalled your firewall and virus checkers? Are you sure? If it isn't some security problem then it is either something wrong with the FSX installation, or just possibly ONE of your FSX SimConnect clients is somehow blocking the others. Did you try what I suggested, renaming the module "FeelThere\Legacy\LegacyXHUD.dll"? Also try re-installing FSUIPC -- but download the version 4.062 from the Announcements above. The installer now checks for and fixes a "simconnect.xml" file if one has been installed for remote connection to the exclusion of a local connection. You could also try getting a SimConnect Log (the method is described in the "FSX Help" announcement at the top of this Forum). I'll look at that for you if you can get one. Ah, you are lucky to have hair to pull out! However, better to save your energies for putting all this data into a report for Microsoft. Describe your system and the symptoms and provde the SimConnect Log, and send to tell_fs@microsoft.com. Hopefully it will help them fix all these things in the hoped-for update in the New Year. Don't expect a reply. TrafficToolbox doesn't use SimConnect, it is only using the Load facilities to get running. The other SimConnect clients are also running -- it is just that SimConnect is not talking to them. Well, you've tried re-installing SimConnect and that usually helps. First try with only ONE client at a time -- EITHER the FeelThere DLL, or FSUIPC, or GoFlight. It seems that SimConnect has a problem with more than one in some systems. If it doesn't even work with one, then, yes, try a complete re-install. Sorry, I'm not sure what you mean. The TCP/IP stuff only comes into it in the sense that it is that part blocked by firewall and privacy programs, which you say you unimstalled? I doubt if they can actually fix bugs in FSX without waiting for the bug fixed code from the FS team, which certainly isn't expected till the New Year. However, if this is primarily a configuration issue on your PC they may just be able to help, but please don't actually expect anything. Regards Pete

Thanks, but didn't you receive the 4.063 version I emailed you soon after my message? I think I found out why the initialisation wasn't occurring correctly, and asked you to check it with that version. Pete

I'd like to see the Log for the crash, along with the FSUIPC4.LOG for the same session. ZIP and send to petedowson@btconnect.com. Sorry, you won't get an answer from Microsoft. They do read all of the reports but it's a one-way syatem. Your response hopefully will be a fix in a future version of FS, or better a bug fix release for FSX soon, maybe early in the New Year 9we hope!). Pete

The "FSUIPC" it finds wil be the FSUIPC interface that WideClient is providing. You have to have WideClient running on the client PC. I cannot really help with Squawkbox as I've never used it and don't have it. It should simply see FSUIPC via WideFS. Are you sure that this is not happening anyway, and that your problem is in the Multiplayer connection? Don't forget it only uses FSUIPC to read the position and COM frequency of your own aircraft, and maybe also to set the weather (though I think that's optional). Most of what Squawkbox does it does via the FS Multiplayer interface, which is nothing to do with FSUIPC or WideFS. I'm afraid I know almost nothing about Multiplayer or Squawkbox. Isn't there a more appropriate Help or Support site somewhere for Squawkbox users? If not, surely your Virtual ATC site should be able to help? Regards Pete

ShowText will work with FSUIPC3 (since 3.60) and FSUIPC4 and WideFS without AdvDisplay being installed. Just run it as usual. Didn't you even try it? The options bottom left on the main front page of FSUIPC's options control what happens with the FSUIPC display window in FS. Please take a quick look at the documentation. Regards Pete

No. AdvDisplay is no longer supported in any case, even for FS9. It was effectively replaced by the in-built FSUIPC Window facility in FSUIPC back in version 3.60 (in April). What makes you ask now? Have you checked the FSUIPC window facilities? Regards Pete

Ah. The very first feedback after changing over to DirectInput! Thanks. I need some -- all my axes are PFC via the PFC driver so I don't get to use these facilities myself. Hmmm. Sounds like the call the create the DirectInput device isn't being made. Strange. I should be able to trace that through. Could you show me the [Axes] section or sections from your FSUIPC4.INI file please? Well, calibrate again, possibly, as I'm not sure whether DirectInput reads them the same way -- probably depends on the "HID" drivers for the joysticks, so it would vary. The only ones which might need re-assignment are those which were classified as "Z U or V" axes which may, in DirectInput terms, be "Sliders" (S and T in my notation). The most likely candidate is a slider throttle, Z before, S now. But even if you needed to do that the values should "stick" not need doing each time you load FSX. I need to fix that -- it will be something to do with the initialisation. 4.062 Axis Assignment IS using DirectInput. There's no old code not using DirectInput. I can't have both sets of code in there. If you mean "direct assignment to FSUIPC's calibrated axes" as opposed to assignment to FS controls, then, no -- that determines where the results get sent, not how they are obtained. I'll check it, find it and fix it as soon as I can, but give me your settings please in case it is specific for some reason. Thanks, Pete

Sorry, it will most certainly be some sort of bad FSX installation. You could try to re-install SimConnect (see the FSX Help announcement above). Otherwise please get a SimConnect log and submit all the details to Microsoft via tell_fs@microsoft.com. Regards PEte

You mean "not repeating", I assume? This will simply be because FSUIPC keeps a list of the last few programs which registered with it so it doesn't need to check them again. Since I removed the checking it doesn't know the program name and doesn't need to keep a list because it isn't re-checking each time. Despite the extra lines in the Log, I assure you the new method is faster! Of course not. as I told you, there is no access registration checking now. The logging of the key is only for information. Oh dear. Please do refer to the very first answer I gave in this rather extraordinary thread. I said: If there is any "problem" it is only that I am puzzled as to why you think it is a problem in the first place, even warranting spending all this time on investigating things I know about and which are designed that way. If you are seriously just objecting to having multiple lines in the Log, then I'll make a note to make them optional in future, possibly only logging them if "Extras" are requested in the Logging. But it is in no way a priority item, and it most certainly isn't a "problem" as far as I can see. Otherwise, if you are just trying to be helpful, then, thank you very much, but there was no need and I thought I'd answered it all in the first reply. ;-) Regards Pete

Wherever you told SimConnect to put it, of course. You did read the Announcement at the top of the Forum about how to get SimConnect logs, didn't you? Remember, I said to you: You should have included the Log with the report to Microsoft -- you'll need to send another now. Regards Pete

No, the new FSUIPC4 for FSX is a completely new program and needs new registration codes for both FSUIPC4 and WideFS7. Be sure to order the bundle, not the individual programs. You will get a good discount as a recent purchaser of the FS9 bundle. Regards Pete

Not for FSUIPC, no. It is quite a complex application to try to control FS in such a manner, expecially from GPS data which is relatively sparse and needing smooth interpolations between values. FSUIPC is really not much more than an interface for program such as the one you want. GPSout is a different animal altogether, only needing to throw data already collected by FSUIPC, as part of its interface job, out of a serial port. Regards Pete

Good! Pete

"Very rapidly"? I don't know about the A32o gauge, but for ASV6, at around 25 bytes each 6 seconds, even in a 12 hour flight it will grow by less than 180kb. Are you really seriously that short of disk space? I am finding it very hard to get excited by all this I must admit. Regards Pete

I think it is odd that it is writing its Key every few seconds, yes, but if it is working okay it isn't really a problem. Although your log will grow slowly, it is started again on each FS session so it shouldn't present a disk space problem. Whether this is new behaviour or not I couldn't say. I'd need to delve into my archives to find earlier FSUIPC code to see whether I would have logged every instance in earlier versions. I really don't have time right now. Regards Pete

You are using Project Magenta? You didn't say. That does make a huge difference you know!!! All the PM offsets are listed in the PM Offsets documentation on the PM website. You never actually mentioned "this function", only a general question encompassing almost everything, thus: Perhaps if you asked specific questions then you'd get more help? So far all I've gleaned from you is not much more than "we got this hardware ..." (I assume it is hardware, you don't actually say, unless "PCB" = "Printed Circuit Board"?) and pretty much "we don't know how to use it". There's plenty of information, but at present I can't see what you are actually asking for! Regards Pete

What is the actual problem? What doesn't work? Why are you looking at the log? Pete

It sounds like you've enabled the steering tiller but do not have or are not using the steering tiller axis (e.g. as fitted in the PFC 737NG). Your observations are precisely what will happen with a steering tiller -- you use that on the ground, but as speed increases the rudder becomes more effective instead and above around 60 knots the rudder is 100% and the tiller is 0%. Just disable the steering tiller. Maybe you enabled it inadvertently whilst browsing? Regards Pete

There's no actual connection between GF's software and FSUIPC except within SimConnect. I'm afraid that, at present, SimConnect appears to be rather unstable when dealing with more than one demanding client. You could get more information by generating a SimConnect Log (there are instructions at the top of this forum for this), and if you do I will gladly look at it so that I can reinforce as much as possible the bug reports I have already submitted to Microsoft. Please include the FSUIPC4 log as well. But at the same time, in any case, I urge you to report all such problems to tell_fs@microsoft.com, in as much detail as possible (including your system) and the SimConnect Log. I am hoping that most of the SimConnect problems have now been reported in sufficient detail for MS to identify the causes and fix them, and that these fixes will be in the first "update" for FSX which we may see in the New Year. Meanwhile I'm afraid it's a matter of muddling through. Regards Pete

What do you mean by "empty"? FSUIPC is just logging the fact that some program wrote that key to offset 8001. Since FSUIPC doesn't check these now, it doesn't go to all the bother to find out what the program is, but I left the logging of the Key as possibly useful information. Why does it worry you? It's certainly a little odd for a program to continually write its key to 8001 (in this case every, what, 6 seconds or so), and I don't know why it is doing that. Even the "ATN.GAU" does it three times in quick succession. But this isn't new in this version of FSUIPC. The key "9G9LCNT2MDUY" is allocated to ASv6,"ActiveSky 6" by "HiFi Simulation Software", if you want to contact them about it. Regards Pete

I would count that as a good thing. If someone went to the bother of installing it, I wouldn't expect them to want it disabled. If you want it disabled, please disable it each time after installing, or simply don't bother installing it again. This really is a benefit for those who don't realise it has been disabled (possibly by accident or another installer) and re-install it in the hope that it will be mended. Regards Pete

Why send screenshots, when all you needed to do, as instructed, is save the on screen log and attach or include that? That's why there is a "Save as" menu entry there!! How did you install FSX? Did you move it after you installed it? The "SetupPath" parameter in the Registry says you installed FSX into a folder: D:\Program Files\Microsoft Games\ but this looks very unlikely -- you would normally have it in a folder "FSX" or "Flight simulator X" or something, within Microsoft Games. Where is the FSX.EXE file? Obviously it wasn't found where the Registry says it should be -- that is why you get the error from the installer. And then why did you abort the attempt to locate FSX.EXE -- which would have enabled FSUIPC4 to be installed at least? Seems a strange thing to do. The installer has the ability to deal with the Registry problem, but only with your help, which was denied. Why? If your registry entries for FSX are in a mess then you will have problems with other Add-Ons for FSX in the future. I think you need to rectify your FSX installation before doing too much with it. Regards Pete

Good. Thanks for letting me know. Version 2.00 of the PFC driver is available now, by the way. It isn't much different to the 1.999b you are using, but the documentation is a little more up to date, at least, and there are a few internal tweaks (which you won't notice on your equipment anyway). You can find it now on the official download site, http://www.schiratti.com/dowson Well, I could do that, but I don't unless it's offensive. It may be useful to others in any case. Regards Pete

You mean it actually shows the wrong direction? What causes that then? If you mean change the reading on the gauge, then, no. Even if you could overwrite it it would be re-written by the FS simulation engine on the next frame or so. The only gauge you can offset is the gyro driven heading indicator where a "drift" can be applied. As already mentioned in this thread, it can be done using gauges especially written to simulate such things, but not with the defaults which read the FS values directly. Regards Pete

I am betting it will be a bad texture file, or something similar. Have you been trying any of the tweaks to speed FSX up at all? Maybe one of the files is corrupted. Before I try any tweaks or add-ons I always make a back-up copy of the folders affected (e.g. "Texture" as "OrigTexture") so that I can try going back simply by renaming (i.e. "Texture" to "NewTexture" then "OrigTexture" to "Texture"). Regards Pete