Pete Dowson

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

Hmmmstrange. I wonder how that happened. Certainly it isn't anything in my installer changing your entire file system. Anyway, I am making some changes to try to IMPOSE the attributes I want on the files my installer installs. Those changes will be in the next update, whenever, so please be sure to let me know how they work on your setup. Thanks, Pete

Strange. I think the "graying out" actually means that the attributes are being imposed by virtue of attributes for the folders above being inherited. If so, it could all be some strange result of how FSX itself is installed on your system. Have you checked the attributes of other FSX folders to see? Regards Pete

Yes, it sounds like you are getting something wrong. The name, email and Key must match EXACTLY to that which you'll find on the receipt. Use cut-and-paste if you are not sure. Please also make sure you are NOT using version 4.00 of FSUIPC4, though that is unlikely as it was only available for a few hours. If you still get a problem, write to me at petedowson@btconnect.com. Tell me exactly what you are entering and show me the receipt. I can cross-check it here. But I can tell you that all such incidents for the last three years and more have been simply down to the fact that folks were entering their name differently. Regards Pete

Does their driver use FSUIPC? What is the name of their program? Is your FSUIPC user registered? If you'd like me to check, try again, then close FS2004 and show me the FSUIPC.LOG file (you'll find it in the FS Modules folder). Regards Pete

Very strange. The folder is created by FSUIPC's installer with default properties. I'll check to see if I can deliberately "unhide" the folder in case it is getting the property from its parent, though that seems unlikely too. Yes, that's correct. Access denied? Even stranger. Why were you trying to reinstall the same version again, by the way? And howw long (how many seconds) after closing FSX did you try this. I have noticed that FSX closed its Wndow and seems to disappear quite quickly, but, presumably because of the sheer amount of clearing upit has to do, the process itself doesn't finish for anything up to 20 or so seconds later. If that was the case, and for some reason you tried to re-install FSUIPC4 then the "Access Denied" error may have simply been because the module was effectively still loaded in tthe closing down FSX process. I don't know how Windows is doing this, because even if the file does get marked "read only" the installer deliberately unmarks it before trying to replace it. I have a fgeeling that this may be an indirect result of trying to re-install it whilst it was still running. Why are you repeatedly trying to install the same version? This is not a general problem, it is somehow very specific to your system. Can you please tell me what version of Windows it is? Are any of the folders in FSX already marked hiddeb or read-only? I am grateful for the report, but I am still puzzled as to why you are installing FSUIPC 4.026 three or more times when the first time worked okay? It may simply be this which is somehow causing the problem, though it wouldn't explain the hidden files in the first attempt. Anyway, I'm making changes so that the attributes like Hidden and Read Only are removed by the installer before it tries anything. Regards Pete

Everything interfacing to FSUIPC is related to FSX. FSUIPC is forging that relationship -- that is what it is for! ;-) SimConnect can also be used directly by other programs, so that is forging relationships as well. Pete

It doesn't sound like the same, but certainly it is worth reporting this to tell_fs@microsoft.com please. There are no important changes I'm making to FSUIPC which are not SimConnect problem avoidance related -- work-arounds where we've found them. Nothing I know of or can do would change FS's abilities to redraw itself on changes of process or mode. I haven't had exactly the same problem that you describe but certainly I've had FSX disappearing to the task bar without warning and just never restoring. And I've had completely black screns, with everything otherwise appearing to be running, when switching from windowed to full screen mode or vice versa. Most of these sorts of problems I know about do seem to be associated with full screen mode, and I think for stability it is currently best to run instead in maximised Widowed mode if possible. (Oddly, I remember problems like this in the early days of FS2004). I can only hope that MS will be able to address these things sooner rather than later. One of the whole points of making FSUIPC almost exclusively a SimConnect-using client is that it means there's no complex invasive code in it, so nothing to go wrong -- at least on my side of the interface. Except for the button, key and joystick scanning (which are still independent and use standard Windows facilities) everything it does is via SimConnect. And 99% of the time it is doing nothing but waiting for information to arrive from simconnect as, unlike previous methods I had to use, the simconnect data access is passive -- FSUIPC files a request for information with SimConnect during initialisation, and then it merely sits back and waits for it to arrive. Admittedly, whilst flying, that's a lot of data which is changing fairly frequently, but on the whole is it no more often than in FS2004 and it is tied to the frame rate. Regards Pete

Actually, I think you are adding to the wrong thread -- but I can see why. The right one is http://forums.simflight.com/viewtopic.php?t=57105. It sounds like another possible symprom of the bug reported and hopefully now "worked-around" (at least in my code, update to be released here later tonight) -- it needs changes I expect to all SimConnect client programs until MS can fix it. Actually only removing it from the Modules folder, or renaming it would be enough. And if you told Windows to trust all software from me (via the option in the dropdown) the "trusted status" is nothing to do with FSX but is recorded someplace else, in a repository you can access via IE's Options. Aha more usual symptom. Please make sure all this interesting information gets to MS, tell_fs@microsoft.com. I've tried to promote this as the most urgent SimConnect problem to resolve, even before firewalls, weather and performance! Regards, Pete