Pete Dowson

The only way that can happen is using the "Wheel trim toggle" control, one of the added FSUIPC controls. It is control number 1000. Either you have this assigned somewhere and you are using it, or something you are running, Lua or other application, is sending that control value to FS. Pete

Well, I honestly don't know. That's why I suggested checking FSINN documetation and/or support to check. You could try it, I suppose. Can't do any harm. There's no way to drive any outputs directly from FSUIPC, and no way to drive LEDs without some sort of electric circuit. I use an Arduino board for my LEDs, with a Lua plug-in send it messages. You need to program both Arduino and Lua that way. No way. Octal is base 8, so only has digits 0-7, no 8's possible. I don't know of anything using octal -- last time I used it was on the Leo III mainframe back in the 60's. FSUIPC doesn't support it for sure. 3584 decimal = x0E00 hex, which wouldn't make sense either, and there's nothing relevant in offset 3584. x7000 id decimal is 28672. Pete

I don't know. You need to consult FSINN documents or support. The Squawkbox support was their action, originally using an FSUIPC offset -- 7B91. Check that you don't have this in your FSUIPC4.INI file: NoActionOn7B91=Yes In SB4 they changed to using SimConnect Client Data, a memory area called ""SquawkBox Data". FSUIPC uses this when 7B91 (or 7B93 for IDENT) is written to. There in no code specific to any other on-line flying client. I don't know if FSINN and iVASP have made their own implementations, but the FSUIPC facility should work if they've used the SB4 methods. See offset 7B93 in the offsets status document in your FSUIPC Documents folder. Easiest way is assign to "Offset word set" with offset 0354 and parameter x7000. The assignments are all saved in your FSUIPC4.INI file. The Button assignments are all in a section called "Buttons". The format is described in the Advanced User's manual, and the codes FS coding for controls in in the List of FSX and P3D Controls document. Numbers less than 65536 refer to added controls which are also listed in the Advanced User's guide, as are Offset encoded values which look like xNNNNNNNN (N's are characters 0-9, A-F). A decoded version of assignments and calibrations in the INI file is actually an interesting idea. I might add such a facility one day, when I have a couple of days to spare. Maybe a Lua plug-in so folks can adapt it to taste. Pete

Please NEVER EVER reveal your key, or it will have to be invalidated. I have obscured it in your message. Your order is never for a specific version, other than distinguishing between FSUIPC3 and FSUIPC4, not for any individual version of it You are expected to keep it up to date. If your key is rejected by the Installer then you are probably making a mistake -- as instructed in the Installing and Registering document included in the downloaded ZIP, you must enter all three parts, name, email and key, exactly as per your registration at SimMarket. As suggested, it is best to use cut-and-paste for this to avoid small errors. The only other reason could be an incorrect system date set on your PC, one before the date of purchase. That makes the key look invalid too. Your questions: 1) Do Keys expire after a limited time ? No, they are valid for all versions and forever. Lifetime updates included. 2) If not then why cannot use it on the latest v.4.95 ? See above. Have you used it before? You seem to imply not. 3) I cannot open the Key file in the FSX Modules folder. What common text editor will work? It is a common text file. Do not double-click to open it, just select it in a common editor or drag and drop it in. If you need to send it to me (but not here, by private email only) you'd need to rename it, as KEY files are generally regarded as dangerous by email systems. No, age is no excuse these days, when 70 is the new 50. I am almost 73 myself! ;-) Best for text files like that just to paste them into a message. If you use the <> button ast the top of the edit area here it will allow you to enclose them neatly to retain formatting. In any case, the Install Log would only tell me that your Registration failed, not which error you are making. Pete

BTW, if you want to convince yourself that FSUIPC is indeed doing the same as an assignment in FS would do, just enable Axis logging in FSUIPC's logging tab. Compare the logging of PAN VIEW events between the two ways of assigning. The log file is FSUIPC4.LOG, in the FS Modules folder. It's a simple text file. Or, if you (temporarily) run FS in Windowed mode, you can check the "Console Log" option on the Logging tab and see the log results in real time, as you operate the hat. Pete

Ok. Then it's to do with the plane. Try a default aircraft, and make sure it is in Virtual Cockpit mode. FSUIPC isn't really involved here. When you assign to an FS control, all that happens is that the control is sent to FS -- after that it is up to it. There's actually no difference to assigning in FS. The only advantage in FSUIPC is that you can have different assignments for different aircraft profiles. Pete

The Delta cannot be set to -1. It can only be a positive number. You are reading the input and output values, not the Delta. The output value of -1 means the Hat is central, or released. The Delta actually is set to 0 for hats (POVs), not 1 as I previously said. I just checked. And you can't change it for hats. And in the Axis dialog there are no "buttons". The POV is an axis, and very good ones can return all values from 0 to 359. Simple ones only return the 4 directions, better ones 8 directions (at 45 degree intervals). It doesn't matter what they return. FSUIPC passes the value directly through to FS in the Pan View control. It is EXACTLY the same as letting FS do it, no difference whatsoever. Did you scroll through the "Send to FS as normal axis" list and select Pan view? Also, you do not need to delete any assignments in the sim, just disable controllers. It is one checkmark. Pete

