Pete Dowson

So where did you see this "Bind" error message pop up after 30 seconds when such an error certainly doesn't occur in WideServer till after 33 minutes? Aha! That shows that you are indeed running a Network where broadcasting doesn't work (i.e. either incompatible Windows versions or differently named work groups, or both). I now see that, whilst you added this to your Wideclient.INI: for some reason you added these lines to the [user] section, not the [Config] section where they belong, so they will be ignored!! Oh, one other thing. The Server log shows the Server name to be KEN-GAMING not Ken-Gaming. Now maybe Windows ignores differences in case in these names, but just in case if I were you I'd use exactly the same in the WideClient.INI file. Pete

Never seen one of those before. Where does this error message appear? Surely not on the screen, as WideServer has no screen messages. What happens after you see this message? Why, have you been changing them? If so, why? Actually they look like defaults except that you have specified the Server name and protocol -- usually totally unnecessary unless you are running two separate network Workgroups (i.e ones with different names), or one of the PCs is running an older version of Windows, like Windows 98. They are not "error logs", they are just logs -- FSUIPC, WideServer and WideClient always prodce logs. And just one would do -- when WideServer runs it saves the previous log. This is to allow auto-restarts without losing error information. WideClient does the same. Why haven't you supplied a WideClient log? both ends of a connection are always relevant. One end is half the story. Anyway, the 'Bind' error isn't particularly relevant by the look of it, as it only affects UDP, a protocol you aren't using. Look: In both logs the error doesn't occur until over 2000 seconds from WideServer being started. That's over 33 minutes! I cannot believe it takes you 33 minutes to select the flight. You said "Shortly after"? 33 minutes? Something doesn't add up here! I really cannot comment further without seeing the WideClient log. Sorry. That sounds suspiciously like some thread not terminating -- probably an add-on which is still running even though FS has mostly closed. You need to check the add-ons and add-ins you have installed. Regards Pete

You don't purchase a specific version, you purchase version 4. 4.26 is out of date -- the currently supported version is 4.28. If you mean the FS controls listed by FSUIPC, they are simply the complete list of which the FS assignment list is a subset. Many add-on aircraft, and especially the PMDG ones, implement a load of subsystems independently of FS and which therefore are not controlled by FS controls. How could they be? They've been added by an add-on! No it isn't, it is part of FSUIPC4 as well as FSUIPC3. You are simply not looking at the correct websites nor downloading the supported version of FSUIPC4 which has been current now for over a month. Please also review the Announcements in this forum which tell you things like the current versions and differences. Regards Pete

Sorry, it is working perfectly here, and I can actually prove, through my source control (which keeps track of all changes) that the code concerned is identical to that in 4.26. Sorry, I don't know what to suggest. There seems to be only two of you with this problem, and I've no idea how it can be happening. I am away from tomorrow until June 10th. If I do think of any way to find out what is happening, I'll get back to you. There are a lot of logging facilities which might record the details, so you could try getting me a log. Edit the FSUIPC4.INI file, adding Debug=Please LogExtras=512 LogWeather=Yes to the [General] section. Start FSX with a saved flight that you know runs into this trouble. Keep it short, only long enough to prove that you have a problem. Close FSX, save the FSUIPC4.Log. Then do the same with 4.26 so I can compare them. Zip both logs up and send them to petedowson@btconnect.com. I doubt i'll be able to do anything till I get back in June so there's no rush. Regards Pete

Strange, because GSPout is exactly the same in both cases Since the code is identical in both cases I really have no idea. The only answer I can think of is that you haven't actually installed GPSout.DLL and the INI file with the required parameters into the correct folder. You do realise that if you allowed FS9 to install into Vista's "Program Files" folder that Vista does some weird stuff with it, because FS9 is not Vista-aware and tries writing to its own folders (not allowed by non-privileged programs in Program Files). Unless you are an administrator with elevated privileges I think it diesn't show you the real folders but does some sort of copy. Confused the hell ou t of me when I tried Vista with FS9, so I uninstalled it and used my usual "C:\FS9" folder for installation instead. I've a vague idea you can get to see the real FS9 Modules folder if you run Windows Explorer using "Run As Administrator". Double check to make sure the right files are in the right place. With FS9 running FSUIPC it will be the folder which also has an up to date FSUIPC Log file. There's really nothing else I can think of, because, as I say, the code is identical. Pete

