Pete Dowson

Really? Why did they display like that then? No, of course not. As I said, the file is corrupted, presumably by those "spaces" you mention (are you sure they aren't nulls, i.e. x00, not spaces, x20?).**** You need to delete lines 2= and 5= and make those macros again. Sorry, but I cannot speculate on how your file has become corrupted. Did FS possibly crash some time? And what version of FSUIPC are you using? ****[LATER] Actually those characters are x01, a non-printable ASCII control character. How they got into your file is unknown, maybe a disk glitch or memory problem? Regards Pete

Well, you have some odd errors, looking like corruption: 2=OH_APU_BATSW_OFFOH_APU_MAST_OFF=RX6a3f0*X83cc 5=OH_APU_MAST_STRTOH_APU_L_BUS=RX69f80*X81cc 8=OH_APU_EXPWR_LBUOH_APU_EXPWR_RBUOH_APU_EXPWR_LBUOH_AC_BUS_X_TIE=RX69ec0*X8b00 9=OH_APU_EXPWR_RBUOH_APU_EXPWR_LBUOH_AC_BUS_X_TIE=RX69ec0*X8b00 What ARE those characters which appear as weird graphics here? Seems you've got a corrupted file. Regards Pete

Either your key (or name/email detail) is invalid, or more likely the date on your PC has reset and is now earlier than your key purchase, making it look invalid. Pete

The parameter field is used for data to be sent along with the control being used. Most controls do not use a parameter, but those ending in "Set" do, as well as some others. I cannot tell you a general answer, you must say what you want to do, what control it is you want to use. There are clear examples in the FSUIPC user guide. Look in the section on Button Programming, starting with the paragraph which begins "Most if not all of those with the word “set” in their name are controls that take a parameter." Pete

Well there's no such thing as "old versions" of Keys. FSUIPC3 (which is for FS98, FS2000, CFS1, CFS2 and FS2002 as well as FS9/FS2004) is current and updated regularly just as FSUIPC4 (for FSX and ESP) is. They are two separate, but live, products. But, yes, you have two FSUIPC3 keys at present, and not one for FSUIPC4. Doesn't your receipt show this? You do not purchase a specific version of FSUIPC4. You already downloaded 4.60a (there is a later version in the Updates Announcement if you are interested). But for the key purchase, yes, unless you can persuade SimMarket that it was an honest error on your part and see if they will replace it for you. Raise a problem ticket there. Regards Pete

What's is an "operational" position for ailerons? Surely all positions are "operational"? Which would not be used? If you really mean that the FS ailerons are not in the position corresponding to the yoke or joystick position (presumably centred), it could simply mean that your start-up situation, the one loaded by FS when it starts, has been saved with the ailerons off-centre. Neither FS nor FSUIPC will send new values UNTIL the control is moved -- and in the case of FSUIPC, moved several times to avoid setting spurious values from an asleep controller. Alternatively, it could simply mean that the driver is returning that incorrect 'spurious' position. Possibly the device is asleep when you first start up. Check that the Windows power management on the USB devices (the hubs in the Settings - System - Device Manager) is disabled. Windows tends to enable that by default, to save power. "Re-calibration" does nothing but reassert the same values again in the INI file. The problem will either be FS's initial settings, or the inputs being seen. But surely it should really not matter in any case? As a routine check when getting into any aircraft you should check ALL of the controls out -- move them all, see that they all move the relevant control surfaces. It is a good habit to get into, believe me! ;-) Regards Pete

