Pete Dowson

I don't know. I'll take a look tomorrow. chase me if you hear nothing in a day or two. Pete

Not possible. I never sold it. It has ALWAYS been sold by only three parties -- SimMarket, Project Magenta and Intercraft (Japanese). You put FSUIPC4 into FS9? That won't work. I'm sorry, but you are completely mixed up. FSUIPC4 is for FSX and the future ONLY. Until Saturday last that didn't exist. The ONLY supported version before that was FSUIPC3 (and WideFS6), which work on all versions of FS from FS98 to FS2004 inclusive, and also CFS1 and CFS2. All this information is clearly available to you if you'd bother to look. Nothing has changed recently EXCEPT the release of FSX and completely new versions of my programs to work with it. If you are not interested in any of that, nothing has changed for the last three years excepting incremental improvements in my software, from FSUIPC 3.00 to the current FSUIPC 3.70 93.709 available here), all of which are covered by the same keys. If you have receipts for things you pay for you can expect to get them serviced. If you keep nothing and no one has records of you (... I wouldn't in any case as I've never sold direct), you cannot really expect that much sympathy. I'm sorry. You do really need to protect your own property a little better unless you have money to throw away. I'm sorry I cannot help you, but it does neither of us any good ranting and raving here, especially with a completely irrelevant subject line and a complete false start because of it! Regards Pete

If you can post there, please refer them to this thread. It is likely to be the same problem. If Simconnect is being blocked it will affect lots of add-ons -- more and more as time goes on. And not just those which use FSUIPC, as TrackIR does not. Regards, Pete

If it doesn't use the path in FSUIPC that could go wrong. FSUIPC wouldn't report anything. I assume you mean HotSeat was reporting that? FSX plans are in XML. The FS9 version of HotSeat won't like that! That wouldn't actually matter. You can put DLLs or other files into the Modules folder till you're blue in the face, but only those listed for loading in Simconnect's DLL.XML file will ever get loaded -- except where one of the properly loaded ones loads another, as FSUIPC4 loads GFDev.DLL, EPICINFO5.DLL and PFCFSX.DLL if they are present. No, it won't. No way. If FSUIPC4 isn't actually named FSUIPC4.DLL it won't be loaded by FSX. Regards Pete

Seems unlikely that's the actual cause, maybe it is related to something in the updates though. I've actually never heard of a problem where you couldn't get Windows updates. Hmmm. So far it seems uninstalling some or all of virus or security software fixes things, but as I say, there are a huge number of WinXP security updates too over the last few months. Maybe there's something wrong with those if, for example, they get installed in the wrong order or similar. Thanks for the info, Pete

I don't know. AutoSave uses the Registry to get this information, and it has worked in previous versions. And as I said, it works here. We need to find out why it is getting the wrong path. In the case of AutoSave I could simplify it and use a local path not a "Universal" (UNC) path, but FSUIPC has to derive the UNC one in any case for programs running on a Network and wanting to access plans, flights and so on. The search for the correct "Share" name is done on this item in the Registry: "My computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares" Do you think you could check this for me? Do RUN, REGEDIT, then find that entry (RegEdit works like Explorer), highlight the "Shares" entry then go to the File menu and select Export. Save it somewhere as, say "MyShares.reg". Then close Regedit (don't change anything in the Registry, mind! ;-)), rename "MyShares.reg" to, say "MyShares.txt" (Reg files are a big no-no for receiving), ZIP it just to be sure, and send it to me at petedowson@btconnect.com. I'll put the same set of shares in a harmless place in my registry, temporarily changing my program to look there, so I can trace through and find out what it doesn't do right. Thanks, Pete

Thank you very much -- I'm passing this on to Microsoft now. Pete

I don't know. It only ever keeps 10 here. In order to be able to delete the files it needs to be able to work out the path to the folder. This would be the one also shown in the FSUIPC4 log file -- for instance on my system it is logged as: 31 FLT UNC path = "\\LEFT\I\My Documents\Flight Simulator X Files" on one of my machines (called 'LEFT'), and 156 FLT UNC path = "\\CORNER\C\Documents and Settings\Pete\My Documents\Flight Simulator X Files" This latter type of path is more usual. If you aren't on a Network and your path is not shared the more usual form: C:\Documents and Settings\Pete\My Documents\Flight Simulator X Files\ where of course your user name would appear instead of 'Pete'. To actually save the files, FSUIPC4 doesn't need the path, as it uses FSX for that and they save to the default FSX user files folder, those shown above. Please check this and let me know what it says, the name of your PC, AND where your files really are. Regards Pete

