longbreak754

Exactly what are you referring to???? Be more specific - i.e. What info should be/is displayed when you select the Scenery Settings page... OR What is contained in a specific folder location... Or Are you getting an error message when FSX loads - if so provide details of the error message...

OK in sequence... 1. The default FSX scenery is stored in a series of folders under FSX\Scenery\World. Each folder represents an area of scenery relating to a region. The folders named using numbers (0000, 0001, 0101 etc) contain default airport/scenery information but as a package - i.e. each file contains information relating to multiple airports etc in that area. 2 and 3. Based on your reply you appear to have added all the files into the same default FSX Addon Scenery folder. Uninstall the OTHH scenery if still installed and then try this... A. Create two folders - one called OTHH Airport and one called OTHH Landclass - note these folders can be in the default Addon Scenery folder (e,g FSX\Addon Scenery\OTHH Airport) or within FSX (e.g FSX\OTHH Airport) OR they can be placed OUTSIDE of FSX in a folder structure designed by you to meet your need (e.g. C:\MyFSXAddonScenery\OTHH Airport). B. Create a subfolder called scenery in BOTH of these new folders and, if the scenery also includes dedicated textures, also create a subfolder called Texture. C. Install the OTHH scenery placing the airport files into the scenery (and texture) subfolders and the Landclass related files into the Landclass folder. D. Activate the scenery in FSX as normal in this order - Landclass folder followed by the Airport folder. E. Test. 4. The OTHH file will only contain scenery objects added by the author to the airport hence the reason why you did not see the objects you want to get rid of. 5. Assuming you opened the OTHH file one assumes it was located in the addon scenery folder....... 6. As mentioned at 1. above the default FSX airports are located as stated and in 'packages'. To view the default airport(s) in ADE you will need to use the Open Stock Airport option (located under the File menu entry). Selecting this option will open a small info screen that displays a number of search options - it defaults the ICAO option by default. Simply type the require ICAO code in the search field (located to the left of the Find Now button) and then click on the Find Now button to start the search. When found you will see the airport name in box below the search field. Click on the entry to select it (note it will display location details in the boxes below the results window) and then click the Open button to load the airport into ADE. A WORD OF CAUTION - DO NOT attempt to open the default location APXxxxxx.bgl file itself....

First, there must be a duplication of some sort because, if you deleted the KNOWN Doha OTHH scenery then you should be seeing the default FSX view - which will be of the original airport (OTBD - the left hand single runway airport in your screenshot) only. It it worth noting that at the time of FSX's release OTHH was not built and therefore is not part of the default scenery. Also of note that OTBD is depicted in the default FSX scenery with a single terminal and parking on the west side of the airport which is clearly not in the version shown in screenshot. Thus there must be another scenery for either OTHH or OTBD somewhere on your system... Second - is it possible that the problem is caused by the OTHH scenery attempting to replicate todays current situation with files that depict both the new airport AND the current OTBD layout. Looking at google it is clear that there is a major construction project ongoing at both airports.. Another possible reason for the problems displayed in the image is how you have added the scenery to FSX - more specifically their priority listing and/or location. You mentioned that it included Landclass. Did you install the landclass files in the same folder as the airport files or in a separate folder specifically for the landclass. If you stored them in the same folder as the airport files you will have issues. They are best stored in there own folder and then placed lower down below the airport folder in the scenery priority list. WRT to ADE - Which airport did you open in ADE - OTBD or OTHH? - and where was the source file located. If you opened the default FSX file for OTBD then you will not see the obstructions as the default (due to the observations made above)...

Definitely due to over lapping aiports - probably due to two activated examples of the same airport. Do a search of your scenery library to find any culprits.... Also note that if you have a AI app such as Ultimate Traffic, Traffic 360 etc, they may also have their own version of the airports and will also have an entry in the scenery.cfg file pointing to their stored location. Placing the scenery entry for these apps below all other addon scenery (but above the default FSX scenery) entries should stop them overriding addons... WRT to removing things from airports - ADE is a suitable tiool - you can use it to remover/add runways, ramps, buildings etc

