In all the cases I have seen of this one, the culprit has turned out to be a badly programmed or incompatible add-on. The most common exception I encounter is C0000005, which is a "Memory Exception" - "something" attempting to write to an area of RAM where it has no access rights. This information you can then copy into a post here.Īll I am doing then is take the "Exception code" from the report, and search the web for it. Highlight each of those, and the error information will show in the bottom center panel. Now, in the top center pane scroll down to the time of the crash, and there should be one or two entries at that time labelled "Error". Click on the little arrow next to "Windows Logs", then on the arrow next to "Application". Then right-click on your Windows Start button, and select "Event Viewer" from the menu. If you don't have the time, provoke a crash. V1.0.1 “SD” – Click on a file to download the corresponding 10×10 degree scenery tile."Interpreting the Event Viewer" isn't exactly rocket science, since I am able to figure it out.įirst of all, you note down the time of a crash. Ģ) Refer to this map to locate the correct scenery tile. Do not download from here as the map links to version 2 scenery, this can be verified by attempting to download a file which turns out to be many hundreds of MB. Remember default scenery is W130N30 ( includes KSFO KOAK).ģ) Using the scenery map to locate the correct tile, note its name, and then navigate to t his FTP location and download the correct scenery tile.Ĥ) Follow instructions in the fgstart.pdf document in your FlightGear 1.0 folder. The instructions for installing scenery from the manual are below, but some clarification is needed: Don't forget to click 'refresh' in FGRUN, the Flight Gear Launcher, for the airports in the new scenery to show up. Now for the Terrain folder: two folders names w122n37 andįlightGear/data/Scenery/Terrain/w130n30/w122n37/ *stg and *.btg.gz filesįlightGear/data/Scenery/Terrain/w130n30/w123n37/ (same thing, *stg and *.btg.gz files)Įxtract the new scenery files, for example w120n30.tgz to a folder called WorldSceneryįlightGear/data/WorldScenery/w120n30.tgz Select extract here and what happens? Navigating further into this folder : ( default scenery remember)įlightGear/data/Scenery/Objects/w130n30/w122n37/ *.stg filesįlightGear/data/Scenery/Objects/w130n30/w123n37/ *ac files, *.xml files, *.rgb files *.stg files (Buildings etc) There is a folder named Flight Gear/data/Scenery:įlightGear/data/Scenery/ contains two folders: Objects and Terrain The structure for default scenery is like this. fg-scenery=C:\Program Files\FlightGear\data\Scenery C:\Program Files\FlightGear\scenery C:/Program Files/FlightGear/data/WorldScenery/ To be fair th efolder is named in WINE after all,a s When Flight Gear is started, do we have scenery? Select an airport in the new scenery such as KLAX (Lost Angeles International Airport) and a whole bunch of similar directories containing stg files only.įlightGear/data/WorldScenery/w120n30/Terrain/w120n30/w113n37. So lets assume it is not hte path bu the wy the data is stored that is the probemĬompare the Terrain paths of the defult and the new scenery nest to eahother, there is an extra folder inbetwenįlightGear/data/Scenery/Terrain/w130n30/w122n37/ *stg and *.bįlightGear/data/WorldScenery/w120n30/Terrain/w120n30/w113n37. So we remove the w120n30 folder so that we have WorldScenery/ w120n30 /Terrain/w120n30/w113n37.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |