Pete Dowson

I assume with a PMDG aircraft and Saitek throttles you have the button operated when you pull back the throttles assigned to reverse with repeat whilst held, then idle when released? If so, then I expect your button was flickering on and off. You can check that by logging buttons. Replacing the same DLL with the same DLL can't possibly make any difference. I would think it likely you just deleted your settings so no longer had reverse set on a throttle.button. Pete

You don't need any logging if things are working. I would be more interested in what you did differently to make things work. BTW you shouldn't have an "FSUIPC5.1.Log". you must have pressed "New Log" to start a new file. you never need to do that unless you are after a clean start. Normally the full log from the start is more useful. Also, I don't see how the Installer log is relevant. The FSUIPC logs just show everything is ok. Pete

So the floating point value supplied has any non-zero digits after the first two decimal places discarded? True. FSUIPC works through SimConnect in any case. If you do find a way please let me know and we'll implement it in FSUIPC too. Pete

What are they assigned to, exactly. If you use P3D assignments instead (temporarily re-enabling controllers) do they then work okay? If so, L-M won't be interested. No really. You could log the axis controls in FSUIPC logging. Maybe they are getting trapped or inhibited somewhere. Also, in the FSUIPC Logging Tab, right-hand side, enter the offset 341A and select type U8. Then chek "normal log" below. This will log a byte in FSUIPC used to stop toe brakes operating -- used by programs wishing to simulate failures -- eg by overheating in the case of the brakes, It has bits used as follows: 0 Left brake (“Axis Left Brake Set”) 1 Right Brake (“Axis Right Brake Set”) 2 Flaps 3 Spoilers So and odd value, for example, would stop Left Brake working. Neither, yet. Pete

PMDG have always said not t use FSUIPC. It's their problem avoidance policy. It's other PMDG + FSUIPC users you need to heed, either here (see User Contributions subforum as well as many threads), or hopefully onthe ASIM Forums -- the users not the Support staff. There are very many PMDG + FSUIPC users who are using FSUIPC to the full with no problems. Assignment in FSUIPC to the FS controls (not to "direct") is actually identical to assigning in P3D. This normally only matters for the throttles because of the way PMDG reads the throttle values. They can still be assigned in FSUIPC but not claibrated, so you shouldn't use "Direct tp FSUIPC calibration" for throttles. Well, that mans you must also calibrate. Some PMDG aircraft don't like the way the changed values are fed through to the Sim whilst it is also reading them at a different level. There are THREE choices cfor assigning axes: "Send direct to FSUIPC Calibration" "Send to FS as normal axis" "Send to FSUIPC Offset" The second is sending to FS normally, i.e. using normal FS controls. Sorry that I thought that was self-explanatory. The drop-down list you get for that list controls which ARE all the FS controls usable with axes. The FS controls are also listed in a "List of ..." document installed in your FSUIPC Documents folder, and there is a "live" list produced as a Text file which is derived, as is FSUIPC's drop-downs, from reading their names from P3D itself. Pete

Probably using FSUIPC assignments which aren't compatible with PMDg. Generally you need to assign to FS controls in FSUIPC, not to the "Direct to ..." ones. But I missed this in your first post: Well the flight controls should not be affecting it then, or if they are the A/P would turn off and you'd get the "beep" warning. It is sounding more and more like PMDG specific problems which would need PMDG advice, or at least advice from folks who use their aircraft. Pete

Not very helpful then. Doesn't it say what about your OS is incompatible with my standard Visual Dtudio coding? It is specifically targetted at Windows 7, but also fully compatible with Windows 10 (I use both here)? Perhaps the problem you mentioned with Windows 7 compatibility on your PC has actualy prevented a fully normal Windows 7 being included and set up correctly. Try setting a different "compatibility" type in the program's properties. And don't forget to terminate those two hung processes in Task Manager. Pete

What amount f IQ does it take to find one number from a list, according to which keypress you want, and to put it next to a comma and another number 98) which I gave you? You simply ignore all the help I've provided. I've spent a lot of time and when I point out that you haven't even purchased the product, which would have made it much easier and quicket for you to as you wished, as well as being fair when you expect support, yor react as if I'm insulting your intelligence. This has gone on far enouh. Sorry. i very rarely lock any threads but this one is simply going nowhere. Pete

On actually checking the FSUIPC Advanced User's guide, I find a list of functions on page 35. There appear to be many functions for this offset, and all involving a different parameter, amongst which are 19 in the 300 range for Airbus and 11 for boeing. so it is as i said above, a different parameter for each PM GC function. Note that it also says that this is copied from the PM documentation! Pete

What do you mean "set up offsets"? Sorry, you still aren't clear. Where do you have such a statement? I'm just not matching anything you say to any options in the FSUIPC dialogue. So if the assignments dropdown, you assign to Offset word set, then enterx4F4 for the offset and 0 for the parameter. However, didn't you say 4F4 should be set to 301? Where does the values 0 come from? I don't know about that. The way Project Magenta processes the offsets it reads will be defined in PM documentation. Did you download this to refer to? It is many years since i used PM, so i don't remember. Maybe some of your buttons need to do something different? And they certainly wouldn't all be the same offset AND same parameter, because then they'd all do the same thing, wouldn't they? As I suggested above, in the Assignmwents drop down. Looking things up in the FSUIPC Advanced users guide, I do see: PM GC Controls (by Param) I think that does use 04F4. So i think you might find it more logical to assign to that, then enter your parameter (301 or whatever -- that list must be in the PM docs). Pete