Another key entry to check that has not been mentioned is the individual (fltsim.xx) texture= entry The entry here must be the same as the relevant texture folder name less the word texture and the dividing . character - for example Texture folder name is texture.abc123 then the entry should read texture=abc123

Hi Lee, Yes but there are limitations due to the respective sims AI engines. Flight plans can be created using AIFP3 - see HERE the download link for the tool is at the bottom of the page - this is a free tool that works for both FS9 and FSX. It is important to note that both sims handle AI traffic slightly differently and you will need to create individual files for each sim. That said, you can create one for say FS9 and then convert for FSX use using the tool. First, it is important to understand how AI works with regard to what happens when it take offs and then returns to land, the associated 'timings' and how it will affect the AIs ability to carry out Touch and Goes (TNGs). Basically, when created, a AI flight plan automatically sets some 'time related' incidents, including a period (window) of time for engine start, taxying etc prior to take off and an estimated 'scheduled' arrival time based on data derived from the AI model config files. This arrival time also includes a period of time allocated for taxying to parking. This is important to understand because the TNG function as provided by the tool, causes the aircraft to perform TNGs from the time it initially arrives in the vicinity of the destination airport until its schedule arrival time. If the time is to short the aircraft will simply land without conducting TNGs. So you will need to adjust (i.e. override) the calculated arrival time using the field provide. Creating a flight plan from an airport (KMLB for example), that have aircraft taking off, doing TNGs and then finally landing back at KMLB is relatively easy. However, having them take off from KMLB, flying to another airport (KVRB for example) doing circuits/TNGs and returning to KMLB in a single flight is not possible. The flight plan would need to be created using two legs - leg 1 KMLB to KVRB with TNGs enabled. leg 2 KVRB to KMLB. During leg 1, once the scheduled arrival time is reached the aircraft will land at KVRB and taxy in. Leg 2 will then have the aircraft taxy out for take off and return to KMLB. A limitation here is that, if the designated departure time of leg 2 is to close to the arrival time of leg 1 it may cause issues and fail to load

Hi Col, Long time no hear - a belated happy new year to you... How long have you have Chrome installed? If its been a while and you had no issues before now then it maybe that a corrupted Chrome update or newly installed extension is the cause of the issue: Although you are now using Firefox if you want to go back to Chrome there are several options to try that may resolve the issue: With Chrome open: 1. Check all the recently installed Chrome extensions. To do this click on the icon that has three dots on (located at top right) and then navigate to More Tools->Extensions. Here, you can either disable or delete the latest extensions installed. 2. Clear Cookies. Again click on the icon that has three dots on (located at top right) and then navigate to More Tools->Clear Browsing Data. Here you will find a number of options - select the required areas to clean (in this case Cookies and other site data) and then click on the Clear Browsing data button to run the process 3. Uninstall Chrome, download the most recent version and re-install

Hi Robert, I've just noticed that the landing page for the NL scenery shows the V5 version of the scenery. If you place the mouse cursor on the Downloads menu option you will see options for two previous versions that are available - V4 and V3 special Edition. Both have far lower system requirements... I am currently using V4 on a laptop that has the following specs: Intel i7-4702MQ 2.2GHz with Turbo Boost upto 3.2GHz NVidia GeForce GT750M with 4GB memory !6Gb RAM

Hi Robert, Take a look at this WEBSITE for some good stuff and this PAGE for a independent review of what's on offer...

Hi Alan, You are correct - AIFP only makes the traffic files but it is possible to use it to see what parking problems may happen at an airport - see section 11 of the user manual. WRT actual AI parking at specific spots it requires a number of instructions to be fulfilled - some are airport based and some are AI model based. The main instructions that determine where aircraft are parked are: Airports 1. The radius of the parking spot. 2. The parking spot type - i.e. Gate, Ramp, Cargo, GA etc. 3. The parking spot code - i.e. a 2, 3 or 4 character code specific to a airline or aircraft type. AI Models 1. Its wingspan. 2. The parking spot data entered in the atc_parking_types= line contained in each texture entry within the aircraft.cfg file. 3. The parking spot data entered in the atc_parking_codes= line contained in each texture entry within the aircraft.cfg file.

Fine shoots indeed.. And as pointed out there is a very well known Low Flying area in the UK called the Mach Loop - official its called Low Flying Area 7 (LFA7) by the Military.... A simple google search will throw up various sites with info....but see HERE and HERE for some videos of low flying around the loop

When you run the installer it offers default locations suggestion for the various elements but you can change these if you wish. Part of the product will, as per FSX, store files at C:\Users\\Docuements in a folder called TrafficGlobal

Hi Mike, Another possible solution regarding the remaining freezes... Disable Windows Optimisation - this is MS's name for its inbuilt defrag utility and is on by default. It will/should have auto detect(ed) the SSD and will not be running defrag on it but it will still run on the SATA HDD. Obviously, it will be taking some system/CPU resources when it does this which may be impacting on FSX performance. Also note that if you have a 3rd party AV or anti-malware suite these may also have an defrag optimiser as part of the package. If it proves to be the source of the problem you will have to decide what is appropriate for your needs regarding whether to leave optimisation on (and live with stutters) or disable it and get into the routine of manually running a defrag regularly or when required. I generally run a manual defrag every 30 days or so. IME, with todays HDD technology (formatting options and bigger cluster sizes etc) the need to defrag is much less crucial than it use to be.

Hi all, Come a bit late to this thread but a possible cause for the stuttering may be related to windows indexing and/or SSD related settings. I helped a friend a couple of years ago who's kids PC was having stuttering issues with a number of games following the addition of a SSD and installation of the games on the it. Whilst none of the games were FS related it did include a number of games that were as old as (or older than) FSX, were very CPU heavy and used similar CPU core usage patterns.... After some trial and error and internet searching we were able to eliminate the stuttering on most of the games by doing the following actions... Enabling trim - which was disabled. Disabling Windows File Indexing Disabling Disable Prefetch and Superfetch A quick internet search will give a number of 'how to' pages to check and change these options.

Hi Lucas Check out this PAGE - it has a number of method to help ID the cause and/orresolve the issue

