Pete Dowson

What do you want to DO to offset 564D? What you appear to have told it to do is set the BYTE (8 bits) at offset 564D to zero (00). If that is what you want to do, you've done it already! ;-) If you wanted to set it to some other value, you need to enter that value as the PARAMETER in the options dialogue. Pete

But you said "I have a registered version of 3.75", and the registration needs an FSUIPC.KEY file, there in the Modules folder. I notice you are using Vista. FS9 is not directly a Vista-compatible program. If you allowed FS to install into its default location (C:\Program Files\etc etc) then all sorts of weird things happen which even I don't fully understand -- except that apparently Vista recognises FS2004 as being non-Vista aware and does weird things with its folders. The problems arise because no folders in Vista's "Program files" are accessible for ordinary non-Vista programs to write to -- they are all protected. To get around this I ensure I always install OUTSIDE the Program files area -- having great long paths to find files annoys me in any case. I put FS2004 into a folder such as "C:\FS9". My FSX is in "C:\FSX". Then you don't get into all this fiasco. I think what is happening in your case is the there IS an INI, and one or more LOG files -- there must be, as you've run FSUIPC and been into its options dialogue. But it isn't in the folder you can see, which is parially aliassed to the REAL folder where the files are kept and updated correctly. I'm not really sure how you get to the "real" folder, but try starting Windows Explorer by right-clicking on it and selecting 2Run AsAdministrator". That should run it with the privileges you need to see the REAL folder! Regards Pete

Yes. They have a good reputation for sorting problem PCs out and getting top performance out of whatever you've got. Regards Pete

If there's no FSUIPC log file, then FSUIPC cannot be running. If it is running it always creates a log file! Please don't click "New Log". This will close the current Log and start a new one. You end up with two files for me to look at, which is a waste of time. Youst enable both Axis and non-Axis logging. That's all. These will be remembered from session to session in any case. Stopping logging merely ends that Log file and starts another. Please don't do that. We'll end up will many log files. Just the normal log will do fine. Please don't mess with anything other than what I asked. It isn't "FSUPIC.LOG", but "FSUIPC.LOG", and with your starting and stopping logs, there mayl be several, with names like "FSUIPC1.LOG" and "FSUIPC2.LOG and so on. The LOG is always produced, just like the INI file -- you do have an INI file, don't you? The LOG is a normal text file and it is placed in the Modules folder, next to the DLL. There is no way that I know of whereby it cannot be produced if FSUIPC is running. Regards Pete

No, I think that will be a result of the crash, not anything leading to it -- the error is being returned by the SimConnect.DLL library which ASX is calling to connect to FSX. What happens, because ASX is an external program (unlike FSUIPC), is that ASX + SimConnect.DLL remain running when FSX stopps responding, so the DLL returns an error to the ASX program which called it. Not in my opinion -- that seems to be a much less likely cause than something related to scenery or texture files. For weather problems it is remotely possible that FSX's own downloads could contain bad data and cause crashes -- that could happen in FS9, though I've not heard about it for FSX. However, that cannot be the case for ASX since its data is checked by ASX itself and then SimConnect before it gets anywhere near the same sort of vulnerable place as FSX direct downloads. There is one data file, "wxstationlist.bin", in the same folder as your FSX.CFG file, which, if corrupt, could conceivably cause a problem. You could try deleting that and see if it helps. FSX wil generate another. Apart from that, why not simply try uninstalling GEX to see if that fixes it? You could always install it again if it makes no difference. I assume it makes backups so it can re-install? (I always make a backup copy of the entire Texture folder -- have done ever since FS2002 -- in case any of the add-ons do cause this sort of thing). Regards Pete

Well, Port Vale is the nearest club, but I'm not a supporter of any specific club, except England maybe (oh dear!). I enjoy watching any good game without taking sides;-) Regards Pete

Maybe one of the files defining the control assignments is corrupt? Only insofar as it reads the list of controls from a table embedded in that DLL, so that it can list those assignable in the Button and Keys assignments drop-down. That's done only once, at the initialisation of FSX, and cannot cause a crash. If the table is incorrect or inaccessible the only symptom you get is no FS controls assignable (in a registered version), and a warning message in the FSUIPC4.LOG. I did recently post a version 4.206 in a different thread which also accesses CONTROLS.DLL in order to operate the controls timer, to allow control acceleration to be suppressed on panels which send too many. But there's no other access except for the table read in 4.20. A corrupt assignments table seems to be the most likely. On WindowsXP, find the file(s) in C:\Documents and Settings\\Application Data\Microsoft\FSX - the same folder as your FSX.CFG file. Delete the files in the Controls subfolder and let FSX build them again. Regards Pete

Actually corrupt or unsupported texture files are one of the biggest causes of crashes in FSX. No, no way. FSUIPC is almost exclusively now A SimConnect client. There is no known way it can cause crashes. Possibly SimConnect is corrupt and is causing crashes, but that is really very unlikely. The fact that you say this points much more towards a scenery or texture problem than anything else. Maybe this GEX package was developed before Acceleration/SP2 was available? There are many changes in SP2, in all these areas -- scenery, textures, panels. It really does sound like an incompatibility with that product, especially if it was okay with FSX + SP1. I'd check on their support site if I were you. Regards Pete

