FSUIPC 3.65 erschienen

[globalrailer]

http://www.schiratti.com/dowson.html

[Beckmann]

Was kann es mehr ?

[Buschflieger]

Original geschrieben von Beckmann
Was kann es mehr ?

runterladen und (lesenswerte Doku lesen):

Version 3.65 (June 2006):
· Most importantly, this fixes an error in 3.60 which makes it crash towards the end of June with a Beta-version expiry message!

· A new axis control is added, for direct assignment in the Axis assignments tab, for a Steering Tiller. This uses the FS Rudder control, but can be calibrated separately (eg to be more responsive -- use the inverse S-shaped slope options).
If the steering tiller axis is assigned, you must then calibrate it in FSUIPC's Joysticks section (this is on the same page as the PAN controls, sorry). It is then used as follows:
When on the ground and at any ground speed less than 60 knots (default -- adjustable by MaxSteerSpeed parameter in the INI), the actual FS rudder action is controlled by a blend of the tiller and rudder axis inputs. At low speed it is predominantly tiller, and as speed increases the tiller becomes gradually less effective and the rudder input more so. Above the MaxSteerSpeed, or in the air, the tiller has no effect.
As with all of the axis and joystick facilities, the calibrations, assigmnents and parameters such as MaxSteerSpeed, can be different for different aircraft.

· The axis assignments facility has been thoroughly overhauled internally to make the “aircraft specific” aspects work more reliably and usefully. In the original release it was easy to get things tangled up between axes generally applied and those which should have been specific to the current aircraft, and the saved parameters were often in error.
Now FSUIPC only retains one set of assignments in memory and therefore in action. This will be the general [Axes] set if the currently loaded aircraft has no specific assignments, otherwise it will be the latter. The short aircraft name option (needing INI file editing) applies just as for Buttons, Keys and Calibrations.
When the aircraft specific option is selected for an aircraft you are now presented with an option to retain (copy) all the general ones, to work from as a basis, or to start from a clean sheet. For minor variations you will probably opt for the former, but if you have completely separate controls for, say, a Boeing and an Airbus, or a prop and a helicopter, then you might find it easier to start again for each one.
If you try to uncheck the ‘aircraft specific’ option, you will be offered the choice to delete all the specific assignments for the current aircraft. If you decline, then the aircraft specific setting remains. This is a cleaner way of removing aircraft settings than deleting the section in the INI file.
At various stages you may be given the option to save any changes made so far. If you don’t do this then axis assignment changes since entering the Options system may be lost.

· A bug is fixed that corrupted the Payload Count value being read from offset 13FC. The value supplied by version 3.60 was very large, and any program not imposing the limit of 61 documented in the Programmer's Guide may appear to hang whilst attempting to read the millions of entries. Etienne Martin's pushback gauge (ATN) is one such application, there may be more.

· An error on FS2004 that could, on some systems, cause the AI traffic information to omit the runways in use, is fixed. This would have affected Radar Contact 4 users.

· Buttons and dials on recent GoFlight devices, such as the MCP Pro, should now be detected correctly by FSUIPC’s Button programming facilities. This needs an up-to-date copy of GF’s “GFDev.dll” (version 1.61.02 or later, dated May 2006), available from my Support Forum.

· Messages to FS’s message display are now not suppressed when FS is busy with a dialogue or progress bar showing. Apparently this could have caused time zone messages to be missed with FSRealTime.

· The INI option “RemoveATC=Yes” should now work on non-English versions of FS. It appears that the Window name is language dependent.

· Additional FSUIPC offset controls are provided to deal with floating point values:
Offset float32 set/1000 (encoded 7000zzzz)
Offset float64 set/1000 (encoded 7400zzzz)
Offset float32 inc/1000 (encoded 7800zzzz)
Offset float64 inc/1000 (encoded 7C00zzzz)
In each case the parameter is a signed 32-bit integer, but this is divided by 1000 (decimal) in the appropriate floating point format before it is written to the offset specified (zzzz in the above encodings, but entered as xZZZZ in the on-line dialogue). For “decrements” use a negative parameter in the increment controls.

· FSUIPC supports the new facilities in WideFS (version 6.599a or later) to copy files from anywhere on the FS system to any WideFS client PC. Please see WideFS for more details.