Solution Center

To contact support via email, please scroll all the way down to the bottom of this FAQ page and look for the blue "Contact" button.

PLEASE READ/SEARCH the FAQs before emailing! The vast majority of the emails we receive are solved in less than a minute by reading a FAQ Article, vs waiting 3 business days for an official response.

This article only applies to purchases made on the Flightbeam Webstore.

STEP 1: Go to your Flightbeam Account, scroll down and find the product you just purchased: https://shop.flightbeam.net/account

STEP 2: Click on the link to download, this will download Contrail. Alternatively, download Contrail here. 

STEP 3: Install Contrail once it has finished downloading.

STEP 4: Open Contrail, on the left menu click "ACCOUNTS", then find FLIGHTBEAM STUDIOS and click "CONNECT" to login to your Flightbeam account.

STEP 5: On the Left Menu, click "MY PRODUCTS", then find the product you just purchased, and click "DOWNLOAD". This will install the airport into your simulator. The product is automatically activated.

If the product is not appearing there, it indicates that you are not logged in with the same account as the one used to purchase the product.

Note: You only need to login to Contrail the first time. It will retain your account information. The next purchase you make, you can simply open Contrail and install.

Instructions:

1. Once you purchase an MSFS product on Simmarket, you will be prompted to download the Contrail app.

2. Download and install the Contrail app.

3. Open Contrail and select the developer, then the product you'd like to install/activate. On the product page, click "activate"

4. You will be prompted to select where you purchased, click "Other Shop"

5. Enter the serial number you received from Simmarket

6. Install and fly!

Note: Credit to Aerosoft for this helpful guide on refreshing scenery indexes. 

If you've just installed an airport addon for Microsoft Flight Simulator to your community folder and it doesn't appear in-game, follow the steps below:

CLEAR THE SCENERY INDEXES

If you've checked the installation path is correct, you should clear the simulators scenery indexes. To do this, delete all the files ending in ".DAT" in the following location depending on your installation method:

Microsoft Store/Xbox App:

Steam:

Due to the nature of digital download products, we only offer refunds under special circumstances:

- Duplicate order: Already have it? No problem
- Fraudulent order: These cases are investigated case by case.
- Accidental order (you will be given a return, in exchange of the correct product you wanted)
Note on Accidental orders: If you installed and activated the product, we are unable to provide a refund.

We do not offer returns for technical issues unless the user has exhausted every possible option provided by Flightbeam technical support AND the order is no older than 30 days.

Chargebacks and PayPal disputes: The nature of chargebacks and Paypal disputes are to report fraudulent activity. For this reason, if your bank has initiated a Chargeback or a Paypal dispute has been initiated, your account and all products will be permanently disabled and banned. Please note that this ban is system-wide with other developers, which includes over 20 companies in the Contrail Network. The ban is an official revocation of your license to use Flightbeam Software, which is described in our End-User License Agreement. (you own a license to use the software, not the software itself)
If a decision has been made to re-instate your account at any time, a $30 fee will be imposed to cover the costs incurred due to the chargeback process.

Due to the fluidity of the production pipeline, we don't offer any release dates. Sometimes we may give out a rough timeline, but even this is subject to change at any time.

To re-download, simply visit our new shop: https://shop.flightbeam.net/

Click "Account" and login, you will see all your downloads for your products.

If you don't see your products there and you've purchased it in the past from us, here are some reasons why this could be:

- You may have purchased them with a different email
- You haven't migrated your old orders yet

If you purchased anything from us before July 1, 2019, we have sent you an account invitation email which automatically merged your previous orders to our new store. If you did not receive this email, please email Support with as much information as possible.

If you purchased from different emails, you can merge those orders as well. Simply head over to our Shop FAQ to find out how.

Head over to the very bottom of this FAQ/Solution Center page to find our contact form.

If you're emailing us, we're assuming that you already searched for the issue you're experiencing in the FAQs. Please be patient, we respond to emails in order we receive them.

Typical response time is 24-72 hours Monday - Friday.

We do have Commercial Licenses available. Do not place an order on our webstore. Our webstore is solely for personal use only. You MUST have a commercial license if you intend to use the product as a business, regardless of your location or intent.To inquire about commercial licenses, please send us an email using the general contact form. 

https://shop.flightbeam.net/apps/help-center#hc-msfs-how-to-install-product

https://shop.flightbeam.net/apps/help-center#hc-how-do-i-install-an-msfs-product-purchased-from-simmarket

Flightbeam points is a reward system that gives you points for every purchase or activity. You can then use these points to purchase coupons which give you discounts on future products!

How to view/use your points:

Simply click on the bottom-right green banner to see your points balance and what you can purchase with them. Note: You need to be logged into your account.

Note that points expire after 4 months of inactivity.

If your points are due to expire, you will receive a reminder email to use your points. Simply use them to acquire coupons, there is no purchase necessary! The coupons do not expire.

Your orders have been migrated from esellerate to our new shop.

