Pete Dowson

That's good news, and rather unexpected. seems that FSX doesn't operate its DirectInput in exactly the same way as FSUIPC after all. Use the REV option in the calibration tab. You ARE calibrating the axes aren't you? You are rather wasting FSUIPC's capabilities if you don't. Please check the User Guide. I suggest you follow the steps given to successful calibration. Regards Pete

BTW, I just saw another comment saying the same things about Win8, here: windows-8-and-ifly Pete

Sorry, what "works like a charm"? Sorry, you've lost me there. I don't know. I don't use any USB connected controls, mine are PFC serial port devices controlled by my own driver. Since I have no idea why Windows8 is losing the connection, and I will not be updating to Win8 in any case (Win7 is serving me very well indeed and I'm not about to mess up a seriously good setup), I cannot advise you. I simply don't understand why you've not even tried! If you browse the threads where others have this problem you will see that no one has found a solution. but I really don't know what they've tried. As I said, some are simply going back to Win7 until Microsoft fixes the problem. Regards Pete

Er, how did you find out how to use it for switches yet not for axes? I don't understand! Buttons and switches are assigned in the Buttons and Switches tab, Axes are assigned in the Axes tab. Have you never seen that? In the FSUIPC Documents folder you'll find an FSUIPC4 User Guide. There's a complete Chapter in there about Axis assignment. Pete

Not really. As I said, I've seen reports of folks going back to Windows 7 because of this very problem. Do the switches on your panel get disconnected too? If not, have you tried assigning the yoke through FSUIPC? Maybe it is only FSX which has this Windows 8 incompatibility? If all connections get disconnected no matter what then it is more likely a bug in Win8's DirectX package. Pete

I had to move your post and give it a thread title. You added it yo the Download Links subforum thread aboutmodule downloads, where it will not be answered. You must post support requests to the Support Forum. Installing Radar Contact has nothing to do with either FSUIPC or SimConnect. It is a separate program and cannot possibly affect FSUIPC. Perhaps you should explain what this "bug" is you think you have got. Can't you give any details? Pete

For several years now you have been able to use different email addresses for WideFS and FSUIPC. The name must be identical, that's all. Just rerun the FSUIPC installer and enter both registrations. Note that WideFS for FS9 and FSX are two different registrations, separate purchases, so make sure you use the right data for each. Regards Pete

So why are you posting here? And did you check your USB power management? Regards Pete

Why do you think it is anything to do with FSUIPC? Seems many fost folks who've changed to Win8 are experiencing this. Haven't you seen the threads about it elsewhere? You don't even say whether you are using FSUIPC for your controls or have tried different ways. Some users have gone back to Win7 whilst they await a Microsoft fix. Regards Pete

Sounds like they are falling asleep. Check that you have Windows power management turned off for all USB hubs in the Device Manager. In any case it is good practice to start off by waggling all controls Aand checking they are operating correctly. You either have a bad connection, a faulty or dirty device, or possibly a conflicting assignment which is interfering. You don't even say you are using FSUIPC. If you want me to help with FSUIPC you need to state the version number, and tell me how you are assigning and calibrating. Regards Pete

