Pete Dowson

That's the process which needs to be terminated then. Right .. so that's just some sort of start-up process, which creates the other one. Hence the problem. I assume, then, that "pdc.exe" is gone by the time WideClient tries to terminate it? Seems the author has done well to evade any sort of control by another program! I suppose therefore that none of the facilities offered by WideFS to send stuff to it would work? Regards Pete

Phew! I'm lost now. What to do? What to do? ... Regards Pete

LOL! no, there's only me. I've made your new post sticky. If you'd like to edit your original (I *think* you can do that, as its originator -- if not let me know) to refer to the other sticky for "add-ons that do work ..." then I'll remove the argument and everyone will be happy .. I hope! ;-) Regards Pete

Good. Well I use the Process ID i get back when creating the process. The only thing I can think is that the process I start is starting another process, and that's the one I'd need to get to. All I can think is that you use a KeySend with a keyboard code programmed in the Wideclient.INI file to send, say, CTRL+C to the correct Window (the one with the correct Classname, perhaps?) What process(es) is(are) listed in Task Manager for FDC? Just the one? With the EXE name you started with? Yes. Dave March might be able to suggest something, or he could discuss it with me. He has my email. Regards Pete

Okay. Then, assuming you have them assigned in FS, next go to FS's assignments and check that the sliders are correctly set -- sensitivity max, null zone min. Shouldn't be -- they don't really interfere with the routing of controls to surfaces. Anyway, it's easy enough to check: load a default aircraft and try that. Pete

It sounds very much like you've not calibrated the yoke in Windows Game controllers, to start with, and possibly you have the Sensitivity and Null zone sliders in FS set all wrong. You should have sensitivity all the way right and null zone all the way left, at least to start with. Merely installing FSUIPC makes no difference whatsoever. If you actually calibrate your joysticks in FSUIPC, then you should do it properly. Else don't bother. To do it properly please just follow the simple numbered steps outlined in the joysticks calibration chapter of the User manual. Regards Pete