You have received an account invite at each e-mail address you have used at esellerate. Accept the invite and set a password for your account. In your account, you will find your orders placed at esellerate.

Absolutely!

You can then merge your accounts into your desired primary account using this webform:

>> Merge Flightbeam Accounts <<

We sent a first round of account invites in July, which imports everyone's order to their new Flightbeam Account. That invite has since expired. Simply email us and ask for a new account invite

We no longer use serial numbers. After your purchase you'll be presented with a download page. You can also download your purchases at any time by visiting your account page. Once installed the Flightbeam Manager will ask you to login. Use the same login as you used for the website.

The only time you'll be asked for a serial number is to activate a purchase made on a third party vendor such as Simmarket.

To redeem a voucher or coupon code, simply enter the code in the "Gift Card or discount code" field during checkout.

Please note: only one code can be applied to each order.

To change your password, log out of your Flightbeam webstore account, and head back to the login page. Click "Forgot Password?" to have a password reset emailed to you.

To change your email: From the Flightbeam Webstore, click on "Account" on the top right, login if needed. Then in the "Account Details" box, click "Edit Account" to change details such as your email address. 

Download the latest version here:

>> Download Flightbeam Manager v3 <<

1. Extract the archive to the root folder of your simulator (where your "Flightbeam" folder is)
2. Confirm overwriting the existing Manager

We have seen an increased number of reports about this issue, McAfee seems to have updated their detection data which now flags the Flightbeam - Manager as potentially malicious software, most likely due to the anti-piracy measure we are using of encrypting the source code.

The Flightbeam - Manager certainly does not contain malicious software.

You can whitelist the Flightbeam - Manager and our product installers with your McAfee software so it does not delete it.

The latest version of the Manager can be found here:

https://cdn.29palms.de/api/client/Fligbeam_Manager_latest.zip

The archive already contains the correct folder structure. You can extract the archive to the root folder of your simulator (where the "Flightbeam" folder is)

We have contacted McAfee with details about our software, hoping they will update their detection data soon.

With the migration of all orders from esellerate to our new shop, serial numbers became obsolete and log-ins required.

We have migrated all of your orders from esellerate to our new shop. You have received an account invite for each e-mail address you have used for ordering at esellerate. Please accept the invite and set a password for your account.

Now use that e-mail along with the password for logging into the Manager.

Did you use multiple e-mail addresses at esellerate? Simply merge them using this webform:

>> Merge Flightbeam Accounts <<

Yes. 

If you log-out from the Manager, your sceneries will be protected since we can not verify ownership.This means you won't see any terminals at your Flightbeam sceneries.

Your personal information (e-mail, password) are neither saved on your computer nor on our server. There is no harm in staying logged-in with the Manager.

It's likely that you have Flightbeam orders under different emails. The product that doesn't appear activated is likely from another email. We have a special form to merge those accounts, simply head over to our Account Merging Form

1. Open the Manager and log in to your Flightbeam account.
2. Stay logged in with the Manager!
3. Switch to the tab of the scenery
4. Is the tab page asking for activation? If so, please follow the instructions.

The Manager accepts serial numbers ONLY from Simmarket, iBlueYonder or PCAvtiator.

> Try typing the serial number instead of copy and pasting it!

If you have purchased the scenery at esellerate / the former Flightbeam shop, you have probably ordered it with another e-mail address. You can simply merge the e-mail into your primary account with our webform:

>> Merge Your Accounts <<

For functioning VDGS (Visual Docking Guidance System), you must download the latest Nool VDGS (free). Minimum version 6.0.8. Please note that as of release day, Nool's latest public version is only 6.0.7. We're expecting the latest version to be up this week. 

With version 6.0.7, the VDGS units are still visible but non-functional - this is normal behaviour until 6.0.8 release. 

The VDGS units mimick the actual devices at the airport:Gates A and B feature SafeGate Type 1 devices. 

Gates E and G have the stoplight style devices.

Other gates use marshallers.If you have Nool VDGS 6.0.8 or later installed and have trouble, please see the Nool VDGS Troubleshooting guide: https://vdgs.nool.ee/resources/troubleshooting/

The nose-loader type jetways at SFO's terminal 3 require precise aircraft placement since they only move up/down forward/backward. The aircraft door must be aligned with the jetbridge for proper connection. Unfortunately, it's impossible with the current SDK to create gates to allow all aircraft types to be perfectly aligned with their doors to the N-Type jetways - We can only place the gate itself and there is no way to position AI aircraft doors, or user aircraft doors. For this reason, you must ensure your aircraft is placed correctly, whether arriving, or departing. 

• A small patch of flattened photogrammetry exists east of runways 1L/1R. This caused by an Asobo/MSFS bug which is generated from an invisible bounding box.
• - N-Type Jetways require precision aircraft placement, unlike traditional jetways. See the N-Type Jetway article: https://shop.flightbeam.net/apps/help-center#hc-ksfo-msfs-terminal-3-n-type-jetways-not-aligning-or-connecting

It's important to uninstall any other KSFO airports before installing Flightbeam KSFO. Many versions of MSFS include a default version of KSFO which must be removed. 

Instructions: 

• Within MSFS main menu, click "Profile" on the top tab.
• Click on "Content Manager" box
• In the search field, search "KSFO". 
• Be sure that the individual packages icon is select to the right of the search bar.
• Select Asobo KSFO.. or any other KSFO 
• Click "Delete"
• RESTART MSFS to apply changes.

One of the biggest shortcomings of the MSFS SDK is the inability to fine-tune traffic patterns at complex airports like KSFO. At this particular airfield on a typical day, the 28's are (typically) used for widebody takeoffs, while the 1's are used for narrowbody departures. At the same time, the 28's are used for arrivals. 

This currently isn't possible to do in MSFS since ATC decides the traffic pattern solely on wind direction. This means you may see departures on the 19s.. which is exceedingly rare at SFO. 

We recommend you fly online, on networds such as VATSIM.. or use an addon such as PSXT which inject live traffic. Using default MSFS ATC is not recommended for immersion and accuracy. 

KSFO users can download a GSX profile specifically tailored to our product. For customers who purchased through Contrail, Flightbeam or Simmarket, you can simply download the GSX Profile using Contrail. Open Contrail > My Products > KSFO and click on the "Configuration" tab to select a specific GSX profile. For users who purchased KSFO in the MSFS marketplace, you can download the GSX Profile here. 

We've received some initial reports that the soundFX are too loud. We've just issued a patch that disables the FXSounds with an option (defaulted to OFF), until we've adjust various volume levels and placements. 

You must exclude KMSP from GSX. More info from our Jetways FAQ Article: 

A very common issue we're seeing lately are customers seeing double jetways or jetways in completely wrong positions. This is caused by FSDreamTeam's GSX Addon, which adds custom jetways to all airports. Unfortunately customers install this and forget about it, this causes significant issues with handcrafted airports like NZAA, NZWN, etc. 

We do not offer technical support for GSX at our airports. 

To fix this, you must disable the airport within GSX. For more info or to solve other GSX issues, please visit the FSDT GSX Support forum: http://www.fsdreamteam.com/forum/index.php/board,73.0.html

Recently due to an MSFS server outage, users noticed trees on the tarmac. This typically happens when Photogrammetry is turned off, which is the result when there is no server response. 

We're issuing a quick patch today to avoid this problem. Thanks for your patience!

Note: Credit to Aerosoft for this helpful guide on refreshing scenery indexes. 

If you've just installed an airport addon for Microsoft Flight Simulator to your community folder and it doesn't appear in-game, follow the steps below:

CLEAR THE SCENERY INDEXES

If you've checked the installation path is correct, you should clear the simulators scenery indexes. To do this, delete all the files ending in ".DAT" in the following location depending on your installation method:

Microsoft Store/Xbox App:

C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Steam:

C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes

A very common issue we're seeing lately are customers seeing double jetways or jetways in completely wrong positions. This is caused by FSDreamTeam's GSX Addon, which adds custom jetways to all airports. Unfortunately customers install this and forget about it, this causes significant issues with handcrafted airports like NZAA, NZWN, etc. 

We do not offer technical support for GSX at our airports. 

To fix this, you must disable the airport within GSX. For more info or to solve other GSX issues, please visit the FSDT GSX Support forum: http://www.fsdreamteam.com/forum/index.php/board,73.0.html

A new bug in the latest version of MSFS causes certain airport lights to flash/flicker with NVIDIA DLSS enabled. We've contacted Asobo to have them resolve the issue hopefully within the next update.

Disabling NVIDIA DLSS returns the lights to normal.

Update 1/15/2023 - Asobo has made an official response:

I checked with the dev and this is an issue we are aware of. This the case for all lights (sceneries / aircrafts.. ) when using DLSS. Fixing this would require a complete overhaul of this implementation and this is not planned in the short term. You can reduce the effect by reducing the intensity of the light. This will not solve the issue but it should make it less noticeable.

Recently FSDT has released a major update to GSX which has affected Flightbeam products. It's our understanding that the problem is GSX isn't able to read the pre-configured GSX ini files.

Please don't email support, there is nothing we can do about this GSX issue. Some solutions:

- Simply delete the GSX ini file in the scenery folder of Flightbeam airports

- Contact FSDT Support

- Visit the FSDT Support forum about this issue: https://www.fsdreamteam.com/forum/index.php/topic,26716.0.html

We're releasing custom MSFS GSX profiles on our dev blog, which can include unencrypted files for Marketplace users.

Our first one is for KIAD: GSX for KIAD profile

Our P3D/FSX products uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/ (SODE is a 3rd party addon, we do not make it) To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12). If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

Note: Credit to Aerosoft for this helpful guide on refreshing scenery indexes. 

If you've just installed an airport addon for Microsoft Flight Simulator to your community folder and it doesn't appear in-game, follow the steps below:

CLEAR THE SCENERY INDEXES

If you've checked the installation path is correct, you should clear the simulators scenery indexes. To do this, delete all the files ending in ".DAT" in the following location depending on your installation method:

Microsoft Store/Xbox App:

C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Steam:

C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes

UPDATE - March 21, 2023: A Patch has been issued. Now available on Contrail if purchased from Flightbeam, Contrail or Simmarket. MSFS Marketplace customers can expect the patch the be live towards the end of March.

We are aware of some watermarking issues caused by World Update 12 (New Zealand). There will be a patch issued very soon to resolve this. Thanks for your patience!

A very common issue we're seeing lately are customers seeing double jetways or jetways in completely wrong positions. This is caused by FSDreamTeam's GSX Addon, which adds custom jetways to all airports. Unfortunately customers install this and forget about it, this causes significant issues with handcrafted airports like NZAA, NZWN, etc. 

We do not offer technical support for GSX at our airports. 

To fix this, you must disable the airport within GSX. For more info or to solve other GSX issues, please visit the FSDT GSX Support forum: http://www.fsdreamteam.com/forum/index.php/board,73.0.html

The recent Sim Update 9 has caused issues with Orbx's NZ Mesh addon, which in turn is causing issues at Wellington Airport. This issue is specifically with the NZ Mesh addon and is a problem across various NZ Airports.

The old tower located on Tirangi Rd. was recently demolished, and therefore not present in the latest rendition of NZWN.

MSFS's current SDK forces layered ground textures into a "projected mesh". The original sharp quality of the assets is lost with this method, but unfortunately this is what we're limited to with the current SDK. We're hoping Asobo will improve this in the future.

A very common issue we're seeing lately are customers seeing double jetways or jetways in completely wrong positions. This is caused by FSDreamTeam's GSX Addon, which adds custom jetways to all airports. Unfortunately customers install this and forget about it, this causes significant issues with handcrafted airports like NZAA, NZWN, etc. 

We do not offer technical support for GSX at our airports. 

To fix this, you must disable the airport within GSX. For more info or to solve other GSX issues, please visit the FSDT GSX Support forum: http://www.fsdreamteam.com/forum/index.php/board,73.0.html

Update - March 3 2023, NZAA Version 1.2 is now available, which resolves this issue. 

We are aware of some minor terrain issues caused by World Update 12 (New Zealand). There will be a patch issued very soon to resolve this. Thanks for your patience!

It's very likely that you purchased NZAA from the MSFS Marketplace.

Unfortunately, VDGS only works on copies downloaded from our Flightbeam webstore or Contrail. It will not work if purchased from MSFS Marketplace because Microsoft does not allow multi-part installations, which is required for VDGS to work. Our copy of NZAA has VDGS completely integrated and there is no need to download a separate addon.

Recently we had an issue with customers experiencing an offset ILS at NZAA. This was caused when Navigraph was installed. Unfortunately when Navigraph is installed, it overwrites our custom nav data.

The problem was that ILS localizer location provided by Navigraph had incorrect coordinates, causing the deviation. Navigraph states that the issue originated from incorrect 3rd party data. They have recently fixed the issue with an update (March 2023)

More info in their forum: https://forum.navigraph.com/t/nzaa-offset-centerline/11259?u=cstigberg

During our onsite survey in 2019, this area was under construction and has been depicted exactly like in the real airport.

This construction has since been completed and we'll be updating this area, along with other new construction once they're all completed.

100% of the effort that goes into our products are aimed at maximizing the immersion for the virtual pilot, not the virtual passenger. Creating detailed interiors is a huge effort for a large size airport, and while it would give a new perspective, it would also take away from the effort put into the gate details, which is more important as a Flight Simulator.

There is also no meaningful way to walk around in the sim, such as controlling an avatar or even a 1st person view. If features like these were to come to MSFS, we will certainly create an immersive space for the player to explore as a passenger.

Note: Credit to Aerosoft for this helpful guide on refreshing scenery indexes. 

If you've just installed an airport addon for Microsoft Flight Simulator to your community folder and it doesn't appear in-game, follow the steps below:

CLEAR THE SCENERY INDEXES

If you've checked the installation path is correct, you should clear the simulators scenery indexes. To do this, delete all the files ending in ".DAT" in the following location depending on your installation method:

Microsoft Store/Xbox App:

C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Steam:

C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator\SceneryIndexes

Few users using Active Sky and ASCA had an issue with trees and grass being white (like covered by fog). Solution is to re-apply the ASCA dynamic theme, and the white vegetation issue should disappear.

Browse to C:\ProgramData\12bPilot\SODE\xml and look for older LFBO files from other developers. When files are found, back them up and then delete them from the XML folder.

This has been solved in V1.1. Please update scenery if using an older version.

LFBO scenery is using 4096* textures in a way to reduce drawcalls and improve performance. Please make sure to set your texture resolution to 4096 in the P3D graphic settings menu.

Please make sure the SODE module is registered for your P3D, in the SODE platform manager.

