Einzelnen Beitrag anzeigen
Alt 19.12.2001, 12:51   #13
Marc
Inventar
 
Registriert seit: 01.03.2000
Beiträge: 3.197


Standard Aus dem AVSim Forum

The first fruits of the Fly! Beta Team are very near. We are now ready to make a formal announcement of our first phase of fixes, changes, additions, and extensions to Fly! II. As many of you know, this volunteer team was formed a couple of months ago to attempt to tackle some of the most requested items & issues with the Fly! II series.
We intend to release our first update on Friday, December 21. This is tentative and could change, though currently things look good for this date. The update will be approximately 6.5MB in size compressed, and will require about 20MB of free disk space on the drive containing Fly! II. You must be running Fly! II version 210 or later to apply this update.

Before I get to specifics, I would first like to recognize the group of folks who have dedicated so much of their time and energy to test, gather info, provide ideas, debate, and contribute to this effort. Without them this would never have been possible, and it's a testament to the wonderful community we have built. These guys have probably installed, removed, formatted, re-installed, and tested more than they would ever care to admit!! Please give your thanks to:

Alejandro Amigorena
Allen Kriesman
Anthony Merton
Braun Tacon
Chris Wallace
Colin Sare-Soar
Dann Church
Dan Martin
Dean Karis
Dominique Klein
Elrond Elvish
Frank D'hont
Jak Fearon
Jeff Burke
Jim Kanold
Ken Salter
Lefteris Kalamaras
Marc Stoering
Nick Curcio
Paul Nielson
Randall Rocke
Richard Harvey
Robert Randazzo
Todd Klaus

The beta team would also like to extend our great thanks and appreciation to AVSIM for supporting the team during our test cycle. In particular, kudos go out to:

Scott Brazell
Tom Allensworth

Now, for specifics. I've included a list of changes below of the items that are addressed in the first update, which is officially 2.01.230 (updated from 2.00.210). If an item near and dear to you is not listed below, it does not necessarily mean it will not be addressed -- it simply means it was either too time intensive or a lower priority for our first update. I also want to re-iterate that this and any future work is being done on a strictly volunteer basis, so we make no guarantees that any particular item will be addressed, nor that there will even be any future updates. It all depends on the participation of the beta team, and time available for coding & testing.

The changes/fixes/additions are:

General Fixes:

- Runway lights would twinkle in & out when approaching from a distance; fixed.
- Runway lights would sometimes not turn on even when taxiway lights were on; fixed.
- Basic flightplan printing now available
> After creating flight plan, press Ctrl+P to print
- Support for Z-sorted model objects
> Only necessary for objects with opacity maps that "bleed through" other models
> In factory.mlf (or .mlf) file, new flag added for this effect: B=Z-sorted (back to front)
> Optionally, add a <sort> tag inside the <mobj> definition in your scenery file to activate this feature
- Support for non-Zbuffered model objects
> Objects should be flat, and placed on a perfectly flat surface (designed for markings/striping)
> In factory.mlf (or .mlf) file, two new flags added: X=no collisions, Z=no z-buffer
> Optionally, add a <no_Z> tag inside the <mobj> definition in your scenery file to activate this feature
- Maximum display list items (visible models) increased to 12000 per scene
- Environment "Overview" window now displays altimeter in both inches Mercury (Hg) and hectopascals (hPa)
- Fly! now validates the render.ini file to make sure minimum slot counts are met.
- Airport lights now properly fade into fog in low visibility conditions
- Runways would stop drawing reciprocal end markings after crossing runway centerpoint; fixed.
- Runway and taxiway lights now properly fog in low visibility conditions.
- Runway markings on reciprocal end would draw in dark gray in low visibility conditions; fixed.
- Fixed "rainbow" cloud discoloration problem due to RGB value overflow.
- Airport beacons, radio towers, and moon opacity maps fixed. (Contributed by Jim Kanold)
- Runway and taxiway light artwork replaced.
- Clouds are now visually "whiter" during daylight hours by default.
- METAR reported winds will now populate winds aloft to match by default.
Marc ist offline   Mit Zitat antworten