Pete Dowson

What versions of SimConnect DLL do you have installed? FSX-SE installs its own. There are three others. ADE probably uses one of the others. But the DLL is simply the interface into FS, and the code which does all the SimConnect things is inextricably bound into FSX modules, all over the place. So really the only "reinstall" is a reinstall of FSX. With FSX-SE there's a check and repair option in the Steam interface. You could try that. But quite honestly I can't see how such a thing can be broken. Why are you pausing the sim in any case? FSInterrogate is a utility for reading and writing FSUIPC interfaces. The SDK is available in all the same places as FSUIPC, and all my other programs and modules. See "Download Links" subforum, for instance, or the Schiratti site. But that's just an FSX option -- change it so it doesn't pause! Pete

ADE being what, Airport Design Editor? Really? FSUIPC doesn't care whether the sim is paused or not, it reads and writes coordinates to order. In that case SimConnect is not supplying the updated coordinates whilst the sim is paused, or they are not reaching FSUIPC for some reason. It won't be FSUIPC -- it is only passing on information received from SimConnect. Have you tested changing coordinates using FSInterrogate (part of the FSUIPC SDK)? You can also monitor the Lat/Lon offsets in FSUIPC, and that will show when the SimConnect values are received. Hmm. I can't see how they can force SimConnect to delay updating variables when paused. Unless one of their DLLs is intercepting them and not passing them on. Reinstall of FSUIPC is merely replacing the FSUIPC4.DLL with the same identical FSUIPC4.DLL, so obviously that can't change anything. When you "uninstalled" the others, did you also prevent their DLLs being loaded by DLL.XML? I don't know why you need to pause in the first place -- the coordinates can certainly be changed all the time when unpaused. Only in FS9 and before did the sim have to be paused or in slew mode to move it about. Pete

The registration option is in the Installer, not in FSUIPC. The Modules folder will contain the FSUIPC.DLL, the .INI. the .LOG and, when registered, the .KEY files, ALL named "FSUIPC ...". If there was only the DLL present then that copy of FSUIPC had never been used, as it ALWAYS produces the INI and LOG files. If that DLL had never been used, then that install of FS had not been run since FSUIPC was installed. If what you say is true, and I do believe you, then you have two installations of FS and the one you ran was not the one you looked at. Pete

Yes, and correct the line as pointed out. Pete

Well spotted! Right near the beginning too! My eyes aren't so good for little omissions like that. I like the idea of syntax highlighting. I use UltraEdit. I think that's got such a facility for XML too. Thanks for the tip! Pete

Could you please post it with a covering message in the "User Contributions" subforum? I could do it, but I'd rather the contrtibutor did it. It looks better! ;-) Pete

Not all add-in DLLs put something in the menu. What was the culprit entry? Perhaps you need to show me one which doesn't work, not one which does? Pete

You NEVER need to "start logging". FSUIPC always produces a log. The button on the logging tab merely closes the current log file, renaming it with a .1, then starts another. You don't need to use that. You do not neede to "search". I told you where! All FSUIPC are in the FS Modules folder. Without an FSUIPC.DLL file there, for instance, FSUIPC cannot run because if it isn't there it cannot be loaded! There will also be an FSUIPC.INI file with your settings, an FSUIPC.KEY file with your registration, and of course the FSUIPC.LOG file which is the log. If you cannot find any FSUIPC files, how did you manage that? ;-) Good. In that case it sounds like you had a bad registration. The log would have told me that, had you found it as you found the FSUIPC to replace and the Registration to delete! Pete

First test it. Did FSX show the Add-Ons menu? One specific entry added, or any one? Maybe the specific one you tried to add is the jinx. If adding any of them causes the problem, show me the DLL.XML file with just one extra added. Pete

Sorry, i see nothing wrong with it either. Is it in the right place, in the same folder as the FS CFG folder? Try renaming it, so you don't lose it, and rerun the FSUIPC4 installer. It will create a new DLL.XML with only FSUIPC4 loading. If the Add-Ons menu then appears it would be a matter of trial and error, doing various cuts and edits on the original, to find the culprit. I do see that it is probably the longest DLL.XML file I've ever seen, with a large number of entries. I wonder if that is a relevant factor? Pete

No, there has been no change whatsoever in any of FSUIPC's DirectInput routines for many years. It just uses standard Windows facilities to read active buttons and axes, same as FS. Windows 8.1 seems notorious for losing joystick devices. Pete

Sorry, I don't understand. Are you asking about FSUIPC registration? What part of your needs requires FSUIPC? I've really no knowledge of "ProPit" or any A2A aircraft. This question might be better directed to one or both of their support forums. Pete

If TrafficLook stopped registering any AI traffic, then either AI traffic itself has stopped working or you are out of range of any. Did you see any other traffic? What traffic program are you using? Ah, that's not good. So TrafficLook isn't receiving anything from FSUIPC. You need to find the FSUIPC.LOG file -- in the FS Modules folder -- and paste its contents here. Reproduce the problem first, then close FS and get the file. Pete

