FSUIPC 2.96

[MeatWater]

...ab sofort HIER


Neuerungen:

Version 2.96 (February 2003) includes:
• Details of nearby ground AI traffic are now available for programs that can use them. The aircraft included are subject to an in-built range limit set to 6 nm if the user aircraft is airborne, or only 3 nm if the user is on the ground. This should be adequate for ground traffic avoidance calculations and airport movement plotting.
• The rate at which AI traffic is scanned has been increased to 10% per FS frame, with a parameter in the INI file (TrafficScanPerFrame) to adjust it (0=off, 100=all traffic updated on every frame).
• If either of the airborne or ground AI traffic tables becomes full, those aircraft furthest away are discarded in favour or new ones arriving if the latter are nearer. This means it is less important to limit the range, although the default of 40 nm for airborne traffic is still retained for performance reasons.
• The cloud options for FS2002 now allow the Virtual Sky or Jet Trails facilities as alternatives.
• A hot key assignment facility is added to hide or show the AdvDisplay window. This is for use with the new version of AdvDisplay (2.00) being released shortly after FSUIPC 2.96.
• The visibility smoothing and graduation operation updates the visibility values in FS at less frequent intervals in order to try to reduce the horizon flickering noticeable on some video cards, notably the Matrox Parhelia. Though it seems these phenomena might be video driver faults, it seems best not to provoke them!
• The upper altitude for the surface visibility layer is automatically adjusted to be above the METAR station elevation (if known). The adjustment is to 1000 feet above when graduated visibility is in operation, or 2000 feet above when it isn’t.
• FSUIPC is now conducting most of its operations once per frame, rather than at regular timer ticks (18/sec). This will mean it is sometimes slower, sometimes faster, just like FS itself. But more importantly it should lead to smoother operation of FS as a whole even in situations where there are many applications using FSUIPC. It may also lead to better stability, but time will tell. [To prevent FSUIPC stopping altogether in some circumstances, such as when FS is minimised, if the frame rate falls below 5 fps FSUIPC reverts to time-based operation until the frame rate rises].
• The operation of changing the gyro drift value (offset 0C3E) is made more consistent, though reading this will still only show the current FS value not the last value set, which may still be in the process of being applied.
• An error in FSUIPC’s processing of application hotkeys meant that these were passed onto FS even if the flag had been left clear to indicate that they should not be. In fact the operation of that flag was the reverse of that intended and documented. Since developers may have already discovered this, and reversed the setting of the flag in their programs to compensate, the correction wasn’t straight forward. The solution was to no longer use that original flag and use the next one up instead. This should mean that by default all current hot key users will set the options so that their hot keys are not passed through to FS. I think this is the safest assumption.
• A bug in the HotKeys page of the FSUIPC options resulted in the “Clear” buttons working correctly but not actually clearing the displayed key press. Additionally, in some releases the hot key changes were not being saved to the FSUIPC INI file.
• A bug in the derivation of the full network path of FS (the “UNC” path) meant that the path at offset 3E00 was only correct if the drive on which FS resided had been shared. If only the path had been shared the path in 3E00 was local, not network-usable.


Und hier die deutsche Anleitung

Die Anleitung ist allerdings etwas angestaubt, Version 2.87