Pete Dowson

Well ALL your FSUIPC settings are in the FSUIPC INI file, in the Modules folder. So, which of those things you restored -- FS9,CFG, FSUIPC.INI -- does the trick? It does sound like a corrupt FS9.CFG file. FSUIPC doesn't care which aircraft. Or maybe you need to uninstall and reinstall the aircraft? You can show me your FSUIPC INI file and I can see if anything is wrong, or at least, odd. Pete

Strange then that #2 appears to be portrait shaped: 768 x 1024 maybe?

Thanks Paul. Looks excellent. I've pinned it so it doesn't disappear down the list. Pete

Just reassigning some keys won't make such differences. Sounds like your device IDs got messed up. You appear to have just stated that you solved it. Pete

Is that picture from nVidia settings (or whatever video card software you are using), or from Windows? When you move your mouse pointer, does it go smoothly from 1, through 3 then through 2 then 4? Which is your main Windows screen? The left top of that will be 0,0. Screens to its left (in Windows, not necessarily in the driver) with have negative x coordingates. What are the sizes of each of those 4 screns (width x height) in pixels? You might want to use a program which shows the screen coordinates of the Mouse pointer, like http://www.adminsehow.com/wp-content/uploads/2012/03/MousePos.exe. Pete

Cannot you assign to FS contorls instead? They would be far more efficient and relaible. The keypresses are onnly assigned in the Sim to those controls in any case. So there is no problem in FSUIPC seing your buttons. I wonder if it is a focus issue. Try clciking on the replaying screen first, then see if the buttons work. Hmm This part is important: That does suggest, as I suggested above, that assigning to the FS controls will work. Not sure about the implication of the second point tere though. Assigning to keypresses is really useful when sending them to add-ons, but for almost all functions in the sim itself all you are doing it sending a Sim-assigned keypress which in turn is converted to a control -- and of course those can be changed in the sim's assignments. so it is far better on several counts to assign to the controls in the first place, instead. If you aren't sure what the correct name is for the controls, enable event logging in FSUIPC's logging tab and use the sim-assigned keypress, and see which control is logged. Note that controls which have a keypress followed by a numeric key usually take that number as a parameter (though that isn't always the case). Pete

I don't know. i don't actually know of the problem. Do you have any references? Are your controls assigned to FS controls or "direct to calibration"? Do you controls respond in FSUIPC's assignment or claibration screens when in the midst of Instant Replay? And does this occur with all aircraft or only certain add-ons? BTW, what would the controls do in instant replay? Can yo change the way the replay behaves? I don't really understand what it is you would want to do with the controls when the replay is just a recording. Just viewing? I would have though "Panning" would be via "Pan View" which is a standard FS control. Pete

The Installer accepts different emails (and even names) for WideFS and FSUIPC. You are making a mistake somewhere. You need to enter all three parts exactly as they were for your WdeFS registration. Pete

As it says: third_party_event_id_min+968. In other words the value third_party_event_id_min plus 968. So just find where it says #define third_party_event_id_min followed by a number then ADD that number and 968 to give you the control number. Sorry, but if you still don't understand I really suggest you ask in the PMDG forum. it is their add-on and SDK after all. They chose to do it that way. Pete

968 is not a valid control number at all. Are you forgetting to add the base value? All the PMDG custom controls are expressed in that file as a base + number. The base number is given at the top of the list I think -- look for the #define line which defines the value for it, by name. Pete

Yes, please -- that's a good idea! Thanks! Pete

I have received clarification from L-M who believe it is a misunderstanding, not a bug. To quote them directly: Sim Rate has always been limited internally to 4X when the aircraft is below about 50 feet AGL. Perhaps this is what you are observing. This is done for usability, as even really small velocities close to the ground would cause immediate crashing at the higher multiples. I have pointed out that, misleadingly, the on-screen and menu selected rates, as well as the return from SimConnect which FSUIPC uses, do state the rate above 4x, but checking the clock you will see it is still 4x. The further clarification was: What you are setting is actually a "requested" rate. You can continue to change the rate, but below the altitude limit the rate is limited to a maximum of 4X. When above that altitude, the request will be honored. So, I hope that explains what you are seeing. Pete

Good, thanks for letting me know. Pete

It seems to be referring to the stuff I mentioned, but is isn't specific or limited to GSX. It knows nothing about GSX, it is dealing with SimConnect displays. See the similar post in this Forum! Pete

This cannot be anything to do with updating FSUIPC. None of your settings are ever changed by an update. I suspect you are not using Joy Letters, which enable assignments to move with changing JoyStick IDs. When you boot up or update Windows, or if you have devices sometimes connected ot sometimes not, the IDs can change. Using letters instead of numbers gets around this problem. Where is this? In the assignments section of the calibration? It is either going to be a calibration problem or a registry corruption. And going back to any different version of FSUIPC cannot possibly fix it. If this seemed to then I think you are saving a copy of your FSUIPC settings and restoring them. You NEVER need to do this as FSUIPC never changes them on its own, only when you make changes. Well, possibly, but probably it still won't make sense until you explain exactly what you are doing because none of it makes sense at present. Pete

