Pete Dowson

Surely it can't be as old as 4.09! That date's back to the start of FSX, 10 years ago, and certainly won't work with FSX-SE. The current version is 4.949h and there is an interim update available called 4.949i. Apart from probably crashing FSX-SE, one of the main symptoms of using the wrong version of FSUIPC would be for it not to be able to locate the Controls list in a different version of the FS module "CONTROLS.DLL". If that occurs the only controls you eill see are those added by FSUIPC, with none of FS's inbuilt ones. ALWAYS look for the latest version. There is a lot of information about supported versions, and links to downloads, in the SubForums here. Please use them. And whenever reporting a problem or asking for help, please find your FSUIPC4.LOG file (in FS's Modules folder), and paste its contents here. That tells me a lot. Pete

They are a bit of a hack. The making process installs a hook into FS to trap the mouse click when it goes via a standard decision routine which determines what to do according to the mouse position at the time. If the decision is made using a table in a very specific SDK-defined format, then FSUIPC can catch the actual memory offset, in the Gauge, of the function to be called. it records this as part of the mouse call definition in the macro file. This only works if the table is there and in a specific format, generated by standard use of a now rather old SDK. In case the Gauge is updated and things move, a check sequence is also stored for comparison first, so crashes can be averted. This is why Mouse Macros usually have to be re-made if you update the aircraft. Pete

Well, it isn't my job to support LINDA, and I don't use it, but have you heard of search engines, such as Google? I just seached for Linda and immediately found fs-linda.com which certainly mentions both a manual and support forum. Pete

Yes, but also check that you are using FSUIPC 4.949i, just in case! Pete

If nothing happens on a specific button/dial it is likely that it doesn't support Mouse Macros. Only gauges written strictly to Microsoft's FS2002/2004 C/C++ gauge SDK are susceptible. That doesn't apply to most modern FSX add-on aircraft. In any case why would you resort to Mouse Macros for the NGX when PMDG has provided a complete range of custom controls for you to assign directly? Custom controls are assignable directly in FSUIPC when you select the <custom control> entry in the drop down. That's what it's for. Pete

The only other times I've seen those symptoms has been narrowed down to a corrupt P3D install. Which version of FSUIPC? This line seems to indicate it is the wrong version, not one for P3D3.2.3.2. 94 ### Failed to obtain SIM1 Frictions access: no frictions facilities available! There's only two ways that can happen - a corrupt SIM1.DLL (part of P3D) or the wrong version of FSUIPC ... the one you should be using, at minimum, is 4.949h. Unfortunately you've removed the top few lines of the log which tell me these things. I don't even know if you are running a registered version or not, which can be crucial! Please NEVER delete any lines in a log. You can obscure your email address if you like, but never delete any lines please. Incidentally, if you had checked in Download Links you would have seen that there's an interim update which fixes one bug which may help -- 4.949i. Have you tried that? To test properly that there's no interaction between FSUIPC and other loading DLLs you should have renamed your DLL.XML file and reinstalled FSUIPC4 so that only it loads. Pete

There's no event actually called "tower view". There are a number of VIEW events -- VIEW AUX 00 to 05 and VIEW CAMERA SELECT 0-9. You could try those. They would be the same as those assignable in FS. FSUIPC doesn't have any added view events, only what FS provides. I've always simply used the default A and S keys to select views. Pete

No. Pete

BUT I've no idea what version you are trying to install because you cut off the first lines telling me that essential fact! The latest version, released the day after P3D3.2.2 appeared, is the one you need. See the download links subforum where it tells you these things. It also seems like you installed P3D3 over the top of P3D2, without properly uninstalling version 2 -- that's ehsat the first few lines of your picture are telling you. The registry is in a mess as a consequence. Pete

Sorry. Two problems with that: 1. I'm no longer doing any FS9 development. After all it is now over 12 years old! The time came to move over exclusively to FSX/FSX-SE/P3D over a year ago. 2. I wouldn't know how to change the autogen dynamically. Someone would have to hack into FS9 innards to work it out. Maybe you could write a Lua program to open the menu (sending keypresses), then manipulating the sliders (using the Mouse library), but it wouldn't be much different to you doing it manually. Pete

Yes. FSUIPC4 is all written in a mixture of C and C++ with Assembly Code parts where needed. (FSUIPC3 is with VS 2005) WideClient is still with VS 2003, for backward compatibility with Win98 and XP, although I suspect it may have lost Win98 compatibility through recent use or additional Windows APIs. Pete

Ah, found it. I was looking at the original version, not the later update! Sorry. That structure seems to give you is some 24 x 14 "cells" each containing 3 bytes, "Symbol", "Clour" and "flags". Is the text made up of abutting the "symbols"? Are the "symbols" ASCII characters? Very strange implementation. Why not an array of 14 24-byte strings? I see it is enabled separately, and is a separate broadcast. So it'd be new code, not just an extension to my current implementation. And 1008 (24 x 14 x 3) bytes of offset to find. I can do it, but it will have to wait till about 2nd-3rd week of April. I am away later next week until then, and very busy till I depart. If you have seen nothing happen by, say, 18th April, do remind me. Pete

Are you sure you don't have any add-on AI traffic program, because the crash is in AI player. The probable reason it is more likely to crash with FSUIPC installed is that FSUIPC is reading the AI Traffic states al the time in order to populate the offsets for TCAS and Radar programs. I suspect you have some corruption in the traffic scenery BGLs or in the AI aircraft installed. I suppose it could also happen with default traffic, but it would seem less likely. It would still be useful to see a Log from FSUIPC4 from a session when a crash happened, instead off the only FSUIPC4 log you did supply which showed everything okay! Pete

The log ends at the exact point where FSUIPC is scanning the DirectInput devices for joysticks. You must have a rogue joystick driver installed which is hanging when being interrogated. You'll need to go into the Windows Device Manager, find anything relating to joysticks listed, maybe in the USB section, maybe in the "sound video and game controllers" section, and uninstall them, or at least any you do not recognise or no longer use. You can also use my HIDscanner program to do a similar scan 00 it may or may not hang as well. If it doesn't, at least it will give you information. t's in the "useful additional programs" thread in the Download Links subforum. There are also other useful USB inforamtion programs around -- USBview and USBDview come to mind. Pete

Sorry, I do not know this file header or structure. Where is this information? I've only ever seen the "PMDG_NGX_SDK.h", on which the structure in the offsets is derived. There's no other CDU information in there. Pete

Unfortunately FSX doesn't work that way. In FS9 and before FSUIPC could actually override a weather station's visibility. This was used to provide the graduated visibility feature. But in FSX and P3D you would need to read the station's current setting, change only the visibility setting, and write it back. And you'd need to do that for all nearby weather stations, because the effect is interpolated across the region. You could do it more easily in global weather mode. That is when the whole world has the same weather. There's onlly one set to deal with then. But FSX becomes localised quite quickly and to stay in global mode means resetting the weather each time. That doesn't look good except when changing flight situations. This is why all of the current weather control programs, to work well in FSX, have to do such complex things. I'm sorry, but I don't know of any easy way. Pete

Yes, there's the old FS2000 weather interface still there. But they didn't even work that well by FS2002 time, let alone FS2004 (FS9). That's why the "Advanced Weather Interface" was introduced, which worked properly in FS2002 and FS2004. But then FS2004 had a lot more weather capabilities, so the New Weather Interface was developed. And THAT is what you should be using in FS2004. In FSX and P3D more facilities were added, including reading and setting weather using SimConnect format METAR strings. But all three older interfaces were carried through, attempting compatibility, but I really wouldn't advise trying to use anything else in FSX other than the NWI, or Metar strings. Pete

Why do you have PFCFSX installed? And what is "PFCFSX. 4.410" compared to "pfxfsx.dll"? If you have no serial port PFC devices connected then you don't need PFCFSX. The PFC device you list is a USB device. It uses only PFCHID. Did you just go mad and install everything with "PFC" in the name? Why not actually read documentation to see what they do? And don't PFC supply any instructions at all with their devices? :-( I wish these manufacturers would support their products. Pete

Blame PMDG. That's where they are in its data structure. FSUIPC just spplies it as it is. I expect PMDG put the additions at the end to save folks who had already written programs for the original data set having to make changes to remain compatible. Pete

That signifies something wrong in itself. If you've never had FSX installed, how is it you have registry entries which say you have, i.e. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX That would be for FSX-SE. I assume you have installed it at some stage, and then just deleted it without properly uninstalling? You really do need to tidy that up -- remove the registry key for it altogether. Then another mess: you appear to have had P3D 2 installed and it looks as if you just overwrote it with P3D v3, as you have entries for both -- and both pointing to the same place! HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 SetupPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3 HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3 SetupPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\ Or is this mess all a result of using some horrible migration tool? I do eish those weren't use. It messes things up for proper installers. At least they should tidy up after them. Anyway, apart from those danger signals I see, I'm afraid there's no information about the actual running of FSUIPC there. I need to see the FSUIPC4.LOG itself. Pete

If you mean by program rather from the CDU on screen ;-), then for the 737NGX I think you can only get the Annunciator and Brightness Knob status (offsets 6599-65A3). Maybe there's another way, I don't know. Really this is a question for PMDG support. Pete

Possibly some clash with some other add-on, though I don't know of any and I use a lot and no one else has reported anything like that for years. To help further I would need to see a log relevant to the crash -- the one you posted shows it running fine and FSX-SE terminating normally. Also the crash data from Windows might help -- it might actually point to the module with the problem. If you can't get the details when Windows reports the crash, look in the Windows Event Viewer. Pete

Er, no. From that log, FSX-SE most certainly did NOT crash, it was terminated normally about 25 seconds after you were ready to fly with everything working. Look at the log you posted, here: ... 101978 System time = 14/03/2016 03:30:43, Simulator time = 12:01:22 (20:01Z) 101978 *** FSUIPC log file being closed Minimum frame rate was 27.2 fps, Maximum was 28.3 fps Minimum available memory recorded was 32768Mb Average frame rate for running time of 5 secs = 24.9 fps Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed *********** After that FSUIPC4 is not longer running and FSX-SE has closed without incident. Pete

You didn't look far enough then! The 737NGX offsets not only include the information you need for the Electrical Meter displays, they provide them ready formatted just as on the display itself. See offsets 6C40 and 6C4D in the "Offset Mapping for PMDG 737NGX" document! Pete

The latest offset lists are installed automatically into your FSUIPC Documents subfolder, as clearly stated in the list of things installed in the Installing and Registering guide inside the ZIP with the FSUIPC4 Installer. Did you NEVER even look at any of the FSUIPC Documents and other goodies supplied there? Provided your PMDG 737NGX is up to date, and you've allowed it in the PMSG SDK settings, all of the information relating to the 737NGX is provided in special offsets, listed in the List of PMDG 737NGX offsets document, also installed where you can easily find it! Pete