Pete Dowson

You are using FSUIPC 4.08, which is not only the wrong version for use with the SP1 update, it was actually out of date for over a month before SP1 was released in any case. It is not supported! Please go and install FSUIPC 4.10 as advised several messages ago! Pete

Since "uninstall" is simple removal of the DLL, and "re-install" is simply putting it back, I don't see how that will make any difference. We haven't yet determined whether FSUIPC even gets loaded -- from what you describe it doesn't (though you could check by looking for the FSUIPC4.LOG file as I suggested). So changing it or "reinstalling" it won't make any difference. We need to tackle whatever it is that is crashing BEFORE FSUIPC gets to run -- either SimConnect or another SimConnect client program, perhaps. All this is described in the references I gave you. Regards Pete

Okay. One last try before I really do have to await more detailed help from MS. Please download 4.103: http://fsuipc.simflight.com/beta/FSUIPC4103.zip and test that in the same way. FSUIPC4 and SimConnect logs to me, please. If it is more or less okay, stop the SimConnect logging (just rename the SimConnect.INI file) -- that may be contributing to any stutters by its disk accessing etc. Regards Pete

See your email. ;-) Pete

Never mind, now. I've managed to reproduce a similar case. It doesn't actually stay displayed forever -- in certain circumstances the time is being supplied in timer ticks (55 mSec intervals) instead of seconds, so the 10 second display time in your case becomes 181 seconds, or three minutes. Sorry. Look out for an interim update for FSUIPC soon, maybe over the weekend. It'll appear in the FSX Downloads announcement, above. Regards Pete

I have no idea because I have no information. It is information which enables us to find things out like "why". If it is the same as described in my Announcement, then it is a bug in SimConnect which is supposed to be fixed in SP1. I'm not sure why you want to delete the DLL, but whether you do or not will not affect a different file which already exists, will it? So it doesn't matter. Pete

You don't ever NEED to enable a log file. FSUIPC always produces a log file. I said: Right? You don't understand any of that, I assume? You could of course refer to the FSUIPC4 user Guide. But to keep it short: First, find the FSUIPC Options. This is via the Menu in FSX. Can you see a menu? If not, press the ALT key. A Menu should appear. In that Menu there should be one called "Add-Ons". Click that. In the dropdown there should be "FSUIPC ...". Click that. In the resulting window there should be a tab labelled "Logging". click that. On the right-hand part there's a sort of table in which you can enter things. It has 4 rows. We will only use 2 of them. In the first enter 32FA for Offset, then select S16 in the Type dropdown. In the second row enter 3380 for the Offset and select Asciiz for the type. Check the "normal log" checkbox below. OK out of the window. Back in FSX proper, reproduce the problem. Close down FSX. ZIP up the files called "FSUIPC4.LOG" you will find in the FSX "Modules" folder, and send it to me. Okay? If you still cannot manage it, please send this off to ActiveSky support and ask them. Pete

HmmmI'll need more information. It may be a Simconnect problem now, as with SP1 installed FSUIPC passes all that stuff on to Simconnect to handle. Before SP1 FSUIPC had to do it directly itself. Did the original message, before SP1, scroll, or was it static? Does changing this option in FSX's options change how it behaves? Can you enable Monitoring (Logging options page in FSUIPC), of offsets 32FA (as type S16) and 3380 (type AsciiZ), and check the "normal log" option below. Then reproduce the problem. Zip up the FSUIPC4.LOG file and send to petedowson@btconnect.com. Regards Pete

Ah, sorry. No I don't recall that at all. but then, with thousands of interactions per week I sometimes surprise myself at remembering anything! Maybe i could remember more when I was younger, but I forget. ;-) Er. What happens if you don't? Do the values they contain revert? Have you any logging to show what is going on? If there's a new Simconnect bug it will need reporting, but I need to understand it more. Please, using 4.10, enable Monitoring of those locations and have them monitored to the normal Log. Also enable IPC write logging. Send the Zipped log to me at petedowson@btconnect.com with an outline of what you were doing during the period of the Log. Try to keep it short, but don't start a new log so i can see the initialisations too. Regards, Pete

Please make sure you have installed FSUIPC version 4.10, not 4.0 ... Then please read the Announcement above entitled "Important FSUIPC4 Installation Notes". Does this describe what you see? If so, please try to do what it says. If not, then it sounds as if SimConnect is corrupted on your system. In that case, please see the Announcement entitled " FSX HELP: Logging or Re-installing SimConnect", and try re-installing Simconnect. I can help get the proper Microsoft help to sort your problems out, but I need more information. First, I need to know if there is actually an FSUIPC4.LOG file in your FSX modules folder. If so, show it to me please. Second, you need to make SimConnect produce a log, so we can see what is going wrong during the load sequence. How to do this is also explained in the Announcement " FSX HELP: Logging or Re-installing SimConnect". Oddly enough, it is exactly as it says in the Documentation! Didn't you bother to look? Simply remove the FSUIPC4.DLL from the FSX Modules folder. Regards Pete

What do you mean by "the new FSUIPC"? Have you read any of the Announcements? Have you installed the FSUIPC verison 4.10, introduced to update it to work with SP1? Is there an AddOns menu entry for FSUIPC? Have you any FSUIPC4 log files to show me? I really can't tell you anything at all unless you tell me more, please. Pete

I don't understand what you mean at all. How are you "commanding" this, and what does it have to do with FSUIPC? Aren't you using elevator and aileron control (yoke)? Pete

I'm not really the right person to ask, but I don't see why not. Why do you suspect a problem? Yes. Why not? Yes. How else will you push the plug in? You can't get two plugs into the one socket. ;-) FSUIPC really has got little to nothing to do with it, so, no, no issue. Regards Pete

