Pete Dowson

Okay. That's ggod. Not sure what that list is all about. I don't use any Goflight gear, but FSUIPC supports buttons and switches on most, if not all, GoFlight units provided only that the GoFlight 3rd party driver (GFdev.dll) supports it, and that dll is either installed in its "normal" place, or in with FSUIPC (or WideClient, from a client PC). All that is stated in the documentation. Okay. So all the preceding stuff was irrelevant now, just some sort of personal history? So, you've programmed a button to send the FSUIPC special added PM control called "PM AB THR TOGA" when pressed. Correct? I don't recall offhand exactly what this does (all the PM "controls" are merely offset manipulations derived from PM's documentation many tears ago -- so some may only work with certain, possibly old releases of PM. Unfortunately things don't stay the same very long). Anyway, I'll just look into the code and see what it does ... [LATER] Right. That control operates PM offset 541C bit 26. Checking the PM Documentation website, on http://www.projectmagenta.com/pmoffsets.html I see this: Airbus THR TOGA Bit 26 So, my added PM control name seems reasonably accurate -- AB = Airbus, TOGA = Toga, and still the correct bit according to the current PM documentation. I don't use an Airbus so I'm afraid i don't know if it actually works or not. That would be a matter for you to take up with PM. I really cannot support other folk's software at all. Sorry. Sorry, you'll need to explain all this. None of that is related to the control you assigned. 080C controls the FS TO/GA facility (see FS documentation). I don't know if that is operative for PM but I wouldn't have thought so. By 0X42 are you abbreviating 0x4F2? These aren't parameters, but offsets. Parameters would be values written to or operating on those offsets. would you give me please one example for that and to what does it refers, to the FSUIPC list, to the FSUIPC.ini ? Or just tell me the side number in the manual. Where do I have to fill in these strings? Run FS. Go to FSUIPC Options. Go to the Buttons tab, press your button, select assign to FS control, drop down the list and scroll down for the Offset controls. They all start with the letter 'O', oddly enough, so you can press the 'O' key to get closer faster. Select the Offset control you need, and you will get an edit possibility to enter the Offset and the Parameter for it. Do so. Offsets are in hexadecimal, precede the offset with an 'x'. The User guide does mention this -- a whole paragraph and some extra more advanced boxed texts. Search for "Offset controls" in the User Guide. It is in the Buttons (and Keys) sections, so if you had read this really you would have seen it. Regards Pete

Yes, if you mean disconnections of axis from control. No if you mean disconnection of FS Autopilot from the control. See offset 310A. (I hope you aren't being confused by the term "elevator trim" being used, as in FS, as opposed to "stabilizer trim"?). There are also disconnection facilities for aileron and rudder trims (see offset 04A0). Regards Pete

As I already replied privately, Look in the FSUIPC guide for Advanced Users. Again, part of the documentation supplied with FSUIPC. A complete list of added FSUIPC controls is given there, including the one which sends values to 04F2. It is called "PM MCP Kcodes (by Param)." Also, in general, you can write any value to any FSUIPC offset by using the appropriate Offset control, with the offset and parameters both entered. There are offset controls to set Byte (1 byte)), Word (2 byte) and Dword (4 byte) values, as well and set, clear or toggle individual bits, or increment or decrement values. They are all listed and you can find them all in the drop-downs in FSUIPC's options. PM offsets are documented by PM -- see their website, in the section called "Documentation". Have you looked at the relevant sections? I can answer specific questions if there are parts you don't understand, but I am not myself going to give you a personal tutorial. You have to be willing to do some of the work and thinking. I assume this is meant as a nasty jibe. Are you willing to do any work yourself? If not I expect you will be out of luck. Regards Pete

Well, that can be done but not easily. The facility to map 2 throttles to 4 engines assumes you may want asymmetric thrust at times (e.g. to assist in ground turns, or cope with an engine out or rudder failure), so the mapping goes 1->1+2, 2->3+4. A mapping as you suggest has got little practical value. How much more can it be "dumbed down" than the one little check box on the single Throttle calibration section saying "map to 4 throttles"? Doesn't that say it all? How many other words do you need? Regards Pete

