Sign in to follow this  
Guest Ken_Salter

Fly!! FAQ

Recommended Posts

This anchored post will be the Fly! II FAQ page. Here you will find tips and tricks to getting the most out of your Fly! II experience. If you would like to add something, please send me an email. You will get full credit of course! :-)Table of Contents:1) Flattening for Beginners 2) How to cure startup crashes3) Steps to Patch Fly! II4) How to display Frames Per Second5) Help for the render.ini file6) Using InfoMETAR in Fly! II7) Fly crashes with 'you did not allocate any 32*32 8888 textures'8) Enhancing runway lights9) Resolution > 1024x76810) Rays of Light issue

Share this post


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

Download from http://ftp.avsim.com/library/sendfile.php?DownloadID=13809. Here is the text, the graphics are no longer on the server:Beginners: my first steps to change elevation dataExperts: fell free to correct, if I got something wrongremark: sorry about myenglish, but my native language is German.You need: "Flattenator" and "flatten help.xls" from Ken Salters homepage.The world of Fly!II consists of 256 x 256 Globe Tile, identified by their x and z coordinate. (like 011,166).If you want to change data of a Globe Tile, you need a directory DATADxxxzzz (DATAD011166).Each globe tile has 4 Quarter Tiles, represented by a .TRN-File (G00.TRN, G01.TRN, G10.TRN, G11.TRN)Each Quarter Tile consists of 64 (8 x 8) Super Tiles, numbered by its x,z coordinates (0,0 0,1

Share this post


Link to post
Share on other sites

1) Remove any .sit files2) Remove any .hst files3) If you are getting a streamio.cpp error, remove the default.key file

Share this post


Link to post
Share on other sites

Since this question comes up a bit, so here is how one patches Fly! II:If you have the US release:1) Install the All Inclusive patch that brings you to build 210: http://ftp.avsim.com/library/sendfile.php?DownloadID=10267If you have the European release:1) Install the Patch Update 4 to go to build 210: http://ftp.avsim.com/library/sendfile.php?DownloadID=9889Then:2) Install the 250 patch: PC - http://library.avsim.com/esearch.php?CatID...atch&DLID=24089Mac - http://library.avsim.com/esearch.php?CatID...atch&DLID=240903) OPTIONAL: Install the Global update patch to fix some coastline issues (can be installed at any time - not patch/build dependent): http://ftp.avsim.com/library/sendfile.php?DownloadID=9678NOTE: If you own PMDG 777, you can install it after the 250 patch, but you MUST REINSTALL the 250 patch afterwards (the Fly! II exe is overwritten by the PMDG install)

Share this post


Link to post
Share on other sites

Open the fly.ini file in the system folder. Find the line allowDebugInfo=0, and change this to allowDebugInfo=1. Save the file and restart Fly! II.You can also disply fps as a graph by pressing + or + !

Share this post


Link to post
Share on other sites

Here are some links for help on the render.ini:http://www.thesalters.org/fly2/render-ini-explained.htmYou can also use the MemCalc program to help figure out your settings: http://ftp.avsim.com/library/sendfile.php?DownloadID=12603Here is a sample .ini from a 64 MB Geforce card (submitted by Biber Salsa):mipLevelCount=8vertexIndexFormat=0premultiplyColorAndAlpha=0allowAutoMipMapping=0directTextureFlag=0maxTextures32=20maxTextures64=16maxTextures64_565=16maxTextures128=192maxTextures128_565=448maxTextures256=48maxTextures256_565=64maxTextures512=9maxTextures512_565=0maxTextures1024=1mipMapFlag=896maxTextures256_565=0maxTextures256_565=0

Share this post


Link to post
Share on other sites

In InfoMETAR, go to Edit/Options, click on the "Misc" tab, and put a check in the "User-specified METAR output folder" checkbox. Then, in the text field below the checkbox, type in (or browse to using the "Browse..." button) the METAR folder inside your Fly II installation folder. (InfoMETAR 1.01 was released before Fly II, so it doesn't know how to find Fly II automatically. You'll only need to set this once ... InfoMETAR will remember thereafter.)After you get the current METARs with InfoMETAR (using the "Download METARs" button), select your intended flight path on the map (using the triangular "Set Flight Route" tool, or by SHIFT-clicking with the arrow tool). This helps by telling InfoMETAR which reports it can discard as unneeded for the flight, which in turn lightens the load on Fly II's weather engine.Then click on the "Thin METARs" button, which does the actual removal of unneeded reports according to the flight route you've selected in the last step. In the "Set METAR Thinning Settings" dialog that pops up, I currently recommend setting "minimum miles between stations" to around 30 miles, and "Buffer space around flight route" to 300 miles when using it with Fly II. (InfoMETAR's default settings were appropriate for Fly 1.0, but not so much for the newer version.)After thinning the METARs as described above, click on the Save button. All of the METAR Modification options should already be checked in the Save As dialog ... if not, puts checks beside them all. Assuming you performed step 1 above, the default save folder should be Fly II's METAR folder, so you shouldn't need to change that. Remember the name of the file that you save here (whether you stay with the default or give it a name of your own doesn't matter, as long as you know what it is in the next step).Finally you are ready to start Fly II. Once you are in the cockpit, drop down the Weather menu, select Load METARs, and then select the name of the file you saved from within InfoMETAR. Don't attempt to set or change any weather options before or after loading METARs, as they will conflict with the METAR load.Posted by David Sandberg, author of InfoMetarhttp://ftp.avsim.com/library/sendfile.php?DownloadID=7750

Share this post


Link to post
Share on other sites

Add this following line to your render.ini (located in system):maxTextures64=4to cure this problem.

Share this post


Link to post
Share on other sites

Section (works with build 230 or higher):viewableTaxiwayPavementDistance=50000 viewableTaxiwayLightDistance=300000 markingTotalFadeOutDistance=30380 viewableTaxiwayHeight=100000 viewableTaxiwayMarkingDistance=3000runwayLightFogPenetration=1000lightScalarDusk=50lightScalarDawn=50lightScalarDay=100lightScalarNight=25runwayLightDistanceFadeMinFeet=12152runwayLightDistanceFadeMaxFeet=30380runwayLightDistanceFadeMaxRatio=75lightIntensityStandard=0.500000 lightIntensityCenterline=0.500000 lightIntensityTouchdown=0.500000 lightIntensityALSF=1.000000 lightIntensityRAIL=2.000000 lightIntensityVASI=3.000000 lightIntensityREIL=3.000000 lightIntensityTaxiway=0.070000Submitted by Johnny Svensson http://www.avsim.com/hangar/fly/josve

Share this post


Link to post
Share on other sites

Open your fly.ini. Look for:gamePIXX=1024gamePIXY=768and change this to whatever resolution you want. Also:askUserForGraphicSettings=1change this to askUserForGraphicSettings=0. This will prevent Fly! II from displaying the graphic selector window at startup, which would overwrite the above settings.Note that there are currently cosmetic issues with the cockpit display when you run higher than 1024x768. The beta team has this item under review...

Share this post


Link to post
Share on other sites

I have seem to found one solution. Like mentioned here, I changed the Direct X setting from T&L to standard direct x. This didn't fix my problem immediately, but I found if I panned around the exterior view of the plane once or twice, the bands went away (wierd?). The downside is the visual quality of the sim seems to suffer when I don't use T&L. I think I have a pretty standard card (MSI Geforce3 128MB), so I'm not sure why everyone doesn't see the problem. Nevertheless, I thought I'd share my workaround.- Dan Larson

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this