Pete Dowson

Assuming you are using an up-to-date copy of FSUIPC4 (current is 4.859s), just enable "Mouse Look" in the Miscellaneous tab of FSUIPC options. The latest updates for FSUIPC are provided in the Download Links subforum. Pete

Nothing that I know of. I've never seen that message with FS9. It works fine here, and if it were a general problem there'd be lots of questions about it here. After all 3.999w is the main current release which very many have downloaded since its release last August. Maybe there's something it now needs which isn't installed on your system? I certainly am not aware of any new dependencies for FSUIPC3 -- I am very careful not to use anything only available in later versions of Windows. These are the Windows DLLs it needs to be able to link to. Perhaps you could check whether you have them all installed? KERNEL32.DLL ADVAPI32.DLL CRYPT32.DLL DSOUND.DLL GDI32.DLL HID.DLL MSACM32.DLL MSCVRT.DLL OLE32.DLL SETUPAPI.DLL SHELL32.DLL USER32.DLL VERSION.DLL WINMM.DLL WS2_32.DLL If any one of those was not installed in your Windows, Windows\System or Windows\System32 folders then it would be explained. However, I've compared that list for version 3.999y5 with the same for version 3.989u (which you have working), and the only extra ones now are OLE32.DLL and SHELL32.DLL. The only function used in SHELL32 is ShellExecuteExA. That was added in the original WinXP release. The only function used in OLE32 is CoInitilalizeEx, and that's been around since Win2000. It must be some sort of dependency, but I'm not sure how to find out what. Is there any extra information in the Windows error logs? Regards Pete

Doesn't it give you a choice at all? That's the last Installer version. there is a later version in the Download Links subforum here. SimConnect is only related to FSX and FSUIPC4. Well if the signature checks, as you say, it cannot be corrupt. So this is very peculiar indeed. No. As you will note if you check, that log is from 3.989u, not 3.999w. And it is, but that is Mr. Schiratti's site. Interim updates, under my control, are always posted here, in the Download Links subforum. Please see if 3.999y5 helps. Regards Pete

The message actually says just "FS9 can't read FSUIPC.DLL"? I've never heard of or seen such a message. Did it not say anything else, no reason, nothing? When exactly did this message appear -- i.e. at what stage? Did FSUIPC get loaded then unloaded (is there a LOG file produced by this version beforehand?). What do you mean by "acceptance of the digital signature"? How do you see this occurring? Could you also check which actual version of FSUIPC you installed? I need the specific number. Currently FSUIPC is up to version 3.999y5, with 3.999z due soon. Pete

Actually the latest is 4.859s, but it is of no consequence. I shall be making a new full release, 4.86, soon. Are you talking about assigning key presses on the keyboard to controls, or assigning buttons to keypresses? Mind you, either way, it works fine here. I have many many examples of both in use on my own cockpit. Shift is treated no differently to Ctrl, Alt, or even odd ones like Tab, Windows and menu keys. Looking at your INI file, I see these Button assignments with shifts of one sort or another set: 4=RC,3,K46,9 = shift+delete 5=PC,14,K49,11 = Ctrl+Shift+1 6=PC,12,K51,11 = Ctrl+Shift+3 7=PC,15,K50,11 = Ctrl+Shift+2 8=PC,13,K52,11 = Ctrl+Shift+4 9=PC,4,K38,10 = Ctrl+Up 10=PC,6,K40,10 = Ctrl+Dn 11=PC,7,K37,10 = Ctrl+Left 12=PC,5,K39,10 = Ctrl+Rght 13=RB,38,K38,9 = Shift+Up 14=RB,36,K37,9 = Shift+Left 15=RB,32,K39,9 = Shift+Rght 16=RB,34,K40,9 = Shift+Dn 17=PB,3,K82,9 = Shift+R 18=PB,2,K82,10 = Ctrl+R 19=PB,1,K85,10 = Ctrl+U 20=PB,7,K80,10 = Ctrl+P So, which of these doesn't work? (If this is what you mean). Enable Button and Key logging and let me see the results of pressing whichever it is that doesn't appear to work. Regards Pete

That simply shows offset 0264 reflecting the Pause state, which it receives from SimConnect. Offset 0262, which is the FSUIPC pause control, remasins at 0, so it isn't something causing pausing through FSUIPC. The only other thing you can do is get a SimConnect log. There's a thread in the FAQ subforum which tells you how. From the results so far I'm afraid I don't hold out a lot of hope for this being useful, but if you wish, I'll look at it. You'll need to show me the same sort of FSUIPC log as above as well so I can locate the place where it occurs by time stamp. The log will be large, so ZIP it and send to petedowson@btconnect.com. Pete

