Pete Dowson

Not a good idea to just copy files about, generally. There are several aspects to FSX installation which are only done by the actual installation. Task bar? Do you mean the FSX menu, when you press ALT? The log simply shows the installation was okay. Once the installation works, and you run FSX, it is the FSUIPC4.LOG, in the modules folder, which will show what is happening. Is there one? I suspect, if you've been messing around moving FSX files from one place to another you may have a messed up FSX installation. Check for the Log first. Pete

It looks like you haven't actually run FSX under that user name (Ten Katen) yet, so there's no CFG file for FSUIPC4's installer to know where to create the DLL.XML file needed to make it run. Best to get your FSX installation set up properly first, before adding anything at all. Set its options the way you like, make sure it all works correctly, then, and only then, start adding stuff like FSUIPC4. Regards, Pete

Ah, yes, I did! One of those English idioms which may not be understood by all. The "last way" is usually meant to indicate the "least desirable". Did you check that repeating was definitely off? I really cannot think of any other reason for your problem. Regards Pete

You have a faulty installation of FSX, one where the original SimConnect section, installed from the main DVD, is corrupted. Please refer to the "FSX Help ..." Announcement above, which tells you how you might succeed in re-installing that component. Regards Pete

What does that mean? You've been elsewhere and go some first? Or what? Sorry, I don't understand you. If you mean my response is too slow for you, I'm sorry, but I do answer as soon as I see the questions here. I'm sure you can't have seen that much of a delay. Most support sites offer 24-72 hour turn-round. I only take more than a few hours when I'm away on holiday or, like this last weekend, actually away at a Flight Sim function. Is that wise? What "PFC documents" are you referring to, here? Why? Best to let it connect automatically (assuming your Windows versions allow, and you have them both in the same WorkGroup), or at least only use the name of the Server, not an IP address which may change. Sorry, do you mean you set the control to repeat, or you haven't done so? If you have it repeating I suspect it might crash SB3 -- I seem to remember a bug in one version of SB3 when a PTT received whilst it was already processing one would crash it. In that case you really do need SB3 support to identify the cause. All the PTT option does is broadcast a standard Roger Wilco/SB3 compatible PTT message on the FS PC and every WideClient. What happens then is completely up to the program receiving it. The most likely problem is that you are using a copy of SB3 which still has that repeat-crash bug in it and you have the control repeating, or you are pressing it more than once, too quickly. Regards Pete

No, there's no dummie's guide labelled as such -- the User guide is the dummie's guide, as it is so damned simple! Users are often dummies, you see! And no "setting up" is needed at all if your Network is okay. You do need to know which part goes where. It tells you. Never heard of VAFs. ASX doesn't use either FSUIPC or WideFS. I don't see how that solves your memory problems. Where does 4->1Gb and graphics card come into it? Seems you are a little confused, or are you missing saying something here? Pete

Negative? Sorry, I don't understand. All I did was point out what must now be obvious to you, and that is that the autofeather arm switch in that cockpit is operated NOT by the FS autofeather arm control, but by the afterburner 2 control. Therefore, if you want to assign a button or key to it, that is the control you have to use. You found this out yourself using the Logging. I can do no more to help if you still don't get it! I'm sorry that you seem to misunderstand me so much. There's nothing at all "negative" about thinking that this strange use of an different control altogether is "weird", surely? I don't know why you think that! It certainly is weird, not negative! :-( Pete

Okay, thanks. I'm tidying up the documentation a little, and will add your example -- thanks very much! I've also fixed a long-standing bug in the "AppOnly" shutdown facilities in WideClient, where the applications shut down (leaving Wideclient running) okay but the "RunReady" applications then do not restart when FS is up and running again. The new WideFS release will be 6.78. I've updated the FS9 WideServer.DL version number too, to match, though there's actually no change in that module. Regards Pete

Assigned button for what, exactly? Do you mean PTT? (Push to Talk)? If so, how have you assigned it? It sounds as if you may have multiple assignments to that button. Have you assigned it in FSUIPC or in my PFC driver? And what have you changed in the WideClient INI file on the Squawkbox PC? And what keyboard are you using which "works fine"? How does Squawkbox terminate? It it a normal termination or a crash? Maybe you have something set incorrectly in Squawkbox's own options? I'm afraid I don't know the program at all, so you will probably need to ask SB support for help with that. Is the PFC yoke connected via a PFC digital control system and calibrated in my PFC driver? Normally PFC yokes, on their own with no digital quadrant or other control system, connect as normal joysticks. If so I wonder why you have PFC.DLL in the modules folder, as it isn't used and shouldn't be there! More information is obviously needed here. Regards Pete

