Pete Dowson

You contradicted this in your previous message So, I am now thoroughly confused. If it works with PFChid.dll in FSX it must also work with PFChid64.dll in P3D4/5 and MSFS. Are you now saying it doesn't work with either? BUT I have never seen a PFC GPS device and therefore have never developed anything for it. As it is recognised by the Scan then there's a possibility that some of the command blocks it sends to the PC are actually covered already by the PFC driver I wrote, but there are probably parts which it won't recognise. There's also the possibility that it operates as a Joystick type device in which can the buttons and switches should be visible to Windows and therefor FS and MSFS without the need for a driver. I haven't done any development work for PFC devices for a long, long time. I assumed PFC only sold the newer devices for use with X-Plane. Did they say it worked with FS? I am retired now and not really able to do further developments. It might be better if you asked PFC about it. Pete

Are you using PFChid.dll with FSUIPC4? Using the same settings as in FSUIPC4 there should be no difference at all. As far as PFChid64.dll is concerned the only difference at all from PFChid.dll is the re-compilation as a 64-bit module instead of 32 bit. The log appears to show that the device hung and stopped processing data sent to it, hence continuous buffer full errors. Pete

The profile system isn't designed to do that. But you could do it by making another entry for the aircraft with a different title. Open the aircraft's Aircraft.CFG file and fine a section like this: [fltsim.0] title=F-14 sim=F14 model= panel= sound= texture= kb_checklists= kb_reference= atc_id=N001 atc_airline=NAVY atc_flight_number=001 ui_manufacturer="Grumman" ui_type="F14" ui_variation="Grey" ui_typerole="Twin Engine Jet" ui_createdby="LM" description="The Grumman F-14 Tomcat is a supersonic, twin-engine, two-seat, variable-sweep wing fighter aircraft. The Tomcat was developed for the United States Navy's Naval Fighter Experimental (VFX) program following the collapse of the F-111B project. The F-14 was the first of the American teen-series fighters which were designed incorporating the experience of air combat against MiG fighters during the Vietnam War." Make a copy of such a section, placing it later in the CFG file with a new number -- [fltsim.1] in the above case, or where there are more such sections, the next number in sequence after the last,=. Then, in your new section, change the Title= line to give it a name which you can use specifically for the other profile. Pete

Note that FSUIPC7 needs a different purchased registration to earlier versions FSUIPC4, 5 and 6. How is the Sim supposed to "start" the radio? Do you mean some sort of driver for your hardware? If so it is definitely a matter for OpenCockpits support. Sorry, I've no idea. I do not know this hardware and simply cannot support products other than our own. I suggest you check the documentaion supplied with your radio, or contact their support for help. Pete

Glad it is all sorted. Good flying! Pete

Many FSX cockpits don't use the standard C++ tools for their gauges. Mouse macros only work for standard C/C++ gauges becuae they depend on intercepting the code called by the mouse click. You'll probably need to look for other methods. Best is to use whatever FS control operates the switch (detect this with event logging). There's also L:Vars to try -- list those (there's an FS control to do that, and a provided Lua plug-in to log them as they change). For PMDG Boeings there are many added controls listed in the aircraft's SDK. Pete

This message occurs when FSX has previously crashed with FSUIPC still trying to close things down tidily. Being the module with the last thread running, Windows wrongly attributes the failure to it and this gets marked so in the Registry. Sometimes telling FS to carry on and load FSUIPC works and clears the condition. If this doesn't help, even after a couple of attempts, then it could be a corrupted weather file, possibly caused by the crash. For this please refer to This thread may also be helpful: Failing all this, you'll need to supply an FSUIPC4.LOG file after FSX crashes when telling it to load FSUIPC. Pete

There will be no new version of FSUIPC4 for FSX. Development was frozen some time ago. The only recent changes were for the installer to cope with the Microsoft FSX-SE Beta (years ago now) and a rebuild using a later compiler version. FSUIPC does not cause any crashes itself. It passively receives data from SimConnect to populate the offsets. It only actively does things in response to requests from applications or the assignments made by users. It is in regular use on uncountable installations of FSX, FSX-SE and P3D versions before P3D4. Crashes tend to get blamed on FSUIPC because it is ubiquitous, but they all turn out to be due to other things on the user's system. Pete Pete