I'd like them to renew their contract, of course, if they are selling new copies specifically for FSX, but not if it is only a user moving it over. There are no access checks on applications in FSUIPC4. No, it won't make any difference. I wouldn't know why it isn't connecting from the zero information you've provided, but one possible reason is that it checks the FS version number and doesn't want to work with anything beyond FS9. If you want me to look at it enable IPC read and write logging in FSUIPC's options. Keep the test short (with no other FSUIPC users please), and show me the resulting Log file. Does that require access to FS's files as well as an interface through FSUIPC? If so then it is likely that it needs an update. Is there a support forum for it? You should ask there. Regards, Pete

Delete what? Pete

It isn't I who can tweak anything I'm afraid. I wish it were. It's something in SimConnect which is being snarled up. The solution will depend upon a Microsoft update. I'll keep folks posted about these things here -- that is this one, and the "No Add-Ons Menu" problem which is similar. Meanwhile I did send you a version of FSUIPC (4.013) in which you can avoid the problem, at least as far as axis delays are concerned. Allen+1 has already confirmed that works okay. Regards Pete

Closed doors? Hmmm. It is early days yet. What was the state of your doors when FS2004 was so young? Upgrade from what to what? FSUIPC3 and WideFS6 have been around for 3 years. The one set of keys applies to all versions of FSUIPC3 to date, and similarly for WideFS6. Both versions are targeted at FS2004 but still work reasonably well on FS2002, less so on FS2000 and a bit iffily on FS98. FSUIPC4/WideFS7 are for FSX only at present -- probably FSXI, FSXII, etc too, but it's a bit early to be sure at present. ;-). FSX presents a completely different ball game for add-ons like FSUIPC and WideFS and these had to be rewritten, for the first time since FS98 days during which seven years they just grew and grew! Me too, with both FS2004 and FSX. ;-) Regards Pete

Okay. Thank you very much for the confirmation! I will be discussing this with Microsoft in any case. Something needs to be done even if it is only big warnings somewhere. I am a bit worried for all those FSX users who buy boxes of Add-Ons and find they simply don't work. How to get this information to them is a big problem, and a better solution would, in the longer term, for MS to program around it -- in a Simconnect update I would hope. Regards, Pete

I'm looking for more data on the report I've seen, but it looks like the antivirus hooks it installs may be interfering with SimConnect. It is also possible that even with the options turned off it still is a problem. Obviously this looks like something which will have to be fixed in the SimConnect side, but that could take a while. Meanwhile, if it is possible for you to do without too much trouble, and if, indeed, you have tried with absolutely everything in McAfee turned off, would you consider uninstalling it completely and re-testing? This would at least prove one way or the other so that a correction can be sought quicker. I would completely understand if this is too much to ask, but I would hope that you could return to the position you are in now with a re-install afterwards, amd of course an update across the Internet. You never know, a re-install may place the hooks differently and circumvent the problem. Thank you. I am currently waiting for the U.S. West Coast to wake up in the hope that I may get some replies soon! Regards Pete

Are either of you using McAfee antivirus? I've just seen information elsewhere that McAfee 10 (at least) somehow stops SimConnect from working -- whether its checking is enabled or not. Something to do with the actual McAfee installed files I assume. Please let me know! Pete

Is anyone here who is not getting the "Add-Ons" menu with FSUIPC4 correctly installed using McAfee antivirus? I've just seen information elsewhere that McAfee 10 (at least) somehow stops SimConnect from working -- whether its checking is enabled or not. Something to do with the actual McAfee installed files I assume. Please let me know! Pete

OkayI've told Microsoft there are now two. I'll send you a version of FSUIPC4 with which you should be able to get around this for now. Please see my reply above. Regards, Pete

No clues there then. Shame. I'll make a version with an option (in the INI file only) to avoid interception of the axis controls entirely. This would mean that you couldn't use the Joystick Calibration part of FSUIPC4 for FS axis controls. However, if you still wanted to use FSUIPC's joystick calibration you could disable the axes in FS and assign them in FSUIPC's Axis Assignments, selecting the "direct to fSUIPC" option so that those get calibrated. So in the end you get no loss of function, simply something a bit more complicated. I'll do this version and email you a copy to try, before I release anything officially. Simconnect is Microsoft's interface for anthing which wants to interface to FS. It really replaced FSUIPC in a way -- new applications will be coming out which use it directly rather than go through FSUIPC. Consider FSUIPC4 and wideFS7 as a compatibility layer -- to enable folks to transfer their FS2004 (and earlier) applications to FSX right now. Oddly, Simconnect itself, although running inside the FSX process (just like FSUIPC), doesn't interface to it directly, but talks to it via the Internet protocols (TCP/IP -- in fact I believe it uses UDP, part of the TCP/IP installed software). I think it must be there that these delays are occurring. Or like queuing on a busy highway? I think queuing must be the problem, though why you should get any is bewildering. Anyway, I'll pass on this extra information to Microsoft. I'll send something later today for you to try. Regards, Pete

