Pete Dowson

Ah, you mean the switches on the panel, on screen, are three position. Can you control those switches by keyboard or standard FS control? If so then you can assign those actions to regions on your axes just as shown for default FS gear, in the example in the FSUIPC User Guide. See page 44 in the current edition. If they are only controllable by mouse clicks then it may not be possible. Possibly they may respond to Mouse Macro treatment, or else operate using Local panel variables (L:Vars). But check if the easier option is available first. Pete

I moved your general support question out of the specialist programmer's subforum on the FSUIPC .Net client so that it may be answered. Please always put FSUIPC or WideFS support questions in the Support Forum. I assume you mean the aileron control axis, the one to bank the aircraft? Have you calibrated the axis on your yoke at all? Have you tried calibrating in Windows? Are you using FSUIPC? Pete

These 3 way selector switches, are they seen as one, two or three buttons (in Windows, in FS, in FSUIPC)? For Gear you'd simply assign the up button to GEAR UP and the down to GEAR DOWN. For Flaps, if your aircraft has more flap positions than just up and down it is a little more complicated. Your switch really needs to be sprung to centre. Then you'd program up to FLAPS DECR and down to FLAPS INCR. Otherwise, if the switch latches, you'd need to always be sure to bring it back to centre manually after eacvh change. Pete

9.929? Please check again. The current, latest supported version is 4.937 (or 4.937d is you are using the latest incterim update). I'm afraid there is no way what you say makes sense to me. I need you to do a few things in an organised way, please: 1. Read the version number more carefully. If it is not 4.937 then go get it and install it. 2. Find the FSUIPC4.INI file in the FSX Modules folder, and paste its contents into a message here. Use the <> button above the edit area here to enclose it. 3. List, step by step (click by click or key by key) exactly what you are doing when you think things go wrong. Pete

