Pete Dowson

I need you to follow the same diagnostic steps shown in the thread to which you referred. I also need a complete list of addons. If the files are big, ZIP them (they will Zip up really small as they are only text) and send them as attachments to my email, which you know already. I cannot do anything with the information you posted above. I will reply here, not by email. The production of the FSUIPC options dialogue is totally dependent on SimConnect prompts from the menu bar, so I'm thinking another add-on has interfered with or messed this mechanism up. BTW, "UseProfiles" defaults to Yes, and your INI file shows Profiles were in use. By changing it to "No" you've now got sets of assignments and calibrations which are not being used -- yu really now need to start again, deleting your FSUIPC4.INI file so a new one is created. Profile use or not has nothing whatsoever to do with the menu mechanisms. In fact nothing has, only the signal from SimConnect saying the FSUIPC options has been selected. Pete

Okay. It is now assigned correctly, and it proves it isn't just the keypress. The action must be coded into the add-on aircraft. I'm afraid you will have to talk to their support, because there's no way to fix it as a user. Pete

Oh dear. The current version is 4.936 and was released a few days after P3D 2.3.11345 is order to cope with the differences! Please always use the supported release! Version 4.934 is no longer supported! Pete

Well, good, but next time I ask for a log, please do NOT enable all those log options. I only needed to see the basic log, exactly as I asked. just run the program, close it, get the Log. Do NOT go into the Log Options and check options or press buttons, please. Such things might come later if it looks like it might be of use, but as it is the log was useless for the purpose intended. Pete

Two points: 1. You are now using button 0 on Joystick 0. Previously you were using button 0 on joystick 2! 2, Clearly button 0, joystick 0 is NOT assigned to a control, but to 'S' still. Look at the part of the Log above which very clearly shows this. The assignment line in the INI is 20=P0,0,K83,8 In the previous log you had: 11=P2,0,K83,8 Seems you are changing joysticks, but not the way you assign! Pete

And for 10 years you've had this assignment for this aircraft too? Is the Aerowinx King Air that old? What's changed if it is doing this now but not before? That's the number of the button as seen by FSUIPC, the one it presumes you are assigning. Why should it not be there? Do you think your button has a different number? The one you used in the example log file you posted earlier was 0, as shown here: [Buttons] 11=P2,0,K83,8 You most certainly have 'S' assigned to button 0. You have a button 24 which is constantly flickering on-off-on-off ... That is what is being detected. I would maybe guess that's the reason for these entries in the log, constantly telling the A/P to turn Back Course approach mode off: But really all this is irrelevant, a distraction. All I suggested was assigning your button to the FS control you want to use, NOT to the letter 'S'. Use the right-hand side of that buttons screen you showed me (... for some unknown reason?). Assigning to controls is always more efficient and more reliable. Only assign to keypresses for add-ons which really need keypresses, as your Aerowinx aircraft seems to, for that AP disconnect. Pretty much all FS actions have assignable controls. All the keypress would do (if not intercepted by an add-on) is go through the FS keyboard assignment tables to select the FS control you could have assigned to in the first place. You should also check the documentation of the Aerowinx aircraft to see what other keystrokes it assigns, and see if they are changeable. They usually are, in most decent add-ons. Pete

Thanks. It's on my list for when I've caught up ... Pete

Well, I've no idea what aircraft you are using (you still didn't say), but look what it does with just the S key used: So, my question now: why are you assigning a button to the S key which, in FS, is assigned to the "view mode" control? Why not simply assign direct to the view mode control.? Pete

Exactly. i used to up for that sort of thing, and did it a lot for FS98 through to FS2004, but I'm too old now ... Pete

Is the aircraft one of the defaults, or an add-on? I'm afraid it does not contain enough information -- it looks like you did not enable the Event logging, only the Button/key logging? BTW rather than attach logs as files it is easier for both of us if you simply paste heir contents into your message. Envelop them using the <> button above the edit area. Pete

If you rename FSX you need to also rename the files associated with FSUIPC. This is to allow different settings to apply to different loads of FS just by changing the name. Please check the FS Modules folder -- you will see a differently named FSUIPC4 INI file, which will have defaulted, and a LOG file. Just make a copy of the KEY file renamed the same way. This is described in the section "Multiple INI files" in the Advanced Users guide. It' isn't something available through the SimConnect interface, and it isn't anywhere near the AI traffic density variables. I think it is deep somewhere in the scenery DLLs, but I've no idea where. If someone has the patience and knowledge of these areas and wants to find where it can be adjusted, I would certainly add it, but i'm well past my hacking days I'm afraid. Sorry. Pete

