The P3d version 4 compatible version of FSUIPC, FSUIPC5, is now released.
There are still be items not (yet) implemented. The document reproduced fully below will accompany each release, in the Download ZIP, updated each time till it is no longer needed. I am providing this detail in advance so that those of you needing any of these facilities will nto be disappointed.
IMPORTANT: What is missing in FSUIPC5? (For Version 5.10, first public release)
There are a number of items currently not implemented but which hopefully are to follow in due course (sorry, no dates predictable at present). These are:
1. GoFlight button and switch support: this depends on a module from GoFlight called GFDev.DLL, and a 64-bit version of this module is needed. (GoFlight devices connected via WideFS are okay, still using a 32-bit WideClient and 32-bit GFDev.DLL locally to the client PC).
2. VRInsight original serial port device support.
3. PFC COM serial port devices previously using PFCFSX.DLL. The conversion of this module to the 64-bit version (potentially called PFCCOM64.DLL) will be under way shortly after the public release of FSUIPC5.
4. PFC Hid devices previously using PFCHID.DLL. The conversion of this module to the 64-bit version (potentially called PFCHID64.DLL) will be under way shortly after the public release of FSUIPC5.
5. AS16 Weather Radar: this will hopefully be implemented as and when the P3D4 version of AS16 is released with details of its Radar interface.
6. “ASE” Metar reading, for the offsets read for weather at airport when it will be set by Active Sky. I don’t think this facility is used these days, so it may not be implemented. It is certainly of a low priority. Programs needing such information are now better reading the AS16 (etc) Weather files themselves, which are stored in a known sharable folder.
7. WideFS file transfer: this is probably not used at all these days, so will be discontinued.
8. Ground friction tables: P3D improvements to ground friction will possibly make these facilities reducndant, but even if not I am dependent on L-M exposing them in a tidy implementation rather than having to hack through 64-bit code and data structures
9. Display window and Lua displays: in previous versions these were implemented by a very convoluted hack into the sim’s internals. For 64-bit P3D I’m instead dependent upone L-M to implement appropriate functions. Meanwhile, displays will be routed to the default “message window”, as used for general messages and which by default in a bar along the top (which can be resized, moved and undocked).
10. Mouse Macros: I have asked L-M for facilities to allow this to be implemented, hopefully in a much nice fashion than the 32-bit hacks which are really quite crude in their operation. However, to be honest, I’m afraid this is one of the things I’ve got less confidence in L-M coming up with anything.
11. SimConnect Text & Menu Interception: Now, as a cockpit user, this is one of the main things I’m interested in. I do NOT like to spoil the view out of the window by having text messages and, worse, menus drawn in the sky or over nearby buildings. The interception facilities in previous versions work reasonably well. The text is moved completely, and the menus moved to a less conspicuous place in a smaller window. Both parts are transmitted to WideClient for display locally, inside the cockpit, on a client PC. I will be pressing L-M hard for a good implementation of this.
12. Control acceleration fix: I’ve really no idea if this is still necessary. Was implemented to prevent controls automatically accelerating (e.g 1 degree to 10 degree changes) even when used slowly if an intervening control occurred which was ‘quicker’ (i.e within the accelerator’s time test). This tended to happen a lot with some of the more sophisticated add-on aircraft (PMDG in particular) which were in the habit of sending FS controls all the time. Anyway, it is on the list sent to L-M, but at a low priority.