Pete Dowson

Are you entering the exact details for both on all three lines? Also, whilst you can have a different email address for each, the NAME must be the same. You can't register FSUIPC and WideFs in different names. Otherwise, please show me the Install log file. Pete

There are lots of threads here about this subject. Just peruse some, or search on "PMDG". Also check the "User Contributions" sub-forum. The main aircraft, 737, 747, 777, are all provided with a complete set of controls, documented only in the aircraft's SDK (the list is at the end of the file of type ".h"). You need to compute the custom control number ("event") from that document then assign in FSUIPC using <custom control>. I don't have or use any PMDG aircraft so I can't help with specifics. And as it's really more of a PMDG support matter, you might get more assistance over in a PMDG-centred forum. Oh, and this system in not specific to the P3D4 versions and FSUIPC5, it also applies to FSX/P3D3 and FSUIPC4. Pete

SimConnect allows me to set 'x' individually for each data request. It cuts down on the traffic to/from SimConnect by only asking for changes which would be noticeable. This value is per data request, so, yes, it will vary according to the data requested. 'x' is called the "epsilon" by SimConnect, and actually, by default, FSUIPC does these days default it to zero for all values. But there is an FSUIPC INI parameter which will make FSUIPC use different values for each value (with 'x' decided by my judgement about reasonable desirable precisions). Maybe it would help in those installations which have several SimConnect users clamouring for data and gradually clogging the interface up. This option is documented in the Advanced User's guide, thus: UseEpsilon is normally omitted altogether. If needed, it can be added, in the [General] section of the INI file, set to “Yes”. This will impose change limitations on most variables sent to FSUIPC by SimConnect Pete

The SDK example here: Core Utilities Kit\SimConnect SDK\Samples\FacilitiesData works very well and demonstrates the problem easily. I wonder if any of the other Facilities lists obtained by this function are also incomplete? Pete

Thanks. I found the C++ version of the MS-provided example now, in the SDK. That should be sufficient. i'll test with that here. Pete

Changes are listed in the Changes document supplied in the ZIP, which you can therefore read without installing. Note, though, I only support the latest release versions (i.e. those with an Installer). Why would you NOT want to install the latest in any case? Pete

Mouse macros have limited application. PMDG's 737 comes with a full set of custom controls which you can assign. These are documented in the file ending in ".h" in the SDK folder, in the aircraft folder. The controls are listed towards the end. You have to calculate the custom control number then assign it to <custom control> in FSUIPC. Pete

But the Helicopter Profile won't apply to it (unless is has "helicopter" in its name) because you aren't using Profiles ("UseProfiles=No" -- default is "UseProfiles=Yes"). Pete

Benny, with reference to the above, have you by any chance got a small simple program which demonstrated the unreliability of the returns from that SimConnect function? If so, would you be willing to share the source and EXE so that I can supply it by way of demonstration to both DoveTail (for FSX-SE -- they've already responded to my requests and would like some way of getting into it), and probably L-M (from whom I'm still awaiting a response). These larger developers do tend to like these things handed to them on a plate! ;-) If not I'll see if I can knock something up, by it won't be for a while as I'm pretty well tied up. It would be nice to be able to get back earlier whilst they are in the mood to look at it. Maybe there's an SDK example of this call? I only just thought of that, so I'll go look tomorrow. Thanks, Pete

They are updated when SimConnect sends a new value which differs from the last one by enough to affect the offset. How often it sends them probably varies quite a bit according to which sub-system they come from. If FS9 days (and before), FSUIPC used to grab the values from all over FS, directly from its assorted DLLs, on a "polling" basis at regular intervals -- basically at an internal sim rate or at the frame rate (depending on the values). Since SimConnect was implemented, in FSX, it takes advantage of the SimConnect facilities. Those supplying data for most of the types of offsets you are thinking about are only requested once on a "please supply when changed by more than x" basis. The updated values then just arrive whenever SimConnect decdes to send them. Pete

Yes, that works fine. Only any Macro (.mcro) or Lua (.lua) files you might have in the Modules folder. One odd thing I note in your INI file. You have "UseProfiles=No" in the [General] section, yet you have [Profile.Helicopter] 1=WILCO_FSTR 2=BA609 PROTO SIM AIR 3=BA609 EXEC SIM AIR You do have assignments in these sections: [Axes.Helicopter] [Axes.WILCO_FSTR] [Axes.BA609 PROTO SIM AIR] [Axes.BA609 EXEC SIM AIR] If the names in last three match any part of any of our installed aircraft names, then those sections will operate on the old "aircraft specific" system (which was really superseded long ago by Profiles, but still left operational for ongoing compatibility). However, the Helicopter section may not match any part of the three aircraft you have listed in its Helicopter Profile. But back to your question, if you were using Profiles, and had opted for "UseProfiles=Files", you'd need to copy over the Profiles subfolder too. Pete

What exactly do you mean by "will not register"? Have you purchased an FSUIPC5 registration? It won't accept an FSUIPC4 one. And anyway the Install log shows you declined to register: BTW your FSUIPC4 is out of date. The current version is 4.972 Pete

When you change Windows, you get new GUID's and usually new Joystick IDs assigned. Therefore devices previously identified by a specific GIUD and ID will now not be so recognised. You omitted what is probably the most important file, the FSUIPC.JoyScan.csv file. That shows exactly what happens during each stage of FSUIPC's scanning and how it arrived at its results. Anyway, the end result is that your three device have these GUIDs and IDs, 1-3. 1=Controller (Gamepad F310) 1.GUID={18ECDE50-CD6F-11E7-8002-444553540000} 2=Logitech Extreme 3D 2.GUID={23DBF0D0-CD6F-11E7-8003-444553540000} 3=T-Rudder 3.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000} whilst your previous assignments were: C=Controller (Gamepad F310) << MISSING JOYSTICK >> C.GUID={A628CE50-0254-11E7-8001-444553540000} J=Logitech Extreme 3D << MISSING JOYSTICK >> J.GUID={F7DD4480-BD9C-11E6-8001-444553540000} R=T-Rudder << MISSING JOYSTICK >> R.GUID={D17FC700-30DC-11E7-8001-444553540000} You see that all three GUIDs have changed. This is Windows doing, as it re-generates them for the fresh install. So you need to delete those letter assignments, then make a copy of the new set and put the letters in again so you get C=Controller (Gamepad F310) C.GUID={18ECDE50-CD6F-11E7-8002-444553540000} J=Logitech Extreme 3D J.GUID={23DBF0D0-CD6F-11E7-8003-444553540000} R=T-Rudder R.GUID={EFC4ACB0-CD6E-11E7-8001-444553540000} That's all. Pete

Good. I thought it must be something to do with Windows or another low level activity like anti-virus, because the symptoms were simply not logical. Pete

Which part? Why not ask questions then? You last message seemed to simply ignore the one I sent before! It is nothing whatsoever to do with programming. You are a computer user. You even fly a flight simulator on a computer! That is enough qualification to understand what is meant by terms like"virus checker", surely? And you obviously did not read the part where I asked for the log from your previous deletion and re-install attempt, so why post something completely ignoring all that? Let's start from basics. Have you ANYTHING at all installed on your PC other than Windows and the Flight Sim? Is it a pure pristine PC as delivered, with no changes? If you are "not a programmer" and understand nothing at all, then I assume you've never done anything with it .. right or wrong? What has "Captain Sim" got to do with it? And as someone who knows so little, how come you are testing for anyone? Sorry, rather than reacting so furiously you really do need to do more to help. Your logs are unique and make no sense at all. Me accessing your PC is not going to happen. I don't do that and don't want folks doing it to mine either. So, unless we can move forward with more cooperation and more information, this is going nowhere. Pete

Still exactly the same! Why did you just do exactly the same thing again without reading and dealing with what i said last? There is no reason EVER that Windows can or should deny access to a folder just created by the program which wants to access it! Something else is interfering. Can you please read my previous message? Pete