You don't "register" a specific version, but 3.xxx (or 4.xxx for FSX). 3.70 is pretty old and is not supported. You should be on 3.75 at least. There's a later one still available in the "Other Downloads" announcement above. Please update. There's nothing really accomplished by "reinstalling" FSUIPC. That whole process would be simply one of deleting the FSUIPC.DLL module and putting it back again. That accomplishes nothing, as you will realise. The only thing possibly akin to "reinstalling" is to delete the FSUIPC.INI file, before running FS. That will reset everything in FSUIPC to initial defaults. Can you give me an example of what messages you are getting displayed which you think should be suppressed, please? Also, try it without the FSUIPC.KEY file in the Modules folder, just in case it is a problem with the Registration. Regards Pete

Ah, yes. I know about Richard Lovett's program. It uses FSUIPC, but you don't need to pay for it. It works with an unregistered copy. Regards Pete

Odd. Why would you want transparent 2D panels anyway? They certainly don't come set like that, but totally opaque. Anyway, glad you got it sorted. Regards Pete

Because unless you are going to only assign the axes in FSUIPC using "RAW" mode (totally not recommended except for software-controlled axes like those from EPIC), the data coming through from Windows to FS and/or FSUIPC is determined 100% by the drivers for the joysticks -- and they are configured, calibrated and tested in Windows Game Controllers applet. That is why Windows provides this, to give access to the settings for each connected joystick. If the settings and calibration are screwed up "at source" then FS and FSUIPC have bad data to work with in the first place and life gets very difficult trying to "fix" the results to anyone's satisfaction. Yes, unless you have something like a PFC digital control system through which all are connected. PFC digital systems don't use Windows drivers at all, but my own PFC driver (PFC.DLL for FS9 or PFCFSX.DLL for FSX). So far you've not mentions any PFC system, only a presumably direct-connected yoke. If you use my PFC driver then you calibrate everything in that, under FS, following the documentation provided. FSUIPC doesn't come into it, but it is used by the PFC driver. Regards Pete

Okay. And are the button values and joystick values related to 5 devices you actually have connected? Are there 5 joysticks listed by Game controllers and FS too? Do the button values only change when buttons are being actively pressed or released? Because it sounds to me like one of the button inputs is activating continuously. Not sure what you mean by "unless the device list doesn't change". What device list and why would it keep changing? May be. Possibly the driver for one of the 5 joystick devices you have connected is not compatible. Regards Pete

Well, I can only think you have something installed which is actively using FSUIPC, because by default, with a complete default INI, FSUIPC does nothing. It is not "active" but "passive", simply doing client programs' (including other DLLs' and maybe add-on Gauges') bidding. Please enable Event logging in FSUIPC (Logging tab, Check both axis and non-axis events). When if happens, look in the Log. Let me see it too please. Regards Pete

Yes, but pedals assigned to rudder shouldn't cause panning of the view at all. Or are you talking about only in slew mode? If so, then all you need is either to calibrate with a larger null centre zone, or assign them directly to rudder only in FSUIPC's axis assignments (using the "direct to FSUIPC" option) -- they won't operate in slew mode at all then. Now I'm confused. You said earlier that without FSUIPC installed it was okay. Now you say FSUIPC is irrelevant, you have the problem in any case? Yes, simply delete the INI file before running FS. ALL (i.e. every single one) of your settings are kept in that one file. That only sets normal defaults for the many assorted options. It doesn't touch button programming, axis assignment or calibration. I'd get shot if I made it do that! ;-) Of course not, because FSUIPC.DLL is merely the program. It doesn't change except when I make an updated version. It can store none of your data. All of your settings go in the INI file. Many programs have INI or CFG files, they are almost universally used to store settings. You surely must have come across this notion before? FS itself uses CFG files, for instance. Regards Pete

Version ".6xxxx" of what? I don't have anything like that. What does a middle mouse button do? I have never used it and certainly don't program for it. Maybe it does something in FS? Have you checked the help? FSUI? Do you mena FSUIPC? FSUIPC never actively asks for a key, at all. No. Please review the User Guide supplied in the FSUIPC ZIP. It tells you everything you need to know about what you get. There was a link where you downloaded FSUIPC from, there are links in the provvided User Guide, and there are links in the Announcements above. The ZIP contains FSUIPC, which you must have known already, otherwise how did you get it. FSUIPC is supplied, with all the documentation you need, in a ZIP. ZIPs are compressed files used for such things. You must have seen them before? No. It contains no such facility. Pete

Easiest is simply to delete your FSUIPC.INI file. It sounds like you've assigned pedals for panning and have them badly calibrated. Regards Pete

First, please find the key marked "Caps Lock" and turn it off. Second, could you tell me what, exactly, is "GRAYED OUT"? What does it say in the top left corner as well? And what version are you trying? Third, when you say you "TRIED ADMIN RIGHTS", what do you mean? Did you follow the instructions in the User Guide and use the right-click "Run As" facility when starting FSX? Regards Pete

Ah, good! I'll make it available in the FSX Downloads announcement above, then. Thanks for letting me know so quickly! Regards Pete

Okay, here it is, 4.206. Please try the "Fix control Acceleration" option and let me know. It should work with the original FSX release, SP1 and SP2/Acceleration, but as I say I've no way of testing. Regards Pete FSUIPC4206.zip

Actually, shortly after my last reply I had a sudden stroke of inspiration and tried a different way to find the relevant timer in CONTROLS.DLL. I think I've found it, so I'm making a new interim version of FSUIPC4 (version 4.206) for testing. I'll append it here later today. I've no way of testing it properly because I've found nothing which causes the problem. Perhaps you and Ed can test it for me and let me know? Regards Pete

So all that means is that you didn't need to try to use FSUIPC in the first place. Why didn't you use GoFlight's software to start with? Deleting your erroneous parameters from the INI file would have accomplished the same thing. The trouble with providing tools with powerful and versatile facilities is that if you misuse them you can get powerful and versatile errors! The joystick and axis parts of the INI file are 100% controlled by what YOU do in the dialogues. FSUIPC doesn't "make stuff up". You obviously made rather a mess of it and didn't know how to undo it. The easiest way then is simply to delete the INI file and start again. You'd need to explain exactly what you meant by "clearing entries", as there is no option labelled that in FSUIPC except when clearing individual fields in order to enter new values. Calibrations are cancelled by pressing the Reset button. Please explain what exactly you think is wrong. These facilities have been in continuous use now for many years (about 5 for the axis assignments and 8 for the calibrations) and this is the first time anyone has come up with such assumptions and accusations. I need to know what you did and what you thought you were doing! Again, this phrase "clearing all ...". What on Earth do you mean? I'm sure you are making assumptions which simply are not correct! If we are going to get to the bottom of this I really must know the truth, please! And please clearly distinguish "axis assignments" from "joystick calibrations". You can use them independently or together. They do not have to be related. Changing things in one doesn't necessarily affect anything in the other. That's okay. But what you say is only partly true. Of course it is true that deleting the INI file then everything FSUIPC was told to do is nullified. But it is equally true that (a) FSUIPC does not interfere in any way with anything unless explicitly told to, and (b) anything it is told to do, through the dialogue, can be undone, through the dialogue. You are implying or even overtly stating that these latter two points aren't true, and that is my objection! Pete

Merely removing the DLL and restoring it changes nothing. All your settings will still be in the FSUIPC4.INI file. There was never any need to remove FSUIPC4. If you cannot sort out your assignments and calibrations in FSUIPC, or made a mess, just delete the FSUIPC4.INI file. That will cause everything in FSUIPC4 to revert to defaults. Nothing about your installation is ever stored in the DLL, which is just a program binary! Of course. See above! PFC throttle quadrants are handled by PFCFSX.DLL, not by FSUIPC. That is a completely different thing. No, sorry. That is nonsense as you just proved to yourself. It was your own bad settings in the INI file. FSUIPC never ever makes any settings at all on its own. They are all made by YOU, the user!!! The joystick calibration feature does NOT assign anything. You assign things either in FSX, or in FSUIPC's "axis assignments" facility. It seems you made use of the latter without knowing what you were doing or reading the documentation. :-( Please discuss these things before making completely wild and incorrect accusations and providing the wrong advice to people!! :evil: :evil: :evil: Pete

Why are you doing that? I asked you to follow the directions to obtain a SimConnect Log, so that we can see what might be going on! Unless you know what you are doing, deleting protected System files under Vista is quite difficult. Having "Admin" rights gives you very little power. Even "elevated admin" rights (which installers need, for example) may not do it. But let's not jump the gun. We don't need to delete anything yet. we are still trying to find out what is wrong, hence the need for that Log. No. Both have the same version of SimConnect. SP1 installs another version, and Acceleration/SP2 installs a third. This is a "side-by-side" library system. Windows gathers as many versions as there are, and programs written to different versions each use the one they know about. For instance FSUIPC 4.0x only knows about the first. FSUIPC 4.1x can use the SP1 version, and FSUIPC 4.2x can use the Acceleration/SP2 version. But I made them all backward compatible so that 4.2x can still work without SP2 or SP1. However, in order for it to be loaded in the first place, it always needs the first version installed. I don't want to see the DLL files!! They are binary library files installed by FSX and will be the same here. I need to see the SimConnect LOG file (it will be a TEXT file) which will be generated by running FSX after you have prepared that little text file as given in the instructions in the "FSX Help" Announcement! Regards Pete

You don't "buy" a specific version 4.xx. You just buy FSUIPC4, then, hopefully, keep it up to date. ;-) The FSUIPC4 package from http://www.schiratti.com/dowson comes with an installer which does it for you. In that case you have another joystick activated in FSX which is interfering. Go into FSX's Options-controls-Assignments and disable all your other joysticks. Regards Pete