Pete Dowson

Your subject title refers to 4.6, which is an old version which knows nothing about Prepar3D. The earliest version supporting Prepar3D was 4.638, but the current version 4.70 most certainly installs and works with the first release of Prepar3D. Was that 1.1 or is there a new release I don't know about? [LATER] I just looked on the Prepar3D site and see that 1.1 is new this month. No one has mentioned it before. I'll try to download it, but it will take a few days just to do that -- the ADSL speed here is miserable and I do have other things to get through as well. Have you tried FSUIPC 4.70 with it at all? I've no idea what they might have changed which will affect FSUIPC. Regards Pete

There's not a different "registered" or "unregistered" version. The difference between registration and no registration is just that -- the entry and acceptance of your registration. It's merely a key which unlocks more facilities. As noted at the top of this Forum, version 3.98a was superseded on Monday and is no longer supported. Version 3.99 is now the only one available and supported for FS9. Ah, those are notes kindly provided by another keen user who likes doing things his specific way. But the reference is the User Guide. Regards Pete

I already told you what to do in that case. Look, I'll repeat it: 2. A corrupted DLL.XML file. In order to get SimConnect to load any modules that file is created or updated to give SimConnect the correct details. If this is the problem there will be no LOG or INI file generated in the Modules folder because FSUIPC won't have even been loaded. In order to check your DLL.XML file you need to find it -- it is in the same folder as your FSX.CFG file. The Install log will tell you where that it, but if you can't find it please paste your FSUIPC4 Install log here and I'll tell you. You could also try running the updated Installer included in the latest version of FSUIPC4, version 4.70, which you will find in the Download Links subforum here within the next couple of hours. It would be a good idea to update in any case as once 4.70 has been made available of the main download siter, support for 4.60 will be withdrawn. You should now know that 4.70 has been released and you should use that. Try that first. Regards Pete

I assume that is simply because that ivap program only uses FSUIPC for such things and nothing else? Sounds like an incorrect or meaningless error in the first place then. I think you should contact them about it. Sorry I know nothing about that program at all. Regards Pete

No, FSUIPC does not touch any files other than its own. it knows nothing about PFCHID.ini. PFCHid defines the [Config] entry MacroFileName=PFC if there isn't one already there. As described in the PFCHid documentation, that is the default name. Er, if you delete the parameter MacroFileName, so there isn't one, it assumes PFC in any case. To override that you need simply to specify a different name. Or, better, use separayte [Config ...] sections for specific aircraft macros. Can you please show me what you normally have? It sounds like the MacroFileName parameter wasn't there when you first used 4.70 and the fact that it happened at the same time was mere coincidence. Regards Pete

What was your particular previous version? Did you perhaps delete anything before running the new Installer? There's been no changes in FSUIPC which would affect this. Pete

If there's a difference between Win7 32 and 64-bit operation you must either be using different Windows drivers or simply haven't calibrated in Windows game controllers first. I assume you are assigning in FS rather than FSUIPC? Because otherwise the sensitivity and null zone sliders in FS will have no effect. However, unless you use FSUIPC's "raw" mode Windows calibrations would affect both ways of assigning. The -15 slope is insane! There's no way you can do delicate maneuvers with such a setting. The best settings for proper aircraft control are generally the ones with flattened centres, around + 5 to10. The completely flat response(0) is okay for stunt planes and fighters. Either way make sure the centre calibration zone in FSUIPC is only just large enough to prevent unwanted aileron movement from jitter or lack of centering spring tension with hands-off. Same applies to elevator. Are you sure you haven't got a corrupted Aircraft CFG file which is ruining the aircraft response? Make sure you are fixing the right thing! Regards Pete