I'm fairly sure the Delta is automatically set to 1 for Pan View and is fixed for good reason. If your assignment doesn't work, how is the hat doing anything? It sounds like you haven't disabled controllers in FS. You must either use FS or FSUIPC, not both. Or perhaps you also still have the hat buttons assigned (the stuff you said you did originally)? They'd fight each other if so. Pete

It means what is says, that the code inside whatever program you are trying to use has a problem finding FSUIPC or WideFS or FS! You either are not running FS or you are but you do not have FSUIPC installed, or you are on a different PC and aren't using WideFS. In other words, it means exactly what it says! I cannot deal with programming problems in programs I am not responsible for and don't even know, whether it be PIREP or something else "I'm not going to worry about". Pete

Which manual? The FSUIPC User Guide? It's page 32 in my copy. Are you up to date, FSUIPC 4.95? Did you try just assigning the Hat to "Pan View" in the Axis assignments dialogue, instead? That's the more normal way these days, now that almost everyone uses "Virtual Cockpit" mode in FS -- the button assignment systems are a fall back for use in the older 2D cockpit views, and also were the only way in any case in FS2004 and before. FS itself uses Pan view for the hat, if controllers are enabled there. See the chat under "Delta value", page 42 in the current manual. It isn't covered explcitly anywhere else, because it's a standard FS control, and most of the many hundreds aren't explained either. It would be an awesome undertaking! ;-) Pete

It means the program you are trying to use has a problem and you need to go to their support forum. I've no idea what PIREP is. Sorry. Pete