You posted your support question into the Download Links subforum, where it was lucky I noticed it. Support is conducted here, in the Support Forum. As documented, just select it then calibrate, all in PFCFSX. No, only tested in flight. If you arm the spoiler on the ground, FS will activate it, so you cannot test the "arm" position on the ground. But in calibration mode FS is not even seeing the axis. Not sure why you'd need that. A throttle setting of 0, which proper idle calibration will give you, should be fine. If you want to assign keypresses to ranges on an axis you'd not only need to do that in FSUIPC, but you'd also need to use the special added FS controls to send the keypress. Since F1 is, by default, only sending an all-engine Throttle Cut control you'd be better assigning to that instead -- assuming you are only going to use one throttle lever (!?). Else you should use Throttle1 Cut for Throttle1, etc. Regards Pete

FSUIPC doesn't use the Registry these days, not for a long time. I expect you also deleted your old INI file with the bad calibration, as I pointed to above. Glad yu got it sorted. Pete

Okay. Nothing odd in either INI or DLL.XML. But I notice also that you have WideFS registered and enabled. If you have no other add-ons, what is WideFS used for? I suggest you monitor the Pause offsets in FSUIPC now. This may help. To do this: Logging tab, right-hand side. In the Offset column enter 0262. and in the Type column select U16. Similarly 0264, same Type. Below select "Normal log". Get the phantom pause. Show me the log. Regards Pete

FSUIPC can only use the information provided by FSX. 0858 is from the SimConnect variable "NAV GS LATLONALT:2" and 085C from "NAV GS LATLONALT:1". The locations it provides must surely always be the one you are currently or have most recently been receiving, which is related to your aircraft position not the Course settings -- which aren't relevant to the reception of radio but only the deflection of the needle. You can't pick which one you are (or would be) receiving, FS does that for you. I am sure it is only based on your aircraft's position with respect to the runway orientation and ILS positions. There will obviously be ambiguous positions which are not receiving either very well and may therefore appear rather random. Regards Pete

You posted your support question to the FAQ subforum, which is a depository for standard answers. I've moved it for you to the Support Forum. Please use this for support. You cannot download a registered copy, only a ZIP containing either the full release (and Installer with instructions), or an update (the DLL alone). You purchase registration separately, and enter the registration details when you install. If you purchased the registration after Jan 1st 2013 you need to update after Installing -- see the Download Links subforum here for the latest DLL replacement. Do NOT start out life with FSUIPC by messing with the INI file. Most all normal user functions are dealt with via the Options in side FS itself. What is it you believe you want to do with the INI file? Did you actually Install and Register FSUIPC? If so, what version number (I ALWAYS need the version number!). Was FSUIPC actually running -- i.e. was there an FSUIPC entry in the Add-Ons menu in FSX? If the program was correctly installed and registered then the Modules folder will contain FSUIPC4.DLL, FSUIPC4.KEY and an FSUIPC Documents folder containing the documentation and add-ons. Only after FSUIPC4 has been successfully run will there also be an FSUIPC4.INI file and an FSUIPC4.LOG Maybe you are confused by Windows hiding filenames from you? As suggested in the FSUIPC documentation, just change the Explorer folder options to not hide known extensions -- it will otherwise show INI files are "configuration" or "settings" files or somesuch. Regards Pete

Hmm. Sorry, then. All I can suggest is making sure you are using the latest version, enabling the Logging (in the MCP.INI file), and submitting details to PM support. Do IOCards interface directly to pmMCP, or do you have a software driver? If so, could it be a problem with the latter? The fact that you are asking about 04F2 access suggests you have your own software? Are you sure it isn't that keeping the MCP in some loop? I have my own driver for the PFC MCP hardware interfacing to the pmMCP and don't have any problems. The 04F2 access is fine, but then I definitely don't have "DisableRemoteMCP" set to on. However, my 04F2 and 04F4 access is via a queuing system which waits a short time (250 mSecs max) for the pmMCP to clear the previous value to zero before writing the next. Also, for dials, I keep the hardware display up to date locally, but only transmit the updated values to the pmMCP offset when the dial stops turning for a while (500 mSecs, for example). This avoids overloading the pm code and the interface for no good reason. Regards Pete

Are you sure? The log shows something is setting "PAUSE ON". And it isn't a key press or button press. I think you need to show me your FSUIPC4.INI file , and also the EXE.XML (if there is one) and the DLL.XML file, both from the same folder as your FSX.CFG file -- i.e. Users\AppData\Roaming\Microsoft\FSX.. If that shows nothing you'll need to make a SimConnect log. Regards Pete

So what is "freezing"? You mean the PM MCP software hangs? If so that is certainly a matter for PM support. Are you up to date? The PM modules are updated relatively frequently -- there was one less than a month ago. Pete

Sounds like they got themselves into a strange state and needed resetting. Regards Pete

