Redeeming a key

Please verify first if:

• V1 is fully uninstalled,
• Reinstall the main scenery,
• Check if any other Irish scenery are installed that may lead to the problems,
• Clean cache and reload the simulator.

In MSFS you can only assign a single jetway per parking. Therefore we have some of them as static, inactive objects, and others attached to the closest stands depending on the airport.

It may not be 100% realistic, but because of this limitation we can’t do more.

This feature is not available in MSFS at the moment. We can only specify parking and gates by size (wingspan).

While others say there’s a walkaround, we’ve checked it multiple times and it didn’t make any difference.

Please verify first if:

• V1 is fully uninstalled,
• Reinstall the main scenery,
• Check if any other Irish scenery is installed that may lead to the problems,
• Clean the cache and reload the simulator.

We’re unfortunately unable to verify those because of limited debugging possibilities for developers. However, this may be also caused by the planes and other addons sharing console resources.

We suggest making sure, that everything is up to date.

I’ve been trying to track this issue for quite a bit of time. What seems to be a problem is stock EFHK content.

You may try to move the files away (make a backup!).

X:\Prepar3D\Scenery\0601\scenery

APX54100.bgl
OBX54100.bgl
cvx5410.bgl (if using Orbx Vector)

The alternative is to download our modified file – cvx5410.bgl and replace it.

Look at the OBX54100 which has a lot of stock scenery objects placed all around. Each of them takes a draw call or more.

This issue is related to Traffic Global by JustFlight. 

You MUST deactivate their AirportFacilities in the simulator Scenery Library.

Custom AFCADS are stored in C:\Users\xxxx\Documents\TrafficGlobal\AirportFacilities.

PAPI lights in BIAR (RWY 01) are calibrated for two types of approaches.
RIGHT -> LOC approach with GS with 3.5 degrees gradient
LEFT -> ILS approach with 5.3 degrees gradient

Please check the charts and select the proper approach for your plane type before going to BIAR.

There may be several reasons for elevation issues. They usually happen because of conflicting files, or wrong scenery layering.

• First of all, check your P3D Scenery Library layering. Make sure the scenery always stays on the TOP and ORBX, MESH, AI addons are below. This is a universal rule that may help to avoid future conflicts.

• Navigate to your Prepar3D v4\Scenery\World\scenery folder and check if there are any files containing BIKF/BIAR in the name present inside?
  If there are make sure to change their extensions to .off or move them away to a temporary location.
• Some AI addons have custom afcads provided, usually with data that won’t match custom scenery. If you own Global Traffic by JustFlight please do the following action:
  You MUST deactivate their AirportFacilities in the simulator Scenery Library.
  Custom AFCADS are stored in C:\Users\xxxx\Documents\TrafficGlobal\AirportFacilities 
• Open ORBX Central and run a VECTOR Configuration tool
  Run Auto-Configuration and check IF AEC IS DISABLED FOR:
  BIKF
  BIGR
  Press Apply and run your P3D.
• Use Simple Airport Scanner to scan your airport afcads.https://www.fsdeveloper.com/forum/threads/simple-airport-scanner-1-70-beta.440300/

  Open the program:

  
  1. Select your FS Version (top right)
  2. Point it to P3D V4 Scenery.cfg

  
  3. Press scan.
  4. Check the results if there are any custom AFCADS present.

• Setup Insertion Point in ORBX Central
  

  

  Navigate to Settings -> Insertion Point

  In ORBX Airports and Regions select it to be INSERTED BELOW last custom scenery you own.

The installer should automatically rename the ORBX files, but in some cases (antivirus, admin privileges, or locating problems) it won’t. In this case, you need to take manual action.

If you have ORBX FTX Iceland or Open LC scenery installed you MUST deactivate/move away the following files:

Prepar3D v4 or OTHER \ ORBX \ FTX_OLC \ OLC_EU8 \ Scenery

01_APTBIKF.BGL

01_APTBIAR.bgl

02_APTBIKF_CVX.bgl

02_APTBIAR_CVX.bgl

FTX_FTXG_BIKF_objects.bgl

FTX_FTXG_BIAR_objects.bgl

Prepar3D v4 or OTHER \ ORBX \F TX_OLC \ OLC_EU9 \ Scenery

02_DEM4109.bgl

We recommend changing the files extensions to .off from .bgl.

This is a BUG of P3D which considers Summer + Day conditions as night. You may observe this problem in the P3D main menu when selecting your Time and Season.

It seems to be related to only a few days in June.

This won’t cause any issues besides lights appearing during the day.

It was reported to the Lockheed Martin team and we hope this will get fixed soon. The error is related to P3D timezones.

We included the following airports in the package:

BIKF – fully detailed rendition.

BIAR – a medium detailed rendition that comes as a bonus airport in the package.

BIGR – photo scenery and afcad adjusted to cooperate nicely with ORBX Iceland Demo/Open LC Europe

BIIS – photo scenery and afcad adjusted to cooperate nicely with ORBX Iceland Demo/Open LC Europe

Our Keflavik scenery is compatible with:

– ORBX Global

– ORBX Open LC

– ORBX VECTOR

You may however have to follow a few steps and disable some BGL files to avoid conflicts.

More specific information about it in another FAQ question.

You can verify that by running your P3D and checking both Add-ons and Scenery options.

The scenery should NEVER appear twice in the Scenery Library. Correct installation is by add-on.xml which means it will be greyed out in the Scenery Library.

This is mainly because of a SODE issue.

1. Verify if you own the last version of SODE: https://sode.12bpilot.ch/

____________________________________________________________________________________

2. Set your system to show you hidden items.

____________________________________________________________________________________

3. Run your simulator and load the MK scenery that has this problem.

____________________________________________________________________________________

4. Then navigate to: C:\ProgramData\12bPilot\SODE\log

You’ll find LOG files there.

Attach them to the support ticket.