Pete Dowson

In that case no assignments, whether edited in the INI or done properly in the Option dialogue will work. Ah, certain hotkeys were used by subscribed applications. That one was for Radar Contact. The 88 is the keycode for "X", the 10 is 2 for Control + 8 for "Normal". Keycodes are all listed in the Advanced User's manual. It is easy enough for you to look up the correct key. Pete

Sorry, I don't know of any "run" prompt. There isn't one producved by the Installer. FSUIPC doesn't need Simconnect "installed". It is built into P3D. You only need to install the separate Simconnect libraries for old programs which use Legacy versions of SimConnect. Pete

Deleting all the supplied aircraft is a bad idea. most PMDG advice is to load a default aircraft as default before sleecting a scenario with a PMDG aircraft. I think this is now a question for the PMDG forum as it is obviously a problem with the aircraft. Pete

What does this "pop up" say? And don't forget you need to right-click and choose "run as administrator". Pete

Where are they assigned: P3D or FSUIPC? In FSUIPC assignments can you see the values changing then they are selected for assignment (whether you do assign or not)? Have you checked with any default aircraft at all? Pete

Why edit the INI file? Why not just program it in the FSUIPC Options in FS9? There will be an "ATC" control listed in the drop-down assignment list -- there's even a "List of FS2004 controls" document in your FSUIPC Documents folder. The ATC menu toggle is simply named "ATC". The key you want assigned is just the default one pre-assigned in FS9. It isn't fixed. The key would invoke the control called "ATC". Pete

You really need to ask in Paul Henty's subforum above. I'm sure he's implemented an efficient method. For a C/C++ program written directly to the FSUIPC interface you would do as many FSUIPC_Read and FSUIPC_Write calls as you wished (and the can be mixed), providing you reserve sufficient space, then one Process call. You only need separate process calls for updates at timed intervals) or getting results of written requests. So, the answer to your question Each Process call does process all the queued requests, so the requests are made again each time (there may well be different requests of course). Paul may have implemented an easier way as a layer on top of this. Pete

Did you turn off joysticks / controllers in FSX? That's the only place where your buttons will also be assigned. If you don't turn off the joystick facilities in FSX then you will get conficts or multiple assignments. Even if you don't assign them yourself, FSX does automatic assignments. It isn't even safe to just unassign those buttons in the FSX options -- next time you load FSX it may do the auto assignmernts again. Pete

Direct to FSUIPC Calibration doesn't use the regular sim Controls ("Events"), but sends the input from your axis to the Calibration section directly. So you need to calibrate by this route. The results are then fed into the Sim either directly or with possibly different Controls, but at a lower SimConnect priority. so a loop is avoided. Generally this is more efficient as there are less messages flying about, but because of the way the controls are then fed back into the Sim it doesn't suit all add-on aircraft. The assignment to the refular FS controls is just like assigning in the Sim -- excepting of course you have the facilities or automatically having different assignments for different aircraft type (as you have with either method in FSUIPC). Some add-on aircraft only work correctly if you do this. Either way, and even if you assign in the Sim, you can calibrate in FSUIPC -- this is why a loop might be caused if FSUIPC fed the results back at the same priority level and re-intercepted them.. But, again, some add-on aircraft don't work correctly because of the changes this may perform. Pete

I don't know. I don't remember sa_wxr. Can you remind me what it does? Does it have documentation you how to tell it where to get the weather? I'm afraid you need to ask PM support about pm_getweather. Does the PM ND have such facilities? Really, on all this, you need to be in the PM support forum. Sorry. Pete

It was this ultra sensitivity I thought you were fussing about! That's why I asked this: I thought you were now saying that, since updating to P3D4.4 all your controls have become too sensitive! Pete

No point, I don't have any over-sensitive controls. if you are calibrating in FSUIPC why not use the slopes facility to change the sensitivity? Ah, okay then! Why the fuss? Good flying! Pete

Try using F11 with a default aircraft loaded so it isn't overridden, and use the FSUIPC logging to see which control is logged. Pete

If you know how to do it from the keyboard without going into the menu, then in FSUIPC logging you can enable Event logging, Use the keyboard presses which od what you want, then see what is logged. If the action you wnt can only be done by using Menus then it is unlikely you can do it by keybpard or button. As far as I recall all the different views can be selected by some keystroke or other, which tend to translate into one or other of Next View, Prev View, View Modeand View Mode Prev. Note that the behaviour of views is not the same with a 3D cockpit as a 2D one. Pete

Please describr what you mean by this. Does it not appear when you run it, or appear and disappear, or what? Is a log produced? Is there any Windows error report produced (sorry, I don't know where to look in WinXP. With Win7 and later it's the "Event Viewer" application logs). Pretty much all versions of WideClient work with all versions of WideServer. The protocol hasn't changed in a long time The changes have been extra facilities and some bug corrections over time. 7.156 is "latest". If there are things like Windows error reports I need you to use the real latest so that module offset data provided in the report can be used. Pete

With FS assignments do you assign "direct to FSUIPC calibration" or to the FS controls. The latter is the same as assigning in P3D. And are you calibrating? The fact that they behave the same whether you use FSUIPC or not really does point to either a change in P3D (from 4.3 to 4.4?), or in your add-on aircraft. Check in the P3D support forum, see if there are any other reports, or report it yourself. Pete