But I don't see that. I only see you making the same complaint, the same questions, even after I thought I had answered them. If you don't understand my answers why aren't YOU asking the questions? 300 degrees? That allows a lot of wild swings in wind direction, which is what you are seeing. This usually only happens at low wind speeds, thank goodness. The three METARs you showed earlier indicated a variance thus: LGAT 172226Z 36009KT 310V050 LGMR 172247Z 02009KT 320V080 i.e. 100 degrees and 120 respectively. With a wind speed of 9 knots that's actually quite high. It would certainly make Cessna flying rather hazardous, though it shouldn't affect the heavy metal too much. A wind with no turbulence, no gusting and no variance is what i would call stable. The smoothing is acting on the CHANGE in that wind over time and space. i.e. as the aircraft is flying, climbing or descending it is moving through different weather areas and different wind layers. Without smoothing these changes can act rather too fast, and the smoothing smooths those changes, so that one area and layer blends smoothly into the next. Turbuence, gusts and variance are effects of the wind at any location irrespective of time and distance. The point, as I tried to explain earlier, is that because of the way FSUIPC has to act to smooth the winds, those three effects which would normally be simulated by FS are completely squashed. Therefore FSUIPC simulates them itself so they are not lost. No. Wind variance is an effect like gust and turbulence. Turbulence is fast small changes in all directions, gusts are slower more rhythmic changes in wind speed, and variance is the same but in wind direction. All three effects can be suppressed if you wish -- and, as I've pointed out, FSUIPC's simulation of them can be adjusted via the parameters I pointed you to. If you'd kindly read back through my previous replies you should see i've been saying these things all along. I really did not see, nor did you ever say, that you thought wind variance was simply the normal varying of the wind with time and distance. It isn't. Regards Pete .

Who's upset? You? I am not. I only fail to understand why the answer in the document isn't acceptable to you. Of course, folks also do assume that I have nothing to do all day but answer questions. I actually put information into the documents to avoid having to answer so many. If you do have a sensible question, and not one that is so easily answered in the document as that one certainly was, please do state it. But really there is nothing more to say about offset 0BC0. it is really that simple, just the full 16 bit signed value for the trim -- the same in fact as a properly assigned and calibrated axis control would provide. Regards Pete

The value, in decimal, is -16383 to +16383. What else is it you need to know? Why on Earth do you mention *360/65536? That's the conversion factor for FS's degrees, for directions like heading. The trim axis is not controlled in degrees. Please, why don't you believe what the document tells you? No one else has been so determined that it is wrong before. It works perfectly well with the normal full axis range! Pete

The Cessna is very prone to do that in gusty and variant conditions. You probably wouldn't want to go flying in such conditions. What was the wind variance figure itself? That will ONLY apply in stable conditions Or if you elect to inhibit the variance and gust simulations (turbulence too if you don't like that). I've explained all this already. Why don't you bother to actually read what I write? It is getting a little tiresome re-explaining things. But you did explain it. WeatherSet confirmed that your wind was subject to variance. You've not bothered to tell me what the amount of that was, but it does seem quite high. I'm really not intereseted in even looking at those until you confirm that you have read what I have written and understand. If you do not like the simulation of variance and so on, just switch it off, as i suggested, or play with the parameters which control it in the INI file. This thread is getting no where and is merely repetitive until you realise what is being said. Pete

Really the user should always be able to calibrate. The readouts from potentiometers are never fixed -- they vary with age, temperature and voltage. With user calibration he can also choose the response curve to suit him, with more or less sesitivity in different areas. I think it is far better than having a fixed input which might not suit all aircraft -- don't forget the calibration can be aircraft or profile specific. PM doesn't have its own throttle offset. PM is an instrumentation system. Flight control inputs are standard. If you look at the range of offsets from 3BA8 you will see you can input many axes there. Please refer to the offsets list, where it tells you. Regards Pete

Are you checking the 16-bit word at 3364 for zero? This is the only way to do what you wish, I know of no other, and all of my other modules and add-ons use this exclusively. I don't know why you are getting any different results? Pete

