Pete Dowson

Yes, in common with others. MS seem to be insisting this is a firewall problem. Please follow the link in the Firewalls announcement above. The error in hexadecimal is 0x80004005. I have no idea what it means but I am pressing MS for answers. Please report it to MS via tell_fs@microsoft.com in the meanwhile, with as much information about your system as possible. Regards Pete

Why's that, John? Guess I'll never understand VB! ;-) Pete

Are you comparing TRUE direction with MAGNETIC direction by any chance? Please take the Magnetic Variation into account. If you still think it is wrong, show more figures for comparison so I can see, but also state where you are in the world. In some places the MagVar is small, other places it is very large. Even in Seattle, for example, it is about 20 degrees. Even better, please try using FSInterrogate, part of the SDK and deliberately provided for exactly this sort of assistance. view the heading there AND the magnetic variation in offset 02A0. There's also a lot of logging and monitoring facilities in FSUIPC for you to use, to find out what you are doing wrong. Please take a look at those. Regards Pete

Well, to start you could use the autostart control. Exactly. So it could send the 4 controls even though you only say one thing? Anyway, try the _SET controls. Pete

FSUIPC always creates a Log file, even if you select no logging. If it doesn't then it isn't running or there's something rather seriously wrong with the file system somehow. In the seven years FSUIPC has been available I've never heard of a case where no log file was produced. The previous log file is always deleted and a new one created each time FSUIPC starts. Regards Pete

That wasn't the point. The controls appearing in the FS assignments are supposed to work. The ones in the FSUIPC list are all those actually present in FS's tables (in CONTROLS.DLL). A lot of those aren't assignable in FS's assignments, and there's no guarantee they will work therefore. They may be hangovers from previous versions or new ones not yet hooked up. Yes, of course. Because it represents a switch position, like the pilot holding the switch on start against the spring pressure. That same switch, when released and allowed to spring back will send abother value, meaning "Both", for example. The starter motor remains connected till the switch is released. Checking my code for FS9, I've never used those OFF/LEFT/RIGHT/BOTH/START values. I've a feeling they've never actually been hooked up inside FS, even back in FS98 days when they were added. An alternative to writing directly to the offsets which should work, though I don't know about FSX (where there's a bit of a mess in this area), would be to use the KEY_MAGNETOn_SET controls with the parameter giving the position 0-4. I just checked and FSUIPC3 uses these. I'm not sure how this relates to SpeechBuddy. Surely with that you are only seeking to replace keyboard use, so the INCR/DECR controls should be the most applicable, shouldn't they? That's what you use on the keyboard. Regards Pete

No, it means running FS, going to the FSUIPC options, pressing the "REgister FSUIPC" button, and entering your name, email and Key exactly as you did on the first computer. If you've copied the FSUIPC.KEY file into the new Modules folder you may need first to delete that before running FS. It does explain these things in the documentation. This is the relevant part: Pete

In that case there is really no way that Windows should tell my program that it cannot find the host called "MAIN". There's no way past that unless you give the client an explicit IP address (ServerIPAddr=n.n.n.n). Then it won't ask Windows to supply the address. To test the connection and the IP address you can get into a DOS box (Run, enter "Command" and press Enter), then Ping n.n.n.n See if it gets a response. If not the IP address is not accessible. It could still be a firewall problem too. Regards Pete

I don't know if any of those work. Are we dealing with FS9 or FSX now? For FSX there seem to be a lot of problems with magetos, starters, all sorts. I bugged them during the Beta and tried to find alternatives for the FSUIPC interface. All FSUIPC does with any FS control is send it to FS. It doesn't interfere with it -- it is identical to assigning it in FS, if it had a complete list to assign to. (Have you looked to see if FS supports direct assignemtn of these BTW?). Anyway, I'll cross-check here if you'll please clarify which version of FS and which aircraft (I think implementation of controls can vary by aircraft too). Regards, Pete

This error: 2564 Trying TCP/IP host "MAIN" port 8002 ... 2564 Error on client gethostbyname() [Error=11001] Host not found means that the server PC "MAIN" is not known to the Windows installation on which the Client is being run. You need to get the network fully working first otherwise WideFS has got no chance. Possibly it's a firewall problem, though generally I find that those simply give no response at all, no errors, nothing. Check that Explorer on the client can see the files on the server. Check that both computers have TCP/IP addresses on the same subnet -- if you didn't explicitly set the IP addresses that should be okay. Check that both PCs are in the same Workgroup. The Workgroup name is in My Computer properties (right click on My computer icon, select properties then the Computer Name tab) and can be changed there too. Regards Pete

Yes, I saw it, but you don't say what the "error" is. There's not actually a question there, even if I did know any VB. Regards Pete

What error? Sorry, I don't understand what you are asking. Regards Pete

Really reverse thrust is not an good function for a button. An axis lever for a separate reverser or a reverse zone on the throttle axis is better. For a sequence of keypresses on one button, the way you seem to want it, you'd need to have a series of parameters 1=, 2= etc each with the same joystick and button number but with different key codes, the codes for 0, F2 umpteen times and so on. [speed brakes should have been armed before landing and so deploy automatically in any case]. Key codes are listed in the Advanced User's guide. If you just want to deploy full reverse with a button you could try simply programming, not in the INI but in FSUIPC Options, a button to send a THROTTLE_SET control with a parameter of -4096. I think that should work -- otherwise you'd need to use THROTTLE1_SET for engine 1, etc (program the one in the options, add the others in the [iNI]). To use it you'd need to make sure your throttle lever was pulled right back to idle and is stable there -- make sure there's sufficient dead zone to stop any jitter. Regards Pete