I'm sorry, but you really do need to learn a bit about programming before embarking on such a more complex exercise as interfacing to FSUIPC. There should be some good books on programming VB, surely? As it tells you explicity in the extract you copied (not sure why, I have a copy already), there are 4 separate bits for engine fires, one for each or up to 4 engines. If you do not understand numbers and bits in binary and hexadecimal, please read up on that first. There's a thread which may help a bit in the FAQ subforum. Try that. Pete

No point in the pictures. Was this before or after you made the INI file copy here, because that shows two connected devices, 0 and 1: 0=Saitek X52 Pro Flight Controller 0.GUID={F3FC8DB0-37FB-11E2-8001-444553540000} 1=CH Pro Pedals USB 1.GUID={E8442DE0-1B54-11E0-8003-444553540000} I suspect that somehow, previously, your joystick appeared to Windows to be reconnected, and it assigned a different number. If you want to avoid that giving you grief in future I recommend that you use joystick letters instead of the numbers. Just change AutoAssignLetters=No to AutoAssignLetters=Yes if you don't want to bother to read the User Guide section about this. No no no! You must NOT have assignments in both FS and in FSUIPC! Use one or the other or you will have conflicts! If you are really so confused I strongly recommend giving up assignments in FSUIPC and do it all in FS. As I already said, you can still use FSUIPC calibration! You'll need to actually calibrate in any case, as currently, according to your INI file: [JoystickCalibration] Aileron=0,0,512,16380 Throttle1=0,0,0,0/8 You only have half an aileron and zero throttle control (the 0's say everything must be 0! Follow the numbered steps in the Calibration section of the User Guide. Pete

Yes. Haven't you tried searching on the word "fire" in the FSUIPC4 Offsets Status document? Pete

Hmm. Have you raised this with PM? Or is it a problem with a specific hardware MCP? I really don't understand how that parameter helps. Very odd. Regards Pete

Yes, but its internal ID might have changed if any other USB device was added/removed, or something just "glitched". I'm afraid Windows is quite prone to such things. Best to use joystick lettering. So, something changed. Software doesn't change, so it was either a data corruption or a hardware glitch. You can still do all that with assignments in the Sim. The calibration facilities are still the same for any method of assignment. Assigning in FSUIPC can be more efficient (if assigning "Direct to calibration", but not to the same FS control that FS uses). The main reason for assigning in FSUIPC is so that you can have the assignments changing automatically for different aircraft, something that FS doesn't do for you. Without seeing how you assigned the throttles I can't really help. That's why I asked to see the INI file. No, don't attach it, just paste it here as I asked. It's a text file, you can simply put its contents into a message. Pete

If any version gives such indications when Registered (i.e. with the "FSUIPC.KEY" file in the FS Modules folder), but appears to work okay without registration (i.e. with the KEY file removed), then either the registration is incorrect in some way (eg wrong name, wrong email, or wrong key), or the date on your PC is set incorrectly, making it look as if the registration was done AFTER today's date. Please check both. If you are still not clear on what is wrong, please run FS with the latest version (3.999y5 from the Download Links subforum), registered, then close it down. Zip the FSUIPC.LOG file together with the FSUIPC.KEY file and send as attachment to petedowson@btconnect.com. Regards Pete

No, but you might be able to find out what is doing it. To start with, in FSUIPC's Logging tab, enable Event Logging and Button/Key Logging.. When it goes into pause mode, check the log and see whether it was a keyboard or button press which caused it, and the "Pause" control resulting from it. If neither button nor keypress then it might be another program, either via FSUIPC offset or direct to SimConnect. The latter would be harder to find -- for that you'd need to use SimConnect logging. For FSUIPC you'd use ipcWrite logging. Depending on what add-ons you have running, it might be easier, once buttons and keys are eliminated, to go through a process of elimination, stopping one add-on at a time till it seems fixed. Regards Pete

Okay. found and fixed. Odd, it was not a very recent error. Just a small change, in a completely different place, must have moved things in memory just enough to show this uninitialised variable problem up. It was to do with the "DynamicFriction" lua plug-in you are using. Please replace 4.859r with 4.859s, now available. Thanks & Regards Pete

Sorry, I don't know anything much about "Elan K Codes". I think that's all to do with keyboards. Have you tried PM support? The values I use when writing to 04F4 are those listed in the main table, aganst the offset for 04F4 -- i.e. "Airbus 1 MAP ...." ertc. I think all the codes you can use are listed there. I think the MCP Throughpass is offset 04F2. If you look in the main table for 04F2 it gives an example. I think, for ogffset use, you are reading the wrong list of codes. The ones you quote above are only for keyboard or character based communications "Elan". If you look in the list before that section you will see. Regards Pete

Thank you for the data. I will use it to see what is going on with your system (and it is only your system -- 'r' is working fine, and as I said, is almost exactly identical to 'q'). Regards Pete