You should simply be ADDING those, not deleting the original lines. FSUIPC still needs the numbers as it is the numbers which Windows understands. It relates your letters to the numbers by using the joystick names and GUIDs. You are not readng the documentation properly! Also, not that it really matters now, you are doing so much more than you need to, but you do NOT need to do both set "Auto" AND manually enter your own choice of letters. I already told you this! The "Auto" in "Autoassignletters" means AUTOMATIC, so, not MANUAL. See? You aren't reading my replies, it seems. :-( They do NOT have their IDs changed! How do you work that out? Look, here's your original which you said was correct: 0=CH PRO PEDALS USB 0.GUID={D5C7D590-2C2D-11E2-8003-444553540000} 1=CH THROTTLE QUADRANT 1.GUID={D5C7D590-2C2D-11E2-8004-444553540000} 2=CH FLIGHT SIM YOKE USB 2.GUID={D5C7D590-2C2D-11E2-8005-444553540000} and here is the new one: 0=CH PRO PEDALS USB 0.GUID={D5C7D590-2C2D-11E2-8003-444553540000} 1=CH THROTTLE QUADRANT 1.GUID={D5C7D590-2C2D-11E2-8004-444553540000} 2=CH FLIGHT SIM YOKE USB 2.GUID={D5C7D590-2C2D-11E2-8005-444553540000} Please point out the difference!? All your A, B ,C additions do is tell FSUIPC which numbers are (currently) related to which letters. If the numbers change, the match in this list will change, thus keeping track of the devices. That's the whole point, which you still seem to misunderstand. Why? Pete

It may be specific to that aircraft. Try a default aircraft. Also check the User Contributions subforum to see if others have worked out how to control your aircraft. Also see if the add-on comes with documentation telling you how to operate the A/P correctly. Regards Pete

This is aimConnect bug. Please see the thread in the FAQ subofrum entitled FSX fails to run after FSUIPC4 first installed Regards Pete

You are rather confused. FSUIPC has nothing whatsoever to do with any of your other DLLs. The DLL.XML file is processed by SimConnect, which is nothing to do with FSUIPC but is part of FSX. And you can see that the Mad Dog DLL has indeed been loaded by SimConnect, here: I'm afraid you are posting in the wrong place. Whichever of your programs is not working, please try ther own support. And send them the Log -- there may be an error reported later in the log when Mad Dog tries to create its menu entry. I can only really support my own programs. I do not own or use either Mad Dog or FSCopilot / FSInn. Regards Pete

How is your potentiometer connected? Can it be seen as an Axis is FS or FSUIPC's assignments? If so, just assign it and calibrate it. Anyway, rather than mess about trying to pre-scale it to write direct to the FS trim (0BC0), write the raw value itself directly to the 16-bit word at offset 3BBE. The value can then be seen in FSUIPC's axis assignments tab as one on a joystick, and you can assign and calibrate as normal. Regards Pete

I can only repeat my suggestions -- try different orders of loading, and check the SimConnect log -- there may well be an explanatory error message in there. Regards Pete

Those events are certainly being produced incessantly by an add-on, most likely the aircraft you have loaded. Try with a default aircraft. Some add-ons, notably PMDG, send lots of FS controls all of the time. I've no idea why, it seems quite wasteful. An alternative is to use the DontLogThese INI file parameter to stop the logging of those controls which are fuilling the log up. This parameter is described in the Advanced Users manual -- see page 10 or thereabouts. If the bug is operated as a standard FS feature it will be AP_ALT_VAR_INC (number 65892). But if it's an add-on doing its own thing for A/P it may not use FS controls at all. Regards Pete

You shouldn't really do both -- only one or the other. Autoassign does the assignment for you, that's what the "auto" bit stands for -- automatic. The place is the list is not relevant at all. The letter stays with the named device, and this is further controlled by the GUIDs which are unique. That's the whole point! No, it will work when the assignments are correct, and then it keeps them correct forever after. It is nothing to do with "first time". Obviously if they are all in a mess, then it would keep them safely in the same mess. Yes, of course, see above. That's the whole point! FSUIPC cannot guess what should be assigned to what, it believes what you told it. If you don't use the letters then it only has the numbers to go by, and as you see, Windows can change those. Regards Pete

Not sure why you post here, as this is nothing to do with FSUIPC -- neither of those programs use FSUIPC at all as far as I'm aware. Your XML.DLL looks fine. I can only think that there's some conflict between the MadDog DLL and FSCopilot. Maybe you can swap them over in the DLL so that FSCopilot loads before MadDog? Otherwise I think you need support from one or the other. You might want to get a SimConnect log file as this may help them work it out -- there's a thread in the FAQ subforum here which tells you how. Regards Pete