Pete Dowson

Aha! Well done! Thanks for letting us know, and do get back to us with results. Pete

It is certainly the only way unless PFC have commissioned someone to produce dedicated drivers for MSFS for their now obsolete serial port range of controls, which seems extremely unlikely. I think they did do this for X-Plane, but that was long ago when the serial port based controls were current. All the later controls from PFC were either standard USB Joystick (Game Controller) types not requiring a special driver, or HID devices requiring either a driver they supplied, or my own PFCHid.DLL to interface to FSUIPC. Pete

Unless there is a bug in the aircraft code, or, as Thomas suggests, you are using an older FSUIPC, then all of the values supplied by the PMDG aircraft must be there, in those offsets, somewhere. It would help if you located exactly where your missing values are. To do this you can use the FInterrogate2 utility found in the FSUIPC SDK. Therer's a facility to do a three-pass test and for it to identify what changes occurred. So you start with a switch OFF, run pass 1, then ON, run pass 2, then OFF again, run pass 3. FSInterrogate will show each offset which changed accordingly. (Three passes because otherwise many changes would occur over two passes, but not so many change back again). A rather more laborious way, in case the displacement has been miscalculated somewhere, is to locate the nearest values below and above which appear to be correct. Then, if you can tell me which, i can double check those in between by dry-running (e.g. making a dummy structure matching that area and ensuring the right values go into the right locations. For this you could use your own program, or FSUIPC's logging, but do verify also with FSInterrogate. Pete

You posted into a reference subForum clearly marked 'not for support resident's. I've moved it for so it can be answered. There's no FSUIPC for Xplane. You probably need something called XPUIPC, a different program and on some other site, not here. We don't support Xplane, sorry. Pete

I can just throw in one idea. If the language you are using supports structures, then you could make structures based on the one supplied by PMDG in their SDK (installed with your aircraft). It's in the .h file. Then you could read all the offsets in a few blocks, directly into the structures. You can then just refer to them by name. Pete

The offsets have been validated by others as we don't have the aircraft. The offset positions reflect the structure documented by PMDG in their SDK (installed with every aircraft). If the value before (64F3, ICE annunWingAntiIceVALVE) and after (64F6, ICE annunWindowHeatINOP work okay, then the values for ICE WindowHeat Sw ON must be in the correct location too. What about 64F5, the other switch? Did you check that? maybe PMDG have put them in a different order to that which you expected, e.g. R-L instead of L-R. Pete

Hmmm. I think the actual surface is given in the BGL as a GUID referencing a texture file somewhere. I didn't think I got a surface type at present. Maybe concrete is default. The XML decode for the surface type is a GUID string like "{0e12195b-4a50-42d1-b8c8-177b270f3aab}" Checking the information I've received from others, the byte for surface type is labelled "for FSX legacy enum". I'll ask what that relly means, exactly. Checking further, the enum value for "concrete" is 0. So the field is simply not populated. I'll let you know. Pete

The picture you post is just of the basic FSUIPC7 window so I don't know why you posted it. what was the point of the picture? Assignments are, as usual, done via Menu facilities. Have you looked in the Menus? Pete

Good! Thanks for reporting this. Pete

