Pete Dowson

Is FSUIPC even loading? Check to see if it creates a new Log -- that's one of the first thing it does. If there is a log, please show it to me. Did you install a P3D update at the same time or just before? What was the previous version of P3D? What other programs are being loaded by your DLL.XML and EXE.XML files? Have you tried without any others? It could simply be a conflict. Pete

Does a new FSUIPC4.LOG file appear in the Modules subfolder when you run FSX-SE? If so, FSUIPC4 is being loaded but is having trouble connecting to SimConnect. You'd need to show me the Log file (paste complete into a message). Sorry, I can't make head nor tail of that. To start with there are none of the important < and > symbols used so much in XML. Can't you paste the original complete file, intact, here, please? Use Notepad or a proper text editor, not any word processing application. (I've never heard of FSXML by the way). If it really looks like that, then something really drastically bad has happened to the file. Best delete it and re-run the FSUIPC4 Installer -- that will create a new one which just loads FSUIPC4. You'll need to see about adding any other DLLs separately. Pete

Just reply "Yes". It's not an FSUIPC4 problem, but a long standing SimConnect bug to do with trust checking. In P3D they've had the good sense to remove all that and it never gives a problem, but even the FSX Microsoft team, back when they still existed, couldn't sort it out and blamed some complexities in Windows itself. Also see the FAQ subforum. The thread "FSX fails to run after FSUIPC4 first installed" is relevant. Pete

Sounds like you've not installed LINDA properly. I think there's a Forum for LINDA somewhere. Does it give a link in the documentation? I really don't know anything about it myself. Pete

If you do need different assignments or calibrations then you need different Profiles. Broad categories are fine when most of the usual assignments are the same and covered by the generic (non-Profile) assignments -- such as all default and many of the simpler aircraft. Once you get onto the likes of PMDG, Aerosoft Airbus, iFly and FSLabs you have at least those catergories already. Profiles are really little different from the old Aircraft-Specific assignments. It's just a bit more capable and hopefully more intuitive to use, that's all. Stick with the old method if you are happy with it. One thing, added later to the Profiles facility, is the possibility of splitting of each set of profile assignments and calibrations into separate files in a "Profiles" subfolder. This makes the main INI file a lot more handle-able and shows more clearly what you have going. That might be worth considering if you have extensive settings for many aircraft types. Pete

FSUIPC - no, not suppressed P3Dv3 -- not in use at present. FSX-SE, no not disabled ASN, don't recall -- default setting I think. I don't use PM at present, but Prosim737, which seems to behave impeccably/ Pete

Yes. I don't use any PMDG or Aerosoft aircraft, but that how I understand it from other use Yes, you should be able to make that work. Pete

I don't know about 1, but I do know that the PMDG Boeings, and possibly the Aerosoft Airbus, do not support reverser on an axis. They don't obey the older throttle controls which have a reverser range. Most folks deal with it by using a button to do "throttle decr" repeatedly instead -- the action by default programmed onto the F2 keypress. Those specific aircraft are probably the worst ones to try to build a realistic hardware setup around. Pete

The setting up of quadrants depends much more on what aircraft you are intending to use with them than what utility you use to "set them up". There are several different ways in FSUIPC alone, and which is best depends on the add-on aircraft. PMDG Boeings and Aerosoft Airbuses in particular need different methods to default and simpler add-on aircraft. for instance. So really you are unlikely to get a useful answer without posting details of your preferred aircraft (The Profile facilities in FSUIPC can of course be used to set them up differently for each aircraft or type of aircraft you use). Pete

No, I don't have any PFC standard USB devices, only serial port ones and some cockpit MIP units they did using USB HID protocols (like GoFlight stuff, USB but not standard joysticks). ANY standard USB joystick type device, recognised by Windows as such, should work fine with all programs which accept standard Windows joystick inputs. That goes for all the games out there as well as all the flight simulators. If P3D has any problems with joysticks, which it has had, it applies to all of them, not specifically to PFC or any other make. Saitek only gets mentioned specifically more often because they probably sell the most, that's all. Problems in P3D version 3 are gradually being resolved and as far as I know there are none now outstanding for joystick devices. Pete

Yes, the default FS assignment uses the Axis set of controls. They do occur earlier in the drop down. The older Throttle N Set controls are the ones normally used by FSUIPC after calibration -- they are the only ones which have a reverse range. The Axis... ones run from -16384 for idle through to 16383 for full thrust, but no reverse zone at all. The (better IMHO) Throttle N Set controls run from -16384 full reverse -- though more usually limited to around -4096 for 25% by the aircraft model-- through idle at 0 to full thrust, again at +16383. Pete

