Pete Dowson

With such things all you need to do is enable Event logging in FSUIPC (the Logging tab), then operate the thing on screen with the mouse and see which control, if any, is used by the gauge. With the default Cessna in FSX the normal "Toggle DME" control does the job with one button/switch -- that's what the gauge uses. But "DME Select" with parameter 1 or 2 (for DME 1 or DME 2) works better for a toggle switch rather than a button or momentary switch. I suspect you could also have found these controls by simply searching the FS controls list (installed for you by the FSUIPC installer) for "DME". Regards Pete

Inside the ZIP file you downloaded were two things: the Installer program and a PDF document which explained how to install and register AND where to find the User Manual. It told you all of the extra goodies and manuals were installed in the FSUIPC Documents folder inside the FS Modules folder. There is also a wealth of additional material available in the SubForums in this Forum. Please have a browse. Pete

Okay. in that case this is not a new bug. I thought it might have crept in when I made some recent changes to eliminate duplicates from the drop-down lists, but evidently not. I'll look elsewhere to fix it. 4.60a is the main current user release for FSX etc. It's one of the many interim releases, the latest one here. There have been 40 of them since 4.60a which was nearly a year ago now. I'll be consolidating 4.70 as soon as I can get all the documentation updated, then 4.60a will be superseded. All interim updates are supplied here, in the Download Links subforum. Regards Pete

How do you work out that there's no tech support? Haven't you seen this Forum though you posted here? Haven't you seen how many tech questions are asked and answered every single day, and often within a few hours. For a tech support response you need to ask a tech question, not "how do I use your software" -- documentation is provided for that. You could have read that BEFORE purchasing, to determine whether you really wanted to buy it or not. You surely don't expect sections of the manuals to be reproduced here when it is far easier and quicker for you to refer to them as installed in your PC? Pete

If both PCs are in the same Workgroup it should connect automatically. the Workgroup name is seen and set in the same place as your computer name -- right click My Commputer and select Properties. No, it does not say you must. But you can if you wish, and the format of it and the place to put it is also described. If you enter the ServerName parameter you must also enter the Protocol parameter. You install and run WideClient in the client computer. Regards Pete

You can't use testbutton on the so-called POV buttons. They aren't really buttons but an interpretation of the 360 degree values supplied by the POV. They can change from one to another without being "released" first. You'll note that the documentation for TestButton does specifically say the button numbers are 0-31. You'd need something like "readPOV" to return the current POV value instead. On your other problem, I suspect that new facilities I added recently are conspiring to foil your code. Structuring names like "ActionButton.timerEvent" means procedure "timerEvent" in table "ActionButton". It's like the library calls themselves: "event.timer" is Procedure "timer" in Table "event", the event table having been added to the Lua environment by FSUIPC before starting the plug-in. Before the latest releases FSUIPC would not have parsed the name and used the '.' in the standard Lua way. I changed it on request for a user who was buliding modules (called by "Require") which effectively adds tables of functions too. What I don't understand, though, is why this line doesn't give an error too: event.timer( ActionButton.timerInterval, "ActionButton.timerEvent" ) Maybe, because you are using the '.' method (which is an alternative to [ ] for arrays -- i.e. ActionButton.timerInterval is the same as ActionButton[timerInterval]) a lot of your names made this way are valid table entries. But in that case why not also for the cancel? If you can't see an explanation perhaps you'd let me see the entire code. I can trace it through the insides of FSUIPC. Regards Pete

IS FSUIPC loaded? Is it in the modules menu? Does it's log file show any problems? FSUIPC doesn't produce a message saying it isn't loaded (how could it?), so you need to find out what program is saying this, and seek an explanation from that quarter. Isn't FSConnect a program which tries to produce a compatible interface to FSUIPC's own? If so I wouldn't think you could use both together in any case. Regards Pete

Interesting that the 4 lines which don't appear to work all need 1,8 pressed. A separate test of that button would be interesting, don't you think? After all it is the only thing I can see which would stop those 4 lines doing anything. Have you checked the logging? Enable button and key logging in FSUIPC Logging tab and see what that tells us. Is this the whole set of assignments? If not perhaps you need to post the complete Buttons section? Regards Pete

Ah. Offset 2910 is for "Hot Button" programming and only operates with regular locally connected DirectInput joysticks. Why not simply assign them? Why are you writing a program to use Hot Buttons? Regards Pete

Yes. The 5 and 6 from the KeySend don't relate to the 5 and 6 for your two programs. KeySends can be 1 to 255, but you can only have up to 8 RunKey programs. Regards Pete

The problem is that it's a WideServer setting, not a WideClient one -- "connected" means WideServer is connected to something. When the connection dies, WideClient no longer receives an update for it. I'd never thought of making WideClient change it -- normally ALL of the data maintained in the WideClient memory is the "property" of the Server, and the client never fiddles with it. I think I'll make an exception for that byte, though. Meanwhile the method i normally use to to check that the timer in offset 3374 is changing. If it doesn't change for more than a second or several, assume no connection or FS has stopped. Regards Pete

