Pete Dowson

There isn't a "free version" and a separate "full version". All you do to "convert" it is buy the registration key and re-run the installer in order to enter the details. That's it. Don't delete anything, just run the installer again and register. Pete

It sounds very like you have the buttons assigned for that aircraft, or generally but the axes assigned only for another aircraft using Profiles. Best show me your FSUIPC4.INI file (paste it her) and tell me which aircraft you were flying -- or show me the Log too so I can see. Remember that axes and calibrations apply either generally, if programmed that way, OR specifically, but never both. Whereas with buttons and keys presses both can be applied, with the specific assignments simply overriding the general ones when they overlap. Pete

There's an art in trying to get projects set correctly in Microsoft C. You need to make declarations for the libraries you are using. there's all sorts of arcane magic to getting things correct. If you are a beginning programmer, then C is really not a good choice. You might want to consider Visual Basic and Paul Henty's easy-to-use .Net DLL -- see the subforum about this. Just use the ANY option. The Header file defines the options, though it might be out of date for FSX and P3D. The current Programming and Offsets guides are the best references. I'm afraid than in the last few years much more attention has been afforded to the Lua plug-in facilities, and these are generally so much easier for new programmers and experimenters. Even though i do write fluently in C I still use Lua for many things, or for prototyping something i later code in C. No. Access through the interface is free (except for commercial purposes). Pete

All versions of FSUIPC4 have always provided the registration option in the Installer. Only early versions of FSUIPC3 (for FS9) had registration done inside FS. There is no such message from FSUIPC -- that must be from the application you are using. If the application program you are using says it needs a Registered version of FSUIPC, then you fix it by purchasing a Key and registering. As Luke says, the log shows that everything is good as far as FSUIPC is concerned. The folks who may know why your ACARS program isn't working will be their support. Maybe they changed it in some way so it now needs a registered FSUIPC? Pete

You most certainly have another assignment to the same button, maybe in FSUIPC but more likely in FS, Ezdok and/or Opus. If you enable Button and Event logging in FSUIPC then operate the control and check the FSUIPC4.LOG file you will see the two controls being sent from the one button press. If you like, paste the log into a message here and I will explain it to you. Pete

There's a list of all of the controls accessible to FSUIPC in your FSUIPC Documents folder. I don't really know what is meant by all of your wording above so I'm not sure i can be specific. For instance, what is meant by " but no for the 2 (When I Switch in the GPS between NAV/COM)"? Do you mean COM2 and NAV2? Because there are controls for those too. I expect that those actions you list which are purely local to the GPS rather than active in the FS avionics system won't have their own controls, being handled internally to the gauge. I don't know, but I wouldn't be surprised if this applied to On/Off, Cursor On/Off and the V and C, whatever they are. One way to detect the control names/numbers in use is to enable Event logging in FSUIPC and operate the unit with a mouse. If you temporarily run FS/P3D in Windowed mode you can enable the Console Log option too and see what happens in real time. It is sometimes possible to drive internal gauge functions with local panel variables, or "L:Vars". You can log the Lvars using an assignable FSUIPC control, or the sample Lua plug-in for this. Lua variables can be written to by Macros assigned to buttons or keys. Pete

You seem to have posted this twice! See other copy. Pete

I don't know Java at all, but if you can write to FSUIPC offsets from Java then just use the offset 3380 to write the text, then 32FA to get it displayed. Please refer to the offsets list provided in the SDK (and also in your FSUIPC Documents subfolder). Pete

HID devices aren't necessarily listed in the Log file. Why should they be? So, is the problem not specifically anything to do with HID, but only that no Lua files placed in the P3D modules folder are recognised -- ie not listed in the [LuaFiles] section of the FSUIPC4.INI file? In what way "logged"? FSUIPC does not log all HID devices. My HidScanner program does. Can you explain what you mean there please? Pete

There's no way FSUIPC can stop another SimConnect user using SimConnect to load a flight plan into FS. I've never heard of any problem with EFB like this -- it sounds very weird. I assume you have asked on the EFB support forum? I use EFB all the time, but I load the flight plan into both EFB and FSX from the same source -- PFPX. Works very well. Pete

Nothing in software can really cure jitter, though it can be smoothed somewhat using the Filter ("F") option in the calibration. It is normally caused by poor power or dirty or worn pots in the controls. Larger movements would more likely be down to bad connection, bad wiring, or interference with other assigned controls. The Filter option will slow down responsiveness somewhat -- an unfortunately side-effect of any smoothing. Except with something like the digital thrust control in Airbuses, It is quite normal in real aircraft for throttles not to be exactly aligned for the same power settings. However, if you really want them lined up to save effort, you could use the sync options provided in FSUIPC's calibration for exactly this purpose. With this you choose a number of points along their movement to line up to, so that the calibration is done to a matching "curve" (series of straight interpolations really). Regards Pete

I've not heard of anything like any of the problems you mention. In particular the dialogue asking you if you want to register of not is a standard Windows dialog and it cannot close until you click one of the buttons. So having it disappearing without any action whatever on your part is extremely weird. Also if there is a Modules folder it will have been actually created by FSUIPC4's installer at the time it copied the files, so I simply cannot imagine how an empty modules folder can arise. I'm wondering if you are looking in the wrong place. Please show me the FSUIPC4 Install log file. You can paste it into a message here. If you can't find it, just make sure to save a copy somewhere you CAN find it, using the File menu for this in the display. Pete

