Pete Dowson

Thank you for the files. The problem is a known SimConnect one, somehow caused by multiple clients. You have three, FSUIPC, IvAp and the FeelThere one: We know already that the FeelThere DLL is giving problems (there are other threads here and in the AVSIM SimConnect forum, and I'm sure I've seen a crash similar to the one you are getting with IvAp. I'm afraid I know of no solution to this yet -- Microsoft are working on these things and we hope for fixes in the New Year. Please send your report AND the three ZIP files you sent to me to Microsoft too, at tell_fs@microsoft.com. Do not expect a reply. Include 'SimConnect' in the title so it gets routed quickly. Meanwhile, until SimConnect is working fully I can only suggest trying without one or two of the SimConnect add-ons you are currently using. Regards Pete

Please give the details of this message. Please produce a SimConnect.Log, as described in the FSX Help Announcement above, and ZIP that plus the FSUIPC4.LOG and send both to me at petedowson@btconnect.com. If you have any other Add-Ons to FSX try removing each one -- SimConnect seems to have problems with more than one client. Regards Pete

You submitted this twice with different thread titles! Please refer to the earlier thread you started, where I already posted a reply. Pete

If you don't believe me, you must report it to your virus checker supplier and ask them. They will then probably update their virus list to be more throrough in that particular check so that when you next update it it will work okay. All my files are supplied compressed in ZIPs. Inside the only Executable files are also compressed and encrypted. That is done to protect them against changes -- they won't actually run if changed. However, this of course produces random sequences of bits and bytes. Your virus checker is mistaking a sequence of compressed and encrypted bytes as a virus because a part of it matches a part of what it has catalogued as part of a virus executable code. This doesn't happen with mature checkers like the Norton A/V I use because they are more thorough in the methods they use and the extensive sequences they check against. I don't know what checker it is you use, but NOD32, for instance, seems to give false indications more than most. Regards Pete

That's not quite correct, it does find FSX okay. The problem is that you either have no SimConnect installed at all, or an incorrect version, as this shows: Did you install the Beta release of FSX earlier, before the final version was released? If so, it looks like that was not properly installed. If not, then all I can suggest is that you try re-installing SimConnect. Merely uninstalling FSX and re-installing it when there's a Simconnect problem doesn't seem to help -- you need to delete the mis-installed SimConnect first. There are instructions for that in the FSX Help announcement at the top of this forum. Try that first. If you have the Deluxe version of FSX you can also install it by first installing the SDK then executing the SimConnect.MSI file you will find in the Core Utilities Kit. Failing any of this I'm afraid you'll need to get help from Microsoft. Such a problem with SimConnect will prevent any add-ons which use it from working, not just FSUIPC4. Regards Pete

Good. I'll wrap the Installer around it and put it up here insttead of 4.062. Regards, Pete

It doesn't ship with the SDK. I don't remember it ever shipping with the SDK, but if it did it must have been a fair long time ago. Anyway, it was written for FSUIPC, not FSUIPC4, hence the wroong INI. ;-) Regards Pete

No, it's a false report. Regards Pete

I sent it to the email address you use here (us moderators can see them). I've received nothing from you yet. Did you send something already? Regards Pete

I notice another user with a problem with Feel There. Please see this: http://forums.avsim.net/dcboard.php?az==402&page= Regards Pete

Er .. the email was a computer-gernerated automatic response, nothing else. The computer responding to you doesn't know what you are talking about, it just sends the same thing to everyone. This is what it means when it says "this email address is a "non-response" mailbox". Regards Pete

The throttle positions, like anything else in the cockpit, are saved in the Flight files and reloaded next time you use the same ones. Axis inputs from joysticks don't have any effect until they change. Just load FSX, set everything the way you want to start (i always have everything cold and dark -- engines stopped, fuel cut, parking brake on, battery off etc), then save that Flight marking it as your default. This isn't different in FSX to any other version of FS I can recall. ;-) Regards Pete

Er .. I assume you mean WideClient.exe? WideClient does not use or invoke Notepad. (What's "below, THEN, THEN"?). Have you added the line in the INI file for it to be loaded? What's "TFS"? I've never heard of that. Duh! Those aren't "Notepad entries", they are the files needed by (INI) and created by (LOG) the wideclient program. If they are appearing on your Desktop it means you are running WideClient on your desktop, instead of from a shortcut to the program in a Folder on your hard disk!!! Install Wideclient.EXE into the same folder as your MCP.EXE program. Add the lines in the WideClient.INI file to load the MCP program and close it. Drag a SHORTCUT (NOT the program!!!) to the desktop so you can start it easily. Pete

Yes, of course they are. The release they are announcing is FSX, the one you have -- this happened a couple of months ago. That's when the announcement occurred! Regards Pete

Sorry, I don't understand what you are talking about. The "new release" of FS is FSX, and it was actually released a couple of months ago. Isn't it FSX that we've been talking about. What is this "direction" you are talking about? I'm afraid all the Logs show is FSX and FSUIPC4 starting up, IVAP's module too. Everything is initialised by the 118th second and then it looks like you simply closed FS after three or four seconds. Even if you didn't close it deliberately, as far as both SimConnect and FSUIPC4 are concerned, the session is simply closed normally -- no crash. You say this only happens in the American continents, so it sounds like there is something else doing this based on location. FSUIPC has no knowledge or checks or anything to do with location. If Ivap is the ONLY other Add-On you are using then I would suspect that, but it seems unlikely -- and it certainly doen't look like a SimConnect problem in any case. Maybe it's some add-on scenery or other product you have added which only affects the Americas? Regards Pete

Is the full text of the FSUIPC.INI file, which is in C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules but when I start FSX, neither of these apps start. There's no "FSUIPC.INI" for FSUIPC4. You need to put those lines in the FSUIPC4.INI file! I already told you all about that in my previous reply!! Regards Pete

Try using FS in Windowed mode, not full screen, at least when using the menu. Pete

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