Yes, it's historical. The interface FSUIPC presents to applications originated with FS98. It's grown some, but it sort-of defines it still. Regards Pete

Not FSX. Even the FS9 facility doesn't do that. You are talking about initial positioning, not locking (preventing accidental movement with the mouse). Nothing in FSUIPC will do positioning for you, but there might be a separate program which will do it. Have a search in the general FS Forums. Regards Pete

I've not heard of a weather problem quite as severe as losing the Themes as well, but apart from the possibility of corrupt WX files, there's a file called WXStationList.bin in the same folder as your FSX.CFG which can cause similar symptoms when corrupt. You can delete it and let FS build another. It is updated from Jeppesen/Microsoft downloaded weather data and if this is corrupted the file can also be so. Regards Pete

Sounds like the USB joystick IDs assigned by Windows changed. This can happen just by unplugging the USB cables and plugging them back in, so using a separate Windows install would almost certainly change them. This is why FSUIPC provides facilities for using letters to assign things rather than the Windows IDs. Just changing disks shouldn't do that, but a different system font size or different video drivers could. See above. 14th actually. It is I speaking to you. ;-) I suggest that you boot with the older system, use the joystick lettering facilities in FSUIPC (you can let it do it automatically, or choose meaningful letters for yourself), and copy the INI file over again. Regards Pete

3.96 is too old and is not supported. The earliest supported version is 3.98. You need to update. Just installing an aircraft should not change FSUIPC settings, unless their installer deliberately and maliciously deletes the INI file. And nothing I know will stop button numbers from a normally connected joystick being seen by FSUIPC. Are they seen by Windows (i.e. control panel, game controllers), and by FS itself? Pete

Put the macro file, named, say "MD11.mcro" into the FS Modules folder. Then run FS. In FSUIPC Options, use the Buttons & Switches tab to assign your buttons to "MD11:mcp hdg incr" and "MD11:mcp hdg decr". Not sure why you mention Lua at all. Regards Pete

These are part of a set of FS controls which are listed in earlier versions of FS but seem to have been omitted in FSX, so FSUIPC4 adds them back in. I've tested them here with FSUIPC version 4.644 and they do stay programmed and do actually send those controls, but FSX ignores them. The assignments you need to use are these: Radio vor1 ident toggle Radio vor2 ident toggle Radio adf ident toggle Radio dme1 ident toggle which do work. There does appear to be a (new?) bug in FSUIPC4 which stops the assigned control number being decoded for display in the options (or in the log) when it isn't listed by FSX -- I will fix that. But I will also remove those controls which certainly do not work in FSX. Can you please tell me what the version number is of the FSUIPC4 you are using? I think this is a recently introduced bug, but I want to be sure. Regards Pete

I can't help a lot with VB, except to say that I think VB uses 16-bit character codes, so trying to read strings as strings probably doesn't work, You may need to read them into a BYTE array, then go into a look converting each byte into a VB character and concatenating it to the string built so far. But two points do arise: 1. Your code would be much more efficient and foolproof if the first 4 steps are accomplished with only one call to FSUIPC_Process, as suggested in the documentation, and 2. You can always see what your program is accomplishing by using FSUIPC IPC logging -- the two options in the FSUIPC Logging tab. Regards Pete

I don't understand either, at least not without seeing the data itself. Perhaps you could post the "before" and "after" (after you used the Options successfully), highlighting the lines which don't work as opposed to those that do. You don't need to paste in all of the files, only the Buttons sections. Regards Pete

I cannot read the Install log from a picture on screen. Please find the FSX Modules folder, get the Install FSUIPC Log from there and paste it entirely into a message here. Whilst you are looking in that folder, see if there is an FSUIPC Log and FSUIPC INI file there. If so, paste also the FSUIPC Log. These files might simply be called "text files" if you have Windows Explorer set in its default mode of hiding filetypes from you. Regards Pete

Oh, right. You mean the experimental FSUIPC feedback controls. Those are test facilities for folks experimenting with values for different aircraft. There's a document about it in the FSUIPC SDK package, which I reproducr below for you: .

No. Once the data has arrived in the WideClient memory it is read directly from memory. The updating of the WideClient memory is done asynchronously, when it changes, so once things are running everything is very fast indeed. The first seconds after WideClient connects are always taken up by administrative operations. There's a 500 mSec imposed wait for data until that part of the initialisation is finished. The 500 mSecs can be adjusted by a documented parameter, but it usually isn't worth it -- you would only be slowing down the initialisation sequences. Regards Pete

Save all .MCRO and .LUA files from the Modules folder too. mouse Macros generate MCRO files. The INI file contains all the FSUIPC assignments, calibrations and other option settings. The KEY file contains your Registration. Regards Pete

See the FAQ subforum thread entitled "WideFS Server names translating into incorrect IP addresses". Your Server PC is being seen with a weird IP address which searches show as opendns.com sited in California. Regards Pete