Well rudder is just another FS axis of exactly the same type as elevator and aileron. Those three are the prime flight controls. The more unusual ones to have on an axis are flaps and reverser. So, have you assigned these things in FSX? (Other than reverser, of course, because FS doesn't treat that as a separate axis). Or in FSUIPC? If in FSUIPC have you assigned "direct to FSUIPC" or to the FS control? I've no idea because you don't tell me very much. There are so many ways of doing things. Calibration is the same for everything, but ASSIGNMENT can be done in several different ways. Maybe you really mean you haven't assigned any axes for those functions and that is what you are concerned about? I cannot guess these things, you have to tell me. The reversing facility can be done in several different ways. I think the Saitek throttle unit has a button which gets pressed when you pull the lever right back. That's what most folks use for reverse -- assign the button to "THROTTLE DECREMENT" and set it to repeat. That can be done in FS or FSUIPC. If you want a separate lever for reversing you must assign in FSUIPC as "direct to FSUIPC". There reversers are clearly listed for assignment. The other way for reversers is to use a portion of the throttle axis. That's a little more complicated, and is done by assigning individual engine throttles in FSUIPC or FS and calibrating in FSUIPC with an idle and reverse zone. It's a little like elevator or aileron calibration then, except the idle area won't be central. All that is clearly described in the manual. Regards Pete

Excellent! I see you've done so! Thank you! Pete

don't wanted to "destroy" the sticky, but if you wish I will post this statement there, also... Of course. Anything helpful, and non-destructive, will be most welcome! You could put in some links to your excellent examples too! Regards Pete

Of course. Perhaps you could add this excellent point of view and advice to the Stickie? Please? Regards Pete

Hmm. I thought the problem was fixed in PFCFSX.DLL 4.34, but I could be wrong. Maybe it was 4.35. The same problem did afflict FSUIPC4 too, before 4.60. Please try the latest PFCFSX version, 4.353, from the Updates announcement at the top of this Forum, and let me know if that fixes it. (You might also want to grab FSUIPC 4.623 whilst you are there). Regards Pete

Sorry, I don't understand. what is "PFC's mini-window"? Do you mean the PFC Options dialogue, obtained from the FSX Add-Ons or FS9's Modules menu? If so I need a lot more information please: FSX or FS9 or some other version? Version number of FSUIPC? Version number of PFC.DLL or PFCFSX.DLL? If you mean something else then I guess you are mixing up someone else's program with one of mine? Pete

The installer produces a Log file, showing exactly what it did. This is displayed on screen AND saved to disk. It is the Installer which created the FSX Modules folder -- there isn't one in FSX by default. So if there is a Modules folder, it WILL contain FSUIPC4 and the Installer Log, plus a sub-folder containing the documentation and Lua package. It sounds like you are being misled by having Windows hide file extensions from you. In Explorer go to Tools - Folder options - View and turn off the "hide extensions ..." setting which Windows infuriatingly sets by default. Then show me the FSUIPC4 install log you'll find there, and also, if there is one, the FSUIPC4 log. Both are ordinary text files and you can paste their contents into a reply here. Regards Pete

Not sure which version of that you are using, and the lastest isn't available there, only on site where I'd need to register, so I tested with this: It seems that all of its windows are top-level ones, not child or owned. That's the problem -- and the windows enumeration of the Process's windows gives them to me in reverse! So I had a choice: either always assume they would be in reverse, and always ennumerate them just to get a list, then close them in reverse order. Or assume all I needed to do was close the last one, none of the others. I think the first choice would be dodgy. Unless I left a long enough delay I might still close one of the lesser Windows before the main one had recorded it correctly for resurrection. so I chose the second method. At first that didn't work -- I found this was because the application first opens an invisible Window and closing that does not close the main application! However, modifying my code so that it closes the last VISIBLE window worked! Try it. Version 6.822 of WideClient is attached. Change the INI "CloseN=Yes" parameter to "CloseN=Last" to get this alternative behaviour. Let me know if it also works on vasFMC. If not I'll need TO INVESTIGATE DEEPER -- perhaps you could email the ZIP for it to me at petedowson@btconnect.com. Regards Pete WideClient6822.zip

Right. what it does is this: By creating the process in the first place it gets the ID of the main thread. It does NOT automatically get the handle of the "top" window -- the one you want me to close. In fact unless all of its other Windows are child windows, there's really no such thing as its "top" or "main" window as far a Windows (the operating system) is concerned. When it comes time to close, I have no idea which Window it is which should receive the WM_CLOSE message -- unless there's only one Window in the process which isn't a child (then it is trivial). To make sure that Window gets the message to close, I have to ennumerate all non-child (i.e. top-level) windows in the program, sending WM_CLOSE to each one. Generally programs only have one top-level window, so this works fine. It sounds like in your applications there are a number of top-level windows, and the one to be closed to suit your needs is one of the later ones in the sequence Windows gives them to me. Maybe if I added an option to only close the LAST one that Windows ennumerates, that will be the first one opened and the correct one to close. However, that's only an assumption. I'd really need to trace the actions of one of the applications to see if this could work. Are they freeware? Can I simply install and run? Where do I get them? I am going to need your help. Regards Pete

Hmm. I don't think I do that, but it was written such a long time ago I honestly don't recall. I'll check now and get back to you... Regards Pete

Whether you use real weather, user-set weather, or program-fed weather, makes no difference to FSUIPC -- it cannot even detect what weather you use inside FS! You have something else going on. Maybe you are using an external weather program which changes the options? Even so, it cannot affect your INI file, so your required options are always reloaded next time! If you think things are going wrong please show me: 1. The FSUIPC.INI file, so I can see your settings, and 2. The FSUIPC.LOG file which shows the options set and any changes. It will also show me the VERSION NUMBER of your FSUIPC, which is of paramount importance. Both files will be found in the FS Modules folder. If you are not using a Supported version of FSUIPC, please update first. The earliest supported version for FS9 is 3.98, and there are later interim updates available in the Updates announcement here in the Forum. Regards Pete

If you mean FSUIPC options set in the Visibility tab, they are saved in your FSUIPC.INI file and reloaded each time you run FS. There are no settings "lost" unless you delete the INI file. Pete

Well that's certainly the windows system error which, according to assorted places (Google it yourself) occurs because of an ultra-safe setting in the Registry. See This for example: http://blog.stealthpuppy.com/windows/wiion-failed I'm afraid all I can do is follow up all the Googled references, but it would be quicker for you to do so yourself. This is only the second or third time, in nearly four years, that this particular error has occurred, and the other one or two have either fixed it or never come back to say. Regards Pete

The log is incomplete. You need to let the installer finish so that it logs the error number. Have you tried running FSX? Is there an FSUIPC4 log file? Did you follow up the other suggestions? Pete

Please show me the Install log and, if you've tried running FSX, the FSUIPC4 log. Both will be in the FSX Modules folder. I need to see these because they contain more information. Try this thread on installation problems which I think must end successfully (though the complainant never confirmed): viewtopic.php?f=54&t=80782&p=488851 The final fix must have been the Registry edit. Regards Pete

If you'd like to post the starter for this, in an appropriately entitled thread, I will make it "sticky". Regards Pete

FSUIPC does not use the Internet. It has no networking or internetting code in it whatsoever. Why do you think it's to do with the Internet? You don't provide any information for me to help you further. Regards Pete

Correct, exactly as described in the documentation. Only Registered users get the User facilities. That's the point. Program access is a different matter entirely. Note that FSUIPC version 3.6 is over four years old and unsupportable. Please update to a supported version (3.98 at least) before coming back! Regards Pete

It only means that it is licensed to use FSUIPC without you paying for the FSUIPC user facilities. You don't need to do anything else. If you mean FSUIPC4, if you want to purchase it you do so at SimMarket. All is explained in the documents installed when you run the FSUIPC4 installer. But you don't need to just to run licensed add-ons. Regards Pete