You don't buy a specific version, other than FSUIPC3 (for FS2004 and earlier) or FSUIPC4 (for FSX and later). I am not going to support and maintain hundreds of different versions, just because one particular one was current at the time you paid!!! You are expected to use the latest one, always, otherwise you aren't getting any support. The latest (4.10) will run on ANY version of FSX, with or without the SP1 patch. As will the next one, and so on. You only pay once for all those future versions. SimMarket do not supply FSUIPC, they only supply the access Key. You get FSUIPC from the Schiratti download page, or, for interim updates, in the Announcements above. Pete

No. You'd need to be able to get to the options display to register in any case. It seems as if it must be a video driver problem. Have you tried switching FS to Windowed mode first, just to see? Nor have I, sorry. It simply has to be something wrong in Windows. The are lots of folks having lots of problems with Vista, and we are all looking forward to the first patch release. I have it installed on a test PC just to make sure there are no problems in my programs, but I wouldn't yet use it for any real work or flying. Anyway, the video driver is my best guess. But try windowed mode (swap FS between full screen and windowed mode by ALT+ENTER). Regards Pete

Not in FSUIPC. You can monitor specific offsets, but you need to specify which ones first. You seem to be going about it back to front. Why not simply look up the functions you want to use in the Offsets list? There's also the excellent FSInterrogate utility, which can continuously monitor all or any selection of offsets, or simply look for changes. This tool is part of the FSUIPC SDK. Regards Pete

I don't think the small stutters are related to fSUIPC, but 4.102 evidently isn't working in any case. The problem revolves around ambiguities in how to identify the User aircraft in Multiplayer mode. I'm still talking to MS about this, but the weekend is going to get in the way. I'll let you know when there's any progress. Meanwhile I'm withdrawing 4.102. Regards Pete

I have made a few small changes in FSUIPC4, as an experiment -- they were suggested by some things asked of me by Microsoft. Whether they will help or make things worse I dont know. But please donwload 4.102 using this link: http://fsuipc.simflight.com/beta/FSUIPC4102.zip This is the DLL only. Just copy it into the Modules folder (you may need to "unblock" the ZIP in its file properties first). If you could get me both an FSUIPC4.Log and a SimConnect log using this, as before, Id be grateful, no matter what the outcome. Thanks! Pete

What does "from then, I can't load FSX" mean -- please say what happens. Does it crash, or what? If it crashes, as soon as you answer that question, then it cannot be FSUIPC4 which is doing it, because it isn't running then -- the question appears BEFORE it is even loaded. It sounds like the well known SimConnect security check bug. If you visit my Support Forum (which is where you should go in any case) and read the Announcements through, you will see precise instructions for dealing with this -- it is due to other SimConnect clients you already have loading. However, MS did say they'd fixed this problem in SP1, though it was only a work-around, I understand. What version of FSUIPC4 by the way? That might make a difference. If it isn't 4.10, the version released for SP1, it will be still using the original SimConnect release, the one with the bug. If it still occurs with 4.10, please check the Announcement in my Forum entitled "FSX help ..." it tells you how to get a SimConnect log. It would help prove to Microsoft that there may still be a problem in this area if you could repeat your problem after enabling SimConnect logging, then Zip up the SimConnect log and send it to me at petedowson@btconnect.com. Please continue this in my Support Forum. I will expect to see you there. Regards Pete

What version of FSUIPC? If not the latest (3.74) please update and try again. It works fine with Vista Home Premium. I've installed it and registered on one myself. There's nothing special about the dialogue FSUIPC provides for the options. It is just a standard Windows dialogue using standard Windows API calls. It sounds like there is either something else in your system which interferes with these (like Window Blinds), or something else is wrong in the installation of Windows itself. Please first try with the currently released supported version. If you still get the problem then it may be that a Vista repair is needed, although first a review of whatever else is running might be in order. Regards Pete

The event system is working, just not the aircraft and other data -- none of the standard SimVars feeding the FSUIPC offsets. This being FSUIPC's main purpose in life, it gets upset if it doesn't receive such data, hence the attempts to fix it by reconnecting 9which worked fine, and once only, before SP1). I've provided the info to Microsoft and am in discussion with them about what might have changed to cause this in SP1. I'll be in touch when I've any news or something else to try. Regards Pete

There's no such version. Your 3.44 is a long long way out of date and not supported. Nor is 3.48, per your subject. Please update to 3.74, the current release. Pete

They are not FSUIPC-version specific. FSUIPC4 runs only in FSX, FSUIPC3 runs in FS2004 or before. Unless you are running both FSX and FS2004 at the same time in the same PC (what?) there's no possibility of any clash whatsoever. You don't need to uninstall anything other that FSUIPC in order to uninstall FSUIPC, and uninstalling is simply a matter of removing the FSUIPC.DLL from the Modules folder, as clearly documented. To "unregister" you only have to delete the FSUIPC.KEY file from the Modules folder. Uninstalling FS2004 is a rather ridiculous thing to do, isn't it? Just delete the FSUIPC.DLL file from the Modules folder EXACTLY as stated in the documentation? Why not read it, or at least just the bits you want to know about? FSUIPC is deliberately kept non-invasive. It affects nothing else but its own files. It doesn't infiltrate anything else whatsoever. Delete it and it is gone, it is as simple as that. But you are still wrong blaming it in the first place. Regards Pete

Okay, thanks. That's all good. We'll never know now what the original problem was. Regards Pete

That really has me puzzled. I would have liked to see the Install Log for thatbut I see it is too late now! :-( I will have to wait for someone else with the same problem now, to see why. :-( Can you please let me see the FSUIPC4.LOG? I'd like to know what SimConnect it thinks it is using. Thanks. Regards Pete