Solution Center

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.

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.

Our airports are addons for Flight Simulators. Currently we officially supported, depending on the product:

- Lockheed Martin Prepar3D

- Microsoft Flight Simulator X and Steam Edition

- XPlane 11

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.

1. Download your product

Directly after purchasing, you will be presented with a download page for your new product. Download and save in a safe location. If you need to re-download at any time, simply revisit your account by going to https://shop.flightbeam.net/account

2. Run the Installer

Be sure to specify the correct location of your sim. For most users, the default location is correct.

3. If you purchased directly from the Flightbeam webstore

You may be asked to login. Use the same login as you used from the webstore. Once logged in, your product is activated and ready to go.

3B. If you purchased from a third-party vendor (Simmarket, PCAviator, iBlueYonder, etc)

You may be asked to login. Use an existing account, or create one for free if you're a new user. Once logged in, click the product tab that you have installed and you'll be prompted to enter your serial number to activate. Once completed, this product will be associated with your account when you login on shop.flightbeam.net

4. Configure the product (optional)

Once activated you can customize the product to your liking depending on your performance needs. Please note most of our products require the free SODE mod to display and utilize the advanced jetways.

Note on Seasons: The season selector on the main page of the Flightbeam Manager changes textures and seasonal variations only for the following northern hemisphere products: KPHX, KIAD, KDEN, KSFO and KMSP. Other products such as NZWN and KPDX dynamically changes season without input.

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.

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!

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.

As of July 1, 2019 we no longer use serial numbers unless you purchased from a third party vendor (Simmarket, PCAviator, etc).
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.

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.

No problem, an account has been created for each e-mail address. If you still have access to those e-mail addresses, please activate all of them via the account invitation you have received. 

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

>> Merge Flightbeam Accounts <<

You can activate those products in the Flightbeam Manager.

1. Open the Flightbeam Manager
2. Switch to the tab of the scenery you want to activate
3. Enter the serial number you have received from the third-party vendor

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

This indicates that the product is not associated with the email you logged in with. It's likely you purchased the product with another email. Simply use the Account Merge form to merge that order into your new email: 

>> Merge Accounts Here <<

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: Send us an email through the contact form at the bottom of this FAQ page. Include the email you have.. and the email you'd like to change to.

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

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 <<

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.

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

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.

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.

September 17 - 2021

Since the latest MSFS "hotfix", we've been made aware that a CTD can occur if you land on RWY 7. We've aware of this issue and have been able to reproduce it. We should have a fix coming within 7 days. Thanks for your patience!

Note: CTD will not occur if you land on other runways.

Update: September 30, 2021:

Since we were not able to fix this issue, we contacted Asobo/MS.

Asobo has acknowledged this bug and advised a fix will be included in the next World Update (October)

We've received reports from a small number of customers of random CTDs that happen at or around KDEN.

While we haven't been able to reproduce this, we've been working closely with some customers to determine the cause. In almost every case, Navigraph is installed on the user's system. We've had various issues with Navigraph in the past, as their navdata tends to overwrite our custom data, regardless of priority in position within the user's config files.

Some customers have been able to resolve the issue by removing Navigraph, while others have had success by updating to the most recent Nav cycle.
Ultimately the bug causing this issue lies with the manner in which the simulator handles nav data. We've forwarded this case to Asobo and they have acknowledged this issue, we're hoping this will be mitigated in the future.

With the July 27, 2021 MSFS update (Sim Update V), there has been numerous changes to the game engine. Some of the changes make wrong textures show at addon airports.

If you purchased KDEN via the MSFS Marketplace:

We've issued a patch and is now live in the Marketplace. Be sure to update via the Content Manager in MSFS.

If you purchased KDEN via Flightbeam webshop, or Contrail, or Simmarket:

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.

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.

This issue has been resolved in the latest version of KDEN v1.0.7

However if you still encounter this problem with a previous version, instructions below.

This occurs when MSFS is set to "OFFLINE mode", or when the sim is unable to make a connection with Microsoft Bing Servers. 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

Be sure that everything in the "Data" settings of the sim should be set to "On", especially Bing Data.

Still see trees after these steps? If so, it's likely security software is still blocking your sim from accessing the servers. To test this, load a flight into downtown NYC. If you are offline, you will see generic looking buildings instead of photoreal skyscrapers.

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.

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

Like a lot of airports, the real KPDX is in a perpetual cycle of construction as it tries to keep up with traffic demands. In order to get a good "snapshot" of the airport, we have to freeze it at a particular time - usually when the last airport survey was done, or when the most recent batch of source photos was taken. While we work to bring those photos to life for your simulators, the real world often marches on without us. There are several areas at KPDX that have been added recently, such as the posh new Atlantic Aviation terminal for business travel, a new parking structure near the control tower, and the E-gates terminal extension. Rest assured that we're committed to adding all these features in upcoming versions of the scenery, which will be easily downloadable free of charge to KPDX customers via the Flightbeam manager once they're ready.

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.

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

Notice: If you are running Prepar3D v5, we are aware of issues with Dynamic Lighting. This was caused by drastic changes made by the Prepar3D development. We're working on issuing a fix. Thanks for your patience.
Please avoid sending a new email regarding this issue, we're already aware of it.

All other Dynamic Lighting issues: