Pete Dowson

Of course. But the big advantage of forums over private email support (which was used for FSUIPC until a few years ago) is that others can read both questions and answers, and so possibly help solve their own problems and questions. This is why I might put more in my answers that you, personally, might wish or expect. It doesn't not mean I think you are stupid, as you appear to imply. Pete

There's no such thing as a stupid question, but it helps others, and avoids more future waste of time for all, if I post details of where the answers are to questions which are asked. This is all I've done, pointed out where the answers are that you definitely missed. Okay, so this wasn't needed to help you, by now, but perhaps it will help others. This is a Forum read by many, not a personal communication medium. Please appreciate that! Pete

There are a variety of slopes like that. Choose to taste. The facility is called "slopes" and you access it from the FSUIPC calibration tab, using the button so called. Pete

But it may have much more to do with the program which issued the message losing contact with FSUIPC because your FS crashed! surely you can see that? Any program connecting to FS, whether via FSUIPC or by other means, will obviously lose contact if FS stops working, and may issue an error as a result. That doesn't identify the reason for the error. you need to work out what is crashing FS. Regards Pete

The SYSTEM hangs? Wow! That cannot be anything directly that FSUIPC is doing. It is all normal user-level code running in the FS process. it simply does not have enough privilege to hang a system! Is that the current version? Mine is 61635. Maybe a difference between SP2 and Acceleration? I think it is only SP1. Aha! That confirms it! Your FSX installation is only at SP1 level. Please update to SP2. It fixes a lot of the sorts of bugs you are now seeing. Regards Pete