They seem to work fine here. Maybe you only have the one view? Then of course they won't do anything. To check yourself whether the controls are operating that far, please use the logging facilities in FSUIPC. That is what they are for. Enable button loagging and Event logging. Possibly you think those controls do something they don't? You need multiple views to make use of them -- all they do is move the focus from one view window to the next, or back, so that actions such as zoom and view left/right etc change that window. If you only have one view the "Next" and "Previous" don't mean much really. How can they? If all you are thinking of doing is changing view modes (the same as "S" and "shift+S" do), these are not the same -- it is modes you change, not views. VIEW_MODE and VIEW_MODE_REV. Please do use the FSUIPC logging when you are trying to work things out. It would save you a lot of time. Regards Pete

Yes, provided your potentiometers interface correctly into Windows looking like a set of joystick axes. You can get 6 on one joystick device even with FSUIPC still using the old Windows joystick API -- the axes are called X Y Z R U and V. In FSUIPC's joystick calibrations pages there's a siingle Reverser for all engines and, separately, a page for up to 4 independent reversers. Regards Pete

This shouldn't be needed if you tell Windows to trust software specifically signed by me -- it's an option in the dropdown on the security warning. It places my certificate into the IE repostiory as a "trusted publisher". The only other possibility is that the Manual.Load entry in the DLL.XML file is for some reason set to "True" instead of "False" -- the FSUIPC4 Installer sets it to False. In the current interim releases (we are up to 4.026 now, in the FSX downloads above) this odd error number is shown in hex too, as it seems to lok more sensible then. It is 0x80004005. Unfortunately this does not appear to be any standard error number and I've not managed (yet) to get an answer on it from MS, but it does seem pretty certain that it is a fiewall permissions problem. I know you say you have these things turned off, but could you follow the link in the firewalls announcement above anyway, and see what MS themselves say? Please asl report this to tell_fs@microsoft.com with as much info about your system as possible. Thanks. Pete

Okay. In that case the puzzle remains as to why Windows XP's mailslot system isn't working on your Network. Not worth pursuing now you have a work-around, but it might help others if we could find out. Not sure how to though. Regards Pete

You need to re-register on each computer you install it on. There are no restrictions on how many provided they are all for your use. You also would need to re-register if you re-installed Windows. Regards Pete

I'd love to help but I'm afriad I don't know what the question is yet. Can you amplify please? Regards Pete

Is it? Oh, sorry. The fix must have missed that one then. It will be okay in 3.71 which has been imminent now for a couple of weeks. I do hope to get to that in the coming week. Regards Pete

Hmmm. Weird though. Thanks for letting us know. Regards Pete

No, the only thing I know that may cause that is something trying to change the time by more than a minute or so. The only facility in FSUIPC for time changing is the clock sync option in "miscellaneous", but that only changes the seconds in any case, which doesn't cause AI traffic reloads. FSRealTime changes the time and can cause those reloads, but it is usually set to something rather long so you wouldn't see it often if at all. But maybe you have it operating every five minutes and with too stringent a stipulation? Otherwise see what other external programs you have running and try eliminating them one by one. Regards Pete

No point. If you've registered WideFS andyour WideServer is enabled, then the FS title bar always had the information telling you so. When clients connect it shows you how many are connected. It has been doing that now for 7 years or more. Regards Pete

Thanks for the Log, It shows the reason clearly and it isn't complicated. I'm sure you would have seen it for yourself if you'd used the Logging before: Everytime you write to the throttle offsets you write the same value to the high word of the spoiler offset. Here: 2659000 WRITEex 088C, 2 bytes: C2 02 .. 2659000 WRITEex 0924, 2 bytes: C2 02 .. 2659000 WRITEex 0BCC, 4 bytes: 00 00 00 00 .... 2659000 WRITEex 0BD0, 4 bytes: 00 00 C2 02 .... 2659046 WRITEex 088C, 2 bytes: C2 02 .. 2659046 WRITEex 0924, 2 bytes: C2 02 .. 2659046 WRITEex 0BCC, 4 bytes: 00 00 00 00 .... 2659046 WRITEex 0BD0, 4 bytes: 00 00 C2 02 .... 2659109 WRITEex 088C, 2 bytes: 86 06 .. 2659109 WRITEex 0924, 2 bytes: 86 06 .. 2659109 WRITEex 0BCC, 4 bytes: 00 00 00 00 .... 2659109 WRITEex 0BD0, 4 bytes: 00 00 86 06 .... etc etc throughtout the log. Those are HUGE values of course (0x06860000). Maybe, in FS9 and before, FS ignored values over the maximum (16383, or 03FFF), or only used the low bits -- but evidently FSX treats this as maximum deployment instead. Really it is an error in your program. Obviously you don't really want to set the two high bytes of the spoiler as you do. However, since FS9 and before ignored it, for compatibility I will change FSUIPC4 to filter those bytes off, in the next release. Regards Pete

These are new FS controls, fully supported through FSUIPC4 (e.g. via the button and key assignments, or by sending the controls via offset 3110. If you men to read the state of the switches, I'll just check to see if they are among the new ones supplied by Simconnect ... .... right -- I can obtain the Hydraulic, Smoking and SeatBelt settings. I'll add them soon, maybe in the next build if I find time. The cross feed is actually currently supported already (as it always has been) via the fuel selector switches -- 3880 etc (one for each engine), but I see there's a separate single indication too now. I'll add that but it would be interesting to find out how that relates to the othershmmm. It should do -- are you meaning when reading or when writing? It's more sophisticated than in FS2004 as it should be showing separate bits for each exit (I cater for exits 1-8 but I think FSX only deals with 1-4). Please can you clarify what you are observing, with IPC read/write logging to show? Regards Pete