Pete Dowson

As I said there is no need to delete ANYTHING. Just close down FS before you run the installer this time! Pete

No, the order isn't relevant -- it's the order detected, that's all. If it acted as if not registered, you wouldn't be able to go to the Buttons & Switches tab because it wouldn't be thjere! Besides which you said the axes were detected okay! What button numbers does FS itself see for those? It sounds like they are out of range. The order in the list is completely irrelevant. Pete

Actually, I see that you DID try to install 4.939t: -- this line was embedded in the odd assorted sections of files you pasted into your message. FSUIPC4.ini"staller for FSUIPC4.DLL version 4.939t However, apparently you tried to run the installer whilst FSX was actually running! There's no way you should EVER tryto install things into FS whilst it is running. The 4.939t install failed because of tat, as stated here: Failed to place FSUIPC4.DLL into folder as "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Error 32 reported ("The process cannot access the file because it is being used by another process. ") That would have resulted in an error message on screen, which I assume you ignored? Pete

Just download and install the current version (4.939u). No need to delete or change anything!!! Pete

Oh dear. Those ARE parts of the INI, the Install LOG and the run time LOG, respectively. You are using Windows Explorer with the option to hide filename extensions from you. If you really wat to be able to find files you need to switch that off, as instructed in the FSUIPC User Guide. Why extract only parts of the files? That makes them almost useless ... almost .... The one piece of information I can glean from all that is that you are using version 4.60 of FSUIPC, which is now well over 5 years old and hasn't been supported for 5 years! The facility you want was not introduced till version4.82 (August 2012)! Pete

My name is Pete Dowson, actually. And sorry, I just didn't see it. It arrived on my first day back from holiday and I had a big backlog. You say FSUIPC sees the axes, but not the Buttons? Are these on the same device? If so then it must be a Windows driver problem, because the axes and buttons are read with the same call to direct input. However, FSUIPC can only handle the first 32 buttons. The other thing which might interfere is any other driver or software you are running for this device. What was the flashing of the firmware for? Does this firmware process trhe buttons itself, perhaps? What does Windows see? Please find and show me the JoyNames section of your FSUIPC4.INI file, in the FS Modules folder. Pete

The total range FS accepts is -16384 to +16383, so 32768 values altogether. Steps of 256 therefore provide 128 discrete different settings, which is about as much as FS will notice, generally. The lower the delta the more messages are being sent through FS's main processing loop, causing performance degradation. And many devices jitter (i.e. provide slightly different values on each scan), which would make things worse. By all means try a lower value if you feel you'd get better control, but probably the only control where it might matter is trim, assuming you use a trim axis rather than simply increment/decrement controls. And you'd need are really stable axis for sensitive trim. Note that all of the control surface Inc/Dec controls, used when flying with keyboard only, have an delta of 256 too, I think (can't remember now). Higher delta values are needed for badly behaving devices, in order to reduce jitter, though there's also a filter facility for this too. Neither are desirable if it can be avoided -- they reduce either sensitivity or responsiveness. Pete

No. FSUIPC cannot be changing stuff in its tables whilst they are also still in use interacting with FS. That's a function of FSX. It didn't go balck in FS9 and before. But it doesn't really matter because FS is frozen whilst in any modal dialogue, including its own. Why? First of all unless you are using home made devices with extra special precion, or very low precision, there should be no need at all to change the delta value. The default gives as many Fs-distinguishable steps as any commercially available device. Second, the idea of calibration is to adjust the values being sent to FS to suit the positions of the lever on the device. The values FS needs are fixed -- max - centre - min are always the same values. It's the device values which vary (and the amount of travel or free space you want to allow), not what FS does with them. Pete

The console log? That's just an optional on-screen live copy of the log FILE. All FSUIPC files are in the FS Modules folder. The log is named FSUIPC4.LOG. and your settings are in FSUIPC4.INI. Both files are text files and you can easily paste their contents into a message here! Pete

Ah, but you checked "title bar" instead of "FS display"? And "S32" instead of "U32"? Please, also check "Normal log", then show me the log file, and your INI file. Pete

Sorry, what instructions, where? I don't think I've ever published anything like that. Is it a user contribution? Offset 024C will be updated at 10 second intervals, unless that's been changed in the FSUIPC4.INI file. The Out of Memory checking can also be turned off in that file (OOMcheck=No), but it is enabled by default. Pete

Well I don't really see how. Sorry. Pete

Ah, sorry. I didn't realise that. I'll see if I can get that changed. Pete

When you get an application which needs FSUIPC it will either install it for you, or tell you to install it. I don't know all of the thousands of programs which need or use FSUIPC. You have things the wrong way around! In any case you do NOT need to purchase FSUIPC for its application interface. That side has always been free, since FS98 times. It isn't a Demo. There is no demo. There never has been, and in all of the 14 years there's been a payware version of FSUIPC, you are the very first person to be confused by this. There is no point whatsoever in having a "preview". FSUIPC doesn't do anything at all unless you actually tell it to. It's a box of tools. Each tool is different and you use whatever bits you need. The only "preview" you might want is the User Guide. After the part you have already read there are chapters explaining the tools available. Pete

It looks like the current version of FSUIPC (4.939t) works fine with this P3D update. The installer will give a warning that the P3D version is later than it knows, but will do its job nevertheless. I may release 4.939u tomorrow (24th June) just for the Installer version check, but meanwhile, unless someone reports otherwise, it looks good as it is. Pete

Okay, you have the Steam SimConnect 62613 build installed, and the FSX SP2/Acceleration 61259. If ADE is happy with that, it's okay. Don't keep attaching XML files which aren't relevant in any way. Sorry, there's no answer here. You say it used to work and now does not. FSUIPC hasn't changed, so something else did. Pete

Yes, that is correct. The free, unregistered installation of FSUIPC provides no user facilities whatsoever, it acts in its original free role of providing an interface into FS for other programs. The user facilities are the reason folks purchase a registration. All this is clearly explained in the User guide, which you will find along with other documents and files in your FSUIPC Documents folder, in the FS Modules folder. You were pointed to this folder by the Installation document you ignored in the downloaded ZIP. Pete

No, that's the XML file. Do NOT try to attach DLLs, they are programs. You just need to review programs installed (Windows control panel), or take a look at the list of SimConnect versions FSUIPC's installer finds -- it's recorded in the Installer log file. Pete

Been back since last Thursday. Not away again now for a couple of weeks! ;-) Seems LM are getting their timing a bit better! ;-) Thanks -- I'll take a look, see what needs doing. Pete

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