Pete Dowson

Really? That's news to me. Sorry, but that is their doing. I cannot support their website, you need to go to their support. All my software is supplied in the Schiratti site or here, in the Announcements. Can you report all this to PFC please, either via their direct support email or their forum. You have a version of the console which supports the 737NG cockpit throttle quadrant? Does it have detentes on the flap lever too? I didn't know they made any changes there at all -- they don't seem to tell me much! :-( In this past you mention, what was different? As far as I recall, the TO/GA buttons on the quadrant are only supported on the Jet cockpit. I wouldn't have supported them on the jetliner console because as far as I knew they couldn't exist! That's why I provided an option to treat the AT Disco buttons as TO/GA -- more valuable there because the AT arm switch is close to hand anyway (or is that removed from the console now?) Maybe you told the PFC driver that you had a 737NG cockpit last time? Really these are all things you should talk to PFC about. Especially if they change things without telling me -- I can't really offer support that way. Maybe you ought to mention this to them too, please. Regards Pete

Okay. Sorry for getting a bit irritated with you. Good flying! Pete

Where are you reading that "aircraft specific" is wrong? I don't understand you at all I'm afraid. Please READ THE CHAPTER ON PROFILES! It is called "User profiles for all control settings" on page 26 or thereabouts. It is even listed in the Contents page near the beginning! It tells you what to do! That is what documentation is for, to help you do what you want to do! FSUIPC defaults to only providing aircraft-specific options, not Profiles, because there are thousands of users already using the aircraft-specific facilities. Changing over is not automatic. You have to select it before running FSX, EXACTLY as described in the Manual. Sometimes I wonder why I bother writing documentation. :-( Pete

That's the install log I asked for. Okayso the INSTALL of FSUIPC4 failed! Why are you running the installer for version 4.40? It is NOT compatible -- the signature check will fail, because I've had to change the signature to that of simFlight! Please run the Install FSUIPC4 program which comes with version 4.50, then show me the install log! You should NOT try running FSX with that DLL until that problem is resolved. But you ran the Installer for 4.40 after you installed 4.50. I need to see the result of the 4.50 installer, not your later attempted install of 4.40.. This is where you are making no sense at all I'm afraid. There is NO installer for PFCFSX. You cannot possibly run it as it doesn't exist. PFCFSX is just a DLL which you copy into the Modules folder. The fact that you got a message stating that you have a later Version of FSUIPC is only ever from the FSUIPC4 installer. You appear to be first running the FSUIPC4 installer for version 4.50 then the FSUIPC4 installer for version 4.40. PLEASE DO NOT DO THIS! There is no program which installs PFCFSX.DLL for you. If there's a copy of PFCFSX.DLL there you must have moved it there yourself. I repeat: THERE IS NO PFCFSX INSTALLER!!! Please go back and run the installer for FSUIPC4 version 4.50. Then install PFCFSX.DLL manually, as it says in the user guide. Just copy it into the modules folder as instructed. No I did not! I asked for the Installer log -- please do read what I write. you did actually provide the installer log as I asked in any case, but foorgot the normal FSUIPC4.LOG, the normal run-time log which is the one showing what FSUIPC4 is actually doing. Once I know you know what you are doing, which doesn't appear to be the case at present I'm afraid, we can proceed to looking at whatever the problem you have is. Until then it is rather pointless I'm afraid. So, step by step: 1. Install FSUIPC 4.50 by running the 4.50 version of the FSUIPC4 installer. 2. Do NOT run any other program yet!!! 3. Install PFCFSX from the ZIP by copying across the DLL into the FSX modules folder. 4. NOW run FSX. Do NOT run the FSUIPC 4.40 installer again as you have been! If you still get a problem, please assure me you are not running some other installer which I don't provide, and show me the two logs I asked for -- the FSUIPC Install log and the normal run-time FSUIPC4.LOG. I am not interested in your PFCFSX INI or PFCFSX.LOG files, they are not relevant. Pete

Well, nice for me, but why buy it again when you already bought it? Just download and install the current release! Pete

Good, glad you got it sorted! Pete

Good grief! You should have mentioned that before. I will not answer questions on such an old version. I can only support current versions, and 3.75 is now getting on for 2 years and 15 versions out of date! Why purchase again? You purchased FSUIPC3. That includes ALL versions of FSUIPC3. You are expected to keep up to date, especially if you want support. Yes. Pete

Erthe check on the installed FSUIPC4.DLL is carried out by the FSUIPC installer. All installing PFCFSX.DLL involves is copying the DLL into the Modules folder. There is no way possible that copying a file, using Explorer or whatever, will bring up a signature check on an unrelated module! So, please explain what you are doing and where you are seeing the message! Erhow does this relate to the stuff you said above? sorry, I'm not with this at all. Not without more information. Can you be a bit more explicit please? Can you show me the FSUIPC4 installer and run-time Log files, from the modules folder? Regards Pete

No. If you asssign only in FSUIPC, then you disable the controls altogether in FS and the sensitivity and null zone are then totally irrelevant. If you assign in FS you must set those sliders as suggested, before calibrating in FSUIPC. The choice is yours. Not necessary, just recommended, exactly as it says. You select the slope to suit your needs. There aren't just the two extremes, but 29 other settings in between! I wouldn't recommend either extreme as you suggest, but it is up to you. Why not start with it flat (0) and see how it feels, then adjust it and so on. Only YOU can tell how you want it to be!! Ignore the numbers, do it by feel. Calibrate it to suit yourself. I cannot instruct you. I provide the tools, you use them to make your system the way you like it. Note that if the potentiometer in your yoke is really too far offset from centre you would be best throwing it away and buying a new one, or get it fixed if possible. It could be that the internal adjustment is bad. Pete

That's the correct method for older versions of FSUIPC where there is no option for "no reverse zone". You should not be doing that now, but using the "no reverse zone" option instead, as I said! No idea. Sounds like something they've programmed which you need to find out about. What do they say? Regards Pete

I've really no idea how or why your FSX is corrupted, so all I can suggest is a complete uninstall of FSX. Then see the FSX Help Announcement above for details of how to delete SimConnect, then, finally, re-install. This isn't an FSUIPC problem, but one which will affect any and all SimConnect applications, so it is important you get it sorted out. In the end it is a Microsoft support problem. I would still strongly recommend applying both updates to FSX because they fix a lot of problems. You've not yet even said why you cannot run with SP1 installed. All you've said is that it recommends you going to a website. Why don't you explain these things? Regards Pete

The thing is, then, WHAT is asking you to go to that site? That didn't exist when FSX was first published (obviously, it is an update). So it must be the SP1 update which is prompting you. Maybe it is for this, which I see there: Sorry, apart from what I've said I really have no idea. Why can't you simply go ahead and run FSX? You aren't telling me what the problem really is, only that you are told there's another update. Many thousands of FSX users have already updated to SP1 and SP2 and no one so far has asked me any question even remotely resembling the one you are asking -- which is more properly addressed to Microsoft in any case. Maybe someone over on the FSX forum can help? Pete

That's interesting. I didn't know it did that. But isn't it optional? It presumably must be referring to the SP2 update which will be on the same website. Usually when programs tell you about updates they aren't mandatory. However, I would recommend SP2, as it makes SimConnect so much more efficient. Some folks say it is slower than SP1 but as many others say it is faster. On the whole I think you should go for it. But it is best to run FSX with SP1 first, then exit and install SP2. Regards Pete

This is an error reported by SimConnect quite rarely. The only times I've heard of it happening have been when a copy of the SimConnect.DLL is installed into FSX someplace. There should be no such DLL anywhere accessible to FSX excepting the one installed in the Windows WinSxS folder. Possibly you or something you've installed has attempted to place a copy in the Modules folder or in FSX's main folder, or else in Windows folders someplace other than in the WinSxS folder? I note that you are still running with only the base version of FSX -- have you not considered updating at least to SP1, or better SP1 + SP2, top fix most of the really bad bugs in the original release? I would strongly advise it. It may help fix this problem too. Regards Pete

I've raised it directly, starting with Joel in a message on 2nd October 2008, and subsequently with both Joel and Brian Gefrich on 8th and 12th October, exchanges where it was evident that Brian understood exactly the approach I suggested and promised to discuss it with Joel (who never actually answered me). I sent a reminder and asked about progress in December, and again on 11th January this year. I've had no responses to any of my messages after October last. As far as I can tell they've abandoned development of Squawkbox. Is there any sign of any life in the development area? I've met Joel and he seems a good sort so I'm sure the snubs aren't meant. He's probably either sick or too busy someplace else. As I said, as soon as they incorporate an accessible facility, I'll provide a route to it from FSUIPC and WideFS. I'm really too busy with my own commitments to go flogging a dead horse. I've decided to continue to use Radar Contact for my ATC instead of trying to go on-line. Regards Pete

You posted this question already in your trim thread. I replied there. Pete

No. I've done it for FSX, but it is a little more precarious in FS9 and the work isn't trivial. I may consider adding it later this year. For the present I'm afraid I am rather too busy on other commitments. No, only in a few areas where they cannot get the information needed using the normal FS-supported methods. Regards Pete

Please check. I am sure this is all explained in the user guide! My signature expires in August this year, after which no such copies will work, at all. GlobalSign now refuse to certify individuals, only companies, so I asked simFlight, my publishers, to do the honours. I still sign them but the certificate is in their name. Pete

No, that doesn't explain anything at all. The facility required in Squawkbox would be like the one for PTT, which is a Registered Windows message. The PTT works well and so could the Transponder. This is nothing whatsoever to do with whether anything uses FSUIPC or not! That is a complete misunderstanding. Pete

As the FSUIPC User Guide clearly points out, you should sent Sensitivity to max, Dead Zone to minimum, in FS, if you are calibrating FS axes in FSUIPC. What delta? The FSUIPC delta only applies if you are assigning axes in FSUIPC. You said you were using the dead zone in FS, which means you are assigning in FS. If you want any assistance you need to be more specific, please. And try looking things up in the documentation. Regards Pete

No idea. Isn't that just operating a pair of buttons too? If so you can program them in FSUIPC. If it is an axis you can only do it by calibrating as I suggested. Pete

I don't think they are "not willing". I assume it is merely that they have other things to do, and this is obviously unimportant if I'm the only one asking for it. No, sorry. That would be a huge amount of additional code, even if I had the many hours it would take to hack into it. I'm not about to add a whole program's worth of code just for something which should be so ridiculously simple. Regards Pete

You'll need to ask him then. Sorry, I cannot guess how he's programmed it. The FSUIPC "mouse macro" facilities can work with add-on panels made using the standard C tools for gauges provided by the FS SDKs. If you are talking about FSX then it may be possible to use the new "L:var" facilities I've added to create macros for XML gauges and the like. Otherwise, you'll need to see if the author has made other provisions, such as a key-press combination. You still didn't actually mention the specific switch, or do you mean all switches on the panel? Pete

This is not setting up FSUIPC, then, but setting up some third party software? The 6DB9 offset is private to TSR. I don't know how to use it. my trim system refers direct to FS offsets. I'm not sure about "Offset byte select bits" either because there's no control listed by that name. Do you perhaps mean "Offset byte setbits"? Anyway, either way, FSUIPC uses the form "x..." for hexadecimal, not "0x..." so the offset box should contain x6DB9 not 0x6DB9. It does tell you this in the FSUIPC documents. Sorry, I don't know this part of Thomas's program, so I really cannot help. Really it is best to seek help with other programs from their own support. Thomas is very good at answering questions on his programs. Regards Pete

Two points: 1. FSUIPC 3.874 is not supported. It was a Beta release of several weeks ago and has long been superseded, both by later beta releases and then, last week, by the full 3.90 release which is availble on the normal download sites as well as here. Please do refer to the Announcements from time to time.. 2. The method of using Profiles is described in the documentation -- for 3.874 this was in the little PDF which was included in the ZIP with it. For 3.90 it has its own chapter in the User guide. Pete