Pete Dowson

Using WideFS, you mean? WideClient can certainly relay keystrokes to FS via WideServer (part of FSUIPC), but the best way is to assign, in Wideclient.INI, a "virtual button" to the "M" key. Then you can program the button in FSUIPC to do whatever action you wish that may be assigned there -- selecting Map view included (I think that is performed by one of the "View Camera Select" controls -- it'll be 0, 1, 2, 3, or 4. Not sure which). Please refer to the "ButtonKeys" section of the WideFS Technical document. It is quite near the end. Regards Pete

Sorry, no idea. I need more information. Like version number of FSUIPC? (If not 3.90 or 4.50, update first). Can you enable Button and Event logging (only) in the Logging Tab, please, and see what is going on via the Logging? Pete

It's actually supposed to be about 12 seconds, and is a safety feature to prevent loss of controls because a fly-by-wire program or gauge happens to stop working (maybe terminated). That's normally something done by program. Why would you want it done by pressing a button? The only way I can think of doing it is by using a Lua plug-in, to loop re-writing the disconnect flag every few seconds 9with a "sleep" for the rest of the time), until you release the button or press another to send it a flag. Lua plug-ins, when installed in the Modules folder, can be assigned to a button and made to recognise flags set or changed by another or the same button, even read buttons themselves. Almost any failure mode could be programmed via Lua plug-ins as they have full read/write access to all FSUIPC offsets. Regards Pete

And, in the latter case, repeating immediately -- or are you suggesting another delay to decide whether to repeat or not? You also realise, I assume, that the latter option would preclude having a separate assignment for the button release? In order to determine whether to do the short-time or the long-time action, the release would need to occur before the short-term action could occur. It is going to be very complicated for ordinary users to understand precisely what is going on, I think. What, exactly is the application for this you have in mind, please? Regards Pete

The problem then is how do I differentiate between a "long press" and someone just normally wanting to repeat the current "press and hold" programming? I don't see how you could have both. Incidentally, in the new releases just out the button repeat action has a delay (adjustable in the INI file), so you can make, say, one increment easily enough and hold for faster repeating. The default gives you something like 2/3rds second. 2 seconds is a long time pressing a button, especially if you are trying to fly and airplane at the same time! ;-) Regards Pete

Glad you/we found the way, eventually! Well, it shouldn't. Trouble with my place in this is that I'm in it too deep and what seems obvious to me is quite the reverse to some, as I find out occasionally in this Forum. So, I stick to what I do best -- programming, and technical support, and try to encourage users to help each other. It works quite well mostly, though no doubt things could be better. But isn't that true of most things? That would be great -- any way you'd like to do it. If you'd like to send anything to me as an attachment, send it to petedowson@btconnect.com. Within the next hour or two, in fact. Well, the 'new' options are (or perhaps were, by the time you get to look) listed in the Changes list in the Updates announcement above, where they've been accumulating over the last three and a half months. This new release is merely the culmination of lots of work, Beta testing and feedback, mostly through this Forum. There's nothing drastically new to anyone who's been keeping up to date here, but there is quite a lot for those who haven't. I would be very grateful for anything you feel you can contribute. Don't worry about the timescale or committing yourself -- no commitments either side, as you say. Oh, and Bon Voyage! Best Regards Pete

4.28 is rather old and is certainly not supported. If that installed okay them most certainly the current version (till tomorrow), 4.40 should install. Installation of SDKs is completely irrelevant to whether FSUIPC installs and works -- in fact it is completely irrelevant to all except those who wish to use the SDKs. So what on Earth your installing of them did to change anything I've no idea. There is a "SimConnect.msi" install package in the folders the SDK installs -- in fact the SP2 version will have the SP1 and base SimConnect.msi's too, probably under "legacy", so after deleting the SimConnect folders those are a more direct way to repair. However, I didn't think they were executed just by installing the SDK. If they did, that might explain your solution -- they would have put the missing two WinSxS SimConnect folders back in shape. If that's all they did it sounds like your earlier "repairs" didn't succeed in doing this. Regards Pete