Yes, but don't enable controllers in P3D. Just assign always in FSUIPC. Assign to "FS control" not direct to FSUIPC calibration, and don't try calibrating in FSUIPC -- it's the calibration which causes the controls to miss being seen by the Airbus, or worse being seen twice with differing values. Assigning to the FS control in FSUIPC is identical in effect to assigning to the same in P3D itself. Pete

I'm not really an expert of the actual physics and electrical characteristics of these things, but, yes, trying other cables (if replaceable) and USB ports is worthwhile. As long as you are using the joystick letters FSUIPC won't lose track. I don't know whether the CH quad uses optical encoders or potentiometers, but in the latter case I've used electrical switch cleaner to good effect. I assume you've already checked that you haven't got dual assignments to those two axes, in FS and in FSUIPC? Check that controllers are disabled in FS if assigning in FSUIPC. Pete

Sorry, I don't know. It may be that the authors of that aircraft are intercepting the flight controls first, so depriving FSUIPC of the ability to calibrate them. You could try assigning in FSUIPC direct to FSUIPC calibration, but there is a danger then that the aircraft doesn't see them at all. Worth a try though. Have you tried to get advice on that specific plane from A2A or their Forum? I don't use many add-on planes, only really the Prosim 738. Pete

It doesn't matter where or how you assign axies, the calibration part is separate and works for FS or FSUIPC assignments. For FS assignments you need to make sure the sliders for sensitivity and null zone are set correctly (max and min, respectively). If you allow FS to see your controllers, then don't assign in FSUIPC -- it's one or the other, or they'll interfere. To use FSUIPC assignment you should disable controllers altogether in FS. Otherwise I can't really help without some description of the difficulty you only just mention. Pete

Only 1 out of 12 named "FLOOD".? If so then something most certainly is confusing Windows. Good luck in finding out what is happening. Please post any progress here too. Let me know especially if changing AutoAssignLetters to No helps at all. Pete

How many devices called "FLOOD" have you actually got connected? 12? The letters are probably changing because there is something drastically wrong with that device. They are registering themselves differently each time scanned. They all appear to be different because the GUIDs are all unique: To check that I had to sort them into order to make comparisons easy: 5.GUID={27253C80-B460-11E5-8001-444553540000} 7.GUID={27253C80-B460-11E5-8002-444553540000} 11.GUID={272B5700-B460-11E5-8003-444553540000} 9.GUID={272B5700-B460-11E5-8004-444553540000} 8.GUID={27312360-B460-11E5-8006-444553540000} 12.GUID={60C43D40-B4B2-11E5-8001-444553540000} 13.GUID={60C43D40-B4B2-11E5-8002-444553540000} 14.GUID={60C43D40-B4B2-11E5-8003-444553540000} 4.GUID={60C43D40-B4B2-11E5-8004-444553540000} 6.GUID={C00D8130-B24B-11E5-8001-444553540000} 15.GUID={C00E1D70-B24B-11E5-8002-444553540000} 10.GUID={C00E92A0-B24B-11E5-8003-444553540000} 3.GUID={C00E92A0-B24B-11E5-8004-444553540000} 1.GUID={D6D9F770-B243-11E5-8001-444553540000} 2.GUID={EA683F60-CAB5-11E5-8001-444553540000} Now, I don't know how Windows assigns GUIDs, but I would assume that if it sees many devices all looking identical it is pot luck which is assigned where. With "AutoAssignLetters", once letters are assigned it is best to change the option to "No" in any case. I don't know if that would help when Windows appears to be changing things, but it might. FSUIPC only assigns letters to things which appear newly scanned. The title you've given this thread is plain wrong andmisleading. The AutoAssignLetters is probably working well -- you have no evidence otherwise. Pete

Yes. There was another question recently which related to PMDG's custom controls. I think you'll find the thread useful: efis tfc button Read from 4th post on. Pete

Yes you could -- though there's more than one section. You'd be better just keeping the existng sections and just edit the name in the [Profile.Maddog CAL] section, i.e change "1=Continental2 to the new name, or a unique part of that name. I'm surprised they gave a title like just "Continental" to an aircraft, without even indicating what sort of aircraft it is! It must look a bit strange in the FS Aircraft Selection menu. Yes, true, for FMC programming you'd need keypresses (though their SDK probably lists controls for those too, but they won't be FS controls). No. You assign buttons to functions you need, rather than find functions and assign just for fun. Decide what you want the buttons to do, then find the appropriate control. PMDG aircraft like the 737NGX and 777X are notoriously non-standard so there will be lots of things in the cockpit which are simply NOT controlled by FS controls or keypresses. They are all accessible using "custom controls" added by PMDG. Those are documented in the SDKs they install. Pete