Everything looks fine, though could you double-check the last line in the FSUIPC.LOG file: ********* FSUIPC Log file closed ***** There should be more *'s on the right. Did you perhaps truncate the file a little when you pasted it? If those characters are genuinely missing it might indicated something wrong. I'd need to delve deeper than. Otherwise, things look okay, so it is something to do with that "ivap" program. How are you starting that? Is it a separate program, or another DLL in the Modules folder? If it's a separate program then there's a possibility that you are running FS "as administrator" and ivap not, or vice versa. If you do that then they are probably being prevented from talking to each other by Windows as they are at different privilege levels. The other possibility which occurs to me is that the error message from ivap does not actually mean it cannot link to FSUIPC, but that it cannot find the module itself. Maybe it does some sport of "is FSUIPC there" check. If so it may be getting defeated by Win7's habit of protecting all files stored in "Program Files". Because FS9 is not Win7 (or even Vista) aware, generally it is better to install it elsewhere, in its own dedicated folder. It makes life easier for third party add-ons, especially those which may also not be Win7/Vista aware. The same really applies to FSX for such add-ons, even though FSX is itself okay with Vista and Win7. I think you might have to check with ivap support what they actually mean by that error message. Regards Pete

Okay. So please check whether FSUIPC installed okay. To do this, run FS and go to the Modules menu entry, the right-most one as shown in the picture you posted. See if FSUIPC is listed in that menu, and if so click it so you can view the details. Does it come up with a dialogue and give the correct version, 3.99? If that's okay, close down FS and look in the FS Modules folder. See if there's an FSUIPC.LOG file (it might just show "FSUIPC" as a "text file" if you''ve not done as suggested in the Installation document and changed your Explorer options). When you've found it, post is into a message here. If it isn't okay I'd need to see the Install log instead, from the same folder. No, not for the "worst", it was just that none of that information was useful. I couldn't tell from what you said whether you couldn't download, couldn't install, or whether it was installed but not correctly, or installed correctly but not working. Now you told me you think you installed it okay but Ivap simply cannot connect, then the information I'm now asking for should be sufficient -- for now. ;-) Regards Pete

It is not implemented because the method found to do it in FS9 doesn't work in FSX and I couldn't find another way. Sorry. It's to do with the change to the way they use Direct3D. Saved flights are the ideal way of having the screen the way you like it. I don't know of any other. I think there are some third party programs (or at least one such) which will put windows back the way you want them, having saved them, but I think they are aimed at multi-screen situations with undocked windows. I don't think they cope with moved and resized gauges. Regards Pete

Other programs can't "load" FSUIPC, you have to install it before running FS. Is FSUIPC installed? Check the Modules menu -- I can't tell what your situation is at all from anything you've said or shown me. Sorry, what have those programs got to do with it? Are you saying you can't even download FSUIPC? Er, how can your "AV free" problem be an FSUIPC "issue"? How are they related? If you managed to download the FSUIPC ZIP file simply run the Install FSUIPC program you find inside it. There's even a document included to help you. Did you read that? I don't see how uninstalling anything else not related to FSUIPC can change anything. you simply need to install FSUIPC. If there's something I you are not telling me, please don't hold it back -- but there is really no point in showing me a picture of FS with a message from IVAP. If there's an IVAP problem you'd need to ask them. Regards Pete

SimMarket do NOT, repeat NOT, sell ANY version specifically, they only supply the Key! They do provide a link to the Schiratti download site for the Installer, and that most certainly has only supplied 3.98a since a year ago. I'd still like to know where you got that old version from so recently! It was certainly not from anything associated with SimMarket and it needs to be fixed! What do you mean "do the sensitiviy setting"? There IS no "sensitivity setting" in FSUIPC. Where are you seeing these joystick axes? Where are you assigning things and what are you assigning them to? Sorry, hardly any of that makes any sense to me. What do you mean by "with FSUIPC switched off"? What is this "quick start tutorial"? The correct reference for FSUIPC is the User Guide. Have you even looked at that yet? You do NOT have to assign anything in FSUIPC in order to calibrate in FSUIPC. Why don't you take one step at a time? FIRST get your joysticks working properly in FS itself. THEN and ONLY then go the FSUIPC's calibration tabs and follow the numbered steps in the Joystick Calibration section of the FSUIPC User Guide. If, eventually, you want to assign in FSUIPC, do that AFTER you''ve researched it a little more. But first, explain WHY you want to do such a thing? It really isn't necessary except for certain applications. Since you obviously don't understand too much about all this yet, it would be best to take it more slowly, one step at a time. Pete