You might have installed the scenery into another folder than the default one. So it might happen that some files could not find their way to some key folders located into the main P3D V5 folder. We recommend using the installer's default path to make sure all files are correctly installed.

Terrain issues are always caused with conflicting addons. The most common conflict for NZAA is Orbx NZNI (New Zealand North Island). Thankfully we've implemented tools to prevent this.

Solution 1: Open the Flightbeam Manager and use the Troubleshooting tool to de-activate conflicting files. Green means the file has been de-activated.

Additionally, ensure that your Scenery Library has a proper order. Airport entries (in gray, unmovable) MUST be above Orbx entries. To move down, simply select Orbx entries and click "Move Down"

The vast majority of cases, this works and no further action is needed.

Please note that you may notice issues with Orbx NZNI after disabling files. 

Solution 2: Only needed if solution 1 did not work. Find your install folder where Orbx installed NZNI. Search for each file and rename their extension from ".bgl" to ".off"

4_mesh_multiLOD4-12_FTX-NZNI_section2.bgl
300_FTX_NZNI_LCpoly_9445_Auckland.BGL
0_excl_FTX_NZNI_GUID_all.BGL
cvx_FTX_NZNI_water_9445_summer.BGL
4_mesh_multiLOD4-12_FTX-NZNI_section2.bgl
2_FTX_NZNI_orthoimage_NZNI_LINZ_ManukauHarbour_2m.bgl
ADE_FTX_NZNI_NZAA_GSE_Clutter.BGL
ADE_FTX_NZNI_NZAA_Markings_Clutter.BGL
ADE_FTX_NZNI_NZAA_Objects.BGL
ADE_FTX_NZNI_NZAA_Terminals.BGL
ADE_FTX_NZNI_NZAA.BGL
ADE_FTX_NZNI_NZAA_CVX.bgl
ADE_FTX_NZNI_NZAA_GP.bgl
ADE_FTX_NZNI_NZAA_Vegetation.BGL

Double lines and duplicate buildings are always caused with conflicting addons. The most common conflict for NZAA is Orbx NZNI (New Zealand North Island). Thankfully we've implemented tools to prevent this.

Solution 1: Open the Flightbeam Manager and use the Troubleshooting tool to de-activate conflicting files. Green means the file has been de-activated.

Additionally, ensure that your Scenery Library has a proper order. Airport entries (in gray, unmovable) MUST be above Orbx entries. To move down, simply select Orbx entries and click "Move Down"

The vast majority of cases, this works and no further action is needed.

Solution 2: Only needed if solution 1 did not work. Find your install folder where Orbx installed NZNI. Search for each file and rename their extension from ".bgl" to ".off"

4_mesh_multiLOD4-12_FTX-NZNI_section2.bgl
300_FTX_NZNI_LCpoly_9445_Auckland.BGL
0_excl_FTX_NZNI_GUID_all.BGL
cvx_FTX_NZNI_water_9445_summer.BGL
4_mesh_multiLOD4-12_FTX-NZNI_section2.bgl
2_FTX_NZNI_orthoimage_NZNI_LINZ_ManukauHarbour_2m.bgl
ADE_FTX_NZNI_NZAA_GSE_Clutter.BGL
ADE_FTX_NZNI_NZAA_Markings_Clutter.BGL
ADE_FTX_NZNI_NZAA_Objects.BGL
ADE_FTX_NZNI_NZAA_Terminals.BGL
ADE_FTX_NZNI_NZAA.BGL
ADE_FTX_NZNI_NZAA_CVX.bgl
ADE_FTX_NZNI_NZAA_GP.bgl
ADE_FTX_NZNI_NZAA_Vegetation.BGL

Dynamic lights that pop in and out of view means your sim has hit the limit it can display, typically caused by many addons.

We highly recommend increasing the number of Dynamic Lights P3D can render. The default value is too low for a common install with various addons.

Instructions:

- Find and open your Prepar3D.cfg file, typically found here:

C:\Users\YOURUSERNAME\AppData\Roaming\Lockheed Martin\Prepar3D v5

You may need to enable hidden folders to view the “AppData’” folder.

- Find these lines:

MAX_POINT_LIGHTS=

MAX_SPOT_LIGHTS=

- Increase both values to at least 500 and save the file.

NZAA uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

This occurs when MSFS is set to "OFFLINE mode". A bug within MSFS manifest trees on top of aprons and ignores any exclusion flags.

Solution:

1. Set "Online Functionality" to ON. (Settings > General > Data
2. Delete "Rolling Cache File" (Settings > General > Data)
3. Restart Sim and be sure your PC has internet connection

If you still see trees with the above solution, then it's likely your firewall or security software is blocking MSFS from obtaining online imagery data. To verify this, load a flight at New York City. If your sim is properly connected to online data, the buildings will look quite realistic. If your sim is blocked or offline, the buildings in downtown NYC will look generic.

The Z-gate jetways are a little special since they're extremely low jetways. This type of jetway will soon be supported for this new simulator.

Good news, there's already been a multi-part update already released. Since the new changes at Denver International are so substantial, we've divided up the updates into 2, or possibly 3 updates. Here they are in order: 

Update 1 (released in 2023): Concourse B new expansion, interior improvements, custom jetways

Update 2 (release in  late 2024): Concourse A and C expansions, interior improvements and custom jetways

Since these are free updates, it takes time due to the substantial changes at the airport. Thanks for your patience!

Recently Bing has updated its imagery which shows the recent construction at Denver Airport. The problem is that these areas used to be grass, and therefore in the sim, grass would be generated. Now they show as flat satellite imagery. 

Fortunately we've already been hard at work on updating the airport with the new terminal sections. We're soon going to release a quick patch to clean these areas up and prepare them for a much bigger update. 

Thanks for your patience!

If you have MSFS Premium or Premium Deluxe installed, you MUST delete Asobo KDEN if you have our KDEN installed. To do so is very easy:

1. Go to your Profile, and click on Content Manager. Search for "KDEN"

2. In the list, select "Premium Upgrade", then click the list icon on the right to expand it.

3. Select Asobo's KDEN and click delete at the bottom. More detailed instructions below if needed:

If you see cliffs, or various terrain issues, you most likely still have Asobo's KDEN installed. This means you have two KDEN's installed at once, creating various issues such as terrain drops/issues, duplicate buildings, etc.

To resolve the issue, you must uninstall Asobo's KDEN as only one can be installed. Instructions: https://shop.flightbeam.net/apps/help-center#hc-kden-msfs-conflicts-with-asobo-kden

If you have MSFS Premium or Premium Deluxe installed, you MUST delete Asobo KDEN if you have our KDEN installed. To do so is very easy (updated for MSFS Sim Update V)

1. Go to your Profile, and click on Content Manager. Search for "PREMIUM"

2. In the list, Asobo KDEN will appear. Select it so that there is a checkmark next to it.

3. Click Delete. You must restart the sim for the changes to take effect.

A recent P3D v5 update has caused some terrain issues such as:

- A hump between taxiways
- Flattened airport
- Some aircraft crashing while taxiing/taking-off/landing on runways

We've issued a patch on December 14th to address most of these issues.

Unfortunately the airport will continue to remain flat, as P3Dv5 seems to no longer support custom terrain at airports, with no updates in the SDK to provide support for such customization.

These are symptoms of a duplicate/conflicting AFCAD file that pre-existed in your sim. In the Flightbeam Manager, go to the main page and click the "Troubleshooting" tab. The Manager will then find possible conflicting files and you will be able to disable them directly.

If this doesn't work, then the conflicting file is a bit harder to find. At this stage, use the Scenery Library to de-activate other addons one at a time to see which contains the conflicting file.

KDEN uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

A mesh addon is causing a problem. If you're using an Orbx mesh, make sure you have the latest version. Some addons such as FSGenesis will cause terrain anomalies and are impossible to correct. Additionally please make sure your terrain mesh settings are at the highest values, these settings typically don't affect performance with modern PCs

For users with FTX Vector, you need to disable AEC (Airport Elevation Correction) for KDEN in the FTX Vector settings. If you do not do this, you will see huge plateaus inside the airport. An example on how to do this is pictured below:

KDEN is FTX compatible and we have a whole set of files just to match it. Open the Flightbeam Manager, click on the "KDEN" tab, then click the "FTX Global Textures" button to download the texture pack automatically.

To ensure smooth operations between KSFO-HD and FTX Norcal, please read the following:

The following FTX Norcal files cause very heavy performance drops and must be disabled (per Orbx's instructions)

You can simply rename the extension from ".bgl" to ".OFF".. or just delete the files.

Under ORBX/FTX_NA/FTX_NA_NCA05_SCENERY/scenery:

FTX_NCA_objects_SRA_marinas_ships_docks_PLC.bgl

FTX_NCA_objects_marine_lights_PLC.bgl

FTX_NCA_objects_CA_Oakland.bgl

MULTIPLE CONFLICTING FILES WITH KSFO:

The following files must be disabled/removed (search "KSFO" in the Orbx folder)

ADEX_FTX_NCA_KSFO_San_Francisco_Intl_CVX.bgl

ADEX_FTX_NCA_KSFO_San_Francisco_Intl.bgl

ADE_FTX_NCA_KSFO_elevation_adjustment.bgl

FTX_NCA_objects_KSFO_PLC.bgl

FTX Norcal water poly issue:

Currently, the water poly file included in FTX Norcal causes the following coastline to be rough-edged.

There is currently no way for us to fix this issue as the Orbx water poly file overrrides our exclude and elevations files.

These are symptoms of a duplicate/conflicting AFCAD file that pre-existed in your sim. In the Flightbeam Manager, go to the main page and click the "Troubleshooting" tab. The Manager will then find possible conflicting files and you will be able to disable them directly.

If the above didn't work: Open your Scenery Library, start unchecking scenery one by one to temporarily de-activate them until the duplicate buildings disappear. This will tell you which scenery entry has the problematic file.

Flightbeam products use SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
Once SODE is installed, be sure to turn on SODE option in the Flightbeam Manager. To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

This happens when using ChasePlane cameras, or looking around in Avatar mode. If using ChasePlane, find your Cameras.cfg (back it up first). Change all instances of "ClipMode = Minimum" to "ClipMode = Normal" and save the file. Restart your sim.

This is caused by FTX Norcal. Unfortunately that product includes a custom water poly which overrides our scenery coastline. There is currently no way to disable this unless you uninstall FTX Norcal

FSX and P3D's programming has all aircraft stop at the same center point in a gate, even though different aircraft have different door locations. Unfortunately like in the real SFO, the large white jetways only move forward and up/down. Since they don't rotate, it's not possible to customize every aircraft stop location for the jetway to line up perfectly. Best solution is to use external view while slowly pulling up to the gate to verify jetway-door position alignment.

A bug caused by DreamFlight's MRLB scenery. Disable the scenery and it goes away.

As always, when default buildings are appearing it indicates a duplicate AFCAD file that should be removed from your sim. Here are the steps in order to resolve (in order):

1 - Use the Flightbeam Manager's troubleshooting tool to automatically find files causing this.

2 - If the above didn't work: Search your Sim folder for "OBX23161.bgl", if found, rename it to "OBX23161.OFF"

3 - If the above didn't work: Open your Scenery Library, start unchecking scenery one by one to temporarily de-activate them until the duplicate buildings disappear. This will tell you which scenery entry has the problematic file.

Unfortunately, this is a sim limitation.

KMSP uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
Once SODE is installed, be sure to turn on SODE option in the Flightbeam Manager. To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

Be sure that your Mesh complexity and Mesh resolution settings are at the highest value. This setting does not affect performance.

Be sure to change the season in the Flightbeam Manager, from the main page. When changing the season setting, it changes the seasonal textures automatically of all the products installed by Flightbeam Manager.

You may be using a third-party camera, such as ChasePlane. If using chaseplane, find your Cameras.cfg (back it up first). Change all instances of "ClipMode = Minimum" to "ClipMode = Normal" and save the file. Restart your sim.

KPHX uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
Once SODE is installed, be sure to turn on SODE option in the Flightbeam Manager. To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

You will experience these issues if your old copy of KPHX is still installed. It appears the FSDT uninstaller may not fully remove some files, or you had multiple versions that went through migration. (the latter is the most likely scenario)

Solution:

Remove them manually after making sure you uninstalled it from Windows Add or Remove Programs.

If any of these folders exist, delete them:

- Delete this folder: C:\Users\USERNAME\Documents\Prepar3D v4 Add-ons\Flightbeam KPHX (the one without the "-" hash)
- Delete this folder: C:\Program Files (x86)\Addon Manager\Flightbeam\KPHX
- Delete this folder: C:\Program Files (x86)\Addon Manager\Simobjects\Misc\FlightBeam_KPHX
- Delete this folder: C:\Program Files (x86)\Addon Manager\Couatl\KPHX


NOTE: Your FSDT Addon Manager location may be different. Default location is "C:\Program Files (x86)\Addon Manager"

As always, when default buildings are appearing it indicates a duplicate AFCAD file that should be removed from your sim. Here are the steps in order to resolve (in order):

1 - Use the Flightbeam Manager's troubleshooting tool to automatically find files causing this.

2 - If the above didn't work: Open your Scenery Library, start unchecking scenery one by one to temporarily de-activate them until the duplicate buildings disappear. This will tell you which scenery entry has the problematic file.

Go to your Scenery Library, move KPHX above Megascenery in the Library order.

Go to your Settings and set your Mesh Complexity and Resolution to the highest values. These don't affect performance. Also avoid slewing through the scenery too quickly. There is an immense amount of detail and the terrain takes a little time to load

Unfortunately as a result of implementing custom terrain to create the inner highway through KPHX, the side effect (bug) is the generation of some "invisible walls" in the airport.

As always, when default buildings are appearing it indicates a duplicate AFCAD file that should be removed from your sim. Here are the steps in order to resolve (in order):

1 - Use the Flightbeam Manager's troubleshooting tool to automatically find files causing this.

2 - If the above didn't work: Open your Scenery Library, start unchecking scenery one by one to temporarily de-activate them until the duplicate buildings disappear. This will tell you which scenery entry has the problematic file.

This product uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
Once SODE is installed, be sure to turn on SODE option in the Flightbeam Manager. To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

As always, when default buildings are appearing it indicates a duplicate AFCAD file that should be removed from your sim. The most common conflict with NZWN is Orbx's NZNI product. Be sure to run the Flightbeam Manager's troubleshooting tool to fix this in a few clicks.

Here are the steps in order to resolve other conflicts (in order):

1 - Use the Flightbeam Manager's troubleshooting tool to automatically find files causing this.

2 - If the above didn't work: Open your Scenery Library, start unchecking scenery one by one to temporarily de-activate them until the duplicate buildings disappear. This will tell you which scenery entry has the problematic file.

Unfortunately, this is a sim limitation with sloped runways. Runways in P3D must be flat for AI aircraft to operate on. For this reason, the runway remains at the general airport elevation, which makes it appear flat between the RWY 16 threshold and the road next to it.

NZWN uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

Be sure that your Mesh complexity and Mesh resolution settings are at the highest value. This setting does not affect performance. For more info please see the Product Manual: https://www.flightbeam.net/downloads/NZWN_MANUAL.pdf

You may be using a third-party camera, such as ChasePlane. If using chaseplane, find your Cameras.cfg (back it up first). Change all instances of "ClipMode = Minimum" to "ClipMode = Normal" and save the file. Restart your sim.

This was removed at the airport. If you still wish to have this texture, you can download it here and install it rather easily: http://www.flightbeam.net/downloads/NZWN_MoME.zip

Prepar3D version 4 is a very different from either previous versions of P3D or FSX in one major respect - it's a 64-bit simulator. That means the sim can use all the RAM your system has rather than a small, set amount. The plus side of this is that out-of-memory (OOM) errors are a thing of the past. That gives us the room to add detail like we never could before without killing performance. By authoring for this new environment, however, we're using techniques that don't translate well to the older 32-bit sims. Creating a version of the scenery for older simulators therefore takes a lot more work, and this is at a time when our research shows that use of those sims is rapidly falling off. So the short answer is, it's not worth the amount of extra effort that would go into downgrading the scenery for 32-bit.

It's likely you're running another product that has added an elevation adjustment file for KPDX.
1 - Use the Flightbeam Manager's troubleshooting tool to automatically find files causing this.
2 - If the above doesn't work, look in your root P3D4 folder, under "Scenery\World\scenery" and do a search for "kpdx". If any files turn up in the search, set their file extension to ".OFF" to disable them. This should restore your runway elevations.
3- If you still have elevation issues, manually remove the following files into a backup location:
In the following folder: ORBX\FTX_NA\FTX_NA_PNW05_SCENERY\scenery

Remove:
ADE_FTX_PNW_KPDX_Portland_Intl.BGL
ADE_FTX_PNW_KPDX_Portland_Intl_CVX.bgl
FTX_PNW_objects_KPDX_PLC.bgl

In Scenery\World\scenery, the following:

ADE_FTX_PNW_KPDX_elevation_adjustment.BGL

KPDX uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
Once SODE is installed, be sure to turn on SODE option in the Flightbeam Manager. To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

Yes to all the above! KPDX was designed to fit seamlessly into the Orbx version of the Pacific Northwest with no additional downloads or tweaks. In fact, you'll find that the Orbx Portland Cityscape freeware is a great companion to it, as is Bill's KVUO Pearson Field, which is just a stone's throw across the river.

We're currently investigating an issue caused by the static aircraft configuration option which makes buildings revert to default KPDX buildings when "No Static AC" has been selected in Contrail. 

For the moment we're advising to leave static aircraft selected to "on".

As always, when default buildings are appearing it indicates a duplicate AFCAD file that should be removed from your sim. Be sure to run the Flightbeam Manager's troubleshooting tool to fix this in a few clicks.

Here are the steps in order to resolve other conflicts (in order):

1 - Use the Flightbeam Manager's troubleshooting tool to automatically find files causing this.

2 - If the above didn't work: Open your Scenery Library, start unchecking scenery one by one to temporarily de-activate them until the duplicate buildings disappear. This will tell you which scenery entry has the problematic file.

SEQM uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442

Navigate to the following path in your main P3D folder "\Scenery\0304\scenery" and search for the file

APX27320.bgl, rename it to APX27320.bgl.OFF

As always, when default buildings are appearing it indicates a duplicate AFCAD file that should be removed from your sim. Here are the steps in order to resolve (in order):

- Use the Flightbeam Manager's troubleshooting tool to automatically find files causing this.

- If the above didn't work: Open your Scenery Library, start unchecking scenery one by one to temporarily de-activate them until the duplicate buildings disappear. This will tell you which scenery entry has the problematic file.

EDDN uses SODE jetways. In order to use SODE jetways, you must first have SODE installed: http://sode.12bpilot.ch/
Once SODE is installed, be sure to turn on SODE option in the Flightbeam Manager. To get the jetway to connect, you can use Tab+S to open the SODE menu and select the gate... or if you have GSX simply use your GSX services shortcut (Ctrl + F12).

If you have installed SODE and jetways don't appear, be sure to check out the SODE Troubleshooting guide on the SODE website: https://sode.12bpilot.ch/?topic=troubleshoot-guide

Please note that SODE is an addon created by another developer, our support with SODE issue is limited since we did not create the software. For more in depth SODE support, visit the SODE support forum: https://sode.12bpilot.ch/?page_id=442