There's nothing much to do to 2set up" GPSout, so I really don't know what you mean. Can't you explain what the problem looks like? The most likely problem is that you don't have a working serial port. Have yuo checked? Are you sure your COM port is working with Vista 64? I've just changed to Vista 64 on one of my systems and it took me quite a while to find a way to get a serial port with Vista 64 drivers which worked -- I had to install a Brainboxes UC246 single Serial port PCI board, which was the only one I found with Vista 64 drivers. None of the USB to Serial port adapters I have (and I have about 4 varieties) have drivers which work on Vista 64, even though some do install as say they are working; there's simply nothing happening with them. Pete

I think you missed a section in the User Guide, in the part about Registration: It is actually emboldened in the document, and in a larger typeface, just so folks don't miss it. :-( Regards Pete

No, do NOT make a Modules folder yourself! It seems that you didn't read my earlier instructions at all, did you? Here, I will repeat them, with emphasis on the part you ignored: Anyway, this error: ... Probe Manifest fails to match a valid base SimConnect needed to load FSUIPC4! proves that your FSX installation is bad. The base version of SimConnect which gets installed when you first install FSX from the DVD is missing or mis-installed. Please see the Announcement above called "FSX Help" for instructions on how to repair FSX SimConnect. No, that is the FS9 version of FSUIPC. How did it get in there if, as you say, you just created a new Modules folder for FSX? I don't know what you are doing but you have got everything very confused. Regards Pete

Good! Thanks for confirming this. Regards Pete

This is certainly not being saved by FS, but by the add-on aircraft code. It is as I explained already. I'm pretty sure that the older editions (in Wilco days) used to detect the saving of Flights more effectively. Seems they've not done so well this time. I repeat, the routine used by AutoSave to save a flight is the actual one in FS used to save a flight, whether from menu or by use of the ';' key. There is no other. If there's extra data added it is by some other add-on which is detecting the menu use instead. Have you looked to see what it is? There is absolutely no way any one add-on, like AutoSave, can save data belonging to another. You must make your requests to Level D, or else choose an alternative add-on aircraft which is programmed to do these things properly. Regards Pete

Seems you are getting the hang of it quite well, now! ;-) Regards Pete

Yes. What else can it do? It isn't aware of what other folks' add-ons may or may not do. Many add-ons, like Radar Contact, and, at one time at least, the PMDG aircraft, monitor the saving of flights by FS and then automatically save their own files, with the same name but a different suffix. In fact, I thought the Level D 767 would do this because I seem to remember its predecessor, the Wilco one, did. In some cases I've known them to actually add their own sections to the saved FLT file instead. I don't know if any still do. That's a question for Level D -- maybe they are not actually trapping the Flight being saved, but looking for the menu action by the user instead. Sorry, I really couldn't say. Did you use the menu, or more directly, via the ";" keypress? Regards Pete

The parameter facility is actually implemented the same in both button and keys tabs. All I have to do is program the Keypress action on the left-hand side , icluding entering the parameter, then press Confirm -- you will see the result reviewable on the right-hand side. This has been working now for around 9 years. I have really no idea why you are having any problems. Maybe you should delete the keypress assignment and try again? Different programs have different ways of reading the keyboard. If it reads the hardware then WideClient cannot help. However, there are several other things it might do. First, with KeySend, if you are having WideClient load this program for you (via Run or RunReady parameters), then you can add ",Run1" or ",RunReady1" (for example) to the end of the KeySend parameter. This will make Wideclient actually send the keypress code directly to the programs main Window. This works with most programs. There are other ways to try -- PostKeys=Yes and UseSendInput=Yes (one or the other, not both together). These are described further down in the Tech document. But these are not often used these days. Pete

I thought you said you wanted F9 pressed on the Client PC -- 82 is 'R'. Sound like you've simply not Confirmed the setting. Pete

Hmm. I have to look up the documentation to do this. I don't see why you shouldn't at least make that much effort if you want to do something. Do you think I carry all this stuff in my head? I don't even have paper copies, so I have to go find the document and extract bits out just to save to all that bother? Why so lazy? I don't mind correcting something you've worked out for yourself, assuming you tried something and it didn't work, but asking me to look things up for you seems a bit much, don't you think? There are already examples in the document for Shift+A, Shift+Ctrl+Backspace and Alt+F1. I don't see why you can't easily find F9 in the list supplied and make your own example. :-( Pete