These weird parameter values are just single bits and much more conveniently expressed in hexadecimal. -2147483648 is just x80000000 (you can enter it either way). FSUIPC does actually allow ALL negative numbers up to -2147483648. There looks to be just a display problem with that one number (which now I've noted I'll fix in due course), but you will find that it is stored in the INI file correctly and should certainly work okay. -- it does here. Just enable Button and Event logging options and see for yourself. Regards Pete

Something is wrong then. Please show me your FSUIPC4 Install log (from the P3D modules folder). You can paste it into a reply here. Pete

Please refer to the FSUIPC documentation, and in particular the boxed section about this in the Axis Assignments chapter. As you will read, provided both Rudder and Steering are calibrated in FSUIPC, all that is already taken care of. Pete

Nice contribution! Thanks. Just a few typos needed correcting, so I've done that for you. There lines in the explanation: won't work because the a in 'and' needs capitalising. Unfortunately I couldn't be consistent with those logic functions "And" and "Or" because, with all lower case, they are of course Lua reserved works. Best Regards Pete

Well they may well have key press or control access to their buttons, or maybe Mouse Macros may work -- they do on a lot of newer add-on aircraft. But I'm afraid I cannot advise about third party aircraft. They are all different, and most of the more sophisticated ones do their own thing in most departments. You may do better asking around in their own support forums. Pete

Do you mean the default Cessna 172 in FSX? I can't see a way except by mouse. I tried applying FSUIPC's mouse macros to it, to no avail -- all attempts cause an "exception", meaning the MS code isn't suitable for direct calls. And there are no L:Vars used by it. So ... no way. You might want to consider an add-on aircraft instead? But check they do what you want first. Pete

Claudio, Can you try FSUIPC 4.934, please? I think your problem might be the same as one reported separately which is now fixed. it applies only to Lua plug-ins loaded by a non-profile specific [Auto] section in the FSUIPC INI file. I'll check back with you after my holiday. Regards Pete

There aren't any. Microsoft programmed the clock as a function completely local to the gauge code. Pete

No, not yet. From Saturday. The latest version is 4.933, not 4.931 as in your title. I haven't sufficient information from the other report, and although I've seen the Lua script he is using it is far too complex for me to understand what is going on. Perhaps yours is simpler and will enable me to determine what the problem might be? If so I'd love to look at it please, so I can see what might be the problem. If you are quick maybe I can fix this before I go away? I don't like having things to worry about when on holiday. :-( Could you therefore do these things, please, ASAP? 1.In FSUIPC's logging tab, enable the Lua debug/trace options. Then close down FS. 2.Reload FS and do the shortest test possible which shows the problem. Close down FS. 3.ZIP up the FSUIPC4 log file and your Lua plug in, and send them to me at petedowson@btconnect.com with a brief explanation of what you did and what you expected which didn't work. I've made no changes which should affect any existing Lua plug-in that I know of, so if there is a problem it must be something accidental. i need to know where to start looking, at least. I use a lot of Lua plug-ins for all sorts of things, and i've not found any which don't work with 4.933. Regards Pete

Sorry, I'm not the person to ask I'm afraid. I don't even have any PMDG aircraft installed for FSX -- I used to use their FS9 737. You need PMDG support forum really, it is their aircraft and their list of controls. All FSUIPC is doing is making an easy way for you to send these controls. If you've used others in their list and they work, then this proves you know how to do it. You can just check, in FSUIPC, that you are actually causing the correct control to be sent. Enable Event logging in the Logging tab, and check that the log does show that you are sending the correct control value. Regards Pete

Leo Bodnar has one in his catalogue. See http://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=210. However, it says 'sold out' at present. Maybe he can point you to other sources? I've thought of one source. Buy a cheap joystick with a hat and take it out. It might actually work out cheaper than buying the switch separately! Pete

Well, I'm pleased for you, but i must clarify some points here, mainly for the benefit of others who may read this thread. First of all there's no way a WideClient can connect to a different server if the ServerIPAddr or ServerName parameters and a Protocol parameter are correctly provided and actually seen in the INI file at the time WideClient is started. This is because it then ignores the Server ID broadcasts, the little once-per-second messages sent to all PCs in the workgroup which identify the Server name, IP address and preferred protocol. Second, the only use of the Client name list in the FSUIPC INI file is to enable button inputs to the Server from joystick or other devices on clients to be uniquely identified for assignment purposes. There is no other use for them, and the Server only knows about them when a client succeeds in connecting and then sending its Name. The names are NEVER used by the Server to contact clients. There's just no way the protocol allows server-initiated connections. The client list in my own INI files on the assorted PCs I have are very long indeed, actually featuring PCs I no longer have or ones which rarely connect. But every client can always be directed to a specific server, should this be what I want. Regards Pete

Yes, but the automatic linking of the Client to the Server is based on seeing something to connect to. It seems pretty obvious, doesn't it, that if you need to direct a specific client to a specific server some additional action is needed. how else can it know which of multiple servers is the one you want it to deal with? That's all this is about. No, don't be like that. I'm sorry if I've put you off answering questions -- it was just the thought of you searching all the way through the Forum for a solution rather than look at the manual seemed, er, a bit odd. That was all. And in this case you don't actually have to read all of the manual, only look up the bit about configuring the network I mentioned. It will tell you the format of the parameter you need in each WideClient.INI file. I always try to answer questions properly, even if it is by reference to the manuals. I can't help emphasising documentation -- it is, for me, the worst part of developing software and so, having done it, it is a little frustrating when folks don't use it! ;-) Regards Pete