Pete Dowson

Haven't you tried 4.063 available above? I pretty sure I fixed it way back in version 4.061, directly after the reports above! Pete

Can you not buy it as Eduardo Passos? The WideFS registration is checked in the Server part, not the Client, so it is a function of the specific FS installation. If you do so and still have difficulty (but I don't think you will) just send me both sets of details (to petedowson@btconnect.com). Regards Pete

Can you try again now, please? The SimMarket Manager says it should now be fixed. He also did say that "there can't be many simmers over there as it is the first time he's heard about the problem in all these years too!" ;-) Thank you for pointing it out! Regards Pete

If you check the log you'll probably find that it is actually disappearing and re-initialising the SimConnect connection when messages from SimConnect dry up! If that happens there will actually be little intervals of 2-5 seconds with no FSUIPC4 service. I hope all this will be cleared up in the first update MS issue for FSX! Regards Pete

strange, then, no one has mentioned this in the three years plus my modules have been selling there -- you'd think someone in the Isle of Man would have been a customer of SimMarket some time over the years. I ask the management. No, the method isn't email, but by raising a "problem ticket" on the web. I'll let you know what the manager says ... Pete

What would that say, then? "Look folks, you may get a virus warning from any of my files, in fact just about any compressed or Zipped files you may ever download. Some of those warnings will prove false, and such is the case with any of my files as of course you can always trust me and my suppliers ..." What good is that? If someone takes one of my files, adds a virus to it and supplies it, then you'll also get a genuine virus warning. The same applies to any and all possible downloads. All I can do is make sure my programs do not run if they are tampered with. I cannot guarantee that for any others, nor can I predict what may trigger a virus checker or not. my files are changing all the time in any case. In all the versions of all the files I've ever provided, only two or three have ever provoked any such warning and then in only one or two virus checkers. There's no way I'm going to "assure" folks their virus checker is lying, nor can I prevent the virus checker programs from doing a suspect job. WideFS 6.71 has been available for a month now and downloaded by thousands. Yours is the only report of it triggering a virus checker. Sorry. It's one of those cases of buyer beware, I can't do it from this end nor can I give absolute guarantees except as above. Any general statement would be totally misleading, and since it only applies to a very very small minority of virus checkers and their particular update levels, file versions and file contents it is hardly something to worry anyone. Pete

It sounds like SimConnect is not properly installed then. I can only suggest trying to re-install it -- see the FSX help at the top of the Forum. If you do choose to reinstall FSX completely, do the deletion of that Simconnect path first, as I don't think the FSX uninstall cleans that up at all. Regards Pete

Erin the extreme that would mean they would virtually not move at all over most of the range of the stick, so I really don't understand how you can get them "moving too easily". In that case they are not actually assigned in FSUIPC's axis assignments. You cannot have them active in both places and assume they will work. If the axes are assigned in FSUIPC's Axis assignments dialog for direction to FSUIPC's calibration, the Calibration part will show "direct" for that axis. If it doesn't then you've not actually assigned them. Were you using FSUIPC's axis assignments before version 4.062? You do realise that 4.061/2 have experimental DirectInput changes included, and were placed here for testing? You should know that there's a problem of them not "sticking" in 4.062 (see http://forums.simflight.com/viewtopic.php?t=58407 ) unless you do a scan each FSX session. I now have confirmation that this is fixed in 4.063 which I'll post here later today. Regards Pete

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