options? In WideClient, as documented in the WideFS documentation. Not related to FSUIPC 3.81 at all. Pete

There are no facilities in my programs to send joystick button presses to clients. Sorry. The parameter for KeySend is a number, 1-255, as it clearly states. It doesn't matter which number you choose, you just match it up with parameters in the client's INI file. If you've not already used "1" I suggest you start with "1". Afdter that, use "2"and so on. If you have 255 keys to send, you'll reach 255. The table of keycodes and shifts for the client are tabulated in the WideFS documentation, as it is WideClient which sees the KeySend and converts it into whatever keypress you want on that particular Client. FSUIPC/WideServer do not send the actual keypress code because that would go to all clients, and who knows what that might do on different ones. The KeySend system allows an event to be created on all clients (a "KeySendN", N = 1 to 255) which can be programmed locally as you like. Please re-check the WideFS documentation provided. Pete

It does actually state in the Registration section of the FSUIPC documentation that the user details need to be the same. The keys are tied to a person's identity (not to a PC as is the case with many products), but for that to work the identity has to be consistent. You could have mentioned the change of email to SimMarket and they would have sorted it out. You probably still can, but otherwise you'll need to send me the full details of both purchases, incuding the Keys, and state which one you want replaced. Send to petedowson@btconnect.com. (This won't work during my holiday breaks of course -- I leave again late this Friday). Regards Pete

Ah, well done! What did you have to do to fix it in the end? Regards Pete

Well, it shouldn't, because the Zapper uses the same AI deletion routine as the Traffic Explorer add-on from MS, and the same sort of deletion is actually done automatically by FS9 if two AI get into conflict for too long. They also get deleted sometimes after being given a Go Around. Of course it is possible that there's a bug in this TCAS DLL which doesn't like the disappearance of an entry, but if there was you'd think it would be happening quite a lot. Regards Pete

It would have been easier to use the Flag facilities provided. This is because in order to get a key press whilst not having the keyboard focus the external program has to use the Windows "hot key" facility, which steals the key press away from FS -- so neither FS nor FSUIPC ever sees it. You cannot use the same keypresses. You say you tried to use a joystick button as a switch. If you have a spare button why not use that to operate the light, via the FS control for it (not a keypress). Why? With FSUIPC keypress assignments to can assign all sorts of key combinations which won't interfere with anything else. But you don't program them to send key presses, but FS controls. No, not if the external program is grabbing the keypresses using Windows hot key facilities. Nothing else can see such keys. Regards Pete

Why don't you try showing me the Install log, as I asked yesterday? If the installer created the FSX Modules folder it will be in there. I can't help you unless you try to rerad what I say and provide the information requested. Pete

The log only shows that the GlobalSign certificate didn't verify correctly on your system. It does give an error number (0x80092026) which may be useful if I have to refer it to GlobalSign or Microsoft, but meanwhile you are still not providing haslf of the information I asked for. i.e. what does the signature checking say if you check it via the DLL's properties, and what version of Vista are you using (version and language). Also, please check in Internet Explorer to see if you have the GlobalSign root listed there and whether I have been listed an "untrusted" rather than "trusted". Go to Tools - Internet Options - Publishers. In "Trusted Root Certificates" there should be "GlobalSign" and "GlobalSign Root CA". In Trusted Publishers you should be able to find me ("Peter L. Dowson", but maybe not yet, if you haven't clcicked on such. I certainly should NOT be listed in "Untrusted Publishers". There was a problem on one Russian installation which used a Cyrillic character set as part of the FS path name. However, yours appears to be okay ("C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES" -- except, of course, that the Program Files location is the very worst place to let FS install itself into on Vista. Apart from FSUIPC you may get lots of problems from other add-ons as Vista protects all folders in "Program Files". If you've only just installed it it may be a good idea to uninstall it and reinstall to somewhere like "C:\FS9" -- I think you'll get far less hassle in the future, as you add more things. Regards Pete

Thank you. It isn't very often someone posts good messages here! ;-) Regards Pete