Those logs are for FSUIPC and the FSUIPC installer, not WideFS. For the message you are talking about you have to install WideServer, the FS end of the WideFS6 package. Is there a WideServer.LOG produced? Maybe you forgot to install it? Regards Pete

There's actually no need to do that for installers: it seems that Windows is clever enough to recognise an installer (I think by the words "Setup" or "Install" in its name), and automatically gives it the right privileges. There are two possible causes of this: 1. A broken SimConnect installation. To check for this please look in the Modules folder again and see if there's an FSUIPC4.LOG file and an FSUIPC4.INI file (a "text" file and a "configuration settings" file). If there are, then SimConnect has loaded FSUIPC4 okay but FSUIPC4 cannot link to it. In this case please shown me the Log file. You can paste it into a message here. 2. A corrupted DLL.XML file. In order to get SimConnect to load any modules that file is created or updated to give SimConnect the correct details. If this is the problem there will be no LOG or INI filer generated in the Modules folder because FSUIPC won't have even been loaded. In order to check your DLL.XML file you need to find it -- it is in the same folder as your FSX.CFG file. The Install log will tell you where that it, but if you can't find it please paste your FSUIPC4 Install log here and I'll tell you. You could also try running the updated Installer included in the latest version of FSUIPC4, version 4.70, which you will find in the Download Links subforum here within the next couple of hours. It would be a good idea to update in any case as once 4.70 has been made available of the main download siter, support for 4.60 will be withdrawn. Regards Pete

You'd need to construct macros for the assorted functions, and assign buttons or whatever to them. It is described in the Advanced User's guide fir FSUIPC, but perhaps more usefully there are several examples of L:Vars being used in this way in the User Contributions subforum. Regards Pete

Did you do what it says, and check the trust status? What did you find? Another possibility, apart from a corrupted DLL, is that your Windows system is not running the required cryptographic services. Sometimes folks stop a number of Windows services to try to speed up their machines, but this one is essential. For other suggestions, please see the FAQ subforum, the thread headed help with fsuipc4 code signature problems. That is actually applicable to fSUIPC3 as well. If you want more help I need to know several things -- the version of FS, the version number of FSUIPC, and the Windows version. If you are not using a supported version of the FSUIPC Installer please update and retry first. I cannot support anything earlier than 3.98 for FS9 and 4.60 for FSX. Regards Pete

When you download the ZIP containing the FSUIPC Installer, that ZIP also contains the Installation and Registration guide document, which does tell you about all the files you get and where they can be found. Regards Pete

Good. What was it? Pete

They are exactly the same number, one is reading the unconverted 32-bit integer as signed and the other as signed. 330 degrees is the same as -30 degrees. Pete

It would be worth while re-posting this sort of information, with a suitable title, in the User Contributions subforum, so it doesn't get lost by eventually scrolling off the front page. Regards Pete

Okay, the Installer log looks fine: nothing wrong there. You forgot to paste the FSUIPC4.LOG, the one generated by FSUIPC4 when you actually run FSX. Make sure you close FSX first, please. Also it would help me check the Registration here if you told me your real name, please. There's no sign of a purchase by "Flusier" so I assume it's a fake name? Regards Pete

Really? Phew, new one on me! thanks! Pete

The User Guide, installed in your Modules\FSUIPC Documents folder, is designed exactly for that purpose. But update to at least 4.60 first. And watch for 4.70 next week. Pete

Did the registration part, in the Installer, say it was okay? There can only be one FSUIPC4.DLL in any one folder -- Windows does not allow more than one file with the same name in the same folder. And re-installing will replace the DLL. Deleting it makes no difference whatsoever if you then reinstall. Please show me the Install log and the FSUIPC4 log. I expect you are simply not entering the registration details correctly. Regards Pete

Sorry, but that version is pretty old and is not supported. Version 4.60 has been available for a year now and even that is being replaced next week by 4.70. many things have been updated and fixed. I cannot undertake to help those who don't update. if you don't touch anything in FSUIPC, it does nothing for you. It might be doing things for other programs you run, that's all. If you don't use it and don't know what it does, why did you buy it? Regards Pete