Yes. II just looked and saw this. You have defined a Profile "Maddog CAL" with this aircraft defined: [Profile.Maddog CAL] 1=Continental So all aircraft with "Continental" in their name will use this profile. Before you added the assignment for button A,0 there was no buttons defined. It looks like all of your PMDG aircraft have Continental in the title. That's the only problem I think. If your Maddog has only got "Continental" as a name, then you'd either need to rename it (in its Aircraft.CFG file), or change one of the options in the [General] section -- ShortAircraftNameOk. Here's an extract from the FSUIPC Advanced User's Guide: The parameter defaults to Substring -- note well the last sentence in this extract. You can change that to Yes instead, in which case it will work with that very short aircraft title. Note that you could make your PMDG profiles apply to more than one aircraft variant by shortening the titles used by FSUIPC. In fact, all three PMDG profiles have EXACTLY the same assignments for buttons and axes, so it would be much more efficient and sensible to replace all of the Profile, Keys and Axes sections for those aircraft by one set, i.e: [Profile.PMDG 2 engine] 1=Boeing 737-824NGX 2=Boeing 737-924NGX 3=PMDG 777 [Buttons.PMDG 2 engine] 0=PD,30,K113,11 1=PD,17,K112,11 2=PD,31,K115,11 3=PD,18,K114,11 4=PB,1,K70,10 5=PB,2,K82,9 6=PB,6,K71,11 7=PB,0,K90,8 8=PB,4,K75,8 9=PB,19,K86,10 10=PB,17,K72,10 11=PB,18,K78,10 12=PB,16,K79,10 13=PB,15,K65,10 14=PB,3,K90,10 15=PB,5,K85,8 16=RA,21,K116,10 17=RA,20,K116,9 18=RA,27,K117,10 19=RA,26,K117,9 20=RB,21,K118,10 21=RB,20,K118,9 22=RB,23,K119,10 23=RB,22,K119,9 24=RB,25,K120,10 25=RB,24,K120,9 26=PD,25,K68,9 27=PD,20,K70,9 28=PB,27,K121,10 29=PB,26,K121,9 30=PA,4,K72,9 31=PA,2,K84,10 32=PA,1,K76,11 33=PA,0,K76,10 34=PB,9,K66,9 35=RA,24,K122,9 36=RA,25,K122,10 [Axes.PMDG 2 engine] RangeRepeatRate=10 0=CX,256,F,65763,0,0,0 1=CY,256,F,65762,0,0,0 2=DZ,256,F,66423,0,0,0 3=DR,256,F,66420,0,0,0 4=EX,256,F,66387,0,0,0 5=EY,256,F,66388,0,0,0 6=ER,256,F,65764,0,0,0 Finally, why is every single button assignment only to a keyboard press? In FS keyboard presses are assigned to FS controls, so your assignment is pretty inefficient -- FSUIPC looking up a table to find a key to press which is later picked up by FS which then looks up that key assignment and converts it to a key which it then sends to itself. FSUIPC's assignment facilities offer ALL of the controls which FS can offer, and many more too. Have you ever looked at those? Pete

It's quite a lot of work to make changes to very VERY old code (button assignments date back to FS2000 at least). Quite honestly there simply isn't demand to justify this, and possibly introduce new bugs as a result of changing code I've mostly forgotten. Pete

The "ButtonRepeat" parameter in the main [buttons] section has two parameters -- repeat rate, and number of repeats to miss before starting. Default is 20,10, so 20 repeats per second after half a second delay. You probably only want to change the second value. Note that these parameters are global -- they affect ALL button assignments. Pete

Just assign to "Flaps Decr" for F6 action, and "Flaps Incr" for F7 action, with the Repeat option checked. Those two controls are exactly what F6 and F7 are asssigned to by default. The repeat action on the keyboard is controlled by the keyboard. In the case of button repeats it is FSUIPC which does it, and the rate is actrually settable in the FSUIPC4.INI file -- but the default should be fine. And, as for the keyboard, it doesn't start repeating till you've held the button/switch on for a bit, so you can still do single increments and decrements. Pete

No, let's try to sort it out. I'm puzzled and would like to work out what is happening. First, some more questions and things to do: 1. When you are in the Buttons tab and you press one of the buttons which should do something specific to the Profile, and select the Profile option at the top, does the correct Profile name display at the top, in the options title bar? 2. Program that button to something, doesn't matter which, so I can see the effect on the INI file. TEll me which button it was (joy,number). Second, please ZIP up your INI file and send it to me at petedowson@btconnect.com. I'm now wondering whether there are some addition characters in the file, unprintable ones, which are not visible or lost when pasting into the message here. I've seen such corruption happen before, a couple of times over the years. Include a log too please, a complete one. Pete

Does the button show the joystick number/letter you expected? Well, FSUIPC hasn't changed, and the INI file you showed me is okay and shows profiles in place, so those actions which you think must have changed things didn't. Without knowing which buttons you are talking about I can't cross-check, but did you enable button logging as I suggested? If you temporarily run FS in Windowed mode you can use the Console Log option to see the results in real time. Pete