No, sorry. I've just tested on P3D4.1 and it's just as bad: EDDC nearest EDCM (17nm) EDDF nearest ETOU (7nm) KJFK nearest 4NY2 (8nm) The only add-on airports I have installed on this test system are EGLL and EGCC. EGLL seems okay, but EGCC gives EGCB as nearet. I'll report it to L-M so that it might just get fixed one day ... Pete

It gets the list using values in ATC.DLL, but only in FSX SP2 and Acceleration. It isn't available at all in FSX RTM or SP1. In FSX-SE and P3D it uses SimConnect_RequestFacilitiesList. You can log what it gets by adding these two lines to the [General] section of FSUIPC4.INI: Debug=Please LogExtras=32 If this list includes the aiport name, as the last item in each one, then the data comes direct from the ATC.DLL hack. Otherwise it's all from SimConnect. And I did report the SimConnect problem with not including all near airports, even sometimes omitting the actual one you are at. I think it was fixed in P3D, but I'm not sure. I'll try your example here. Pete

FSUIPC is not involved in any of that stuff at all. Why imagine that? It is easy enough to read what FSUIPC does without buying it. it isn't a problem solver for other add-ons. 1. Why are you SHOUTING? \ 2. What do you mean by "this new file, the 5"? 3. Describe what you really mean by "not start". What happens? Does it hang or crash or what? 4. Show me the FSUIPC log files -- the Installer log and, if there is one, the run time log (FSUIPC5.LOG). Look in the P3D Modules folder. Sorry, what SDK? Unless you are a programmer you do NOT need the FSUIPC SDK. And I provide no other. Pete

We have no manuals for PMDG products, only for mine. You probably really need help from PMDG or the PMDG forum. But take a look in the SDK folder of your PMDG aircraft. In there you'll find a file of type ".h" (I don't know the filename). The first part gives some instructions, then a list of data which can be enabled (it is this data which FSUIPC makes available, if it is enabled, in Offsets), and towards the end a list of all of the controls or "events" which can be used. These are "custom controls" because they are NOT "FS controls" but they are custom - added by PMDG for that aircraft. You can calculate the control number and assign it is FSUIPC using the <custom control> assignment. Pete

Something is really wrong, but it must be with Windows, not P3D, because P3D itself has nothing to do with the Installer program getting access refused on a folder it just created. But please, you should show me the Installer log file from the attempt you just did, the first after deleting the Modules folder completely. IO ask this because looking back, the first Install log you posted showed : Prepar3D v4 Modules Modules folder already exists. followed later by:"Modules\FSUIPC Documents" folder created okay! Now, if an FSUIPC Installer had already created the modules folder and installed the documents, the FSUIPC Documents folder would also already exist, yet it says it is being newly created. And the second log shows exactly the same! Having deleted both folders before the last instasll test, what does the log show as a result? So, do you perhaps have some sort of anti-virus checker running which somehow has determined that something about what is being installed is not trustworthy? If you have it might be worth trying to suspend it or stop it for another test of installing. I really cannot think of anything other than the blocks such checkers put on things which could give such completely illogical results like this. Pete

Still the same failure -- access denied on a folder it created? It makes no sense at all. Try deleting the entire Modules folder, including the FSUIPC Documents subfolder, and installing again. Pete

If you are using P3D version 4.0 you need to update to 4.1 as FSUIPC no longer supports 4.0! No idea what this means. What have FSUIPC and WideFs to do with IVAO? Neither needs or uses the other! Pete

How can it "back up"? Is it parked on a slope, or are you loading a flight which has been saved with engines running and throttles set at full reverse thrust? If the latter, best set things to normal then re-save the flight. Check your assignment by using the normal default keypress for parkng brake, or look at the screen indication "PARKING BRAKE" (unless you've suppressed this). Or you can use FSUIPC's event logging. Pete

You have NOT installed P3D4.1! You are still using 4.0, as is cleartly shown during the FSUIPC installation! I will be changing the Installer soon so it refuses to install on an incorrect version of P3D. Meanwhile, i did think the strong notices both here ansd in the Changes document would avoid all this unnecessary hassle! Pete