Sign in to follow this  
Guest Gregg580

Okay..... I have Fly!2 reinstalled

Recommended Posts

.... and patched up to build 210. What advantage is there to patching up to build 230?Also, in the Setup splash screen, I enabled DX8 T&L; it recognized my video card (GEForce2 Ti); and I choose >32 mg video RAM. I started up at the default SanFran airport, but at sunset, there was no nice golden glow on my plane. (I enabled the "environmental mapping under Options). What did I miss? My next task will be to install the fixes and such for the various planes...... get my 3rd party planes reinstalled..... not to mention the TS sceneries that I've downloaded. Boy! will I be busy this weekend.-Lindy :-spacecraft

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

LindyTaken from the readme 230:------------------------CHANGE LOG------------------------There have been numerous changes made to Fly! II for this patch release. One of the most significant is the inclusion of "fly2slice.exe", which automates the creation of scenery with the TerraScene 2.1 scenery creation system. With these two tools installed, you can create stunning, photo-realistic VFR scenery with the click of a mouse! The pairing of these tools into a seamless system greatly enhances the ease of scenery generation. You must download and install TerraScene 2.1 or later for this feature to work.The following code changes, bug fixes, and enhancements have been added to Fly! II since the 210 patch release:General Fixes:- Taxiway lights could overflow maximum vertice count in renderer. Fixed.- Taxiway pavement had hard coded cutoff of 3nmi. or 5000' AGL. This has been changed to the .ini settings viewableTaxiwayLightDistance and viewableTaxiwayHeight.- Taxiway lights had hard coded cutoff of 3nmi. This has been changed to the .ini setting viewableTaxiwayLightDistance.- Tweaked blue taxiway lights to be more blue and less purple- German language translations corrected (contributed by Marc Stoering)- Tweaked flight plan printout to add a small amount of footer margin to prevent partial lines at bottom of the page.- Some users felt airports were too "bright"/visible from a distance at night. This can now be adjusted by tweaking light fade-out intensity: - In [Graphics] section of FLY.INI, set runwayLightDistanceFadeMinFeet to distance in feet where lights began to lose intensity - In [Graphics] section of FLY.INI, set runwayLightDistanceFadeMaxFeet to distance in feet where lights are at lowest intensity - In [Graphics] section of FLY.INI, set runwayLightDistanceFadeMaxRatio to set percentage of how much lights fade at max intensity (0..100)- Overall light intensities for various airport lights can now be tuned in the FLY.INI file: - In [Graphics] section, set INTENSITY_STANDARD to adjust standard airport lighting intensity - In [Graphics] section, set INTENSITY_CENTERLINE to adjust centerline airport lighting intensity - In [Graphics] section, set INTENSITY_TOUCHDOWN to adjust touchdown airport lighting intensity - In [Graphics] section, set INTENSITY_ALSF to adjust ALSF airport lighting intensity - In [Graphics] section, set INTENSITY_RAIL to adjust RAIL airport lighting intensity - In [Graphics] section, set INTENSITY_VASI to adjust VASI airport lighting intensity - In [Graphics] section, set INTENSITY_REIL to adjust REIL airport lighting intensity - In [Graphics] section, set INTENSITY_TAXIWAY to adjust taxiway airport lighting intensity- Clouds of the same type on different layers should no longer align themselves vertically.- On debug tab screen, Navaid count was calculated incorrectly. Fixed.- Replaced VOR model with higher detailed version (contributed by Biber Salsa)- 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 [custom].mlf) file, new flag added for this effect: B=Z-sorted (back to front) - Optionally, add a tag inside the 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 [custom].mlf) file, two new flags added: X=no collisions, Z=no z-buffer - Optionally, add a tag inside the definition in your scenery file to activate this feature- Maximum display list items (visible models) increased to 12000 per scene- Added .INI variable to allow customizing of the distance runway lights "fade" into fog - In [Graphics] section, set runwayLightFogPenetration=XXX, where XXX is the fade distance in feet (1000 is default)- 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.- Added REIL to ALSF1 and ALSF2 (coding by Chris Wallace)- Added new .INI variable to allow Fly! to still operate when running in the background. - In [Game] section of fly.ini file, set suspendOnTaskSwitch=0 to allow background idle processing- 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.- Cloud light scalars can be modified in the .INI file for dawn, day, dusk, and night: - In [Graphics] section, set lightScalarDawn=XXX, where XXX is percentage of light scalar (0..100; 50 is default) - In [Graphics] section, set lightScalarDay=XXX, where XXX is percentage of light scalar (0..100; 100 is default) - In [Graphics] section, set lightScalarDusk=XXX, where XXX is percentage of light scalar (0..100; 50 is default) - In [Graphics] section, set lightScalarNight=XXX, where XXX is percentage of light scalar (0..100; 25 is default)- METAR reported winds will now populate winds aloft to match by default.- METAR input routines converted meters to feet with incorrect formula. Fixed.- Cockpit camera head pitch is now saved to .INI file to remember last setting.- Environment "Other..." window altimeter slider no longer snaps to ticks, allowing finer control of setting.- PAPI light spacing adjusted (coding by Chris Wallace)- ODALS lighting should flash in sequence, not in unison. (coding by Chris Wallace)- All default PAPI lights use a 4-light configuration instead of 2-light (coding by Chris Wallace)- Added sequenced flashing lights to codes 23, 24, 33 and 39 (coding by Chris Wallace)- Added new runway marking database code (9) for ICAO PIR markings as per UK CAP637 (coding by Chris Wallace)- Implemented new type of bright 'strobe' light for REIL, PAPI and sequenced flashers (coding by Chris Wallace)- ALSF1 and ALSF2 length extended to more common 3000' (coding by Chris Wallace)- ALSF1 and ALSF2 sequence light extended to 20 lights to encompass full 3000' length (coding by Chris Wallace)- Added new runway marking database code (8) for ICAO PIR markings as per UK CAP637 (coding by Chris Wallace)- Implemented REIL (Runway End Identification Lights) (coding by Chris Wallace)- Implemented new versions of ALSF1 and ALSF2 which use CLightLine class (coding by Chris Wallace)- Implemented Approach Lighting AI (Centerline & Bar), database code 17 (coding by Chris Wallace)- Implemented Approach Lighting BG (Left Single Row), database code 20 (coding by Chris Wallace)- Implemented Approach Lighting BF (Center Row), database code 21 (coding by Chris Wallace)- Implemented Approach Lighting BO (Center Row), database code 23 (coding by Chris Wallace)- Implemented Approach Lighting BP (NATO Standard), database code 24 (coding by Chris Wallace)- Implemented Approach Lighting BS (Center Row), database code 27 (coding by Chris Wallace)- Implemented Approach Lighting E (Two Parallel Row), database code 30 (coding by Chris Wallace)- Implemented Approach Lighting J (Calvert CAT II), database code 33 (coding by Chris Wallace)- Implemented Approach Lighting S (Cross), database code 38 (coding by Chris Wallace)- Implemented Approach Lighting T (Calvert CAT I), database code 39 (coding by Chris Wallace)- Implemented Approach Lighting X (Centerline 2 Crossbars), database code 41 (coding by Chris Wallace)- Implemented Approach Lighting B (US Configuration), database code 18 (coding by Chris Wallace)- Implemented Approach Lighting Q (Alternate Centerline and Bar), database code 37 (coding by Chris Wallace)- Implemented Approach Lighting O (Centerline), database code 36 (coding by Chris Wallace)- Implemented Approach Lighting M (Single Row Centreline), database code 34 (coding by Chris Wallace)- Implemented Approach Lighting N (Narrow Multi Cross), database code 35 (coding by Chris Wallace)- Implemented Approach Lighting BN (Former NATO Standard), database code 22 (coding by Chris Wallace)- Directional gyro gauge correction knob was broken in the Flyhawk (VFR and IFR panels). Fixed.- Runways now honor the glideslope angle defined by glideslope ILS entry tied to the runway.- Localizer/DME combinations were not shown in runway frequency list. Fixed.- DME components are now tracked independent of the localizer location.- Added new .INI variables to extend visibility of taxiway pavement, markings, and lights. - In [Graphics] section, set viewableTaxiwayPavementDistance=XXXXX, where XXXXX is slant distance in feet - In [Graphics] section, set viewableTaxiwayLightDistance=XXXXX, where XXXXX is slant distance in feet - In [Graphics] section, set viewableTaxiwayMarkingDistance=XXXXX, where XXXXX is slant distance in feet - In [Graphics] section, set viewableTaxiwayHeight=XXXXX, where XXXXX is AGL distance in feet- Auto-tune would not work with ADF radio. Fixed.- Scenery system could "leak" memory by not freeing scenery models when appropriate. Fixed.- At non-US airports, runway IDs 8)- Flatten airports logic rewritten and integrated into single pass elevation import.- Slicer would show graphic options or intro dialogs if set in .INI file. Fixed.- Terrain data files are now deleted before attempting to slice a new area, solving some crash situations.SDK Fixes:- Added APIGetFilePath to return selected file path from an Open or Save dialog box.- Added GetFilePath to Python system to return selected file path from an Open or Save dialog box.- APIGetTunedType incorrectly returned TUNED_NAVAID when tuned to a localizer. Now returns TUNED_ILS.- APISetWeatherInfo now sets winds aloft to match wind settings passed in SWeatherInfo struct.- Added APIGetWindsAloft and APISetWindsAloft to modify winds aloft at users present location.- Added APIGetLightScalars and APISetLightScalars to set cloud lighting scalars for dawn, day, dusk, and night.- Added GetLightScalars and SetLightScalars to Python system.- Python GetJoystickAxis incorrectly returned an integer instead of a float. Fixed.- DLLGetPopupHelp no longer requires a tag to be defined for the gauge for popup help to work.- Setting cursor to CURSOR_TURN_LEFT or CURSOR_TURN_RIGHT would crash Fly!. Fixed.- Added SetWeather to Python system; pass in a WeatherInfo dictionary (defined in fly.py) and weather is set at users present position.- Added DLLKeyIntercept routine to allow DLL's to capture Fly! keystrokes and prevent further processing.- APIDefineKey did not handle the modifier value correctly. Fixed.- APIBlitPanelToSurface and APIDrawBitmap no longer leave a 1-pixel black border.- Key handler changes not always activated properly when added or removed. Fixed.- Keyboard callback routines had a bug causing DLL's not to get notification. Fixed.- DLLBeginFrame was not being called. Fixed.- APIDefineKey did not handle the modifier value correctly. Fixed.- Key handler changes not always activated properly when added or removed. Fixed.- The maximum number of active fonts has been increased from 20 to 40.- APIFreeFont has been added to the SDK to allow freeing an unused font.- APIGetFlyVersion has been added to report the current revision and build number of the Fly! executable.- DLLFilterMetar has been added to allow DLL's to pre-filter METAR files before they are processed by Fly!.- Keyboard callback routines had a bug causing DLL's not to get notification. Fixed.- APIObjectInAirport incorrectly searched airport database, causing inconsistent results. Fixed.- APIGetScreenDirect added to allow direct manipulation of the Fly! frame buffer (valid during DLLDraw* callbacks only)- APIGainFocus/APILoseFocus added to forcibly change the focus of a UI component or window.Ben

Share this post


Link to post
Share on other sites

To get the full effect.. Go into the flyII /system/fly.ini in the and edit the line under the header of Graphics to useEnvlighting=1.This should give you the yellow glow effect. You may want to try video update 2, but is not needed if you do not have a geforce3./ Still got the joystick problem........getting a replacement tomorrow. Take care..........

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this