I never noticed the .pnl files. I'll add that in the next update. Not sure when that'll be though. You can do it by simply adding one line to the [AutoSave] section of the INI file. Please see the Autosave section in the Advanced User's guide for FSUIPC4. Pete

Hmm. Never seen a message like that from SimConnect. How strange. Well, registering it only enables the user facilities (assignments, programming, Lua plug-ins, autosave etc), it doesn't change anything it is doing with SimConnect. There's not much information here. Please try again, get the symptoms, then close FS and show me the FSUIPC4.LOG file, from the FSX Modules folder. Paste it into a message -- best to use the <> button above the edit area to envelop it. Pete

1. Yes, SimMarket offer both registration keys for less outlay than if you purchase them separately. You still do two downloads though. 2. Of course documentation for FSUIPC and WideFS is included in the ZIPs. You can download them both and install them and look at the documentation BEFORE you sepnd any money if you have doubts. I can't comment of how easy it is to set FSCommander up, as I don't use it. Maybe that is documented too? 3. Sorry, I don't have FSC or the NGX. 4. WideFs runs best if all computers are in the same workgroup. I don't know if Win8's default workgroup name is the same as Win7's (WinXPs was not), but that's easy enough to change. Computers in the network must all be running WinXP, Vista, 7 or 8. Earlier than XP is no longer supported. Pete

Yes. The same Wideclients will be okay in the Client PCs, but of course you need FSUIPC4 + WideFS7 for FSX, not the FSUIPC3 + WideFS6 you have in FS9, in the FS PC. There's no overlap or commonality at all between the two, FS9 and FSX. The cannot be run at the same time on the same PC, but that is the only restriction. Pete

I wouldn't have thought they used the same FS control to operate AP power. That would be rather daft -- it would happen using the normal keyboard actions in FS too. Have you checked? My betting is that you have more than one assignment to that button, maybe in FS as well as FSUIPC. Use the Event logging in FSUIPC's logging tab to see what controls are being sent when you press the button. Pete

This appears to be the same question you asked in a separate thread. Please see my answer there. Pete

If the value in that offset is always 1 or 2 (already), then all you needs is to use "toggle bits" with a parameter of 3 instead of "Set". You can do such an assignment direct in FSUIPC options, you don't need to edit the INI file. If it isn't 1 or 2 initially, but 0, say, then, yes you'd best use a flag to get a goling action between two "sets". But check first. Pete

Have you checked the User Contributions subforum? I'm sure there are lots of examples of just what you are talking about, and there may even be one there already for the popular PMDG 737NGX. Pete

Ooops! Sorry. No idea when that went missing! I've put ity in now -- Download Links subforum has the link to the Lua package. The Lua examples are just that, examples for folks to develop their own. Odd ones modified for some users in threads don't necessarily get back as the main examples. The only changes I would normally do would be to correct errors or re-insert missing ones, as now. Thanks, Pete

Please run FS, try the connection, close it down, and show me the FSUIPC4.LOG and WideServer.LOG files. You can paste them into a message -- use the <> button above the edit area to envelop them, separately. Pete

Hi Paul, It's not been requested before, unlike Buttons, so it was never implemented. I also never suspected key presses would ever be so widely used, as usually they merely translate into controls which could better be assigned directly. I'll have a look to see how much work it might be. I'm loathe to disturb too much code -- that's how errors are introduced -- and the code in that area is almost as old as FSUIPC (i.e. 15 years), but if it looks easy and relatively isolated I'll add it -- FSUIPC4 only, though, not FSUIPC3. Not sure when I'll get to it. Still catching up at the moment. Pete

Please run FS then close it and show me the FSUIPC4.LOG file from the FS Modules folder. Also, find the FSUIPC4.KEY file, ZIP it (VERY important) and send it as an attachment to me at petedowson@btconnect.com. Pete

Surely you don't need all of the SDK, documents, multiple language packs etc. What component are you talking about here? Pete

I always debug serial port (COMn) problems using the free debugging tool "PortMon" from http://technet.microsoft.com/en-gb/sysinternals/ Pete