This is the typical problem reported when your base ~SimConnect installation is corrupted in some way. From reports it sems it stems most often from attempts to uninstall / reinstall FSX itself. I think MS have made a bit of a mess with the "side-by-side" library system. It sems that it installs okay (normally) but it is a devil of a job to uninstall! It is also very odd that you appear to have no SP1 version of SimConnect recognisably installed. That will really stop quite a lot of FSX add-ons which are written to use that version. By tomorrow morning I will have released FSUIPC4 version 4.50. This version will use any old SimConnect it can find so the dependency on having the base version installed for it to load disappears. I had to make this change in order to have one program working on both FSX and ESP -- with neither FSX nor ESP being developed any further the overhead of maintaining two versions was not justified. So, tomorrow your problem with FSUIPC4 may be fixed. But I'm afraid that won't help with ASX or possibly any other SimConnect client program. How? What exactly did you 'remove', and surely not all? Initially just remove the one WinSxS SimConnect relating to the base version, 60905, so you can repair. I think you will now have to completely uninstall Acceleration (and SP1 if installed separately) and FSX itself, in that order, then check and delete any WinSxS folders relating to SimConnect, then install FSX from scratch again. RUN FSX in that state and check it before adding Acceleration -- if you don't do that I think it goes wrong, as files need to be there for Acceleration to operate on which are only created when FSX is run. I'm not sure about your ordering of SDK updates either. Do they each need the previous one in order to install? I didn't think so. I would have thought you could install the SDK after FSX, from the DVD -- that's needed to provde you own the DeLuxe edition -- then just install the SP2 SDK until after you've installed (and checked) Acceleration -- i.e. completely leave out the SP1 and SP1A versions? Doesn't that work? Regards Pete

"Texture" entry? Really? What is that? How does it relate to an ATC name? I expect it reads the aircraft Identification which FSUIPC gets from FS. FS supplies it based on the ATC information near the beginning of the aircraft.cfg file. If sometimes you get one thing and sometimes another it will be because you have those variations in your Aircraft CFG files, that is all. If you make them all the same, it will be more consistent. If the ATC data really does say "GWI-Germanwings_D-ABCD" or anything like that, then your PFE program has no choice but to voice the GWI phonetically. You are lucky it does not try to voice the dash etc. the same way! Try my free TrafficLook program to display AI traffic data. The names PFE uses will be shown there too. Regards Pete

Sorry, that's confused me already. Which "same" are you referring to? This thread seems to have wandered around a bit. Not only that, is is over two years old! So, it your problem "I cannot install FSUIPC4"? If so I need to see the Install log in the first instance, please. Never ever rename things in the WinSxS folders. That is going to really cause you problems. Looking back I don't see any such "method" being discussed except over two years ago, and then there was no FSX SP1 or SP2 or Acceleration, just the one layer of SimConnect to sort out. It sounds like you really have a screwed up system. Did you read my FSX Help announcement and try anything there, regarding fixing the base layer SimConnect? I think that's all you should need to do -- delete the base SimConnect folder and run FSX repair from the original DVD. Regards Pete