A quick search on "engines" reveals offset 0AEC for the number of engines actually provided on the current aircraft, and the combustion flag in each of the engine details tells you if it is running. The flag for Engine 1 is at offset 0894, those for the others are in a similar position in their batch of values. You should try using search on the document with suitable words. For engine data always start by looking at the group of engine data values (152 bytes per engine) starting at 088C. Pete

Are they calibrated in FSUIPC? Do you by any chance have the "spike removal" options set in FSUIPC (on the Miscellaneous tab). They might be seeing extreme values and assuming they are invalid. (Mind you, they''d simply ignore them, not change them to zero). If neither, then it sounds like the controls are faulty. Test them with the attached Logitech program, DIVIEW. Only if you are assigning them in FSUIPC! They must be assigned to whatever you want them to do in one place OR the other, just not both! Evidently you aren't assigning then, then. They can't work if they aren't assigned to a function. I never suggested that CFG file was in your root directory. It's in your Document and Settings folder, under your log-on name, in the Application Data, Microsoft, FS9 folder. Please refer to general FAQs for FS in the FS2004 Forum. The FS CFG file for the version of FS you are using, of course. Every user of FS should always become familiar with that file, it is the common repository of everything you set in FS. Please check the general FS2004 Forum to learn more about FS2004. Don't mess with such files first. Before using anything to do with Joysticks in FSUIPC you really need to be reasonably confident that they work in FS using normal FS methods. FSUIPC cannot fix faults in hardware, so if they aren't working properly (as seen in FS) then you will only confuse you more and things will get worse. First, just see if they give correct repsonses in the attached program, which is actually by Logitech too. Regards Pete DIView.zip

FSUIPC4 will most certainly not be responsible for that alone. It acts as an interface for other programs, and one of those may be the cause. FSRealTime, for instance, could cause this to happen by adjusting the time. You have to get the parameters just right -- FS reloads everything is the time is adjusted by a minute or more, so you need to get this down to less. There is an option in FSUIPC4 which you may have set up incorrectly for your system. Look at the Miscellaneous options Tab. Check whether you have the "Keep FS Clock sync'd" option checked, and if so try a lower number of seconds -- 0 is the default, and that certainly doesn't change the minutes at all. This is actually noted in the documentation. If the option is not checked, then FSUIPC4 is most certainly not the responsible party and you need to see what is. Regards Pete

Ah, as it did here. It must scan the CFG and do something like assign the next "free" ID above the highest one it finds. Something like that. Strange that ApChart chose a different one in the first place then. Probably they already have a 10000 ID used. You might want to find that and see if the panel will still work okay with than changed. The double sending may, possibly, get the 2nd Window with the 10000 ID selected, but having any setting you make in FSUIPC options, whgich are saved in the INI file, is what I cannot understand -- there is no way a setting in the FSUIPC INI file will be erased unless it is in error. Something odd is going on there, as I said. Please, go into FSUIPC options, set it again, OK out of the options, and show me the buttons sections of the INI file as it is there and then. That isn't possible automatically, and if you did that each one would need a different name. Better to simply omit the ",10000" part in the Macro off, so making it take the parameter you give in the FSUIPC options "parameter" field. You'd then have to put 10000 in, instead of 0, for all the defaults, and whatever number is assigned for the others. Regards Pete