Yes, it was down to new GUIDs. The INI has references to two devices which appear not to be connected at the time: E=CH FLIGHT SIM YOKE USB F=CH PRO PEDALS USB You do have assignments to E in the A2A Cessna, the Warrior, and the FSX Cessna profiles), but I can find none to F. Without the CH devices being connected, though, I can't fix that. Anyway, I've left the E= line in in case you reconnect it. That leaves the two HOTAS Warthog devices and the two MFD devices. If you replace the [JoyNames] section in the INI file with the following, most of your assignments should be fine. Those to those two CH devices won't work of course. [JoyNames] AutoAssignLetters=Yes E=CH FLIGHT SIM YOKE USB 0=F16 MFD 2 0.GUID={D06D41D0-2C92-11EA-8002-444553540000} D=F16 MFD 2 D.GUID={D06D41D0-2C92-11EA-8002-444553540000} 1=Joystick - HOTAS Warthog 1.GUID={61550B20-2BC0-11EA-8001-444553540000} A=Joystick - HOTAS Warthog A.GUID={61550B20-2BC0-11EA-8001-444553540000} 2=F16 MFD 1 2.GUID={D06CF3B0-2C92-11EA-8001-444553540000} C=F16 MFD 1 C.GUID={D06CF3B0-2C92-11EA-8001-444553540000} 3=Throttle - HOTAS Warthog 3.GUID={0AB01870-185D-11EB-8001-444553540000} B=Throttle - HOTAS Warthog B.GUID={0AB01870-185D-11EB-8001-444553540000} Pete

That's correct if you have a dedicated profile for that one aircraft, but if you want to keep the profile but just remove that one aircraft then you can find it in the list in the [Profile.<name>] section of the INI. Just remove the line referring to that model. Pete

So it's a HANG not a CRASH? What do you mean "shows to be missing"? There should be 2 copies of wxstationlist.bin (note the name which you have wrong). The default or 'master' copy is in your FSX weather folder. Don't touch that -- it is the one copied back into the AppData folder by FSX if you delete the (possibly corrupt) opy there. Be sure you are lookig in the right folder. It will be C:\Users\<YOUR USER NAME>\Roaming\Microsoft\FSX which is also where your FSX.CFG is. [LATER]] Oh, I see Thomas helped with that one, with the path illustrated. If that is without an add-ons running it means your FSX installation is corrupted. You need to uninstall it and re-install. [LATER] Seems you do anyway because of your missing wxstationlist.bin! Pete

Again, the log shows a successful start and close of the FSX session, this one lasting 78 seconds. There's no crash. If FSX crashes, FSUIPC, which is within FSX, would crash too. But FSX is being closed normally. You have no flights at all? Really? When you start FSX and go to the main Menu are there no flights listed for you to choose from? Did you delete them all? From the Log you did supply, you Flight is being loaded here: C:\Program Files (x86)\Steam\steamapps\common\FSX\flights\other\FLTSIM.FLT That appears to be the default flight for FSX-SE. So you've NEVER saved a flight? Normally folks set up the sim the way they want, with their chosen aircraft. You always start as if it is a new simulator you've just installed? Anyway, it is possible that default .WX is corrupted. Check the date on the file C:\Program Files (x86)\Steam\steamapps\common\FSX\flights\other\FLTSIM.WX if it isn't the same as on the FLTSIM.FLT file, delete it. Did you re-test after deleting the wxstationlist.bin file? I'm afraid that, so far, you've not supplied any information showing any crash at all in FSUIPC. Pete

Your Documents folder, the subfolder for FSX documents -- where your saved Flights are! Pete

Neither of the Windows crash log entries point to FSUIPC. The AI_Player one could be a corrupt AI aircraft model, but I've never seen a crash in MSCTF.DLL, whatever that is. I still need the FSUIPC log for a crashed session. And do try the weather file deletion test -- if any of those are corrupt then it won't make any difference whether FSXWX is running or not, because the damage is already done. But it might point to a previous crash or abortion of FSXWX which corrupted the file(s). Pete

Unfortunately the Log file you supplied is for a perfect session closed normally, but only lasting 101 seconds before FSX-SE was closed. No crash. So there's no useful information. we would need a log from a session which crashed. Additionally, if the sim is crashing then it is likely that Windows has logged the details. Use the Windows Event Viewer (Windows Logs -- Application), copy the info and paste it back here. Also, see if the crash still happens without FSXWX. I'm not sure what that is doing. If it is crashing just when FSX is ready to fly, or before, that it might be a corrupted weather file. SimConnect reads the .WX and wxstationlist.bin files without applying checks, and any corruption can cause crashes and other unpredictable results. So try deleting the .WX files from your FSX Documents folder, and the wxstationlist.bin file in your Appdata folder for FSX (where your FSX.CFG file is). Pete