@piet06273, One thing to consider if you are going to do a reinstall that IMO lessens the pain is to store as much addon scenery outside of FSX (and FS2004) in a folder system that meets your needs. This also includes AI traffic files. The only addon scenery that I have installed in my FSX is a few payware items that will only install into FSX - I have been doing so for many years including my FS2004 years. The misconception that many people seem to have is that scenery related files must be installed into set FSX default locations but, with the exception of some payware, all addon scenery can be installed practically anywhere, including being spread across different drives or partitions. The only 'rules' that must be followed are: 1. Scenery related files (.bgl) MUST be placed in a subfolder called Scenery and Texture related files (.bmp, .dds etc) must go in a subfolder called Texture...e.g MyAddonScenery\ will not work but MyAddonScenery\Scenery\ will... 2. FSX must be told were the scenery is - i.e Activated via the FSX scenery settings page or by the use of a scenery tool such as Scenery Config Editor as mentioned in earlier posts. A bonus of installing outside of FSX is that those payware items that use a authentication that writes details to the registry can remain installed and will be normally be unaffected by the reinstall of the sim. However, a possible exception to this would be if you choose to reinstall the sim into a totally different location from the previous install (say D:\FSX instead of C:\FSX for example) - this may cause issues for some payware. WRT to your specific circumstances - you could consider keeping the Flight 1 stuff with the default FSX install and only move all other stuff onto the SSD. Dependant on where and how you have installed the other scenery will depend on how much work is involved but at the very basic simple level if you have installed it all into the default FSX scenery simply: 1. Make a copy of the complete default Addon Scenery folder and paste a copy onto the new SSD drive and, as a backup in case of problems, place another copy in a safe location.. 2. Delete all non Flight1 software scenery from the default addon scenery folder. 3. Delete the Flight1 stuff from the SSD copy of the folder. 4. Make a copy of the Scenery.cfg so that you have a backup copy if things go wrong. 5. Open the scenery,cfg for editing using Notepad. You need to make the following changes to the Local= entries for ALL of the scenery items moved to the SSD, as per this example: Current entry for scenery stored in the FSX default Addon Scenery location (i.e: FSX\Addon Scenery\LSZA Lugano AP: [Area.472] Local=Addon Scenery\LSZA Lugano AP Title=LSZA Lugano AP Required=FALSE Active=TRUE Layer=472 New entry for the new Addon Scenery location: [Area.472] Local=D:\Addon Scenery\LSZA Lugano AP Title=LSZA Lugano AP Required=FALSE Active=TRUE Layer=472 As stated the first item assumes that the item is stored at FSX\Addon Scenery\LSZA Lugano AP. Other variations may exist based on where you have stored it. Some users may have installed it at FSX\Addon Scenery\Scenery\LSZA Lugano AP for example. In this case the new layer entry would need to read D:\Addon Scenery\Scenery\LSZA Lugano AP

Hi Alan, Further to my last post... First, a correction - the Priority view listing I gave at the end of the post is in the wrong order - it should be reversed so that Area 480 is at the top followed by 479, 478, and so on... To clarify the differences between the FSX setting page view and the text views - the FSX view shows the latest piece of scenery added at the top in the P1 position whereas in text view the entry will be at the bottom of the list and has a higher layer value. Technically, therefore, the FSX setting page view is misleading as it implies that the new scenery has priority over the rest. Based on my experience here a very basic overview of how FSX handles and loads scenery and the P list ordering and its effect: The scenery is built up in 'layers' with layers loading later being placed on top of the previous layer. Therefore, if you add new scenery for an area it must be 'layered over' the default scenery and therefore must be of a lower priority. If you look at the default loading sequence for the default FSX scenery areas and the contents of those areas, you can get a feel for how things work - obviously this description is only valid if you have not made any changes to the areas in the P List. You will see that the first item to load is the default terrain files - these render the 'basic' world providing the basic landclass and waterclass scenery. The next to load is the Base scenery that provides further landclass and waterclas scenery. Next up are the files that are for specific areas (such as 0000, 0001 and so on) that add such things as default FSX airports layouts and backgrounds, basic static objects etc to the specific area that the folder is for. The next areas to load (NAME, EURW etc) are those that provide specific detailed areas for major cities. Finally the last default areas to load are the Global (provides airport buildings, vehicles etc), Props (generic propeller objects) and a entry for the default FSX Addon Scenery folder. Based on this you can see that certain items of scenery need to be loaded earlier (i.e given higher priority) than others. Based on this and experience I use the following criteria when assigning priorities: Highest Priority - Default FSX scenery - I have not changed any of its positions in the list Next Priority - Addon Terrain type Mesh scenery - i.e. scenery that adds the lumps and bumps Next Priority - Addon Environment type Mesh scenery - i.e. scenery that adds landclass/photoreal textures Next Priority - Object Libraries - i.e. commonly use libraries that provide objects in scenery such as Rwy12, EZ, etc Lowest Priority - Airport and other individual scenery It should be noted that some scenery, especially more complex Terrain or Environmental stuff, may be split into regions and/or have their own specific object libraries that necessitate a specific installation process and priority listing - Orbx stuff springs to mind here. It is also worth noting that if you use a payware AI traffic product (such as Traffic360, Traffic Global, Ultimate Traffic etc) that they normally include scenery files of their own that are automatically activated as part of the install process. Therefore any entry relating to the scenery would be best placed below any other airport scenery - in my setup its the first entry after the last Object Library entry

Hi Alan, First, a +1 regarding using Scenery Config Editor - see HERE to download it and HERE for a overview and user info... As to info on 'areas', 'layers' and ordering - here's a very basic guide... When you add a new bit scenery it is assigned an unique Area.XX number - usually the next available number. This is a 'placeholder' for the scenery within the .cfg file. It is also assigned a unique Layer number - this is usually the same as the Area.XX number and denotes when the item is loaded into memory when you start FSX. The Area.XX number remains assigned to the scenery entry until you actively delete it. However, the layer number will change if you move it up or down the Priority listing. It is also worth noting that you will see differing views when you view the entries in Text view or Priority List view (i.e. via the FSX Setting page).... As an example - the two entries below are examples from my current .cfg [Area.472] Local=D:\Addon Scenery\Airports - Detailed\LSZA Lugano AP Title=LSZA Lugano AP Required=FALSE Active=TRUE Layer=472 [Area.473] Local=D:\Addon Scenery\Airports - Detailed\LIRE Pratica di Mare AB Title=LIRE Pratica di Mare AB Required=FALSE Active=TRUE Layer=480 As can be seen the first entry [Area.473] has not been changed - as the Area. and Layer numbers are the same. However, [Area.473] has been change and moved down the Priority listing so that it is now at layer 480 So when viewed in text mode it will appear as shown above but in the Priority list view the 473 entry will be 8 entries below the 472 entry - e.g. 472 - LSZA Lugano AP 473 - Scenery Title 474 - Scenery Title 475 - Scenery Title 476 - Scenery Title 477 - Scenery Title 478 - Scenery Title 479 - Scenery Title 480 - LIRE Pratica di Mare AB The basic way that FSX loads scenery is that each Layer is loaded in turn stating from layer 001.

Hi, By default Steam is installed at C:\Program Files (x86)\Steam\ The actual contents of the games are stored at C:\Program Files\Steam (x86)\SteamApps\Common\ The structure of the folder will then follow that as set by the game producer and, in the case of FSX, this is where you will find the relevant folders...

Yes. The product is developed for both FSX and P3D BUT you don't need to own both sims or to have both installed for it to work. In fact, if you own both, you can only legally have one active instance of it installed at any one time - installed in either FSX OR P3D but not both sims at the same time. FYI the Just Flight installer will either ask you to chose which product you have OR, on some of its installers, it will auto detect what sim is installed....

Hi Rick, See this entry I posted in another thread...see HERE Download the tool and run it and see if that makes a difference...

Hi Mark, Where have you installed AIFP to? Also, have you by chance recently moved/copied FSX to another location...

Hi Allan, Clearly moving FSX has caused an issue - probably an issue with a registry entry that AIFP, AFCAD and ADE reference... Go to this PAGE, download the FSX/FS9 Registry Repair Tool (fourth entry down) and install it with admin rights then run it... Then test the affected apps - if none work uninstall one and then reinstall it to see if it changes anything...

@ Allan... WRT to AIFP... Are you sure that you have installed it correctly and not attempting to run it directly from the .zip file? If you are attempting to run it it directly from the .zip file it will cause issues.. Just for clarification AIFP should be installed as follows: 1. Unzip the contents of the .zip file to a temp location. If should create a folder called AIFP**** (whereby *** denotes the version number i.e the latest version will be AIFP3416). This folder will contain a number of files (31 in total) plus a subfolder titled Base Data - this folder will contain 13 files plus another subfolder with 2 files). 2. Copy the complete folder 'as is' to a location of your choosing. 3. Open the folder and run the program by clicking on the AIFP3.exe. This should run the program and it should create a number of new files (qty 3) and new subfolders (qty 5) in the background and the program display the initial screen.

@ Allan, Jorgen has fully answered your questions for me (thanks Jorgen)... For links to get the Visual C++ and .NET files mentioned see HERE