You paid for FSUIPC4, not a specific version "4.46", which is in any case out of date, unsupported, and won't work with Keys purchased in 2010. It isn't included in the purchase. For efficiency in operation the WideServer.DLL component of WideFS, which used to be separate, in built into the FSUIPC4 code. I have on record two purchases by you, both for FSUIPC3. The first was on 30th April 2007 (order #332840) and the second on 3rd July 2010 (order #634931). It seems you have made a mistake in your purchase! FSUIPC3 keys will certainly never work in FSUIPC4. Didn't you read the page you purchased from or check your receipt? Regards Pete

No, that's the FSUIPC4 installer log. In the same folder there should be a file "FSUIPC4.LOG". That will show the run-time situation of FSUIPC. One thing first though. Are you using a paid-for registered FSUIPC4? If so please check that your windows system date is correct. Secondly, when in FSX flight mode is there a menu item, right-most, called "Add-Ons"? If so, see if FSUIPC is listed there. Regards Pete

You must be running an old unsupported version of FSUIPC because since the last message in this thread (November 2009) the problem has been fixed. The oldest supported versions of FSUIPC are 3.98 (for FS9 and before) and 4.60 (for FSX and ESP). There are also updates to these in the Updates Announcement above. Please update. Regards Pete

You've evidently not read the thread you are appending to nor even its title, as the problem here is a connection between PCs on a network. You mention no network nor WideFS, so how is it "similar"? It is simply not possible for software to work one time and with no change whatsoever, in software or hardware, not work again. Something has changed. But you provide no information so I cannot tell. Are you running on a Network or not? If you are, is WideFS connecting? What does the title bar in WideClient say? I need to see the WideClient and WideServer Log files -- the WideClient one is in the folder in which you placed WideClient. The WideServer one is in the FSX Modules folder. Either way, WideFS use or not, I also need to see the FSUIPC4 log file -- you'll find this in the FSX Modules folder too. Close FSX first. PS: if you wouldn't mind e-mailing me instead of this forum, i would much appreciate it. I understand e-mail and find it easier to navigate through e-mial a lot more But it helps no one else to keep things private, and it makes much more work for me as a consequence. You only have to deal with me, I have to deal with thousands or users. I'll send you a link to this reply. That's the most I am going to do via email unless things need to be confidential. I hope you understand. Regards Pete

This is patently not true, as shown in the log you supplied. It even shows what joystick/button numbers they generate. I think you are seriously misunderstanding something. Does the M-Panel initialise? It runs through a title display when SerialFP2 initialises it. It appears to be okay, but if it is still waiting with a dialogue awaiting your confirmation, you should certainly confirm it. You have something wrong in the command line for it in that case. Check it and correct it. In the previous log you provided it all worked fine. (And I see too, in the new one). Why? There was nothing wrong with it, except for the fact that you've assigned nothing to the Buttons which were shown to be recognised in your Log -- i.e. all these on "joystick 260": [From your earlier log] 231875 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 233625 VRI COM5 ---> FUNAPMOD [from Device] 233625 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 234141 VRI COM5 ---> FUNRADIO [from Device] 234141 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 234813 VRI COM5 ---> FUNRADIO [from Device] 234813 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 238922 VRI COM5 ---> GEAUP [from Device] 238922 VRI command GEAUP trapped as Joy 260 Btn 5 Toggle 239313 VRI COM5 ---> GEADN [from Device] 239313 VRI command GEADN trapped as Joy 260 Btn 6 Toggle 300297 VRI COM5 ---> FUNRADIO [from Device] 300297 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 300891 VRI COM5 ---> FUNAPMOD [from Device] 300891 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 302532 VRI COM5 ---> FUNAPCTL [from Device] 302532 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 303641 VRI COM5 ---> FUNUSR [from Device] 303641 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 304500 VRI COM5 ---> FUNAPCTL [from Device] 304500 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 305282 VRI COM5 ---> FUNAPCTL [from Device] 305282 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 306016 VRI COM5 ---> FUNUSR [from Device] 306016 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 307219 VRI COM5 ---> FLPDEC [from Device] 307219 VRI command FLPDEC trapped as Joy 260 Btn 7 Toggle 307750 VRI COM5 ---> FLPINC [from Device] 307750 VRI command FLPINC trapped as Joy 260 Btn 8 Toggle 451657 VRI COM5 ---> FUNRADIO [from Device] 451657 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 453313 VRI COM5 ---> FUNAPMOD [from Device] 453313 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 453953 VRI COM5 ---> FUNUSR [from Device] 453953 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 454938 VRI COM5 ---> FUNAPCTL [from Device] 454938 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 455688 VRI COM5 ---> FUNUSR [from Device] 455688 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 456672 VRI COM5 ---> FUNAPCTL [from Device] 456672 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 467110 VRI COM5 ---> FUNAPMOD [from Device] 467110 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 468891 VRI COM5 ---> FUNRADIO [from Device] 468891 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 469594 VRI COM5 ---> FUNUSR [from Device] 469594 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 470313 VRI COM5 ---> FUNAPMOD [from Device] 470313 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 518516 VRI COM5 ---> FUNUSR [from Device] 518516 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 523016 VRI COM5 ---> FUNRADIO [from Device] 523016 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 524532 VRI COM5 ---> FUNAPMOD [from Device] 524532 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 524938 VRI COM5 ---> FUNRADIO [from Device] 524938 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 657297 VRI COM5 ---> FUNRADIO [from Device] 657297 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 658922 VRI COM5 ---> FUNRADIO [from Device] 658922 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 660782 VRI COM5 ---> FUNRADIO [from Device] 660782 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 661032 VRI COM5 ---> FUNRADIO [from Device] 661032 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 662188 VRI COM5 ---> FUNRADIO [from Device] 662188 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 663328 VRI COM5 ---> FUNRADIO [from Device] 663328 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 664297 VRI COM5 ---> FUNAPCTL [from Device] 664297 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 667391 VRI COM5 ---> FUNUSR [from Device] 667391 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 668453 VRI COM5 ---> FUNAPCTL [from Device] 668453 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 669250 VRI COM5 ---> FUNRADIO [from Device] 669250 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 671016 VRI COM5 ---> FUNAPMOD [from Device] 671016 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 672563 VRI COM5 ---> FUNAPMOD [from Device] 672563 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 673266 VRI COM5 ---> FUNAPCTL [from Device] 673266 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 674235 VRI COM5 ---> FUNUSR [from Device] 674235 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 675125 VRI COM5 ---> FUNUSR [from Device] 675125 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 675719 VRI COM5 ---> FUNAPCTL [from Device] 675719 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 676813 VRI COM5 ---> FUNUSR [from Device] 676813 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 677375 VRI COM5 ---> FUNUSR [from Device] 677375 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 678688 VRI COM5 ---> FUNAPMOD [from Device] 678688 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 679297 VRI COM5 ---> FUNAPCTL [from Device] 679297 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 679735 VRI COM5 ---> FUNRADIO [from Device] 679735 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 680172 VRI COM5 ---> FUNRADIO [from Device] 680172 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 695516 VRI COM5 ---> GEAUP [from Device] 695516 VRI command GEAUP trapped as Joy 260 Btn 5 Toggle 695797 VRI COM5 ---> GEADN [from Device] 695797 VRI command GEADN trapped as Joy 260 Btn 6 Toggle 714250 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 719000 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 752922 VRI COM5 ---> FUNRADIO [from Device] 752922 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 753157 VRI COM5 ---> FUNRADIO [from Device] 753157 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 754141 VRI COM5 ---> FUNAPMOD [from Device] 754141 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 754860 VRI COM5 ---> FUNUSR [from Device] 754860 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 755797 VRI COM5 ---> FUNAPCTL [from Device] 755797 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 756344 VRI COM5 ---> FUNAPCTL [from Device] 756344 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 756875 VRI COM5 ---> FUNUSR [from Device] 756875 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 757938 VRI COM5 ---> FUNAPMOD [from Device] 757938 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 758453 VRI COM5 ---> FUNRADIO [from Device] 758453 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 758875 VRI COM5 ---> FUNRADIO [from Device] 758875 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle ... Yes, and the same recognition, again: 231875 VRI COM5 ---> FUNRADIO [from Device] 231875 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 233625 VRI COM5 ---> FUNAPMOD [from Device] 233625 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 234141 VRI COM5 ---> FUNRADIO [from Device] 234141 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 234813 VRI COM5 ---> FUNRADIO [from Device] 234813 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 238922 VRI COM5 ---> GEAUP [from Device] 238922 VRI command GEAUP trapped as Joy 260 Btn 5 Toggle 239313 VRI COM5 ---> GEADN [from Device] 239313 VRI command GEADN trapped as Joy 260 Btn 6 Toggle 300297 VRI COM5 ---> FUNRADIO [from Device] 300297 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 300891 VRI COM5 ---> FUNAPMOD [from Device] 300891 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 302532 VRI COM5 ---> FUNAPCTL [from Device] 302532 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 303641 VRI COM5 ---> FUNUSR [from Device] 303641 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 304500 VRI COM5 ---> FUNAPCTL [from Device] 304500 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 305282 VRI COM5 ---> FUNAPCTL [from Device] 305282 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 306016 VRI COM5 ---> FUNUSR [from Device] 306016 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 307219 VRI COM5 ---> FLPDEC [from Device] 307219 VRI command FLPDEC trapped as Joy 260 Btn 7 Toggle 307750 VRI COM5 ---> FLPINC [from Device] 307750 VRI command FLPINC trapped as Joy 260 Btn 8 Toggle 451657 VRI COM5 ---> FUNRADIO [from Device] 451657 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 453313 VRI COM5 ---> FUNAPMOD [from Device] 453313 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 453953 VRI COM5 ---> FUNUSR [from Device] 453953 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 454938 VRI COM5 ---> FUNAPCTL [from Device] 454938 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 455688 VRI COM5 ---> FUNUSR [from Device] 455688 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 456672 VRI COM5 ---> FUNAPCTL [from Device] 456672 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 467110 VRI COM5 ---> FUNAPMOD [from Device] 467110 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 468891 VRI COM5 ---> FUNRADIO [from Device] 468891 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 469594 VRI COM5 ---> FUNUSR [from Device] 469594 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 470313 VRI COM5 ---> FUNAPMOD [from Device] 470313 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 518516 VRI COM5 ---> FUNUSR [from Device] 518516 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 523016 VRI COM5 ---> FUNRADIO [from Device] 523016 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 524532 VRI COM5 ---> FUNAPMOD [from Device] 524532 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 524938 VRI COM5 ---> FUNRADIO [from Device] 524938 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 657297 VRI COM5 ---> FUNRADIO [from Device] 657297 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 658922 VRI COM5 ---> FUNRADIO [from Device] 658922 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 660782 VRI COM5 ---> FUNRADIO [from Device] 660782 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 661032 VRI COM5 ---> FUNRADIO [from Device] 661032 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 662188 VRI COM5 ---> FUNRADIO [from Device] 662188 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 663328 VRI COM5 ---> FUNRADIO [from Device] 663328 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 664297 VRI COM5 ---> FUNAPCTL [from Device] 664297 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 667391 VRI COM5 ---> FUNUSR [from Device] 667391 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 668453 VRI COM5 ---> FUNAPCTL [from Device] 668453 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 669250 VRI COM5 ---> FUNRADIO [from Device] 669250 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 671016 VRI COM5 ---> FUNAPMOD [from Device] 671016 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 672563 VRI COM5 ---> FUNAPMOD [from Device] 672563 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 673266 VRI COM5 ---> FUNAPCTL [from Device] 673266 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 674235 VRI COM5 ---> FUNUSR [from Device] 674235 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 675125 VRI COM5 ---> FUNUSR [from Device] 675125 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 675719 VRI COM5 ---> FUNAPCTL [from Device] 675719 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 676813 VRI COM5 ---> FUNUSR [from Device] 676813 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 677375 VRI COM5 ---> FUNUSR [from Device] 677375 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 678688 VRI COM5 ---> FUNAPMOD [from Device] 678688 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 679297 VRI COM5 ---> FUNAPCTL [from Device] 679297 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 679735 VRI COM5 ---> FUNRADIO [from Device] 679735 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 680172 VRI COM5 ---> FUNRADIO [from Device] 680172 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 695516 VRI COM5 ---> GEAUP [from Device] 695516 VRI command GEAUP trapped as Joy 260 Btn 5 Toggle 695797 VRI COM5 ---> GEADN [from Device] 695797 VRI command GEADN trapped as Joy 260 Btn 6 Toggle 714250 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 719000 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 752922 VRI COM5 ---> FUNRADIO [from Device] 752922 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 753157 VRI COM5 ---> FUNRADIO [from Device] 753157 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 754141 VRI COM5 ---> FUNAPMOD [from Device] 754141 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 754860 VRI COM5 ---> FUNUSR [from Device] 754860 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 755797 VRI COM5 ---> FUNAPCTL [from Device] 755797 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 756344 VRI COM5 ---> FUNAPCTL [from Device] 756344 VRI command FUNAPCTL trapped as Joy 260 Btn 0 Toggle 756875 VRI COM5 ---> FUNUSR [from Device] 756875 VRI command FUNUSR trapped as Joy 260 Btn 2 Toggle 757938 VRI COM5 ---> FUNAPMOD [from Device] 757938 VRI command FUNAPMOD trapped as Joy 260 Btn 1 Toggle 758453 VRI COM5 ---> FUNRADIO [from Device] 758453 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle 758875 VRI COM5 ---> FUNRADIO [from Device] 758875 VRI command FUNRADIO trapped as Joy 260 Btn 3 Toggle It is all working perfectly, exactly as planned. You can clearly see that all the buttons you pressed are recognised and intercepted with assigned button numbers, as well as the Flaps inc/dec and the Gear Up/down buttons. Please look for yourself! Though I notice you are only pressing some of them once instead of the twice you may need in order to ensure an "off" to "on" transition. Don't forget that, as documented, each press is alternately "off to on" (the "press") and "on to off" (the "release"), because VRi devices do not send anything when buttons are released. When programming you need the "press", but you can (and should, for VRi) still program both press and release. I think you must misunderstand what you need to do when assigning buttons in FSUIPC. :-( Regards Pete

Well, to do that you'd need to assign the keys to operate the equivalent functions on the CDU from the aircraft model you are using. Assigning "Ctrl+F1" doesn't do much if "Ctrl+F1" does nothing in that aircraft. As it is your logs do not show any such assignment in any case. For an assignment in FSUIPC to perform an action you have to choose the correct assignment for that action. That should surely go without saying? Additionally, considering that a CDU needs almost all of the keys otherwise normally associated with other actions in FS, I should think that it would need keyboard focus first -- e.g. "clicking" on it with the mouse. I think your best option is to work out how to use the CDU in FS without the VRi hardware. Once you know how to do that, see if you can apply what you learned to the VRi device, whether by assignments in FSUIPC or by using the VRi software provided for it. Regards Pete

But WHAT are you seeing running "continuously"? Something is wrong, but I can't see what you are seeing, I am too far away! ;-) The contents of the console log are merely copies of what is put into the FSUIPC log file, on disk. That will not go too fast for you to read because you can load it into Notebook or any other editor and read it at your leisure! Not only that, but it is easy for you to paste it, or part of it, here, so I can tell what you are seeing! I have said this before but you must have misunderstood. Also, I need to know what it is you want to read from the Log so I know what you think you are doing. I cannot tell you any answer since I don't know what you are seeing. There should be no "continuously running scripts". Maybe you have enabled too many logging options (I asked you about that too, but you do not answer my questions :-( ). In either case the answer is in the Log file itself. I don't understand why you do not refer to this as I asked. Regards Pete

I'm sorry, what "console log" do you mean? Have you enabled this in the FSUIPC Logging tab? What logging items have you checked? What is it you want to do with this logging? Sorry, what do you mean by that? What are "open offsets"? This exchange is very confusing. I do not know what you are trying to do, nor what you are looking at, nor why. If you have a specific problem could you please explain what it is? If you want me to look at some logs for you, please paste them in. Regards Pete

You must have deleted more than merely the wxstationlist.bin file, because I just did that and FSX doesn't worry about it. It just makes a new one when you close the session. The file which it is referring to is nothing to do with the weather, but the keypress mappings. Just click "yes" to accept the default key mappings of course. What else? And? What do you expect your LSK1 key to display there? Sorry, I really don't know what you are asking me in this thread. You can program any of the buttons on the CDU2 in FSUIPC, to do whatever you want that FSUIPC provides. This is if you want to, of course. It works exactly as stated in the documentation. Alternatively you can let the VRInsight software do whatever it wants. It is all up to you. You must decide what you want to do. FSUIPC just treats the buttons on the CDU as programmable buttons, it doesn't simulate a CDU for you. Regards, Pete

With the device on COM5, yes. Okay. What do you expect to happen on the display? It is only another screen on your PC, assuming you've connected it to a VGA port on your video card or motherboard. Nothing of mine handles any display windows. I think you have to undock the FS CDU and drag it over to the CDU. That's not my subject I'm afraid. Okay. Let's see ... ... First of all, I don't like all those: You might get one or two of those now and then, when a weather station isn't populated with weather, but you have it occurring constantly. Something is wrong with your weather option settings in FSX or you have a corrupted FSX installation somehow. Maybe the file "wxstationlist.BIN" is corrupted. You'll find that in the same folder as the FSX.CFG file. Try deleting it so FSX generates a new one. But here is proof that the LSK buttons are being seen in FSUIPC and assigned to button numbers: So all you need to do is assign them to whatever you want them to do. Note that because VRi devices don't send "press" and "release" indications like normal joystick buttons, FSUIPC has to toggle the switch "on" and "off" on alternate presses. So to see them in the Buttons tab you often need to press them twice, and for actions you want to occur every press you need to program FSUIPC to do the same on Press and Release. This is explained in the documentation too. Regards Pete

The FSUIPC4 console log is enabled in the Logging Tab in FSUIPC4. Is that what you mean? You have to run FSX in Windowed mode to see it because it is another normal Window. But all it shows is the same data as goes into the normal FSUIPC4 log file, so you can look at that instead. Are you now referring to the prompt for a macro name when creating macros? The (n of n) part will only appear if a mouse area has several different entries in the Tables in the Gauge which handles it. This enables you to select different functions when the Gauge is programmed in that way. If it is not, you do not see the (n of n) part because it doesn't apply. All this is explained much better than I can do here in the User Guide. Maybe you are asking a specific question, but if so I cannot yet understand what your question is I'm afraid. Regards Pete

The little joystick selector switch is internally handled so you don't see that. The detection of the other buttons and the dial (and the button numbers assigned) depend upon which function you selected with that joystick switch. The AP/CTL selection, for example, makes the device handle the 5 little buttons internally -- the dial and white button are still detected though. When in FSUIPC's Buttons tab, you have to press most buttons twice to see them, because they act as "toggles" -- no signal is sent on "release" so FSUIPC has to treat every alternate press as release. I notice you've enabled logging: but unfortunately you only supplied the INI file (which I don't really need), but no Log which would show us what is going on. I'd also need to know which version of FSUIPC you are using. You might want to check the Updates announcement in this Forum to see if you are sufficiently up to date. Regards Pete

But the next response might take longer. I'm off to bed now! ;-) Pete

Very curious. And this is for all aircraft? The same string is logged in the standard FSUIPC Log file, merely using a normal printf with the %s string selector. What you are getting can easily be logged -- check the "IPC read" logging option in FSUIPC Logging options. Regards Pete

Of course I know that. ;-) Oh, you just mean the Dialogue which comes up when you select "status". I thought there was some number or status name you were referring to. Whoops! ;-) So somehow the adapter is hanging or going wrong? Hmmm. I'm still using AVG Free. I wonder how the full version can clobber the LAN Adapter making it need a reset? You wouldn't think it would touch it? Regards Pete