You most certainly have something wrong, then. Are you sure you downloaded FSUIPC4, not 3? The current version of the Installer is 4.937. There's never been any change in the registration system, and apart from a mistake in entry the only other things which would result in a rejection are if the computer date pre-dates your purchase, or if the Registration has been detected in use fraudulently -- i.e. by someone other than the registered owner. No, of course not! No, I only need the order number on your receipt. Even your name would help -- I assume it isn't "Andreas BlueRadar"? (I never understood why folks are so ashamed of their own name that they don't use it in Forums). Regards Pete

Nothing FSUIPC can do will bypass anything Windows might do, it has to read the joysticks using Windows facilities in exactly the same way as FSX! I assume you turned off USB power management in Windows? I'm afraid I have no idea. These sorts of problems seem specific to Windows 8. Whether they will ever fix it I don't know. From reports seen here it also appears to be Saitek devices which suffer most, although that may be only because there are more of those than any others. Pete

There has been no change whatsoever in the checking system, and all you had to do is run the Installer -- your existing registration (copied over from FSX) would carry over, no need to enter anything again. However, if you do re-register then all three parts MUST be exactly correct -- the original name, email and key as notified to you originally. If it is rejected then you are either making a mistake (eg name spelled differently, or email changed) OR the date on your computer pre-dates your purchase date (as it can, for instance, if the PCs date has not been set correctly). Pete

I've modified MakeRunways to use double (64 bit) floating point accuracy for the Gate positions in G5.CSV, instead of 32-bit floats. But as far as your example is concerned, it is the same. The G5 positions are likely to be more accurate than those logged in the Runways.txt file because they've gone through less transformations from FS's 32-bit integer packing format. In the next update to MakeRunways I will probably truncate/round all the Lat/Lon positions logged to the equivalent of 1 decimal place of minutes. If you want the modified G5 download MakeRunways 4.677. Pete

The GATE structure being used, from the BGLs, has two fields: int nLon; // longitude in packed format int nLat; // latitude in packed format The FS "packed format" involves a calculation as follows to get a floating point position (this is for Latitude. Longitude is different of course): #define MAXSOUTH 536870912 double f = (((double) nLat)*180)/MAXSOUTH; if (f>90.0) f = -((f-180)+90); else f = 90-f; return (float) f; There's also a need for some of the results to return a 64-bit (long long) version, which would be: return (__int64) ((f * 10001750.0) / 90.0); FS, in different places, uses a mixture of all these ways of storing positions. If any inaccuracies arise they will be withing the limits of the precision of the storage methods used. The one used in the G5.CSV would be the floating point one. The one listed in Runways.txt is the __int64 one. Maybe the G5.CSV, using the 32-bit floating point form, is less accurate than the one logged in RUNWAYS.TXT. But is isn't "wrong". Hope this helps understand what is going on here. It these computations gives a difference of, what, just over 1 foot, I'm not sure what problems then arise. Perhaps someone can enlighten me? Pete

There's no specific accuracy being used. I just log the value I get with a default precision. By "recalculate from an original source" I've no idea what you think is going on. There are no recalculations to do, it is just a value in a file! What on Earth do you think is the recalculation being done? Re-projecting the Earth's surface or something? No, it's just the data that is available. Full stop. And the same data, albeit in a different format, goes into the G5 and any other files which demand it, all from the same database built up from reading the BGLs. Pete

Ah, well FSX doesn't make it, itself, FSUIPC4 does. ;-) Pete

I thought mgh had already explained that they are not different. They can't be, they are obtained from the same data in the BGL! You don't appear to have noticed that my question was to mgh about why he thought "runways.txt is clearly not right". Pete

Updates are never charged for. You buy FSUIPC3 for FS9 or FSUIPC4 for FSX and P3D, ONCE only, even though both have gone through hundreds of updates! If P3D ever gets re-written as a 64-bit application then FSUIPC4 most definitely will not work with it. I may or may not try to do a 64-bit version of FSUIPC, but if I do it would be FSUIPC5 and need purchasing separately -- as will, of course, just about every other add-on. Pete

Sorry, but this is the support forum for FSUIPC, WideFS and my other FS-related programs. I do not use X-Plane and cannot possibly support it. You need an X-Plane support forum I think. Pete

Runways.txt is only logging values it finds. It is a progress log. What do you want it to show? Pete

Doesn't Visual Basic 2010 Express come with any debugging tools, so you can find the error yourself? It is the address in your process memory of the file mapped file. don't you have any reference information for Windows APIs? They are all available on-line! Do NOT confuse FSUIPC offsets, which are really just tokens representing data, with addresses. They are NOT addresses in anything in your process! They are just data references as documented in the lists. You use your debugger! The sources for all the parts which go into your program are provided in the ZIP. Sorry, this question makes no sense and isn't even a question. Pete

You most certainly have another assignment to the same button. You need to find it and remove it. I don't know what you mean by " it disables my joystick option for prepar3d to use it with fsuipc" (what is "it"?) but you will need to either disable controllers altogether in P3D, or at least find the additional assignment and remove it. Pete

Sorry, I don't know FSGW3. Maybe you need to get the author's support? Pete

Yes, but now you won't have all those other DLLs running, which presumably you need? Best to correct the original file as I suggested above. Pete

Wow! I've never seen so many add-in DLLs being requested. I wonder if the SimConnect DLL loader is choking? Do all those others load and work correctly?What's that, 22 DLLs with only the three default SDK ones disabled? There is one error, in the first of the three entries (?!) for Mindstar Hypergauge, in this line: <ManualLoad>Fasle</ManualLoad> "Fasle" should be "False" of course. Whether this would stop the subsequent DLLs loading I don't know -- but if not, maybe trying to load Mindstar Hypergauge three times causes the entries following to fail -- i.e. FSUIPC4 and maybe others? The entries following the erroneous line are trying to load these: Mindstar Hypergauge (the second time) PMDG Interface RAASPRO CMeteoXml FeelThere EJetX Helper Flight Recorder Mindstar Hypergauge (the third time) FSUIPC 4 Try correcting it first. Delete the entire first two entries for Mindstar Hypergauge. i.e. this part: <Launch.Addon> <Name>Mindstar Hypergauge</Name> <Disabled>False</Disabled> <ManualLoad>Fasle</ManualLoad> <Path>Modules\HyperGauge.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Mindstar Hypergauge</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\HyperGauge.dll</Path> </Launch.Addon> Pete

Well, yes. The Registry most certainly points to both 9.0 and 9.1. These are the Registry enties: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0 These are there, despite you claiming "I did not find in the registry microsoft\microsoft games\flightsimulatir. I cannot find the Microsoft games.". The installations are "D:\Programme\Microsoft Games\Flight Simulator 9" for 9.1 and "D:\Programme\Microsoft Games\Flight Simulator 9" for 9.0. In other words, they are actually one and the same. This in no way affects FSUIPC's installer. it will just do the same thing twice, and no harm will result. Pete

I'm rather confused by this. What INI file does FSX make? I assume by FSX you mean FSUIPC4? Note that the GUIDs changed sometime BETWEEN your two extracts: In the first extract: B=Saitek Pro Flight Yoke B.GUID={B3E3E640-81F7-11E4-8001-444553540000} C=Saitek Pro Flight Throttle Quadrant C.GUID={B3E3E640-81F7-11E4-8002-444553540000} D=Saitek Pro Flight Throttle Quadrant D.GUID={B3E3E640-81F7-11E4-8003-444553540000} but in the second: B=Saitek Pro Flight Yoke << MISSING JOYSTICK >> B.GUID={462ADCF0-6329-11E3-8002-444553540000} C=Saitek Pro Flight Throttle Quadrant << MISSING JOYSTICK >> C.GUID={80483940-632A-11E3-8001-444553540000} D=Saitek Pro Flight Throttle Quadrant << MISSING JOYSTICK >> D.GUID={4FC0AFF0-5EBF-11E4-8001-444553540000} Those GUIDs can only arise from Windows settings -- and those B, C, D entries must have been changed in some session between the two you've recorded. i've really no idea how the B, C, D GUID values can have been changed -- FSUIPC only changes the current ones, the ones for 1, 2 and 3 in this case. That's the point. The lettered versions are actually created by you, UNLESS you have automatic assignment still enabled. Then, if Windows has some sort of twitch, as here, it will affect those values. FSAUIPC is trying to help deal with those changes. So, once you've got them assigned, best turn off the Auto assign option to prevent these changing just because Windows does something weird. BTW are you using Win8 by any chance? Pete

You can install FSUIPC on any number of machines and any number of places on any one machine. And there is no difference between "free" and "payware" versions, they are the same. Purchasing just opens up the user facilities. And you can still install on as many computers as you like -- providing they are yours and you, the purchaser, is the user. I've never heard of such a technique, and it isn't needed. Just copy your FS Modules folder from one to the other. There's nothing else to an FS9 installation of FSUIPC, it's all in the Modules folder! Pete

Best to leave the weather stuff to those programs. ASN is excellent and needs no assistance at all from FSUIPC4 weather options. Pete

Okay. And when you ran FSX, was there no prompt to ask you to approve the running of FSUIPC4? Is there no FSUIPC4.LOG file in the FSX Modules folder? If these things didn't occur, then the problem is that SimConnect isn't loading FSUIPC4 in the first place. This is usually because of a corrupted DLL.XML file. Maybe this was caused by some previous installer. You can find this file in this folder: C:\Users\Zack\AppData\Roaming\Microsoft\FSX It is also a text file. If you'd like to paste it here I'll see if I can spot the problem. An alternative, as a test, is to rename it (rather than delete it) then try running the FSUIPC4 installer again. It will create a fresh copy with only FSUIPC4 being loaded. Pete