Zitat

FSUIPC4 version 4.10
This is a complete new user version

http://fsuipc.simflight.com/beta/Install_FSUIPC4_410.zip

Changes since 4.09 are:

1. This version is compatible with both the original FSX release and the update (SP1) made available in May 2007. If you install SP1 you need to be using FSUIPC 4.10 at minimum, or many things will not work correctly.

2. A solution has been devised for the Vista problem of writing to files in the FSX Modules folder. Consequently, the FSUIPC4 KEY, INI and LOG files are now all placed back there, where they really belong. When FSX is run after installing this (or a later) version of FSUIPC4, such files found in the “Documents\Flight Simulator X Files” folder will be automatically moved back to the Modules folder.

3. Solutions for some of the problems of weather filtering have been solved with FSX SP1, and you should now find it is okay to check the option, on the Miscellaneous page, to allow FSUIPC to influence FS’s own weather. Feedback on this is welcome. Unfortunately it is still not possible to provide the assorted smoothing options (wind, visibility, pressure).

4. The Clear Weather facilities (hot key, button and application interface) all now work properly provided the FSX SP1 update is installed.

5. The FS2000-compatible Advanced Weather Interface (AWI), as used by WeatherSet and some other programs (including WidevieW) is now capable of setting above-ground lower altitudes for the single visibility layer.

6. Changes to the Weather Mode being used are logged (i.e. whether Themed, Real-World, User Defined or Global). Unfortunately, due to FSX limitations, the initially-set mode is not determinable by program at present.

7. Facilities are provided to automatically write-back the Transponder value and the COM1 in-use and standby frequencies whenever they change. These are switchable in the Miscellaneous options page. These are used to overcome synchronisation problems for these two components in multiplayer and shared cockpit modes.

To avoid fast feedback problems preventing changes to these values, there is a delay imposed before the changes are written back. By default these delays are 1000 milliseconds (1 second) for the transponder and 100 milliseconds for the COM1 frequencies. FSUIPC4 waits for such a period of no changes before writing back the last change. If necessary the delays can be adjusted in the FSUIPC4.INI file:

ReWriteXpndrTime=n, milliseconds, default –1000 (off).
ReWriteCOM1Time=n, milliseconds, default –100 (off)

Negative values are used to indicate the facility is off, but still provide the time-out for when enabled via the Miscellaneous options. Non-zero timeout values of 10 or less are taken to mean “immediate” (not recommended).

Note that the re-writes can only be done on FSX visual frame changes in any case, so the granularity of the time is dependent upon the FSX frame rate.

8. Provided the SP1 update is installed for FSX, the “white messages” option now works for the single-line message window (but not yet for the FSUIPC multiline window facility).

9. Changes to the way the TCAS traffic data is accumulated allows AI traffic injected by programs such as VoxATC and on-line flying interface programs, to be shown more or less correctly. Where such traffic is not placed under FSX ATC control (i.e. with no FSX flight plan), no flight number identification is possible, however.

The airspeed and vertical speeds are computed in cases where these appear to be missing for aircraft in flight—this might occur, for example, when the driving program is moving the aircraft bodily rather than trying to make it fly.

10. A possible recursive loop, causing FSX to crash, resulting from trying to use a virtual button to repeatedly change a virtual button, is fixed. Virtual buttons are those represented by bits in the 36 bytes from offset 3340.

11. The GPSout sentence ‘GPVTG’ now has the correct kmph value inserted for the speed. The knots value was okay.

12. The pairs of values in offsets 3080 and 3088, and also in 31B0 and 31B8 have been found to have been interchanged. This is due to a misunderstanding of the order of values in a SimConnect XYZ structure.
The correct order should now be seen.

13. Offset 3BFC now contains the correct (computed) ZFW. It used to contain the “empty weight”, which is now available instead at offset 1330.

14. Offset 1334 contains the maximum gross weight for the aircraft, as a 32 bit integer, in lbs x 256.

15. Offset 3500 contains the user aircraft’s “ATC Model” string (from the Aircraft.cfg file), with up to 24 characters including a zero terminator.

16. An error in the Installer is fixed which could have caused problems if the registry install folder data is wrong and the user had to point the installer to the correct place for FSX.EXE.

17. The Logging and Monitoring facilities for SimConnect variables has been improved in this release. You can add a line in the form:

LogSimC=xxxx,xxxx ...

To the [General] section of the FSUIPC4.INI file, where each ‘xxxx’ is either an offset, or a range (xxxx-xxxx). The list can request several disparate offsets or ranges—the limit is imposed only by the INI file maximum line length (255 characters). Then, whenever the values associated with the listed offsets are read from or written to a SimConnect Variable (“SimVar”) those values are logged.

Additionally, for any Monitored offset (the Logging options page, right-hand side), if the options is selected to send the Monitored data to the normal log, the offset is also treated as a “LogSimC” offset automatically.