f16jockey_2

The info is taken from the [General] section of aircraft.cfg, the active [fltsim.X] section and from the flightplan BGL. In case of double assignments (eg. flt #) the flightplan takes priority. Wim

Should be modified in [CameraDefinition.001] section. Be sure you edit the file in the correct location! NOT the one in FSX Root!!! If the parameter already exists (eg. SnapPbhAdjust = Ordinal), modify it to Swivel. If a parameter doesn't exist yet in the section (eg. PitchPanRate = 10.0) , add the complete line. Leave the guid= {...} line alone. Wim

Try this: File cameras.cfg - Location C:\Users\\AppData\Roaming\Microsoft\FSX Change the red entries only. [CameraDefinition.001] Title = "Cockpit" Guid = {B1386D92-4782-4682-A137-738E25D1BAB5} Description = This is the description of the cockpit view Origin = Cockpit ShowPanel = Yes SnapPbhAdjust = [color=#ff0000][b]Swivel[/b][/color] SnapPbhReturn = No PanPbhAdjust = [color=#ff0000][b]Swivel[/b][/color] PanPbhReturn = No Track = None ShowAxis = Frontonly AllowZoom = Yes InitialZoom = 1.00 SmoothZoomTime = 2.00 ShowWeather = Yes XyzAdjust = Yes ShowLensFlare=No Category = Cockpit [b][color=#ff0000]PitchPanRate = 10.0 HeadingPanRate = 15.0 [/color][/b]Panacceleratortime = 0.0 HotKeySelect = 2 Be aware: panning/zooming in 2D view only affects the enivironment. The 2D panel and popups always stay fixed. Wim

Easy in theory: map the keyboard combo for GPS (eg. 3) to the button on yr box (it's documentation will tell you how). In practice: the GPS can (and will) be assigned to a different combo ( 1-9) for different aircraft (depends on panel.cfg). I haven't found a simple solution yet to get eg. Joy#1 always call the GPS. The easiest I've found 'til now is working with Profiles in payware FSUIPC (I can elaborate on this if the need arises). Another laborous way would be to edit all panel.cfg files to get the GPS-window mapped to the same combo. Wim

I agree on the latter (I use SceneryConfigEditor for that purpose), but yr statement on the active aircraft entries is new to me. For sure, it'll save you some time on the Aircraft Selection Screen popping up, but IMO it has no influence on OOM errors. Once an aircraft is loaded into memory, the Airplanes folder isn't accessed anymore (I'm talking about user flyable aircraft, not AI Traffic). Wim

I might be wrong, in the way that the GrantedRewards.BIN only is created upon receiving yr 1st reward. Try one of the 1st missions (take off with the trike IIRC), and see what happens once you get the mission reward. btw the BIN-files from the CD are for the installer only, leave them where they are. Wim

It is. Either you're overlooking it, or it's in a hidden folder, or in another location if you're running an older OS like WinXP. Anyway, it's in the same folder as fsx.cfg. The logic escapes me: even if you could (which you can't) all you'd get is a "virgin file". So what's the point? Wim

Rewards are saved in GrantedRewards.BIN. Location C:\Users\\Appdata\Roaming\Microsoft\FSX. In the unlikely case you ever made a backup of that file, you can restore it. Wim

Could it be you're on the edge of the +/- 120 Nm radius in which AI traffic can be followed? The go-around for the 2nd TNG could bring the AI plane outside that radius. Just a thought... Wim

https://www.flightsim.com/vbfs/showthread.php?248567-How-do-you-keep-FSX-interesting&p=2166493#post2166493 Wim

I moved FSX from my D: to a new H: SSD. Then I fooled Windows by creating a symbolic link from the new location on H: to exactly the location on the D: drive where FSX was before. Wim

By "rebuilding a new scenery.cfg" the following will happen: A copy of the stock scenery.cfg (the one with 120 entries) will be placed in C:\ProgramData\etc... All your previously added scenery will no longer be recognised, and you'll have to add them one by one. I would call that "demolishing" rather than "rebuilding". OTOH given the fact your install looks quite sloppy to me (e.g. Addon Scenery\Scenery\Alicante\SCENERY where it should be Addon Scenery\Alicante\SCENERY) that's maybe not a bad idea. The choice is up to you. The file to delete is the active one of course, the one in C:\ProgramData\etc.. Wim

You're looking at the backup scenery.cfg in the FSX root directory. The active scenery.cfg is located in C:\ProgramData\Microsoft\FSX. That one will definitely go to [Area.156] or above. As for the definitive, all embrasing solution: These problems are caused by the user (sorry to say, but that's you). The most common mistake is to manually delete/move/etc active scenery folders. Wim

From previous post... Dunno what more to say about it. I's free, it has a manual and a dedicated website with a tutorial. Install it, try it. Wim

No. In fact, scenery that's outside the user aircraft's range isn't loaded either. Scenery is loaded and unloaded as yr aircraft moves around the globe. This is where a fast hard disc (eg. SDD) will save on loading times. There's one big exeption: if an active scenery contains photoscenery, it's ALWAYS loaded no matter where it is on the globe. Most payware (and lots of the better freeware) airports use photoscenery as base ground texture. So it's a good habit to deactivate scenery you're not currently using ​in order to save memory. A tool like Scenery Config Editor is great for this, as it allows grouping, and activating/deactivating by group. Wim

For a $50 addon, I’d do my own research. Wim

IMO there's a "revised altitude"-bgl leftover in Scenery\World\scenery. Check for any files mentioning HAAB in that folder and delete them. In fact, better to remove everything you've tried and we'll go through the correct process. Problem with HAAB is that the FSX mesh is far off, and they've lowered the airport to make it fit into the wrong mesh. So when using a correct mesh (like FreeMeshX) the airport will be in a canyon. This is what you should see when flying over the default airport with FreeMeshX enabled. If you see something else, you still need to check for leftovers. Now to correct this, open ADE and load the stock HAAB airport. File -> Open Stock Airport Find HAAB and open it. First, set the airport elevation to it's correct value. Tools -> Change Airport Reference Data -> Change elevation to 2324 m/7625ft (found on any RW chart) -> Change + OK to the next dialog box. Now we'll draw two polygons (click the icon with the green polygon in ADE toolbar). End the polygons by double-clicking, then add the properties as shown + OK. Save the airport, and compile it to Addon Scenery\scenery (or another active scenery folder). The result: The crucial step is to change the airport elevation before adding the polygons. BTW if you do this without FreeMeshX installed, HAAB will be on a plateau now. Wim

IMO you have different elevations set for the airport and the flattens. Wim

AIGTech AI Manager has an OCI-mode (one-click-install) which does what you discribe above. The bad news: OCI is only supported for P3D, not for FSX. Which means you'll have to install the aircraft models manually and let AIM detect them at startup. AI Manager will then automatically download and install the flightplan and the needed textures for the models. I wouldn't delete the WoAI aircraft folders, as many of them are reusable for AIG. One thing you could do is replace any FS9 models by FSX-native ones. OTOH the redundant WoAI flightplan should be deleted. Once installed all BGL-based AI traffic is identical, no matter what's the source or what program installed it. So yes, they'll work together. Wim

Must be an error in AIFP data in the latest version. I checked KDCA in my installed version and it was [uTC-5]. Then I got a message my version was outdated, so I downloaded and installed the update to the latest version. With the new version KDCA is [uTC+12]. Stupid me forgot to make a backup... Can be fixed: In the airport list, double-click the faulty airport (eg. Dulles) In the edit window, change the State from "DC" to "Virginia" and click the "Apply Updates" button down below. Fixed. Do the same with Reagan Intl. etc. Hopefully this gets permanently fixed in a new update. [EDIT]See you've already found it while I was writing my post. Wim

When I get that double icon in the taskbar, it mostly indicates a popup dialogue needs to be answered. Like a gauge needing to be registered. Hovering over the icons with the mouse allows me to select the popup and answering/closing it. On some occasions it happened the popup was hidden by the FSX loading splash screen (was behind it). So it wasn't apparent the program expected some input (making it look like it was frozen). Wim

In FSX.CFG, add following lines in the [Display] section. [Display] RUNWAY_LIGHTS_SURFACE_SCALAR=1.0 //Runways, Taxiways, Aprons RUNWAY_LIGHTS_VASI_SCALAR=1.0 //VASI lights RUNWAY_LIGHTS_APPROACH_SCALAR=1.0 //Approach light bars RUNWAY_LIGHTS_STROBE_SCALAR=1.0 //RAILs etc. 1.0 is default, the above wouldn't change a thing. Higher (eg 1.2) is brighter. Lower (eg 0.8) is dimmer. Wim

You don't need to install Acceleration from yr new disc, as you have it already running. You don't need the new Product Key. All you need from the new disc is the SDK installation folder. Those installers aren't protected with the product key. From the article for which I already gave the link: FSX Acceleration Pack OR FSX Gold Pack users To install the SDK for FSX Acceleration Pack OR FSX Gold Pack: Install the RTM SDK from FSX Deluxe Edition disk 1, (see 3.1.1 FSX Deluxe RTM users instructions above). Insert your Acceleration Pack DVD. Browse to the subfolder called SDK\SP1a\ Install the SDK SP1A from there using fsx_sdk_sp1a.exe, (dated 26/09/2007, size 165,569KB). Browse to the folder called SDK\ Install the Acceleration SP2/XPack SDK using sdk.msi, (dated 06/10/2007, size 216,929KB). So there's no need to modify yr current FSX/A installation. Wim

Time to refresh the basics, mate. Wim

IMO you're missing something in setting up the weather. Try hitting Z for the status line, and see what wind direction and speed is actually active. Wim