Pete Dowson

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

Maybe different levels of WinXP SP2 security updates represent the differences? I notice that these have been trickling through on my auto-updating systems regularly. I'm not sure how to compare update levels between two systems. Maybe only by looking at the list in the Control Panel "Add or Remove Programs" table? If you check the box "Show Updates" it seems to include a whole load of Security and other updates. Alternatively, maybe you could try invoking the Windows Update mechanism manually and make sure your WinXP SP2 is fully up to date -- my main PCs are all on "automatic update" settings, with installation being done at switch-off, so I know they are pretty much bang up to date. Regards Pete

127 not 27, yes. Pete

Nor me! A peek at some typical lines in a Log would help. But I think to detect negative you just need to check the top bit (0x8000) in the 16-bit value from bytes 2-3 (or the 0x80 bit in byte 3). To do you could either use AND or TEST (if those instructions are supported -- see I just don't remember!) or, considering EPL doesn't have negative numbers, see if the 16-bit value is greater than 32767 (0x7FFF) or the high byte greater than 127 (0x7F). Or do the whole job in reverse by testing if the 16-bit value is either Less than 25 (i.e. 0 - 24) or between 32768 and 32793 (representing -1 to -24). Regards Pete

Where does this "+K" condition come from. there's nothing in the docs like that. The button scanner doesn't scan the keyboard too, they are separate facilities. Well, closer. But there are several problems there: First the button 2,0 will operate your line 24 whether control is held or not, AND line 26 when the Flag is set. Simlarly for 2,1. You need conditions on those too to stop that: 24=CR(F-10,1)2,0,C65879,0 ;Heading_Inc 25=CR(F-10,1)2,1,C65880,0 ;Heading_Dec Next, in the lines 26=CR(F+10,1)2,0,1024,0 ;Heading_Inc_Fast 27=CR(F+10,1)2,1,1025,0 ;Heading_Dec_Fast you need the 'C' still before the control number, thus: 26=CR(F+10,1)2,0,C1024,0 ;Heading_Inc_Fast 27=CR(F+10,1)2,1,C1025,0 ;Heading_Dec_Fast Finally, and this is mainly my fault for not thinking through what I documented: 0=0,10,1003,2561,1004,2561 won't work because, although 0 (null) is listed as a valid code, this is only for key values being sent to FS (from a button push). It's my error for not spotting that the same table is used both for Buttons converting to Keys to be pressed and for Keys being detected. There are some additional KeyCodes which can be used. I'll need to add these to the table: 16 Shift 17 Control 18 Menu Now you still need the shift codes to match, because what will happen is that FSUIPC sees the shift so sets the shift code, ready for matching, then checks both the keycode and shift code against your list of Keys. Thus, to use Shift you need 16,9 Control you need 17,10 Menu you need 18,72 So, if you have: [buttons] 24=CR(F-10,1)2,0,C65879,0 ;Heading_Inc 25=CR(F-10,1)2,1,C65880,0 ;Heading_Dec 26=CR(F+10,1)2,0,C1024,0 ;Heading_Inc_Fast 27=CR(F+10,1)2,1,C1025,0 ;Heading_Dec_Fast [Keys] 0=17,10,1003,2561,1004,2561 then it should all work as you wanted! Regards Pete

I don't think the install path makes any difference, provided you got the installer to do it, not moved it after installation. I never use the default path, it's too long! My FS's are all in places like D:\FSX, G:\FS9 etc. AND shared on the Network. Don't think so. Whilst developing I don't bother to sign my code, and of course each recompile makes a different version in FSX's eyes, so I always have you explicitly tell it to Run this module from this "unknown publisher". I'm still hoping to get some answers or at least some help from Microaoft. Regards Pete

Advdisplay is not supplied for FSX. It isn't even supported or developed now on FS2004. There are new facilities built into FSUIPC and FSUIPC4 for menu displays from the likes of Radar Contact, and ShowText can be used on Clients as before. What are you trying to use Advdisplay for? Pete

I've enabled the Windows XP firewall here, and nothing got blocked in FSX at all. So it isn't simply a matter of "on" or "off". There's evidently more to it somewhere ... Pete

In order to try to find out what this "FSCopilot.dll" is doing to lose the FSUIPC menu entry, I downloaded and installed both FSCopilot and FSInn. Now I have both FSUIPC and FSCopilot in the Add-Ons menu. Interestingly, although FSCopilot put itself at the top of the list in the DLL.XML file, the FSUIPC menu entry is still first in Add-Ons. Whatever I do I cannot either get the order to change, nor make either disappear. I'd be grateful for some more help here, please. How do you do it? Regards, Pete