Pete Dowson

As well as what John has advised, I note that somehow you have set the delta value to 1691. The delta is the minimum change in the axis valu which should be acted upon. The delta is used to stop too many commands unnecessarily clogging up the pathways. The default delta is 256, which out of a normal (windows calibrated) range of -32768 to 32767 gives 256 distinct positions -- more than can usually result in any different results. The delta rarely needs changing for normal controls. Pete

Yes, you can enter a hex parameter by starting with "x", so, for example, x80000 for "right release". Pete

Please refer to the "FSUIPC UNAVAILABLE" post not far below yours! It should have been fixed by now, but sadly still not ... 😞

You need to use either the built-in Windows backup facilities, or, better, a back up program! As I said I use AOMEI -- the basic version is free and will do the job. You also normally need a bootable partial system -- again Windows or an external program can do this -- in case you ever get corruption stopping a proper boot into Windows. However, it is too late to take backups now everything is in a mess! I assume you are saying you never made any backups!? Oh dear. in that case it is a start-again job. Pete

Well, you can get it using this link: GA28R64.zip That includes the INI with all log options set, so the log will be pretty big. if you post one back here please be sure to ZIP it. If it appears to be working, or almost so, please feel free to reduce the logging before posting -- the value 1020 will remove a lot of repetetive stuff about con port I/O. Pete

Oh dear. Seems that your FSX installation is well and truly messed up somehow. I'm afraid that, yes, you will need to uninstall it and get it nicely cleaned up, then install the main version, check it, then SP1, check it, then SP2. Check it. Only then start re-installing add-ons -- but be wary of installing anything in bulk. always check the system is still okay each time. FSUIPC is relatively easy to re0install. Save your FSUIPC4.INI and FSUIPC4.KEY files and restore them to the Modules folder after re-installing it. If you have a backup of your system from when it was last all working correctly you could try going back to that instead. I do backups regularly, and keep three past copies of backups. I use the AOMEI Backupper with is very good. Pete P.S. Aren't all the latest versions of ProSim aimed at P3D v4, not FSX?

I've just been told it should be sorted out this evening. Don't forget you can still download it and install it. To register later just re-run the installer. Download Links subforum above. Pete