If the payware product is really not much more than a shareware endeavour by an individual merely trying to cover his costs, then there's no problem -- let him use your gauges if you wish. If it is something which will be sold for profit either via download or in boxed form by a major operator, then I will readily agree with them, but I would simply ask you to tell them that it does use FSUIPC and that they should get in touch with me for permission -- I would take it from there. Don't worry about enforcing this though. If they don't bother to ask I cannot do much about it now. But mostly these companies are pretty good. Regards Pete

Yes, in the sense that I was fed up with all the hassle it caused me (and others), and it was no guarantee of payment from some payware producers in any case. The larger payware and box producers are pretty trustworthy -- at least that's been my experience over the last three years -- especially if I play fair with them, which I believe I always have done. No. Regards Pete

Ah .. right. I was looking at Thomas's reply not your original. Sorry. Thanks for the Log, it was very useful. I think I've found the problem, but before I release it I am sending you just the DLL zipped up to try. Let me know please. It will be 4.012. Thanks, Pete

5 to 30 seconds!!!!? Where are those values going? With FSUIPC4 installed all axis events, are routed through it. This allows FSUIPC to calibrate them on request and, yes, optionally delay then -- but only up to about a second and then that not only requires joystick calibration but also subsequent editing of paramters in the INI file -- it was an addition requested by someone doing a particular aircraft or helo which had a delayed response in reality. In your case something is certainly very very odd. The fact that it happens without you even registering the program means that absolutely no options are being applied, merely the interception and pass through. It certainly sounds like some sort of horrible queue is being built up in the TCP/IP stack used by SimConnect. I'll send a note to Microsoft, but please also report it as I suggested. Not reported to me, no. In case it is needed could you tell me exactly what Windows version you are using (XP SP2 I assume) and whether it is fully updated? If not, could you try running Windows Update? Regards Pete

How strange. There's really nothing in FSUIPC4 which could do that. It sounds like something is wrong in the link between SimConnect and FSX -- it uses TCP/IP. Possibly you have some third party firewall or virus checking which is interfering with the passage of this data? Could you check, and maybe temporarily disable all that, as a test? If this is happening then I'm afraid only Microsoft can fix it. After you confirm or otherwise I will write to the appropriate person in the FSX team, but I would also ask you to send a report to tell_fs@microsoft.com. That was it gets lodged properly. What key from flightsim.com? They don't supply keys. Have you purchased a new one for FSUIPC4? Let me see: Marc Lynn? Yes, your key works fine. They are generated and sent automatically, so there's not likely to be any mistake. The only key problem was with FSUIPC4 version 4.00. You say you have 4.1, but tht doesn't exist yet -- so can you re-check the version please? Go to the FSX Modules folder, right clcik on FSUIPC4.DLL, select Properties -- Version, and read the EXACT version. Thanks. Either way, registering FSUIPC4 won't fix this delay you are getting -- assuming you are running 4.01 or 4.011 then that is something in FSX's SimConnect on your specific system. Regards Pete

Hi Thomas, In actual fact 3102 and 281C do exactly the same thing -- they both simply write to the SimVar "ELECTRICAL MASTER BATTERY". They are effectively one and the same. The 3103 and 2E80 case is similar, except that whilst they should write to the SimVar AVIONICS MASTER SWITCH, that doesn't work for writing, so I have to see if the value being written is the same (logically) as the current value, and if not send the Sim Event "TOGGLE_AVIONICS_MASTER" instead. Both seem to work fine here. I'll need more data from one of you to understand why you are seeing different things for coding which appears the same. Please log Events and IPC Writes in FSUIPC4, and add LogSimC=281C,2E80,3102,3103 to the [General] section of FSUIPC4.INI. Reproduce the problem and send me the Log. Thanks, Pete

Are you sure nothing else is controlling those too? I do use those here. What was the period of your "cycle"? I'll try to test the same here. Regards Pete