But they are not. Only the axis assignments are -- it should surely be obvious that assigning an axis for the same function in two places would likely cause conflicts. The same with buttons. If you assign a button in FS and the same button in FSUIPC, then that button will do two different things. Maybe that's what you want, but you obviously need to think about that. The same goes for axes. Why isn't that obvious even to a newcomer? Not only should this be rather obvious, but it is explicitly stated in one of the early paragraphs in the User Guide section on Axis Assignment, thus: IMPORTANT: Before making any assignments in FSUIPC4, you should be sure that the same axes are not being assigned in FS itself. Please do review this and reassess your opinion of my "shoddy" work! I really don't like unjustified accusations, simply because you haven't read even the introductory warnings and statements but plunged in wrecklessly. The FSUIPC joystick calibration features, however, are most certainly usable with assignments made anywhere. So your statement " the FSUIPC joystick features were a "or" and not an "and" when accompanied with FS' own joystick settings." is most certainly not true. That is also not true. I have no idea how you are getting that information. Provided axes are assigned in FSUIPC and are quiescent (i.e. not moved) then two sets can be simultaneously assigned to the same functions without the quiescent ones interfering. This is not with one set assigned in FS and the other in FSUIPC, because the values would then certainly not operate harmoniously. But multiple sets are often assigned in FSUIPC, even for use in the same aircraft -- one set for Pilot and the other for CoPilot. FSUIPC now even arbitrates between them, for maximum deflection, if they are assigned "direct to FSUIPC calibration" (this is a very recently added and documented feature). I really don't know what you mean by the part saying "a third required ...FSUIPC", but you are again wrong about the documentation. Every feature of FSUIPC is documented. You are apparently just choosing to ignore parts to make your points, it seems, though I hope not deliberately? Well, I'm sorry, but you are quite a rare specimen in this regard. I evidently cannot cater for all, and I most certainly cannot cater for those who choose to read some parts and ignore others. And regarding the differences between the two assignment methods, I feel it is explained quite clearly -- please review the several paragraphs explaining this. I think you must have skipped over those too! I feel I am quite justified in using harsher tones when wrongly accused by someone. I'm sorry you feel that is also "rude". It is never my attention to be rude, but I do feel that I am entitled to tell people off when they are in the wrong! Regards Pete

Have you tried the built-in steering controls FSX provides? They are called Steering Inc, Steering Dec and Steering Set -- the latter is the Axis version. If you cannot assign them in FSX itself, you certainly can in FSUIPC drop-downs. I don't know whether they affect the rudder position or not, but I'd hope not. Whether holding it fixed (i.e. keeping writing 0 to it, or possibly two alternate values close to the intended value) would prevent the rudder steering seems unlikely though, but worth a try. Regards Pete

No, there's no way to do this with FS9 or before, or in FSX with FSUIPC's steering tiller, as it uses the rudder to do the steering. There's only a separate control supplied by FSUIPC so you can calibrate it for greater movement in a shorter space, varying with speed and gradually moving to the real rudder assignment as speed increases. In FSX there is a steering tiller control added by Microsoft, and assignable (I think, never actually checked) in the FS assignments. If it isn't there it certainly should be found in the FSUIPC axis assignments drop down (for FS controls, not direct to FSUIPC). There's no FSUIPC calibration for this axis at present though, and I've never actually tried it to see if it moves the rudder surface -- it may still do in any case. For me, it doesn't actually matter whether the rudder surface moves or not because I tend to steer from inside the cockpit, and I cannot see the rudder from there! I can see it might be a nuisance if you are using FS as a radio-controlled aircraft simulator, though. ;-) Regards Pete

Which documentation? You really want the PM documentation rather than FSUIPC's. I did add some named PM controls, for the more usable actions, to FSUIPC, but in general PM is controlled according to their documentation, not mine. There are two distinct ways of controlling PM modules. One is via the keyboard, and the other is via PM offsets. They are both covered, separately, in PMs own documentation, available on-line. You should note, though, that some of the facilities are only available via keyboard, and some only via offsets. Both keyboard commands and offsets can, of course, be manipulated via FSUIPC. For Keyboard across WideFS you'd use the KeySend controls. For offsets you can use the pre-prepared PM controls added to FSUIPC, or the Offset controls where you explicitly specify the offset and the operation on that offset (value written, bits toggled, set or cleared). Some of the offsets actually send keyboard characters to PM modules, though i think this may be limited to the CDU. Regards Pete

I don't have any CH gear, but have you checked the "FSUIPC Guide for CH Users", in the sticky thread above? Faulty, you mean? Contact CH, they are reputed to be very good at fixing things for folks, parts, etc. Just getting FSUIPC doesn't do anything. You, the user, must have done something WITH FSUIPC to mess it up? FSUIPC cannot fix broken hardware, so don't try to use it for your broken units. Contact CH about those. If you've made a hash of settings in FSUIPC, simply delete the FSUIPC INI file, which you'l see in the FS Modules folder. Do this before running FS, then, when you run FS FSUIPC won't do anything at all with your yoke or pedals. If the numbers from the units change a lot all on their own, without you touching them, either they are faulty, or your USB ports or motherboard are. I attach a program from Logitech called "DIVIEW". Just run that and watch what your units are doing. You can select what to display in Edit-settings. Regards Pete DIView.zip