GSX? Nothing specific to GSX, no. There has always been a plug-in to display FSX and P3D text displays on a Client PC. This normal one, used for many years by many folks with Radar Contact, was provided in the La Library document in your FSUIPC DOcuments folder. The recent change has been more extended facilities added by L-M into P3D4. These allow SimCnnect Message Windows to be shown on client PCs, and this is implemented in FSUIPC5 and the latest WideClient. You can then suppress message windows -- except the menus -- in P3D4, by unchecking the "information text" item. All this occurred with the recent updates for WifdeFS and WideClient, so if you kept up to date you already have the plug-ins and documentation explaining it all. Pete

Sorry, I don't unerstand any of this. Please can you explain in English, or use your normal language and hope Google translate does a good job. The point of RudderBlendLowest is to STOP the rudder appearing to move in the Lower DU display when the tiller is checked whilst stationary. That is ALL it does, nothing complicated. It was just faulty in 5.141. The only difference between 5.141 and 5.141e as far as Rudder and Tiller are concerned is that the RudderBlendLowest value is now compared against the actual ground speed, not a random value picked up incorrectly! If you don't want the function at all, just set it to 0. But if you have a problem I need it spelled out clearly, and with actual dsta. Maybe you could paste in your FSUIPC5.INI file? Pete

Yes, please. Either ZIP and attach it here, or ZIP and send to petedowson@btconnect.com. Well, unless you have some Lua plug-in which does such odd things, I don't see that either your plug-ins or Wideclient would know anything about it. And WideClient isn't sending anything TO the Sim if you are not sending things from your plug-ins. You need to use FSUIPC logging to see what's going on in the Sim itself. I use the ProSim738 model, but I have 7 satellite PCs running the cockpit. Only the main ProSim737 EXE is running on the sim PC. For pushback i either use the sim itself (via ButtonKeys on a touch screen) or GSX, with its menus appearing via WideClient of course on a cockpit PC#s screen. Pete

Not sure what that is, but re-reading your question I now think you might have been talking about the SimConnect mesage windows and the Lua script(s) i provide with the latest WideFS to display them elsewhere. Of course these are really designed to be used on a client PC with a separate screen in the cockpit. But I'm interested in how you solved the layering conflict you suggest was occurring. After all, there's no "wnd.focus" or "wnd.bringtotop" facility. Maybe I ought to be looking at adding some more facilities to the library? Pete

Of course! You are merely setting it to 10000. To scale it you'd need to READ the input value, multiply it by your scaling factor, then write it back. I thought that was what to meant by "scaling"!??? If the script is assigned to the axis you want scaled, you receive its value as a parameter, so you simply multiply it and use that instead of your 10000. Just make the multiplcation conditional on speed. Pete

When you say "green band" do you mean a display window with several lines, as illustrated in the User Guide? The changes from Green to Red and reverse are done to indicate that the mouse action of its operation has changed, it has effectively selected a different function. Can you show me the FSUIPC4.LOG from an attempt which produces this result? Set the Button/Key logging option in the Logging tab first. If you can read the codes logged for the action you need (and the Log should help) then you could change the your previous equivalent working macro to use the newer code. BUT really mouse macros are completely unnecessary for PMDG switches, as they kindly provided a complete set of controls which you can assign in FSUIPC via the <custom control> option. Why not use those? See the SDK fo;der for your aircraft. The controls are listed at the end of the file with type .h Pete

What text message Lua script library functions are you using, and why WideClient and not in FSUIPC itself? Using WideClient on the same PC as the sim is useful when using functions NOT available in FSUIPC, such as those in the Wnd and Display libraries. With those you can have the displays doing almost anything you like. So, in order to advise I do need more information, or even a sight of your script. Pete

No, the default was not corrupted. If the next session was problem free then FSUIPC's deletion of the bad one and, presumably, the deletion now of the good default, has prevented whatever it is which was corrupting it from doing so. Otherwise, it was either the WX file being loaded (the default, by the look of it: C:\Users\Daniel\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.wx). or something else is corrupted in P3D itself. To prevent FSUIPC even trying to read weather, you can add "NoWeatherAtAll=Yes" to the [General] section of the INI. This will stop FSUIPC having anything to do with weather and therefore not invoke SimConnect actions which these corruptions affect. Of course that doesn't stop other weather programs doing it. But it will at least identify whether this was really the problem or not. Otherwise it sounds like a repair job on the P3D4 installation. Pete

The one in Weather is NOT the active one, but the default used to put one into the Appdata place! If there wasn't one there it's because FSUIPC now deletes it when you close the session. So, did it help? If so the default has been corrupted! FSUIPC now deletes it in Appdata so that the next session is ok. If it then gets corrupted again some app is doing it, or the default is corrupted. Compare the one you attached to yours. (I'll do that tomorrow when I'm at my PC again. This is my phone) Pete

Ah. well, as it says in the READ.ME, all that option did was pinch the details from the EFB file. I've no idea where to get those details from otherwise. Just because they have the same filename doesn't mean they have the same data. I assume the TAs come from the AIRAC updates, but I don't know. sorry. More recent ATC programs use AIRAC data. I moved from RC long ago, to ProATC.X for a while, and just recently Pilot2ATC which I really like, even though it is rather expensve if you want good voices. Still, compared to the cost of building my cockpit ... Pete