The latter is exactly what one set of the slopes provided in the calibration system provides. Have you not checked that facility? It is described, with pictures I think, in the User Guide section on calibration. Half of the slpes exaggerate centre response, the other half go towards what you want. The former would involve assigning in FSUIPC and using the multiplier option on the axis inputs, after calibration has been done, so that the full input provides a smaller range than that calibrated. Axis scaling is described in the Advanced Users documentation (see the section entitled Additional parameters to scale input axis values. Regards, Pete

Hmmm. The log of what it is doing is displayed on screen whilst it is doing it, and that confirms it. And, if you did read carefully you'd have seen the first sentence introducing the Registration screen, stating "Finally, the Installer offers you the chance to Register ...". A clue, surely? And of course it does not insist that you register as you implied in your post. It explicitly says: "You do NOT have to Register at this time. In this case simply click the Cancel button to continue. " So any "very careful" read, even a casual read, would have clarified everything for you, wouldn't it? Pete

You have a VERY old version of FSUIPC, then. No idea. There's nothing than any of my software does with that. If you don't want to use FSUIPC just delete it from the FS Modules folder. Else download a current version (3.98) and install that. It does NOT need any password whatsoever. That's for Registration if you want to purchase it. Please PLEASE read the installation instructions, where it tells you all this. You say you "followed the instructions" but evidently not far enough! Please READ THE TEXT relating to the dialogue allowing you to Register!!! Just below the picture of it! Pete

I'm pretty sure that's caused by a bug which has been fixed in one of the many updates released this year. Please check the Download Links subforum and make sure your FSUIPC is more up to date. Pete

Didn't the HiFi site provide the link? In any case, it was withdrawn this morning and replaced by 4.632, to fix a bug. It has not been tested yet -- it was released via HiFi for testing by those who had expressed an interest over a week ago, but the first feedback I received was last night, which showed up a bug when FSX and ASE are on the same PC. I have fully tested the WideClient facilities, though, for use when ASE is running on a different PC to FSX, and that works fine. If you want to try things out, the current links are: FSUIPC 4.632 WideClient 6.831 but by Monday or Tuesday these will both be replaced by later versions, linked via the "Download Links" subForum updates thread. Please keep a watch on that and update again when the proper versions are available. Regards Pete

The fact that there is a Log produced means that SimConnect is loading FSUIPC okay. So something else is happening. I need more information: 1. Can you get any more information from Windows when the crash occurs? I need at least the type of crash (access violation? Some number?), the module name, and the memory address if possible. Look for buttons on the report screen which reveal additional information. Or else, afterwards, see if the details are placed in the Windows error log (eg right-clcik on My Computer, select Manage, then Event viewer - Windows Logs - Application. look for the red ! error note relating to the incident. 2. Get me a SimConnect log. For information on how to enable SimConnect logging please see the FAQ subforum -- there's a thread there which explains how. Regards Pete

So FSX is only running on one PC, and you are using WideFS to link the two. Okay. You don't "buy" 4.53, but FSUIPC4. Version 4.53 is now too old and unsupported. You need to update to 4.60, or go without support. Just to update to the currently supported version of FSUIPC? Of course not. FSUIPC doesn't touch any other products. No. You cannot uninstall it that way in any case. If you don't want to use FSUIPC any more, just delete it from the Modules folder, as described in the User Guide. You are really thinking things are complex when they are really very simple! To update FSUIPC just download the latest FSUIPC ZIP, for 4.60, and run the installer. It's a few seconds work, no more. If you like you can then copy on the very latest update from the Download Links subforum. We're up to version 4.628 there at present -- 4.633 or later next week! There's also a more recent copy of WideClient available in the same subforum. Regards Pete

Far easier by far to simply change to Profiles instead. you can name those what you like. Aircraft are assigned by name (long or short) to profiles in sections in the INI, but you can convert automatically initially, and then rename the profiles afterwards, in the INI. Regards Pete

You cannot remove all of the elements affecting FSX like that. There are also critical files, controlling SimConnect actions during loading, in the AppData folders. It was pointless deleting FSX and reinstalling -- in fact that tends to wreck SimConnect completely, sometimes making it necessary to reinstall Windows completely too. This in fact shows you didn't delete the crucial parts. The modules folder to start with: and, crucially, the DLL.XML file in C:\Users\Jerry\AppData\Roaming\Microsoft\FSX: There may also be an EXE.XML there, also loading add-ons via SimConnect. If you did delete all of the folders in FSX, including the Modules folder, are there now FSUIP4.LOG and FSUIPC4.INI files there? If not then FSUIPC4 has never got to run, and FSX is crashing in the SimConnect loading as I described. If there is an FSUIPC4.LOG file, show it to me please. Regards Pete

An error message from WHAT saying "FSUIPC is trying to re-connect"? Re-connect to what? It sounds like something is wrong with your FSX installation which is causing it to crash. When FSX crashes, FSUIPC stops working (naturally, it is part of the FSX process which is crashing), and then any programs which are trying to talk to FSUIPC obviously can get no response. Why are you posting here? Why do you think your FSX crashes are related to FSUIPC? Regards Pete

FSUIPC never "requests" registration in any place at all. Please explain what you mean. You can only register FSUIPC4 in the installer. There is it optional. It provides facilities to register, or check registration, or simply cancel to bypass new registration. There is no such message! The only message anything like that is when you already have the same version or a LATER version installed, and then there's obviously no need to copy the new one in. That is absolutely NOTHING whatsoever to do with registration, and is only a precaution against overwriting a later version with an older one. Why should it? FSUIPC is not a Microsoft Game or anything to do with Microsoft! You don't want to use it any more, even though you paid for it? Uninstalling FSUIPC is completely described in the User Guide, in the section with that name. It merely consists of deleting the DLL. Nothing more complicated! If your registration worked on the PC it will work on the notebook. There is no difference. You must me making an error when entering part of the details. All three parts must be correct. Use cut and paste to be sure. If this is not your problem, with all this talk of installation problems which are not problems and wanting to uninstall, you are confusing me a great deal. What is the actual problem and what is it you want to do? Incidentally, I assume you aren't registering using the name "Flugente" as there's no sign of anyone purchasing FSUIPC4 by that name. If this is a pseudonym then I can't check things for you. Pete

If you have no files in the modules folder yopu must have deleted them. Sorry, I cannot help with that. You need to take better care when deleting things! New? Version 4.60, the oldest supported version, has been available now for most of this year. Regards Pete

What upgrade? From FS9 to FSX, or some computer upgrade? There are "latest versions" for both FS9 and before ("FSUIPC3" and "WiodeFS6") and for FSX and later ("FSUIPC4" and "WideFS7"). No. If you changed from FS9 or before to FSX there's nothing to uninstall for FSX. And there's no uninstall process apart from removing the FSUIPC files as described in the User Guide in the (obscurely named?) section about uninstalling FSUIPC. I think you need to explain what this "upgrade" is. If you already purchased FSUIPC4 and WideFS7 you NEVER have to purchase them again! GoFlight "stuff" is nothing to do with FSUIPC but is to do with GoFlight. Just install their software. I don't control that company, it is separate and unrelated. Pete

Sorry, "I control" means what, exactly? Are you saying you looked in the FS Modules folder and there were no files there? Well, something else has deleted your files because there are no mechanisms in FSUIPC or any of my programs for deleting things. Version 4.30 pre-dates Lua support by some time. The earliest supported version of FSUIPC for FSX is 4.60. Regards Pete

Er, sorry, I don't understand the question. If your yoke is a game port or USB one recognised by Windows, then who made it is totally irrelevant to FSUIPC. You can calibrate in Windows and assign in FS -- that's the first thing to do in any case. If you want to calibrate in FSUIPC do that when you are sure everything is okay in FS. If you want to assign in FSUIPC do that before calibrating in FSUIPC, and make sure you tell FS not to use it. If your yoke is connected via a PFC throttle system or one of their other digital controllers, and connected via a serial cable (or serial cable with USB adapter), and not recognised in Windows, then it is driven by the PFC driver I provide -- PFC.DLL for FS9 and before, PFCFSX.DLL for FSX and later. Sorry, I don't understand what you are asking here either. "When do I do" what? You can't "do values". That means nothing. The last version you saw somewhere? The last version you downloaded? Please always give numbers. Regards Pete

That's what I use -- FSX on Win7, 6 clients on XP. Perhaps that's because there's no program called "WideFSClient". You need to run "WideClient.exe", and you can do that by double-clicking on it, just like any other EXE program! Pete

All current versions of FSUIPC accept different email addresses, but accepting different names as well would be going too far. The quickest way normally would be to raise a problem ticket with SimMarket and explain that you miss-spelled your name and could they please issue a revised registration. Regards Pete

Sorry, I've no idea how to do that either. I'm not familiar with widevieW or any of the interfaces it uses. You think you should be able to change the tail number dynamically, through FSUIPC, in such a way that it somehow gets to WidevieW? Not sure how that would work. All I know is what is written in the FSUIPC SDK. Offset 313C contains the user's tail number, and in FSX that can be written to but I've never found out whether doing so actually achieves anything. All of the AI data read by FSUIPC for TCAS type displays is read-only. I don't know of any way to change any of it. How? And how would it help WidevieW? What is it doing? Have you asked Luciano at all? Seems more up his street, After all, he did write WidevieW. Seems to me that WidevieW should be matching planes by aircraft title, not tail numbers -- after all that's the way virtually everything else selects aircraft by, including FS itself, and of course FSUIPC. Tail numbers aren't necessarily unique, whilst aircraft titles have to be (for menu and flight selection purposes). Regards Pete

It's a clash with one of your other add-ons being loaded by SimConnect. It will be due to the bug in SimConnect which was never actually fixed, though Microsoft did do some work-arounds in SP1 and SP2 (better in SP2) which stops most (but not all) of these problems occurring. It only occurs when one or more programs are being subjected to SimConnect's security check (via windows) at the same time that it is trying to load another. When it happens it is an unfortunate timing clash, and very elusive (which is why the FS team never managed to fix it before they were moved on). Normally allowing FS to continue gets one or both of the conflicting security checks done and then on subsequent loads you get no problems. Probably, having recently re-installed everything, you have several add-ons competing during the load time, all needing the security check. The easiest way to sort this out is probably to temporarily disable some or all of the other DLL or EXEs from being loaded by SimConnect. You need to get each approved and working before adding the next, or even do them singly before enabling more than one. The way to do that is by editing the DLL.XML and EXE.XML files, changing one param in each entry to disable them. But take care. It is easy to mess those files up. Make copies first. I use DBS Studio's "DBS FS Startup Editor" which might be a good investment if you are keen on FSX add-ons -- especially as it appears to be Free still! Go to http://www.dbsim.com/ . Regards Pete

That's all okay except for the signature failure: Problem! My signature check fails on the installed FSUIPC4.DLL. (Error ref 80092026) There's a strong possibility that something you've installed, or maybe a Windows update, has changed your security settings. That error number means: " The cryptographic operation failed due to a local security option setting", and there's a fix described in this thread: http://blog.stealthp...eration-failed/ which is easily found via Google for that number. But .. did you do as suggested in the error message and check that you don't have the relevant publishers listed as untrusted? In previous versions that was me ("Peter L. Dowson") but now it is simflight (as explained in the documentation). That's the first thing to check. Please see the User guide (already installed in your modules\FSUIPC documents folder) -- the section entitled "Next … running FSX. But read this first" (on about page 9) describes this. the box at the bottom tells you where to check in Internet Explorer. There's a lot more about all this, with assorted other suggestions, in the FAQ subforum -- look for the thread entitled "Help with FSUIPC4 code signature problem". Regards Pete