Well, that's another story. I did most of the conversion from the 32-bit version long ago, but I never got to test it yet because I've been concentrating on my 737NG cockpit using ProSim instead. I upgraded the main PC for that, and the previous one was "passed down" to the GA28R setup. I've not had time to connect that up yet. So, if you want a tested version of GA28R64 I'm afraid It'll be a few weeks yet -- but i do aim to have it all up and working correctly again before Christmas. If you'd like an untested version to try I can send it this week, and i'll need some logs back to see how it was. But otherwise i'd recommend waiting -- please send me a reminder now and then, maybe at 2-3 weekly intervals (else i'm bound to forget, sorry ... old age!) Feel free! But I think in that case you ought to include details of other INI options: All in [Connection]: Debug = n -- where n is the sum of the following choice of values: -- 1 = Log COM port data -- 2 = Log COM Read/Write actions -- 4 = Log input packet decodes (most useful) -- 8 = Log Write packets -- 64 = Log Writes to FSUIPC Offsets -- 512 = Send copy of log entries to "DebugString" (for use in debuggers, for real time view ------------ (you can get a program called Debugview.exe to show these too - somewhere on Microsoft web sites. AutoRestartTime = 6000 (milliseconds). default 6000, minimum 1000 ReadSleepTime = 20 (milliseconds) WriteSleepTime = 20 (milliseconds) ClearOnReset = No (or YES) SyncInit = Yes (or NO) Those are really not for general use changes, but may be advised if needed (judging by errors or whatever in log). The other parameters are as in the INI file I already presented. Pete

Why not? Anyway, I think Sp2 includes SP1 so there should be o need to install both. No need to remove it, but if you really want to it is merely the FSUIPC4.DLL file in the Modules folder. Run the Installer for the latest version, which you can download here (dowsnload Links subforum). A good reason not to delete it then. But in any case you can always get your registration again from your SimMarket account. And always make backups. The key is saved in the FSUIPC4.KEY file in the Modules folder. Save that file, and of course your settings (FSUIPC4.INI). Pete

No, you need to remove that. GA28R.dll is loaded automatically by FSUIPC when it is seen in the Modules folder. If it is already loaded then the linking GA28R and FSUIPC does will fail to properly complete. It isn't coded for any particular version. FSUIPC tends to all the differences. GA28R only talks to FSUIPC and the device. Is that the original fixed serial port driver supplied by Aerosoft? I wasn't happy with that, which is why I wrote my own. I was using GA28R with FSX-SE, but now I use GA28R64 - the 64-bit version for P3D4. If you need the P3D4 version let me know. I don't openly publish either because I am too lazy to do any documentation! 😉 (and as far as I knew there were only 5 of these cockpits ever made -- Aerosoft wanted to buy mine back at one time!). The only setting up to be done is to put the correct COM port and speed into the INI. My INI is: [Connection] Speed=38400 Port=COM1 [User] LEDdaytime=48 LEDnighttime=16 ADF100Hz=Y But, as I said, you must let FSUIPC load it, not pre-load it via an Addon XML file. Pete

Apparently one of the servers which sees to key generation is down at present. They are working on it, but it may not be running again till Monday. Sorry. In all these years (since FSUIPC3 was released in 2003) I've not known this to happen! Pete

There's one runway -- 04/22. length 3 feet only. So it is too short for any use at all, even by a model aircraft! Runway 4 /22 centre: N45:23:44.6055 E006:37:57.1330 6586ft Start 4 : N45:23:45.9660 E006:37:58.9435 6586ft Hdg: 44.0T, Length 3ft Hdg: 44.000 true (MagVar 1.000), UNKNOWN 126 (Transparent), 3 x 1 ft 3 feet long by 1 foot wide! Why on Earth the airport designers have made this I've no idea -- you should ask them. The three Helipads are not miniature at 33 feet. Please refer to the MakeRwys documentation ("Makerwys READE.pdf") supplied withthe program. Om page 4 it explains the MINIMUM RUNWAY LENGTH and how to override this. Pete

Well, I wouldn't accept it myself. i'd be trying to eliminate every add-on, one by one, till I nailed it. Pete

Apparently one of the servers which sees to key generation is down at present. They are working on it, but it may not be running again till Monday. Sorry. In all these years (since FSUIPC3 was released in 2003) I've not known this to happen! Pete

Runways.txt is merely a log, not a database file. Runways.xml has data which is available even if there is no valid runway -- vaklid in the sense that there is a "start". Runways without "starts" are not included in the Runways.csv or R4.csv because there is no way a program using those lists can determine exactly where to put aircraft. MakeRwys relies on the "start" records" to derive such data. So, check the log (Runways.txt) for one of these 'missing' airports to see if there are Start records listed. The other possibility is that the runways are too short. MakeRwys, by default, won't include airports with short runways -- you can override that with a command line parameter. Same with water runways -- those are usually not included but again that can be overridden. If you are still not sure, please copy and paste one or two of the entries in Runways.txt for the airports which concern you. Make sure, please, that these are from the LAST such entries should there be more than one -- later entries override earlier ones (scenery priority). Pete

Well, you shouldn't be checking any log options at all really. Why are you? Thomas only asked that you showed the whole log, not a partial one. However, that said, I am not sure what you are doing with your buttons or on the screen because the Event logging shows many fast repeating controls. Are these to do with your controlling of your flight? there seems a rather excessive number of repeats each time. At this point: 3498042 *** EVENT: Cntrl= 65584 (0x00010030), Param= 0 (0x00000000) BAROMETRIC 3536168 **** Restarting traffic scanning due to non-reception **** 3540334 *** EVENT: Cntrl= 65584 (0x00010030), Param= 0 (0x00000000) BAROMETRIC there was a pause long enough to cause FSUIPC to restart its traffic scanning. Looks like reception from Simconnect was stopped for 38 seconds! That's certainly long enough to cause any Simconnect-using applications to decide things had gone wrong. The sheer nuber of consecutive "PAN VIEW" events being sent by something is astonishing. Surely that cannot be you using a hat? Here you seem to be using another program which takes focus from P3D and may be causing other delays: 5464902 Deactivated: culprit unknown 5464902 Focus lost: culprit unknown 5847604 *** EVENT: Cntrl= 65584 (0x00010030), Param= 0 (0x00000000) BAROMETRIC 5935901 *** EVENT: Cntrl= 65584 (0x00010030), Param= 0 (0x00000000) BAROMETRIC 5978317 Deactivated: culprit unknown 5978317 Focus lost: culprit unknown 6015836 *** EVENT: Cntrl= 66856 (0x00010528), Param= 1 (0x00000001) VIEW_CAMERA_SELECT_6 6050702 *** EVENT: Cntrl= 65584 (0x00010030), Param= 0 (0x00000000) BAROMETRIC 6051934 *** EVENT: Cntrl= 66851 (0x00010523), Param= 1 (0x00000001) VIEW_CAMERA_SELECT_1 6056053 Deactivated: culprit unknown 6056053 Focus lost: culprit unknown 6258698 *** EVENT: Cntrl= 65584 (0x00010030), Param= 0 (0x00000000) BAROMETRIC 6264938 Deactivated: culprit unknown 6264938 Focus lost: culprit unknown and later this occurs again and is bad enough to cause a break in reception from Simconnect: 6858288 Deactivated: culprit unknown 6858288 Focus lost: culprit unknown 6896056 **** Restarting traffic scanning due to non-reception **** 6898864 Deactivated: culprit unknown 6898864 Focus lost: culprit unknown 7048937 **** Restarting traffic scanning due to non-reception **** 7051651 Deactivated: culprit unknown 7051651 Focus lost: culprit unknown 7100230 *** EVENT: Cntrl= 65564 (0x0001001c), Param= 0 (0x00000000) ATC 7103428 Deactivated: culprit unknown 7103428 Focus lost: culprit unknown Yet another long pause here: 7160259 *** EVENT: Cntrl= 65880 (0x00010158), Param= 0 (0x00000000) HEADING_BUG_DEC 7182364 **** Restarting traffic scanning due to non-reception **** 7358911 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW and again: 7689087 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BUG_INC 7689430 **** Restarting traffic scanning due to non-reception **** 7690974 *** EVENT: Cntrl= 65879 (0x00010157), Param= 0 (0x00000000) HEADING_BUG_INC and 7896365 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR 7927472 **** Restarting traffic scanning due to non-reception **** 7930592 *** EVENT: Cntrl= 65758 (0x000100de), Param= 0 (0x00000000) FLAPS_INCR And on and on go the PAN View events. What could possibly be doing that? I don't know where in all this your "SLC" program lost contact, but I'd be very surprised if you didn't notice the pauses and/or jerks all these interventions mustsurely have caused. I think you might need to use a process of elimination on your add-ons to see which is responsible for each of these oddities. Check also you haven't got a button on a control which is permanently sending events, as those are very odd. Then you can turn off the Log options you've enabled. Pete

The ipc.display function uses the SimConnect Message Window, which, if you are using P3D4 (you don't say) can be suppressed. When testing Lua plug-ins it is best to use "ipc.log" so that the message is directed into the FSUIPC log file (or into a separate Lua log file if so opted). Anyway, without more information, like how your plug-in is being loaded (is it actually running?), which FSUIPC version, and which sim you are using, it isn't really possible to help further. Pete

Unfortunately the added controls from PMDG use parameters which are actually related to what you'd do with the mouse on the same switch in the cockpit display. The read-out from the offsets only gives the positions or values, not the action to set them. If i remember correctly (sorry, I don't use PMDG aircraft), that .h file in which you found the control (Event) number also contains a list of the mouse codes they need as parameters. Pete

Sorry to hear about your eye accident. Interesting about the rule changes. I know that one-eyed flying is allowed, but that does require an adequate field of view in that remaining eye. My problem was not width to my vision in either eye. And five years after failing the medical for flying I failed the mediacal for a driving license. These days I travel by bus, train or aircraft but only as a passenger! I think that must have been 4.974, the current version? Pete

Then best to just pass on the information i specifically supplied above back to him! The name of the SimConnet variable to register in Simconnect is the string "..." at the end of each of the 8 lines. I read it as a % Pete

That can't be correct, as FSUIPC uses only SimConnect for those, as for almost everything else! { 0x3367, 1, 0, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:0" }, { 0x3367, 0, 1, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:1" }, { 0x3367, 0, 2, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:2" }, { 0x3367, 0, 3, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:3" }, { 0x3367, 0, 4, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:4" }, { 0x3367, 0, 5, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:5" }, { 0x3367, 0, 6, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:6" }, { 0x3367, 0, 7, F32V, DOORS, WR | WROK | BITS, szPc, "EXIT OPEN:7" }, Note that FSUIPC reads the door states as 32-bit floats. those give the % of opening. It changes the bits in 3367 based on this value. It sounds to me more like an error in their Simconnect access code. And why does he use IP sockets to interface, which needs a Lua plug-in? Wouldn't it have been a lot simpler for them to use the published FSUIPC interface? Pete

FSUIPC only uses sockets for WideServer links to WideClient. I see John has pointed you to a Lua sockets solution, originally posted by another user, to solve the absence of a 64 bit sockets module. The socket number to be used will be set in the Lua plug-in you will presumably need to use. Seems very strange to me that a GoFlight module needs IP sockets to get information. Pete

No, not at all. Use FSUIPC as it stands or registered. WideFS is a separate add-on to spread the FSUIPC interface for applications to other PC's in your home network. if you want to do that then you need to register WideFS -- but even that doesn't actually need a registered FSUIPC, only an installed FSUIPC. You register FSUIPC only to use it's user facilities, not its interface for application programs. Pete

Looks like John and Reinhard have already both supplied excellent suggestions for you to follow. I don't think I can do better. Pete

Sorry, I've no idea what your "Majestic Q400 variables" are!! PMDG has implemented a memory block sharable using SimConnect facilities to provide "variables" relating to settings, displays, values etc -- for cockpit builders -- but only for its Boeing series as far as I know. I've no idea if other add-on aircraft makers have done the same, but FSUIPC only supports this for the three Boeings from PMDG. Yes, mouse Macros are used for inputs -- clicking buttons or changing dials on panels when no other commands are provided to do this. If you explain yourself more clearly then maybe you get proper help. I did ask you in my first reply what you were talking about. I still don't know -- all i now know is that you want some information OUT of the aircraft.. i've no idea what, or if they provide anything different than that already available in SimConnect and mapped to FSUIPC offsets. Pete