Either your quadrant is faulty in that movement of one axis affects the output from another, or, and this is more likely, either you have not disabled controllers in FS so there are conflicts, or you are running some GoFlight driver which is doing the same things you want FSUIPC to do. As far as the settings in your FSUIPC4.INI file are concerned, I can only observe that whilst you have assigned two throttles, two mixture controls and two prop pitch controls, all "direct to FSUIPC calibration", you have in each case only calibrated #1. there are no calibrations set for any of the three axes for #2. You have calibration set for a default all-engine prop pitch axis too. That needs unsetting (i.e. press its reset button). Pete

There's no delivery and no download purchase method. You simply purchase a KEY to unlock an installation of FSUIPC, which you may already have, or can easily download at any time -- using the link provided on the purchase site, or the Download Links subforum, Updated Modules thread here in the Forum. The only difference between a free installation of FSUIPC and a paid one is the Key you purchase which unlocks more facilities. Pete

Without using Lua (to read), or Lua or button/key macros (to write), you cannot. It can only be done from an internal module or gauge. Pete

No idea what is doing that. FSUIPC is a module inside FS, it has no icon for the task bar. It sounds like you ave some other program being run for your Saitek panels, and which is a wrong version in any case (FS2004 not FSX). I think you need to go to the Saitek support forum if you still have some problmes. Pete

Get it from your SimMarket Account, as stated in the FAQ subforum thread entitled "READ THIS IF YOU LOSE YOUR FSUIPC or WIDEFS keys" Pete

Why separate reads? Just read the whole structure as one item. In fact read ALL of the table, every entry, in one go, into your array of TCAS structures. i.e. just one read, no loop, like this: FSUIPC_Read(tcas_base, sizeof(MyTable), (BYTE*) &MyTable); Only one Process for all the reads you want to do in one cycle. Each process call means a change of process, twice -- back and forth. it is very inefficient to do more Process calls than needed. Up to 30,000 bytes of assorted data can be transferred in one Process, almost as fast as one byte if on the same PC as FS, because it's all done by shared memory. Yes, far better for any FSUIPC client to be external to FS. Why would you want the hassle of trying to make it work inside FS? It's not easy. Were you thinking of using the Gauge SDK? Pete

There's no 16-digit key only ever 12. I think you must have bought a different product. If you want me to check tell me your order number. I can only check FSUIPC and WideFS orders, I've no access to any other products. Pete

Okay. This is the one I use. It only does anything once every 500 milliseconds (half a second), and on my system it runs in parallel with several other programs, including Radar Contact, with no noticeable ill effect. Since it hardly does anything nearly all of the time, I don't think there is any way it can be the cause of your problem. To prove this to yourself, just try changing that line: event.timer(500, "mytimer") Change the 500 to, say, 5000 (5 seconds), or even 50000 (50 seconds), so it does even less, and see. You could also make it do less by removing the Frame Rate display and monitor, but again I don't think that'll do anything. here's a copy with that removed: w = wnd.open("VAS Monitor", WND_FIXED, 0,100,523,50) wnd.backcol(w, 0x000) wnd.textcol(w, 0x6c0) wnd.font(w, WND_ARIAL,-3) -- Update the display at 500 msec intervals (see event at end) function mytimer(time) wnd.clear(w) mem = ipc.readUD(0x024C) memmb = math.floor((mem/1024) + 0.5) wnd.text(w, "VAS free " .. memmb .. " Mb") end -- Adjust timing to taste: 500 = 1/2 second event.timer(500, "mytimer") Pete

Ah, that's interesting. Ah, good! So something somewhere was corrupted! I wonder what? Well, I just popped over to the P3D forum on AVSIM and checked, and there does appear to be quite a number of folks using UT2 with P3D quite happily, though with struggles to get it correctly installed. No w you have a solution if P3D does get corrupted again, maybe you could be adventurous again! ;-) Anyway, glad it is all sorted out -- relatively quickly as well. Pete

One other possible trick. Instead of having UT2 start up from the EXE.XML file, try letting FSUIPC start it, e.g. via: [Programs] Run1=READY,KILL,"E:\1 Simulator\Lockheed Martin\Prepar3D v2\Flight One Software\Ultimate Traffic 2\UT2Services.exe" in the FSUIPC4.INI file ... assuming I have the path correct? This may avoid any timing or pre-hooking problems. Maybe? Pete

Maybe something about the way UT2 (now a very old product, and not necessarily compatible with P3D) sets the AI traffic data, which of course FSUIPC continually reads for the benefit of other programs. Didn't you yet try with UT2 not running, as I suggested? That would seem to be an important thing to check, now? Of, probably more likely, it's a timing matter -- something FSUIPC doing changing the roder of events somewhere else. It's all a very complex system with lots of interactions. Still, though, the Hook errors logged by FSUIPC suggest something else wrong in the installation itself. Until that's solved I suspect there'll be problems if not like this then elsewhere.. BTW, next time, rather than post a screen shot, just cut and paste the data itself. There's even a facility to do the copying for you in the "Details" tab. Pete

Just additional information: those two hook errors would simply stop FSUIPC's wind smoothing abilities, not crash P3D. The errors may actually point to a problem with the WEATHER.DLL, not SIM1 or VISUALFX. Pete