What does it do instead of "starting" -- and what "latest" version do you have please (version numbers are always important)? Do you have WideFS 7 properly registered and enabled? No. It is a 32-bit program. But it may not be suitable for Win XP -- that is now very much out of date. The earliest version I have to test with is Vista. I could try a copy on that. But if it starts then there should be a wideclient.log. There will also be a WideServer.log in the P3D Modules folder. Both are very relevant to trying to sort out any problems. Pete

I don't know of any changes in P3D4.4 which could affect this at all. Are you sure there's no other coincidental changes which have been made? Pete

Sorry, but I've never used these controls in any case. Just try them, see what they do. FSUIPC is only presenting you with a list of controls as supplied to it by P3D or FSX. That may even change with P3D as it is developed. The names used are the ones supplied by the Sim. For "New View' it probably does the same as the [ keypress: i.e. just opens a new view. But I don't know. There are many hundreds of controls, I just don't know what they all do. If you know how to do it on the keyboard, direct to the Sim, then note that the keyboard shortcut may well be invoking one of the controls. You can see which one by enabling Event Logging in FSUIPC's logging and seeing what is logged when you invoke the action. You can even see this on screen in real time if you run the Sim 9temporarily) in Windowed mode and enable the Console Log, also on the Logging Tab. If no event is logged it is likely that what you want can't be done by simple assignment. Pete

The log shows a normal startup and a normal termination, user instigated, after about 50 seconds from the flight and aircraft starting to load. no errors are shown and certainly nothing crashes. So, it doesn't actually match the statement that FSX-SE "doesn't start". Can you describe what really happens please? What do you see on screen? Also, please look in the windows "Event Viewer" application logs to see if there are any relevant (i.e. time-wise relating to your problem) crash reports referring to FSX_SE. If so I'd like to see the details please. You can copy and paste them here. Also, in your FSX.CFG file, find the section [Trusted] and search that for "Modules\FSUIPC4.dll". This will be followed by a long sequence of apparently random characters then an = followed by a number. that should be 1. Change it if it isn't. There might be more than one entry, so carry on searching. Pete

I don't think you can, not by assignable control. You can only cycle through them, forward or back. And the position is controlled by you moving and sizing the window as you wish. I think that is saved when you save a flight. These are not FSUIPC functions, more questions of FSX. Pete

Really FSUIPC cannot cause a crash just be seeing an axis move. It will merey be passing the value received on to FSX in some fashion, depending on the assignment method you actually made, and calibration options, if used. In your Axis assignments in FSUIPC4.INI you have these for the rudder pedals: [Axes] PollInterval=10 RangeRepeatRate=10 0=0X,256,D,7,0,0,0 1=0X,B,0,0,0,0,65733,0 2=0Y,256,D,8,0,0,0 3=0Y,B,0,0,0,0,65733,0 4=0Z,256,D,3,0,0,0 Axes X and Y will be the toe brakes. Why are you using control 65733 in those? That control is "ABORT". Why have you done that? is was assigned on the right hand side of the assignments, where yu can set different controls for different ranges. The "D" means when moved "down" (numercaly). However, the range is 0 - 0. Possibly FSX crashes because it doean't like "ABORT" being sent at certain times? Or maybe repetitivaly. Delete those two lines (in red) and try again. There was no point in showing the log: it was a perfectly successful run of FSX where you just closed the session after about 40 seconds. The log would only be relevant if it realted to the problem! Pete

It was just that you said "I have followed the above recommendations but no joy.", and the "recommendation" appeared t be not to run FSUIPC, or uninstall it. If you mean FSX-sE crashes or hangs if you allow FSUIPC to run, then please check whether there is an FSUIPC4.LOG file or fragment produced. That is needd if so. There are several known causes of this problem, and the log will decide which, I hope. Just paste it in a message here. Pete

The recommendation to uninstall or disable FSUIPC? So, without FSUIPC you still can't run FSX-SE? In that case it isn't really FSUIPC which is the problem. It cannot be if it isn't running. Pete

Ah. Maybe you are correct and the airport one should reflect on all the runways. Sorry, I probably was making what seemed to be logical assumptions. MakeRunways dates back many years -- to FS98. I have since then modified it to fetch additional BGL data, stuff that didn't occur in the files back then, and one major revision for the change in formats for FS2004 (I think). And some additional file formats made on requests. But I've not got a good memory for all the details.:-( So, the problem is presumably that fsaerodata does what is thought to be enough, but it doesn't suit the way MakeRunways is designed. MakeRunways produces the data for the runways when that runway data is presented. From what you say, it must include then the MagVar for the airport do that it will be used for each runway. I suspect that if I'd have known about this potential problem at the time all that was programmed I'd have designed the end data differently so that this happened automatically.... But I didn't. It may or may not be easy for me to correct for this. I can certainly look at doing this, but it won't be for at least 4 weeks. My days are booked up solid for 2 weeks then I'm on holiday for nearly another 2. Apologies for my earlier incorrect assumptions. Pete