If they are changing by small amounts up and down, that's called jitter, and is caused by dirty controls or poor power. If the changes are more violent then it will either be a very bad faulty unit, a bad connection, or interference. The "IN" value merely relays the value being received from Windows DirectInput. Check also the values seen on the assignments tab -- where you assigned these axes. They will correspond. And if they are changing all the time you'd have to use the "ignore" button to allow you to assign any other axes, as they would be seen first. I actually suggested you first check the action in a default aircraft. Really, if the inputs from the troes brakes are so wild then there's nothing PMDG could do. So, why haven't you at least tested with a default aircraft first? That's always the main step in deciding where the problem lies. (Though if your inputs are playing up I doubt there's an other source but hardware). Pete

Not the range values, One in, one out. Of course! They'll change all the same according to the axis position! and your calibration! Those look fine. That sort of range from minimum to maximum is quite normal, especially if that allows a little dead area in case you push them inadvertently during rudder operation. I think the /16 [art just means that they are reversed (the "REV" checkbox) always necessary for brakes. Sorry, but I think you need to look elswhere. Check with a default aircraft, as i keep telling you, so you can determine if it's a PMDG problem. Pete

Either leave that DLL disabled 9it isn't operating in any case with that error), or re-install whatever it is you've installed which needs it. Pete

Yes, and I told you which was which and what the "normal" value was (8). So, find the keypress you want to use and replce the 88 with its number, and the 10 with 8. Considering you can't even purchase FSUIPC you are asking a lot of questions, none of which would be needed if you had the licenced version and did this the proper way. Please re-read the answers and apply a little intelligence.

But you showed me the line. All you had to do was change the numbers, as i said!

Buttons can be assigned to be general or specific to a profile. Just uncheck the Profile select check box before assigning them. Only axes have to be either generic or profile specific, because otherwise unwanted inputs from generic ones can interfere with their operations in the profiles. This should not happen with buttons 9or keypresses) as you wouldn't press an inapplicable button or key. If a button or keypress is assigned for general use and differently in the current profile, the latter assignment takes precedence. Pete

You are trying to use FSUIPC to operate things in Project Magenta. FSUIPC is only acting as the messenger, allowing PM to read the offset you are changing. what it then does it up to it. The problem there is that none of that tells me anything. it doesn't show me anything about how you are programming anything I know of. Sorry.

Didn't you find a page with the list of key codes? It isn's hard to find. Just try searching for "key presses". I think it's about page 23. (They are standard Windows key codes).

It is that prompt I don't understand. FSUIPC's Installer has no such prompt. Is it from Windows, or from some other program you are using? Maybe a pic of just that prompt is needed after all, as you seem unable to describe it.

"Preview" box? In the calibration screen? On the left it has an IN value (before calibration) and an OUT value (after calibration). Most joystick axes have a range of something like -16380 to + 16380. That's fine for ailerons, evelators, and rudders, as they go left and right or up and down as well as having a neutal centre. But brakes only run from neutrol (off or 0) to full pressure (16383). Proper calibration maps your unput value to the output values required. I really don't have any idea of what you regard as an "anomaly". Did you be sure to disable controllers in P3D? did you check things with a default aircraft? Pete

So why did you just say: ???? Please just describe what you are doing with "Install FSUIPC4.exe" and what you see. Try to be precise, because you've told me very little so far. Pete

I think you have conflicts. If assigning in FSUIPC be very very sure to disable controllers completely in P3D. Do not just unassign the axes and buttons. Pete

No, please don't bother. Do not try to install FSUIPC until you have installed FSX first! Also FSX at least once before attempting to install anything else. Screenshots are not often useful in any case. A verbal description is far batter. Pete

FSUIPC doesn't use AFXModuleFSX.dll which is where the problem is actually occurring. Looking at your DLL.XML: So, the module is loaded ahead of FSUIPC and starts doing its stuff before FSUIPC gets to fully initialise. It then crashes, because of the problem as stated, but Windows blames FSUIPC because it was the last module loaded. As a test just try renaming your DLL.XML to, say, DLL.XML passive, then run the FSUIPC Installer. Test then (you might need to load twice or more to clear Windows marking FSUIPC as bad. Then try re-instating the original DLL.XML, but for a first test change the <Disabled>False</Disabled> line for AFXModuleFSX.dll to True. Test again. Only then re-enable AFXModuleFSX.dll. If you still then get problems I think you may need to re-install whatever it is that nstalled and uses AFXModuleFSX. Pete

Sorry, I do not understand any of that, and the picture doesn't help at all. What software are you using? Is "PM" for "Project Magenta"? Some proper logging, instead of a joined up sequence of stuff i can't urecognise, would be better. And if it is Project Magenta you are talking about, shouldn't your questions be directed at their support forum? Pete