Well, it is a collection of information of possible interest to advanced FSUIPC users who want to delve deeper into some areas. It is information which would be out of place in a user's guide as it is for detailed reference only, not general use, and certainly not tuition. That would not be an Advanced User's reference but a programming tutorial, which I am most certainly not qualified to write. If you are volunteering to write one i am sure we will all applaud your efforts! Thank you for finding that typo just in time for me to correct it before the update due out this Friday! I'm afraid I did not comb through the user's submission before appending it. I was just too grateful for the help, I suspect! ;-) Yes, I suspected something was up with your logic earlier on in the thread, but, honestly, I did not have time to think it through. Really, unless there are specific facilities associated with the Camera views you wish to select, I think there's no tidy way to do what you want to do. In FS9 and before FSUIPC could tell you what your main view mode was currently set to, but even that isn't available in FSX, so it cannot even be programmed internally. Exactly, which is not possible programmatically, or at least in any way I know, in FSX. Have you investigated the possibility of referring to the camera views directly, or even changing the order, possibly with duplication? I think the solution to your quest lies in that direction. If you look at the CAMERAS.CFG file (in the same folder as your FSX.CFG file) you will see that some of the CameraDefinition entries have "HotKeySelect" numbers defined. According to the FSX/ESP SDK: hotkeyselect integer 1 to 10 No default. Links the camera to one of the 10 pre-defined key events for activating cameras; see the Control Assignments dialog. So it looks like you can select a view, provided it has a HotKeySelect parameter defined, by a direct control: try View Camera Select 0 to 9? These appear to do the job -- they are new to FSX and I've not tried them before now. There are also View Aux 0 to 5, but I've no idea what they do. Regards Pete

No, it is not of any use at all on one PC. It is networking software, to share FS data over a network. And it isn't anything to do with cockpits or views either. The networking of FS for views is done by a product called WidevieW, by Luciano Napolitano. With dual monitors on one PC you should be able to simply stretch the FS windows you want over both monitors. You'll need to run in Windowed mode, but generally that's just as fast and can give sharper graphics. Regards Pete

This is WideFS6 (for FS9 and before) or WideFS7 (for FSX and ESP)? For WideFS6 it is done in the FSUIPC main options tab, in Fs-Modules-FSUIPC. You'll see the button on the right-habd side. For WideFS7 it is an option offered to you by the FSUIPC4 installer, so just run the Insteller again. Regards Pete

Ahdidn't you realise you had the PFD set up as the First Officer side? ;-) Regards Pete

Check the "Hot Keys" tab. You have to assign a key combo, but you can then drive that from a button assignment. Regards Pete

Oh, it shares the PFD screen? Or is it independently movable? If it is provided in the Boeing set, I wonder why it is described as being for Airbus? Regards Pete

Well the only relevant bit I see is the 9=76,10,2999,62 line. The log file you appended separately doesn't appear to be at all relevant. Why did you press the button to start a new log, as indicated by this? [Log closed by user request, and continued in new file] Maybe, by creating separate log files you got hold of the wrong one? Really it is best not to go around pressing buttons for no good reason. You should really just set the options as suggested. Anyway, I apologise -- the offset affected is 04F4 not 04F0, as a quick visit to the PM website confirms, so you should monitor that, not 04F0. And you can look inside the log file (the ONE log file, not multiple please!) yourself to see what is going on. Here, I've enabled 04F4 monitoring (as U16 type), and also enabled Button and Key logging (one of the checkboxes on the left side of the Logging tab) so you can see clearly what happens. This is without PM running. I'm afraid my PM cockpit is not powered up at present. I assigned Key press Shift 1:: 605641 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 605641 .. Key not programmed -- passed on to FS 606078 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=1 606078 FSUIPC Control Action: Ctrl=2999, Param=62 606078 PM request: 04F4 value 62: Queued (entry 4) 606078 .. This key is programmed in FSUIPC4 'Keys' options 606141 PM sent from Q: 04F4 set to 0x003E 606141 Monitor IPC:04F4 (U16) = 1062 A word of explanation there -- the value 62 is written with 1000 added. Alternately FSUIPC adds 1000 or 2000, so that the value is seen to change each time by PM even though you request the same thing. Otherwise toggling wouldn't work. You don't need to worry about that -- FSUIPC does this automatically. So, the next time I press my key: 606235 KEYUP: VK=49, Waiting=0 607266 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=1 607266 FSUIPC Control Action: Ctrl=2999, Param=62 607266 PM request: 04F4 value 62: Queued (entry 5) 607266 .. This key is programmed in FSUIPC4 'Keys' options 607344 PM sent from Q: 04F4 set to 0x003E 607344 Monitor IPC:04F4 (U16) = 2062 I get 2062 in 04F4. Did you check the notes about this GC controls facility on the PM website? I just did. Here, read this: Okay. Now the second part is what FSUIPC is doing -- using the thousands to indicate a change. But what about the first? Maybe you are looking at the FO's display but changing the Captain's one? You'd need to send 162 for the FO side. Also read this, from the same place: Might this be applicable to your situation? I really don't know what overrides there may be (but then I didn't know PM provided a timer for Boeing, nor even where it is displayed -- you never said!). However, I also don't see any other reference to the timer except to the Airbus one which is the 62 in 04F4. After you check your key is doing what mine is doing, I feel you really do need to seek help with PM. Or maybe first over at the PM Forum. Regards Pete