Since the complete source for the interface to FSUIPC is also provided in the SDK package, you can simply pull it out and build it into your program with any minor adjustments you need to make it compile correctly. This is necessary in any case when the LIB file format is not compatible with your compiler. Regards Pete

ASA running with FSX does not use FSUIPC. There is no setup in FSUIPC needed. Best to reset everything to default, though the wind smoothing is a possible option depending on the sensitivity of your aircraft models. All your "realistic weather" is set using ASA options which deal with SimConnect in FSX directly. Pete

Version 4.20 is definitely NOT the latest version! It is completely out of date and will not work with any keys purchased recently. The current user release is 4.60 and there's a later version also availble in the Updates announcement. Please do not ask for support with any old versions. Also the oldest supported version for FS9 is 3.98. Note that FSUIPC3 and FSUIPC4 use different keys-- they are different products. Regards Pete

I just use the standard "strlen" function, which does a compact loop looking for the first zero byte (which is how ASCIIZ strings are terminated by definition). Really? What you call "white space" should be zeroes, which are NULLs in ASCII. Although there is no guarantee that there will be any more than one byte of zero, to terminate the string. The rest might be rubbish from a previous longer name. Sorry, I don't know what language you are using nor how it manasges to interpret a zero terminator for a standard Windows ASCIIZ string as a space, let along so many of them. Of course. It is a standard zero-terminated ASCII string, usually termed as ASCIIZ. Exactly as used universally in C and C++. You should certainly not be using any characters past the first zero. Pete