Yes. Pete

As Thomas suggests, you need to update your FSX installation. There were many bugs in the original. You can get both SP1 ans SP2 updates from the Microsoft websites. Here for example: https://www.microsoft.com/en-gb/download/details.aspx?id=8986 Pete

Please take a look in the Modules folder in your FSX installation. See if these files are there: FSUIPC4.LOG FSUIPC4 Install.LOG If either or both are there please show us them -- you can attach them, in ZIP files if necessary for size. Also, please check Windows' Event Viewer (type event viewer in the search edit box bottom left corner). See if there's an error logged in the Windows Logs-Application section. If so please copy the details and paste them in a message here. Pete

For such detail you only need to check on FSUIPC.com. You need FSUIPC4 to go with FSX-SE. All documentation is included in the download. You can download and install it and read the User documentation supplied before buying it. Then you go to SimMarket and check the price there for purchasing a registration key. You'd need to run the Installer again to register. Pete

But my point is: when would you ever turn it to a negative value, assuming you could? To stop the control "breaking" just program it to stop at zero -- i.e just keep at zero. Or ask MS/Asobo to change SimConnect to let you set negative values. It would be good, too to find out if you really can set negative values in the real aircraft. Have you done' any such checking? I'm sure you can't with any Boeing or Airbus airliners, nor in the Cessna I took my flying lessons in. Pete

I think you missed my question, which wasn't about HOW, but WHY? Anyway. onwards: Because that's what it receives from SimConnect. I think it writes a FLT32 also. BUT the offset is defined as a Signed Dword (SD or S32). Most offsets are designed to match what FSUIPC has always provided, since FS98. In those days the offsets were actual values in an FS module, not mapped after reading them through an interface. FSUIPC has striven to maintain compatibility across all versions of FS since FS98. New facilities and data are added, but the original ones are continued as far as possible, so applications can continue to work with changing flight simulator versions. That was always its main purpose. If you want to write an application specifically dedicated on one flight Simulator then you probably should use it's provided interface (SimConnect in MSFS) directly. Pete

If the SimConnect facility to write a negative value to the Sim Var doesn't allow it then I don't think anything FSUIPC can do will fix it/ If this is something you really believe is needed then you should put the request to MS / Asobo on Zendesk. BTW could you explain, please, when you'd actually want to use a negative altitude for the autopilot? I know some parts of the world are below sea level, but you wouldn't use the A/P at low altitudes in any case, except maybe in landing (APPR) mode,, in which case the descent is via a glideslope in any case, not a target altitude. Pete

That's because it isn't a Float32. Why did you select that? To see the Signed DWORD value you'd use S32 (Signed 32-bit). Or, better, UIF32. Please see the description of the Types in the Advanced User manual (about page 15 or so, depending on edition). Search for the heading "Monitor facilities". Because it isn't a FLT!!!! I already pointed out to you that it's an SD! Have you forgotten already? Please do read the descriptions of offsets before misusing them! It's metres*65536, so to write -100 metres you'd write -6553600. For feet write (-100 / 3.28084) * 65536. But as SD. Pete

It's a support request, so goes into the Support Forum, not "Announcements"! I've moved it. Add-on airports using the "add-on.xml" facilities have to be located and listed in the MakeRwys_Scenery.cfg which is automatically created by the Lorby program. Check that file. AddOns will normally be found at the end. Note that many add-ons won't be registered for use in P3d until you actually run P3D after installing the add-on. That's because it just doesn't go wrong if you follow the instructions. Make sure you run MakeRwys.exe "as administrator" (a right-click option). If the Lorby program is failing that will need support from Lorby-Si. But first check that MakeRwys_Scenery.cfg file. Pete