Then I don't think they are panels as such. They are just different preset views, which I think you can accomplish by moving your view around. I suspect a lot of add-on aircraft with so-called 3D cockpits don't actually bother with the traditional 2D panels as such, as you can move around and zoom in and out as you like. From your PANEL.CFG I see panels iwth IDs 29, 10002, 10005, RADIO_STACK_PANEL, GPS_PANEL, 11004, 11223, 11005, 10050, 10007, 11040, 11041. I can't tell what they all are -- the gauge names for some are rather obscure. But you could try them. Pete Pete

ALL THREE parts need to be exactly correct -- name, email and key, not just the key. And please read the documentation to make sure you are following the correct procedure. I'm afraid if you still get no joy you may been to wait till next week as John is on holiday at present. Pete

Both that and the previous one do not indicate FSUIPC as the culprit. The Log too shows normal running. I'm afraid you have something else going on. If it NEVER crashes with FSUIPC not running then you need to check your other add-ons to see which is using FSUIPC. Otherwise you'll need to consider an FSX re-install. Something is corrupt. It may be an add-on aircraft or add-on scenery if not the main FSX modules. Try a different aircraft to start with. And also keep track of what scenery is in use when it crashes (i.e. where you are flying over). Pete

Seems very strange to me. Which name is used in the selection to load the aircraft? Will users be aware of the Air file name so they can edit the Profile sections correctly should they wish? I think I’ll have to leave it to John — he’s away till Monday. I assume he’s doing something different with profile matching in FSUIPC7, otherwise I can’t see how those profiles end up classified the way you describe. Pete

Sorry, I don't follow you. The names used are from the title= lines in the Aircraft.CFG, the ones used in the sim's selection list. You are saying that some substring of British Airways OperatorLand468 FBW matches Airbus A320 Neo Asobo Now, how do you think that can be? Please explain. Is the title not used for selection in MSFS? Pete

Delete the one in your AppData\Roaming folder. FSX will regenerate it. Pete

The FSUIPC options display does make FS blackout the main display. But the options dialogue should show on top. Try first setting FS into Windowed mode (ALT+ENTER). If the options then show then for some reason they were previously showing underneath the main FS display. The only other possibility is that the options are being displayed off-screen, maybe because you've changed screen arrangements. In this case, close FS and look in the FSUIPC4.INI file. If there's a OptionsDialogOffset parameter line in the [General] section, delete it. Pete

Please always supply the FSUIPC4.log file after a crash (ZIP if too big), and the actual Event Viewer details from Windows, not just an offset! As this appears to be at random it does sound likely to be a corrupted weather file, which in turn cuases something in memory to be corrupted when FSUIPC asks SimConnect to supply weather. To test for this, try adding NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad. Pete

Find the PANEL.CFG file for the aircraft -- it'll be in a folder with Panel in the name, within the files for the aircraft. In there look for the Ident= line. Please refer to the explanation given here: https://docs.flightsimulator.com/html/Content_Configuration/Instruments/Panel_Config_Definition.htm If there is no such line, you can add one yourself giving it a unique ID number (10000 - 19999 as it says). If there's a name given, look it up here: // Panel identifiers #define IDENT_MAIN_PANEL 0 #define IDENT_MAIN_PANEL_ALT1 1 #define IDENT_MAIN_PANEL_ALT2 2 #define IDENT_MAIN_PANEL_ALT3 3 #define IDENT_MAIN_PANEL_ALT4 4 #define IDENT_MAIN_PANEL_ALT5 5 #define IDENT_MAIN_PANEL_ALT6 6 #define IDENT_MAIN_PANEL_ALT7 7 #define IDENT_MAIN_PANEL_ALT8 8 #define IDENT_MAIN_PANEL_ALT9 9 #define IDENT_THROTTLE_PANEL 10 #define IDENT_RADIO_STACK_PANEL 50 #define IDENT_COMPASS_PANEL 75 #define IDENT_MINI_CONTROLS_PANEL 100 #define IDENT_ANNUNCIATOR_PANEL 125 #define IDENT_ANNUNCIATOR2_PANEL 150 #define IDENT_IFR_MAIN_PANEL 175 #define IDENT_COLLECTIVE_PANEL 200 #define IDENT_GPS_PANEL 225 #define IDENT_OVERHEAD_PANEL 250 #define IDENT_PARKING_BRAKE_PANEL 251 #define IDENT_FLAPS_TRIM_PANEL 252 #define IDENT_FUEL_PANEL 253 #define IDENT_ELECTRICAL_PANEL 254 #define IDENT_TRIM_PANEL 255 #define IDENT_LANDING_GEAR_PANEL 256 #define IDENT_MISC_POPUP_1 260 #define IDENT_MISC_POPUP_2 261 #define IDENT_MISC_POPUP_3 262 #define IDENT_MISC_POPUP_4 263 #define IDENT_MISC_POPUP_5 264 #define IDENT_MISC_POPUP_6 265 #define IDENT_MISC_POPUP_7 266 #define IDENT_MISC_POPUP_8 267 #define IDENT_MISC_POPUP_9 268 #define IDENT_MISC_POPUP_10 269 to get the ID. Then you should be able to toggle the panel on and off using the PANEL_ID_TOGGLE control, or open / close it using PANEL_ID_OPEN and PANEL_ID_CLOSE. Pete