You told me all that already. I need to know what you actually assigned them to in FS -- i.e. the words in the assignments dialogue! I have no idea still. :-( There's no sign of any assignments whatsoever in the INI file you showed me. Didn't you also calibrate those? How did you assign them -- in other words, in which of the assignment modes provided, and ?to which controls in the drop down list? It always says that till you press "SET" to start the calibration process. Did you not read any of the Calibration chapter in the User Guide. There are numbered steps to follow. I also need to know which calibration section in FSUIPC you are trying to use, eg the page number. There are at least two pages which have throttles. It is very very difficult to get any information from you. This could take weeks at this rate! If FSUIPC is running then it is installed properly. There's absolutely nothing else to it. It is very simple. It runs if installed, it doesn't if it isn't. The only component to the program is the DLL itself, the part which runs. Perhaps the INI file you showed me is the wrong one. Perhaps you have more than one installation and are looking in the wrong one? The INI file certainly shows it has detected your devices: 0=PFC Throttle Quadrant Console 0.GUID={7FFE5A50-FEF0-11E5-8005-444553540000} 1=PFC USB Pedals 1.GUID={7FFE5A50-FEF0-11E5-8002-444553540000} 3=PFC Remote Instrument Console 3.GUID={7FFE5A50-FEF0-11E5-8004-444553540000} 2=PFC Avionics Adaptor 2.GUID={7FFE5A50-FEF0-11E5-8003-444553540000} 4=PFC USB Joystick 4.GUID={7FFE5A50-FEF0-11E5-8001-444553540000} But that's it. Nothing else. Maybe you are pressing ESCape or CANCEL when you've done in the options instead of OK, so any settings you make are not saved? Pete

Hmm. It looks like two of the axes are not within the 6 (XYZRUV) supported by FSUIPC as axes. It does also support one POV, but only for up to 8 button assignments. Additional axes, supported by a later version of DirectInput, are supported by FSUIPC4, but you are out of luck woth FSUIPC3 and FS9 I'm afraid. FS9 is now over 12 years old, and I did continuously maintain development of FSUIPC for it all this time, but, alas, there is no way I'm going to rewrite it now for such an old simulator. That shows no attempts whatsoever at assignment or calibration, so it doesn't help at all. In order to work out why you don't see axes assigned in FS in FSUIPC's Calibration tab, I need to know how you've assigned them in FS (i.e. exactly which described axis), and where you've checked and enabled in FSUIPC's calibration. Since it looks, from the INI, that you've not begun this process in any case. I did ask for this information earlier. If FS is truly assigning all 6 of your axes and they are being assigned to normal control surfaces, then they will be seen and calibratable in FSUIPC. Pete

Is this the quadrant the serial port type, which needs my driver, PFC.DLL, or a newer USB device of which I am not aware? Is it being by PFC significant in your query? Just one? Doesn't the PFC quadrant have up to 6 axes, usable depending upon which front end you fix to the main box? At least, mine looked like that when I had one Of the possible 6, which doesn't it recognise, and what designation does it give the other <6 axes? Ah, so I assume the device must be a regular USB joystick device also recognised as such by Windows? In that case, how does FS recognise that axis? What designation? Please tell me exactly what controls in FS you assigned them to, and which one(s) you do not see. FSUIPC calibration does not operate on axes at all, but on FS controls, so where they are seen in that section depends on which controls were assigned. That's true no matter where they are assigned. In fact the calibration facilities were there a long long time before assignments in FSUIPC were possible. Finally, it might be a good idea to show me your FSUIPC settings file. This is FSUIPC.INI and it is found in the FS Modules folder. It is a text file and best just pasted into a reply here. Pete

Button assignment formatting and programming is fully described in the documentation installed in your FSUIPC Documents subfolder, as pointed out in the Installation Guide you would have found in your FSUIPC downloaded ZIP file. See the Advanced User's guide, pages 19-27, and the Appendix 1 which was contributed by a user to expand on this further. This subject is better dealt with also in the documentation you already have, but this time in the main User Guide, in the Chapter entitled "Keeping track of multiple control devices ("Joy Letters")" and listed in the Contents list right on the 2nd page. Full documentation for the program is provided for good reasons, to help purchasers to make full and correct use of it. Pete Pete

That's a rather daft arrangement. What were they hoping to achieve with that? Yes, that looks fine. That code would work in any version of FSUIPC. The offset comparison facilities were introduced many tears ago, in FSUIPC2 I think! "RC" is not a function. "R" means keep repeating whilst button is pressed (as opposed to 'P' from 'Press' and 'U' for "un-press", and "C,1" or "C,2" mean button 1 and 2 on joystick C. The poster is sensibly using Joystick Lettering so that FSUIPC can keep track of his joysticks even if he moves them or if he updates Windows. I suppose you are still using numbers, but even so his numbers, if he used them, wouldn't necessarily be the same as yours. Windows assigns the joystick numbers on each specific PC. Pete

It's out of date. Earliest supported version is 4.95. Er, surely the reverse thrust switches are at the idle/off extreme end of the throttle lever movement (i.e. pulled back towards you as far as they go), NOT at full thrust which is at the opposite end! Are you sure you have the throttles the right way round? Nothing has been removed from FSUIPC, so that doesn't make sense either. Pete

The PMDG controls are nothing to do with "offsets". They are control numbers, documented by PMDG not by me. In FSUIPC you assign to <custom contro> and enter the control number, which I think has to be computed from the list in the .h file in the PMDG SDK folder. This is really a PMDG support question. I've provided a facility for you to assign custom controls, but I do not use any PMDG products and cannot operate as their support. Have you tried PMDG forums at all? Pete

Typo? The current release is 4.95. Pete

Delete all of the .mcro type files in the Modules folder. The names before the : character as listed in the assignments drop down are the filenames of those .mcro type files, so you can be selective if you wish. There's also a section in the FSUIPC4.INI file called [MacroFiles]. After you have deleted the .mcro types files, best to also delete the entries in there with the same names -- or if you are deleting all macros, just delete that whole section. The "Macro Controls" chapter on page 38 of the Advanced User's guide does explain the .mcro files. Pete

No, sorry. It's a standard Windows dialogue and not sizeable. You can make the text larger (it s simply the font defined in Windows for its use also), but the box won't grow to accommodate this. Pete

Yes. The problem was that you were still on an old version of P3D3 (3.0). There are two other recent threads where I provided interim solutions (a pre-release of the DLL supplied with version 4.95. See this one, for example: fsuipc-p3d-crash-on-startup As I explained in those threads, it seems L-M introduced, for the first time I think, some backward incompatibility into the few older functions FSUIPC uses. The revised SimConnect module is built with the P3D version 3.0 library. I'm actually quite surprised to see that's now 3 users reporting here who've not bothered to update their P3D3 to the latest and greatest. No one has explained why yet. Pete

It is never a good idea even to have controllers enabled in the sim if you are assigning in FSUIPC. All versions of FS have a habit of doing automatic assignments if at any time they think a controller is newly connected, even if it's ownly due to a USB glitch or hub power problem. Why not have all the common ones defined generically, and simply use those each time you build a profile. And how many profiles do you have in any case? surely not one for every aircraft in your list? There's no way FSUIPC can come between controller axes assigned in the sim and the sim seeing them. This is why conflicts are so easy to get when using both. If you use FSUIPC to assign them to the Axis throttleN set controls and do NOT calibrate them (all in your PMDG profile of course), then this is absolutely no different to assigning in the sim, except that the sensitivity and dead zone sliders aren't used. Pete

But most other P3D3 + FSUIPC users are fine? Explain that. I cannot help you with no information. Maybe you are using an out of date and incompatible FSUIPC4. Maybe you have corrupt wxstationlist.bin or .WX files. There are many things outside of FSUIPC itself which can case a crash when FSUIPC is running. FSUIPC makes a run-time log called FSUIPC4.LOG, every time it runs. If you want me to help rather than just make accusations then I need to see it. You'll find it in the Modules folder -- paste its contents into a message here. I also need the Windows crash details. You'll find those in the Windows event viewer. Pete

Well, to start with FSUIPC4 is for FSX and later, not FS9. For FS9 you need FSUIPC3! However, looking at the Install log you seem to have FSX installed (as well?). You also seem to have a P3D version 3 installed, at least according to the Registry: But then you got this: So what is going on there? What is happening when you enter you three parts of the registration? Do you get it rejected? If so, then in all likelihood you are making an error. All three parts must be exactly right. Also check that your computer date is set correctly. Pete