Not a waste. Vista is a bit of a pain, it catches us all out now and then. I've constantly beleaguered by it eve though I've switched UAC and most other things I can find off. Grr! Regards Pete

Understood. :roll: Well it still worries me a little that you may not be seeing the full example for the 737-400 in the manual, and so follow it and get the exact same displays. That's all you need to do if you weren't sure. If following that exactly doesn't work then something is very wrong somewhere. Regards Pete

Please read the Installation instructions in the User Guide more carefully. In particular note the special paragraph for Windows Vista (yes, in red and emboldened so you can't miss it! :-( ) which tells you you must run FS "as Administrator" for registration purposes. Being an Administrator is not enough. Vista has an "elevated Administrator" level which is needed. It is automatically given to Installers, but not ordinary programs. This is why the emphasised section, which is supposed to be unmissable, is in the documentation. Only because I have moved the Registration to the Installer, which has sufficient privileges. Regards Pete

The INI file [Axes...] and [Joystick...] sections would have been ar more informative. Pictures don't really help, and I'm certainly not interested in watching YouTube videos. Sorry. You took your Throttle as the first example. You say: but in the pictures immediately following you show that you calibrated the "Throttle", yet assigned the axis to Throttles 1, 2, 3 and 4 independently. There are 5 (FIVE) throttle controls in FS -- one generic throttle which controls all engines (just called "throttle"), and separate ones for those with separate levers. This isn't anything to do with FSUIPC, it is how FS has always been! The same 5 throttle controls are also listed in FS's assignments list, so there's really no excuse just because you are using FSUIPC! You have assigned, inexplicably, your single throttle to all 4 separate throttles, but then calibrated the one you've not assigned to! I've no idea how you've managed to do the latter as the single throttle won't respond to the individual controls -- it does rather imply that you couldn't have disabled it in FS after all! If you look in FSUIPC options, further in the pages for calibration (I think, from memory, it's oage 3), you'd find the 4 throttle calibration page which you would use instead when assigning 4 separate throttles! But why, with a single throttle, are you assigning to multiple throttles in the first place? Just assign it to the Throttle, not Throttle 1, 2,3 or 4! It's called 2Axs Throttle Set" if you assign it to FS, but just 2Throttle" if you assign it direct to FSUIPC calibration. Really, I cannot help more until you provide proper information, technical information which is definitive, not pictures and videos. If you show me the sections of the INI file, I can tell you what sort of mess you've made. But it looks as if, despite Microsoft's efforts at documentation and making things easy, and mine in FSUIPC, you manage to misunderstand what Microsoft are doing and therefore what FSUIPC can do and does. I hope it may become clearer now, but if not then maybe you need to take it slower and not be so ambitious? I think the best thing for you to do at this time is delete your FSUIPC INI file and start all over again. If you want to use FSUIPC for axes and buttons entirely instead of FS assignments, don't disable individual axes and buttons in FS, disable the entire range of controls -- I'm sure there's a separate checkbox for that. Do it for every one. Then you'll at least know that FS own assignments cannot be interfering. Your description of the problems are exactly describing what would happen with multiple assignments to the same simulation control. Take each axis, one at a time, and THINK what you are going to do with it. Don't barge in assigning left right and centre without thinking, as it appears here. Look at the list. For throttles, can you not see there's a difference between "Throttle" and "Throttle 1, 2, 3 and 4"? Do you not wonder why? Take a moment to think about it. What do folks with one throttle lever use? How does the keystroke for throttle manage to change it for all 4 engines? Because there's a generic all-engine throttle, that's why! If you use that, you calibrate that. If you use separate throttles, you calibrate those -- they are separate and on a separate page in FSUIPC's options. Regards Pete

Just one more (possibly impolite?) question for you, whilst I'm here. When you first wrote you said: Now, I assumed you were OK'ing out of the Buttons or Keys dialogue BEFORE the bit about making some clicks. Is that correct? If not, if you are simply leaving the dialogue showing and clicking on the panel, then it most certainly won't work. The dialogues are Modal, nothing else is running in FS when they are showing. It does clearly tell you to press OK in the documentation. For additional clarification, and possibly the reason for my additional (apparently impolite) responses, you then said: which really is insulting me, as the very B737 you ask about is the one given as a lengthy example, with pictures, in the documentation. If, as you say, you have read this, why have you not noticed that? Please do explain how you arrive at me being impoliteit still hurts! :( :( :( Pete

Sorry, I try to be helpful, and respond to the question I think you are asking. As I said, then, please use the documented examplethe one explicitly for the very 737-400 you asked about, and the one for which the pictures in the document were generated. Surely that will tell you? Why did you ask me about trying it on the 737-400 if you've already read that? Why not try exactly what it says first? Excuse me, but what was not polite about anything I've said? Please explain that hurtful remark, as you obviously speak a different language to me and I cannot see it is anyway impolite in English. :-( Pete

Why would you think it might not be working okay? Do you think I release and document facilities in a non-working state? Has my software got such a bad reputation? :-( Please do read the section in the User Guide. For the default 737-400 it certainly works on the two functions it says it works on in that section -- the 737-400 is the example actually used, so why not follow it? They are the only ones I know on in that panel which don't have a normal FS control (and so don't need a Mouse Macro in any case) and which work in a way a mouse macro can use. None of the EFIS ND options will, they are all internal. In general the facility is not of a great deal of use on any default aircraft, though when I was developing it I had hoped otherwise. Most Microsoft-made panels use internals which aren't hookable. The main use is for add-on panels made using the Microsoft C/C++ panel-making toolkit, as those all follow a simple logical structure which the facility can trap and emulate. Pretty much all of the Level D and PMDG panels are amenable, for example. Regards Pete

Strange. The Toggle control should show it on one use, hide it on the next, so if you send it twice it should self-cancel. Are you sure you haven't got "Repeat" enabled? Maybe you are now sending it three times? Enable Button and Event logging (in the Logging tab), then use it once and check the Log, see what is happening. You must "OK" out of the FSUIPC options, not Cancel or press ESCape. Changes are written to the INI file at that time. Check the INI file. It sounds like you programmed it with "Aircraft Specific" set and the wrong aircraft loaded. You shouldn't need any of those ApChart macros programmed "aircraft specific" as if it used 10012 for one aircraft it probably used it for all (check another to be sure). What do you mean "both parameter boxes"? There is only one parameter entry field for each control -- there are separate places for control sent on "Press" and "Release". Each control can have ONE parameter. Where are you seeing more? See the pictures in the documentation? Don't they match? In any case, with this Macro the parameter for the Toggle Panel control is in the Macro itself -- you don't supply a parameter with the control you program on the button, so that can be left to the default (0). If you want a macro to take a parameter you have to omit it (and its comma) in the macro definition. Maybe if you are getting this confused you'd better let me see the [buttons...] sections in the INI file! Regards Pete

What is this "patch" you are talking about? I have never provided a "patch". You said you downloaded FSUIPC4 version 4.30. You never mentioned whether you installed it, but I assumed so. If you installed FSUIPC4 into FSX it must be in the Modules folder of FSX. Do you actually manage to run FSX from a memory stick? Anyway, if you delete it, then it is deleted. You cannot delete it and have it still present -- that means you did not delete it after all! Maybe you need to explain what you mean by "patch". It sounds like you are mixing my software up with something completely different. Pete

The window will only appear if you click on something which can be trapped as a gauge "hotspot", one which does something, and even then only if that hotspot is processed in a Gauge -- some are processed directly by the PANELS DLL of FS, and those cannot be used this way. Regards Pete

You didn't say that. Evidently you aren't actually assigning them in FSUIPC then. Are you assigning them to FS controls or using the "Direct to FSUIPC calibration" option? If you use the latter then you MUST calibrate in FSUIPC as well. In the former case that is optional. Never ever assign things in two places. You are asking for trouble. No idea, sorry. You'll have to tell me exactly what you are doing, step by step. I don't know anyone else who can't assign axes in FSUIPC. It is a much used facility, and documented with pictures as well! Sorry, but I produce the best documentation I know how. If I could do better don't you think I would have, rather than have to repeat something different here? Please tell me what you are doing. I really cannot imagine how you could do it wrongly. It is very very hard to do it wrongly! Pete

None of those are simulated by FS9 or before. For FSX there's a single hydraulic switch at offset 341E as listed. Why are you reading the entire list? Try using simple word searches. Pete