Hi Bill, Take a look at the "mouse macro" facilities in FSUIPC -- anyone can generate macros for any panel which is written using the standard C/C++ panel SDK, one with the regular mouse rectangle structures in its coding. Once generated and tested, the panel doesn't even need to be visible any more, only loaded in memory, as the macro simply calls the routine itself rather than emulating the mouse action. Regards Pete

Best peruse the User Guide first It was intended that FSUIPC4 contained the same visibility facilities as FSUIPC3, but as it turned out the ability to do the same is severely restricted by the way FSX works. The visibility options are, in fact, removed from FSUIPC4 by default and only re-introduced by user INI-file option for user experimentation, without guarantee. In my experience they work sometimes, but produce some odd graphics effects at other times. They would be more successful when used merely as a filter on Weather program inputs (as opposed to attempting to change FSX's own weather), but the major weather program for FSX (ActiveSkyX) does not use FSUIPC4 in any case so the latter does not filter its inputs. However, ASX is supposed to be capable of providing its own limits -- it is just that FSX sometimes defeats these efforts. All in all, I would say that if your only use for a registration of FSUIPC4 is for visibility control, then don't bother. I wouldn't want you to buy it and then regret it. Regards Pete

When you run the installer it produces an Install log, a list of what it did and what it found. This is not only shown on screen for you to see clearly, but also saved in the Modules folder in FSX if possible. If it wasn't possible to create that folder you can use the "Save" option on the Log window in order to save the Log where you want. The reason this log is produced is so that there will be ample information to show why you have a problem! Therefore it is that information which you need to find and bring here, if you want answers. None of this is in any way related to whether you are going to register FSUIPC -- that comes later, at the end of a successful installation. Regards Pete

Yes it should be a button. A button with null label, I assume, else you havea button with the same label as one of the GoTo's. When you've got a version you are happy for me to publish, let me have it and I'll revise the User Guide with it as a more advanced example. Thanks, Pete

Yes, I see that -- as long as you did want the button numbers shown. But then you didn't need any entries for those positions (as in the example for Page 7 I sent back). As I said, the only error was this line: 417=Bl4G260"G1000\rMFD""" which makes no sense -- it says it is both a Button and a Go To instruction. In fact it is treated as a button and labelled so, giving you two buttons with that label. one being a Go To. I don't know VoxATC, but you can invoke FSUIPC (for instance) with an ALT+M F (FS9) or ALT+D F (FSX) sequence (multiple key assignments, ALT_x first, then the letter after), because these do arrive in time. You can't get FSUIPC to send more keypresses afterwards because by then Windows is in its dialogue mode (this is FSUIPC, as it uses dialogues). VoxATC may be different. Pete

Look in the FS Modules folder. In there you will find a file called "WideServer.LOG". Show me that. Also, on your client PC, look for "WideClient.LOG" in the same folder as WideClient. These files contain all the details of what is going on. I cannot help without seeing those. Also, you ALWAYS need to specify version numbers, please -- FSUIPC and WideFS. (You don't even say if you are using FSX, FS9, FS2002, FS2000, FS98, CFS1 or CFS2). Most of that is irrelevant. If you have a firewall blocking WideFS, it cannot work, nor will the automatic linking work if you have your PCs in different workgroups. Not normally, but you have to unblock it if it is blocked, obviously. Regards Pete

Okay. Please download this: http://fsuipc.simflight.com/beta/WideClient6775.zip It fixes the problems on the last page (those representing positions later than the max 432), and also allows definitions to go up to space 1023. Hopefully that should be enough for all applications -- after all there are only 288 buttons, so this allows a lot of unused or management spaces. I tidied your Page 7 a little but I'm not sure it is how you intended. I replaced your lines with just this: =========PAGE 7 MISC =================================== 390=4G0r"SYSTEMS" 391=Bl"" 401=Br"" 402=4G325l"GPS" 403=4G65r"AUTO\rPILOT" 404=Bl"" 414=Br"" 415=7G390l"Misc" 416=4G130r"NAV\rCOM" 417=Bl"" 427=Br"" 428=U 429=4G195b"G1000\rPFD" 430=4G260trb"G1000\rMFD" 440=Br"" Perhaps you'd like to look and see if it is what you intended before i add your super example to the documentation with your name on! :-) Thanks & Regards Pete

Yes, it worked fine. Thanks. Okay, but let's make it work fully first! ;-) Well, not here - but Buuton 51 and some blue and red coloured buttons. Looks like a load of uninitialed rubbish is getting used. i'll fix that and upload a revised WideClient today or tomorrow. Meanwhile there are some oddities in your parameters. first, on that page 7, did you want all those default labels with button numbers? The reason they appear is because you still have some null labels specified, i.e. 391=Bl"" 392=B"" 393=B"" 394=B"" 395=B"" 396=B"" 397=B"" 398=B"" 399=B"" 400=B"" 401=Br"" instead of using a space, " ". Then there's one line which makes no sense, though it seems to have been interpreted more or less okay: 417=Bl4G260"G1000\rMFD""" I'll work on the problem in WideClient. Maybe you could see what you intended with these lines? Thanks! Pete

Not for me! I don't need the situation clarified -- I don't even use such an aircraft. But you surely have clarified it for yourself, not me? It looks like this "Aeroworx" aircraft has implemented its autofeather switch using the "Toggle Afterburner 2" control -- very weird! So, you will have to use the same control, obviously. Regards Pete

FSUIPC 4.40, some time next week (i.e. 10-14th), I hope, if I can find time to update the documentation. Should be okay -- I have an FSUIPC3 version to do too. Regards Pete

Have you checked the FSUIPC log to see if there are any errors? You'll find it in the FS9 Modules folder. If you installed FS9 into "Program Files" (which is where it would go by default, then you will probably have problems with any add-on which may need to write to any FS folders, as Vista protects them all. Furthermore, because Vista recognises FS9 as not being Vista-aware, and likely to want to write to its own folders, it creates aliassed folders which look like the real ones and which can be written to but which aren't actually read by FS! To avoid all this hassle it is best to install FS9 (and any other non-Vista add-ons) some place else, NOT in the Program Files folder! Finally, if you are running FS9 with elevated administrator privileges (e.g. by "Run as administrator", or setting a property for this), then every FSUIPC client application on that same PC will have to be run at the save privilege level, otherwise Vista stops them talking to each other. It is best to only ever use "run as administrator" for installation and registration, never for normal operation. Regards Pete

Did you try looking in the User Guide at all? There is a section called "De-Installation", and it is even listed in the contents on the 2nd page! Pete

Turn on "event logging" in the FSUIPC logging page, then test both the assigned button and also the mouse click, and see in the FSUIPC Log file if both send the Autofeather Arm control. Show it to me if you aren't clear what is going on, but tell me the order in which you tested things. Since you started a new thread just for "AutoFeather", and I don't recall your original query, I do not even know if you are referring to FS9, FSX, or some other FS, or which aircraft you are using for this. If it is an add-on aircraft, not a default, it may be that it does not use the FS facility at all, but does its own thing. Regards Pete

You are not allocating a wide enough zone for the Arm position, then. One or two close values will not suffice since it is virtually impossible to find the exact same position again -- especially considering that the Delta value is probably defaulting to 256 or 512 in any case (i.e. changes less than that are being ignored). The zone would need to be larger than the delta, obviously. The spoiler system and its calibration method, with an Arm zone, is used and tested extensively over several years and on all sorts of joystick axis inputs, from the very cheap to the very expensive, and it has never failed to operate yet when correctly calibrated! Regards Pete

Not by default, at least until FSXI or ESP2, assuming they fix the severe problems in doing anything useful with visibility in FSX/ESP. You can of course enable the visibility options tab now (and always could in FSUIPC4), and try these things. But I cannot guarantee that any of it will work as you would hope or expect. That is why the options are not put in front of you by default -- because I don't think they work well enough. If you hadn't even realised that the Visibility options were still there (but optional), please do, very soon, have a look at the User Guide supplied with FSUIPC4. Even the Visibility section is still there, and in the contents list (clearly marked as optional), and with a red statement at the start of the section telling you how to re-enable it. Regards Pete

I've found the bug and am in the process of fixing it now. Please look out for FSUIPC 3.849 and 4.332 in the Downloads announcements above later today. Sorry, but you'll either need to re-do the assignments or edit the INI file as you surmised. Regards Pete