Oh, easier than I thought. The Log still shows this error: 172 WARNING: Joystick ID 1 is duplicated in Registry But it seems that this doesn't adversely affect the outcome. I think the "other" device ID 1 must be the data channel on the X56, used (I think) only for firmware updates. Good flying! Pete

The problem seems to be that both devices are Registered with the same ID, as indicated by this error message in the Log: 219 WARNING: Joystick ID 1 is duplicated in Registry So, first thing to try is changing this part of the INI file [JoyNames] AutoAssignLetters=Yes 0=Alpha Flight Controls 0.GUID={FB3177A0-6E0F-11EB-8014-444553540000} A=X56 H.O.T.A.S. Throttle << MISSING JOYSTICK >> A.GUID={FB3177A0-6E0F-11EB-8014-444553540000} B=Alpha Flight Controls B.GUID={FB3177A0-6E0F-11EB-8014-444553540000} To this: JoyNames] AutoAssignLetters=Yes 0=X56 H.O.T.A.S. Throttle 0.GUID={FB3177A0-6E0F-11EB-8014-444553540000} 3=Alpha Flight Controls 3.GUID={FB3177A0-6E0F-11EB-8014-444553540000} A=X56 H.O.T.A.S. Throttle A.GUID={FB3177A0-6E0F-11EB-8014-444553540000} B=Alpha Flight Controls B.GUID={FB3177A0-6E0F-11EB-8014-444553540000} Also there are unwanted assignments in the [Axes.Twin-jet] section: 4=2X,256,D,1,0,0,0 -{ DIRECT: Aileron }- 5=2Y,256,D,2,0,0,0 -{ DIRECT: Elevator }- 6=2R,256,D,3,0,0,0 -{ DIRECT: Rudder }- Remove those as you no longer have a device with ID 2. Let me know how that goes when you have both devices connected (same files again please). If there's still a clash we may need to look at editing the Registry. (Ugh). Pete

As John points out, this is a question for Dave at Pilot2ATC. The support forum is here: https://www.avsim.com/forums/forum/713-pilot2atc-users-forum/ Pete

You need to buy one from SimMarket -- https://secure.simmarket.com/pete-dowson-fsuipc4.phtml Pete

No, the LorbySceneryExport program does the job of making a scenery cfg file which includes all scenery.cfg layers and the Add-Ons xml layers too, in the correct processing order. Using it for P3D5 is exactly the same as for P3D4, so it needs installing in the same way, and running in the same way ("as administrator"). If you are getting no results check the MakeRwys_scenery.cfg file and look at the Runways.txt file to see if any errors are reported. Pete

What problems do you have? If you mean the PFC COM and/or HID DLLs, then there's no "installation" necessary other than placing them into the same folder as the FSUIPC7 DLL. Pete

The trim values in FSUIPC offsets are from SimConnect, but they all relate to the built-in subsystems. Detailed addon aircraft such as those from PMDG tend to provide their own subsystems supplanting the default ones. This is why the PMDG SDK is so important -- these's no otherway to set or get subsystem values. The fact that the current trim vales aren't available from the SDK (and hence not from the PMDG offsets either) is rather strange. I suggest that you ask PMDG about that. Pete

The ThrottleN_Set sequence of controls date back to FS98 or earlier, and provide a reverse thrust zone as well as forward thrust. That's what FSUIPC supports them and uses them for reverse/forward calibration. The Axis ... Set controls are relatively new and provide no reverse zone. Some add-on aircraft work better with those than they do with the older ones. Pete