Right, so you want to change a button into a latching toggle switch. that is usually done with the button's own flag (as i see you already worked out). No. All the flags will be clear when you load FS, but there is no under-cover operation on your flags when you load an aircraft. The state of a button or switch is regarded as irrespective of the current state of the sim, it is a property of the buttons on the devices. Though different aircraft may use the different buttons differently, they remain the same physical things, and the flags are associated with them and their state (i.e. pressed or not, switched on or not). The parameter is as documented (though actually I see it is only mentioned for the C1003, the "set button flag" control -- evidently I thought it obvious that all three button flag controls take the same parameter form, 256*joy + btn. You need to replace the ",0" in your assignment with that value. Controls cannot have "conditions" so cannot be checked. Controls are just commands -- to FS or to FSUIPC. Like "pause". You might have a state called "paused" but the control would be "pause on", "pause off" or "pause toggle" -- the control has no condition, it is a request, and order. Button flags have a state -- set or clear. That's what flags do. It is ALL they do. Have a state! You cannot "switch" a control, you can send it or not send it. You can only switch switches. It lists all of the controls which FSX provides. It obtains its list directly from FSX's own "CONTROLS.DLL" which tabulates all of them by internal names -- it is those names which are listed. I suspect you are referring to something specifically added in particular panels? Can you give any more details? Maybe they are mission specific assignments, not general FS controls. Regards Pete

I assume you mean 4.40. There's no installer for intermediate versions like 4.440. The error definitely means that your SimConnect installation is in a bit of a mess -- Really? Is there no Modules folder in FSX with FSUIPC4.DLL in it? Show me the Install Log please -- if it isn't being saved in the Modules folder you'll need to save the screen copy via its own menu. The next version of FSUIPC (4.50) due to be released before the weekend, is more flexible, in that it will work even with a broken base SimConnect -- all it needs is one working version of SimConnect, any version. I had to work on making that happen so I could have one module for both ESP and FSX. However, if you don't fix it (repair SimConnect) it may well mean you will run into trouble with other SimConnect add-ons also needing the base version. If this doesn't bother you, either wait a couple of days for FSUIPC 4.50 or, if you do actually have a Modules folder with FSUIPC4.DLL in it, try replacing that DLL with the latest interim update for FSUIPC4 which you will find in the Updates announcement at the top of this Forum. If you want to try repairing SimConnect you'll need to see the FSX Help announcement above. But I'd recommend you do the above things first. Regards Pete

I probably don't understand what you are after, but if you mean "how do i make button X send "A" 4 times, then this would do it: 1=P0,20,K65,8 2=P0,20,K65,8 3=P0,20,K65,8 4=P0,20,K65,8 If you want to make one action conditional on another, then that is rather different. But first you have to work out the logic of what you want to do. Are you sure there isn't a way of selecting the views directly, rather than having to cycle through them like this? It seems pretty awful. Also, please note that it is generally far far better to assigned the FS control for this sort of thing rather than use the keypresses which just happen to be assigned in FS to those controls. Why make things so long-winded? I believe the controls you are trying to use are simply "Next View" and "Prev view". If these are Camera Views in FSX (you don't say what version of FS even), then you will probably be able to select them more directly. I think most camera view have an ID or keystroke associated with them -- though I'm not sure about that without checking. Perhaps if you could be more speicifc I could have a look. There are a lot of View controls in FS and I'm not totally sure what they all do! Yes, Windows is identifying that joystick as #0, so it's the same for everything arriving from that joystick. However, if you plug the joystick into a different USB port it will probably change. In the latest updates of FSUIPC the relationship between the ID numbers and the names of devices is made more explicit, and FSUIPC gives you the option of choosing letters to use, instead of numbers. Regards Pete

Ouch. There's hasn't been any problem reported at all with keys or buttons -- the recent report, for FSX, was concerning only the [General] parameter settings, and I found that very specific bug and fixed it directly. [LATER] Uh Oh! Managed to repro the problem. Sorry, yes -- only when trying to assign a key aircraft specific and there are already some generic ones. Working on it. Thanks! ... Found it! 3.875 will be up within the hour. Regards Pete

Oh, right? And where does that show? On a real 737 there are separate chronometers, one each side of the main instrument panel. I'm not aware of any in the PFD, ND or EICAS, which is all I have being driven by the PM GC software. Do you mean that it "doesn't work" in the sense that 62 is not being written to the PM GC Controls offset at 04F0, which is the trigger for PM's module, or that the key assigned is doing what it is supposed to do, but PM isn't responding? You can check that 62 is being written by using FSUIPC's monitor facilities -- right-hand side of the Logging tab. Enter 04F0 for the offset, and select U16 for the type. Check "to normal log" below. Ok out. Press your key, check the log. Personally I'm inclined to believe that the reason it "doesn't work" is that it is only applicable to the Airbus. After all it does explicitly say this in the PM offsets list currently on the PM website, so that hasn't changed since I listed it so in the FSUIPC documentation. However, maybe it is just that you are not assigning the corect control in your FSUIPC interaction. If you want me to check the assignment, show me the entry in your FSUIPC INI file. Regards Pete

Sorry, I don't know what that could be. There is absolutely no use or reference to mice in any of my code. If FSUIPC4 is not user registered it really isn't doing anything at all except what is asked of it by client programs . Is AS6.5 your only FSUIPC client program? If so, have you tried not running it and checking whether the mouse is okay then? If so, maybe it is related to AS6.5? BTW you do realise, I assume, that AS6.5 was designed for FS9, not FSX, and that since FSX came out there have been two versions of Active Sky designed specifically for FSX -- ASX and ASA? Regards Pete

FSUIPC cannot differentiate the reason for going into the menu system, it is just told by SimConnect that simulation stopped. If FSUIPC insisted on smoothing continuation after returns from the menu it would make it very difficult for folks wanting to set weather explicitly or even loading a new flight with its own weather already saved. FSUIPC's wind smoothing (and all the other smoothing actions it did in FSUIPC3 too) have always done this, for 7 or 8 years now. It isn't different or new. Maybe the use of ASA now has somehow induced more distant target for FSUIPC to reach? Certainly if you have smoothing set to 4 seconds for every knot or degree of change i should think it will hardly ever actually catch up with any wind changes. Perhaps if you tried a more reasonable 1 or 2 knots/degrees per second you might not get such violent effects? After all the idea of smoothing is to smooth changes, but still allow them to happen reasonably timely. Regards Pete

AdvDisp has not been supported for several years now. The facilities it offers are all included in FSUIPC itself. To see messages on another screen on a network you just use the little utility Showtext (see inside the AdvDisp ZIP). (That reminds me -- I should upload ShowText itself to the "Updates and Goodies" announcement above). I've no idea what that facility is, sorry. I don't think it is what you think it might be. Please ask PM support for details -- is it documented anywhere? In any case you shouldn't be using AdvDisp.DLL, even with FS9 -- the Window facilities it provides are embedded in FSUIPC now, and for several years. Please see the FSUIPC user guide, near the beginning. You don't need AdvDisp installed to use ShowText. I use Showtext to display a small window on my EICAS screen, overlaying one of the standby instruments. Sorry, I cannot imagine what you are expecting to see. I think this is a question for PM? Maybe it is an old facility no longer supported? Regards Pete