useful tip BUG REPORT - TE Oregon - Tillamook - Fix attached - post 73

[rinkerbuck]

yeah i dont have it 

[Jon Clarke]

3 hours ago, mauricecohen said:

Jon and rinkerbuck, please try the following - unzipped and above Global Airports

 

KTMK Tillamook (Modified default).zip 41.15 kB · 0 downloads

I have tried both the recent mods but get the same view as per my pic earlier.

Really appreciating your efforts here. 

[Nick Cooper]

I have merged the duplicate topic.

[mauricecohen]

4 hours ago, mauricecohen said:

The above struck-out text is wrong

 

I guess it was correct and it is only a solution for those who have the custom museum with an embedded white building.

[rinkerbuck]

Unfortunately same here, no change. Thanks for trying.

[Sentry11]

The first screen shot is with "@mauricecohen" 's patch installed and TE Oregon - TE Washington - TE NoCal set-up in the "ini" file as follows:

 

SCENERY_PACK Custom Scenery/Global Airports/

SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/

 

The second screen shot is with "@mauricecohen" 's patch installed and TE Washington - TE Oregon - TE NoCal  set-up in the "ini" file as follows:

 

SCENERY_PACK Custom Scenery/Global Airports/

SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/

SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/

 

 

I'm thinking that maybe KTMK - Tillamook is close to the demarcation line between TE Washington and TE Oregon and also the order they are  positioned in the "ini" file has something to do with how the museum hanger is, or not displayed properly.

 

 

 

Edited November 22, 2019 by Sentry11

[mauricecohen]

Interesting, my order is

 

SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/

.

.
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/

.

.
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/

 

so essentially your order for the first screen shot, where you do not see the custom museum,  and yet I do.

 

This is getting to be very strange.

 

I will say it again, if the developers want to add a custom object within an airport, I think that to be safe they should provide the whole airport in the package, placed above the global ones, as is the case for WA56_IsraelsFarm in the TE_WA set.

[Sentry11]

Try arranging yours in the "ini" file like the following and see what you get.

 

SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/

SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/

SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/

.

.
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/

SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/

SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/

.

.
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/

SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/

SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/
 

[Jon Clarke]

@mauricecohen @Sentry11 You 2 are a great problem solving combo and i want to thank you for your combined efforts in resolving this annoying anomaly.

Tests show that users need @mauricecohen modified KTMK airport file, and that they then need to ensure that the layering sequence in the scenery_packs.ini is as per @Sentry11 example number 2.

SCENERY_PACK Custom Scenery/Global Airports/

SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/

SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/

 We now need to get the devs to fix the issue in a suitable manner to ensure that customers who don't have TE Washington nor @mauricecohen's modded KTMK file also get to see the Museum.

@Nick Cooper suggest we may want to add this as a possible limited fix for the anomaly for those customers who have the required addons of both TE Washington and TE Oregon

 

This is what I now see:

 

[Nick Cooper]

Hello,

I have not touched the ini file, so I expect that without outside influence,

Orbx Central writes the entries in like this:

 

SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/

 

Thanks indeed to Maurice and Sentry11

I have slightly modified the title and as the topic is already in the Bug Report forum,

the developer(s) should see it.

[Jon Clarke]

21 minutes ago, Nick Cooper said:

Hello,

I have not touched the ini file, so I expect that without outside influence,

Orbx Central writes the entries in like this:

 

SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/

 

Thanks indeed to Maurice and Sentry11

I have slightly modified the title and as the topic is already in the Bug Report forum,

the developer(s) should see it.

It may well be written in an order depending on when the 3 TE addons were installed. For example NorCal may be first on the layering if it was the first TE added by a customer ans subsequent TE entries may be layered below NorCal. Just a theory not a fact that I have tested. The current layering in your example is based on a sequence of installations, TE Washington was the first TE US released followed by TE Oregon and lastly by TE NorCal. That installation sequence is what is reflected in the exampled layering. Could be different if a customer installed NorCal first, liked it and then installed Oregon, for example. The sequence could then well be :

 

SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/

SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/

[Nick Cooper]

Hello Jon,

agreed and I absolutely agree with Maurice that it is an unintended consequence that does need to be addressed.

[Sentry11]

Not just that but what about the Orbx Central installer having a tendency to fiddle with the "ini" order when installing certain scenery items itself.

Think of "Needles" for one, and others have even reported this happening with other entries as well.  Eh!!

 

 

.

[Nick Cooper]

Hello,

please don't derail this topic, it's a bug report, intended for the developer to

see and address.

If you have wider issues, please post instead into the X Plane 11 Support forum,

or indeed the Orbx Central support forum for problems with installations.

[Flappy]

Thank you ALL for looking into this.

     I was using some freeware to get KTMK into XP but the sale and THIS topic ensured that I bought not only Oregon HD but Washington HD as well. And the museum spawn continues to be random. When I start a flight at KHIO or Stark's I can fly TO KTMK and the museum is visible. If I START at KTMK it hasn't been so far. Additionally I have been playing with the object and terrain resolution sliders but so far no joy in replicating it exactly.

[rinkerbuck]

Still waiting on any updates on a fix

[Jon Clarke]

8 hours ago, rinkerbuck said:

Still waiting on any updates on a fix

There is no timeframe given. The situation can be remedied as you know by adopting the advice and modifications given in the above posts.

[rinkerbuck]

None of the remedies above worked for me. I thought that was known, that the fixes don't work.

[Jon Clarke]

On 12/16/2019 at 10:36 PM, rinkerbuck said:

None of the remedies above worked for me. I thought that was known, that the fixes don't work.

You need all the correct requisites for the remedy to work:

1. You need this modded  airport from maurice:

Link removed on the instructions of the developer

 

 

2. You need to ensure that the layering sequence in your scenery_packs.ini is exactly like this example below. The main important factor is to have TE Washington above TE Oregon.

 

SCENERY_PACK Custom Scenery/Global Airports/

SCENERY_PACK Custom Scenery/Orbx_A_US_Washington_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Washington_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Washington_TE_Orthos/

SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_A_US_NoCal_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_NoCal_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_NoCal_TE_Orthos/

[rinkerbuck]

I don't have TE Washington, only Oregon. Also where should the line for SCENERY_PACK Custom Scenery/KTMK Tillamook (Modified default)/ be?

 

Otherwise, the way you have the scenery ordered is the way I already had it,:

 

SCENERY_PACK Custom Scenery/Global Airports/
SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/

 

 

currently I still have the same problem, flat version of the building but no 3d model.

[mauricecohen]

2 hours ago, rinkerbuck said:

where should the line for SCENERY_PACK Custom Scenery/KTMK Tillamook (Modified default)/ be?

Above  SCENERY_PACK Custom Scenery/Global Airports/

[rinkerbuck]

Yeah, still not working I'm afraid, just getting the 2d non overlay image of the building. Here is my entire scenery.ini

 

I
1000 Version
SCENERY

SCENERY_PACK Custom Scenery/Orbx_L52_A_Oceano_County/
SCENERY_PACK Custom Scenery/Orbx_ENOV_A_Orsta_Volda/
SCENERY_PACK Custom Scenery/Orbx_ENHA_A_Hamar_Flyplass/
SCENERY_PACK Custom Scenery/Orbx_EG20_Clench_Common_Field/
SCENERY_PACK Custom Scenery/HD Forests/
SCENERY_PACK Custom Scenery/Airport Environment HD/
SCENERY_PACK Custom Scenery/Princess Juliana Int'l Aiport- TNCM V1.0.1/
SCENERY_PACK Custom Scenery/KPDX - Portland International/
SCENERY_PACK Custom Scenery/WashingtonDC/
SCENERY_PACK Custom Scenery/Aerosoft - EDDF Frankfurt/
SCENERY_PACK Custom Scenery/Aerosoft - EDLP Paderborn-Lippstadt/
SCENERY_PACK Custom Scenery/Aerosoft - EGLL Heathrow/
SCENERY_PACK Custom Scenery/Aerosoft - LFMN Nice Cote d Azur X/
SCENERY_PACK Custom Scenery/Aerosoft - LFPO Paris Orly/
SCENERY_PACK Custom Scenery/Aerosoft - LPFR Faro/
SCENERY_PACK Custom Scenery/x_Prefab_FSE_Airports/
SCENERY_PACK Custom Scenery/x_Prefab_Library V8.0/
SCENERY_PACK Custom Scenery/KSEA Demo Area/
SCENERY_PACK Custom Scenery/LOWI Demo Area/
SCENERY_PACK Custom Scenery/world-models/
SCENERY_PACK Custom Scenery/X-Plane Landmarks - Sydney/
SCENERY_PACK Custom Scenery/X-Plane Landmarks - New York/
SCENERY_PACK Custom Scenery/X-Plane Landmarks - Washington DC/
SCENERY_PACK Custom Scenery/X-Plane Landmarks - Chicago/
SCENERY_PACK Custom Scenery/X-Plane Landmarks - Dubai/
SCENERY_PACK Custom Scenery/X-Plane Landmarks - Las Vegas/
SCENERY_PACK Custom Scenery/X-Plane Landmarks - London/
SCENERY_PACK Custom Scenery/KTMK Tillamook (Modified default)/
SCENERY_PACK Custom Scenery/Global Airports/
SCENERY_PACK Custom Scenery/Orbx_A_US_Oregon_TE_Custom/
SCENERY_PACK Custom Scenery/Orbx_B_US_Oregon_TE_Overlay/
SCENERY_PACK Custom Scenery/Orbx_C_US_Oregon_TE_Orthos/
SCENERY_PACK Custom Scenery/Orbx_OrbxlibsXP/
SCENERY_PACK Custom Scenery/SAM_Library/
SCENERY_PACK Custom Scenery/MisterX_Library/
SCENERY_PACK Custom Scenery/OpenSceneryX/
SCENERY_PACK Custom Scenery/R2_Library/
SCENERY_PACK Custom Scenery/3D_people_library/
SCENERY_PACK Custom Scenery/Lyndiman_NZ_North_Island_Ortho_East_Cape_R3/
SCENERY_PACK Custom Scenery/Lyndiman_NZ_North_Island_Ortho_Northland_R3/
SCENERY_PACK Custom Scenery/Lyndiman_NZ_North_Island_Ortho_Taranaki_R3/
SCENERY_PACK Custom Scenery/Lyndiman_NZ_North_Island_Ortho_Wellington_R3/
SCENERY_PACK_DISABLED Custom Scenery/yOrtho4XP_Overlays/
SCENERY_PACK H:\SteamLibrary\steamapps\common\X-Plane 11\Custom Scenery\yOrtho4XP_Overlays/
SCENERY_PACK Custom Scenery/zOrtho4XP_+33-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+33-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_+33-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+62-007/
SCENERY_PACK Custom Scenery/zOrtho4XP_+62-008/
SCENERY_PACK Custom Scenery/zOrtho4XP_+65-014/
SCENERY_PACK Custom Scenery/zOrtho4XP_+65-015/
SCENERY_PACK Custom Scenery/zOrtho4XP_+42-106/
SCENERY_PACK Custom Scenery/zOrtho4XP_+42-107/
SCENERY_PACK Custom Scenery/zOrtho4XP_+64-022/
SCENERY_PACK Custom Scenery/zOrtho4XP_+64-023/
SCENERY_PACK Custom Scenery/zOrtho4XP_+65-037/
SCENERY_PACK Custom Scenery/zOrtho4XP_+50+000/
SCENERY_PACK Custom Scenery/zOrtho4XP_+50-001/
SCENERY_PACK Custom Scenery/zOrtho4XP_+51+000/
SCENERY_PACK Custom Scenery/zOrtho4XP_+51-001/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-123/
SCENERY_PACK Custom Scenery/zOrtho4XP_+32-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_+07-081/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+34-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-115/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-156/
SCENERY_PACK Custom Scenery/zOrtho4XP_+19-155/
SCENERY_PACK Custom Scenery/zOrtho4XP_+19-156/
SCENERY_PACK Custom Scenery/zOrtho4XP_+19-157/
SCENERY_PACK Custom Scenery/zOrtho4XP_+20-156/
SCENERY_PACK Custom Scenery/zOrtho4XP_+38-077/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-077/
SCENERY_PACK Custom Scenery/zOrtho4XP_+21-158/
SCENERY_PACK Custom Scenery/zOrtho4XP_+21-159/
SCENERY_PACK Custom Scenery/zOrtho4XP_-28+152/
SCENERY_PACK Custom Scenery/zOrtho4XP_-28+153/
SCENERY_PACK Custom Scenery/zOrtho4XP_+33-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+33-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+34-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+34-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-114/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-115/
SCENERY_PACK Custom Scenery/zOrtho4XP_+35-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-114/
SCENERY_PACK Custom Scenery/zOrtho4XP_+34-115/
SCENERY_PACK Custom Scenery/zOrtho4XP_+34-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+34-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+34-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_+62+007/
SCENERY_PACK Custom Scenery/zOrtho4XP_+63+007/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+37-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+37-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+38-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+39-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+17-066/
SCENERY_PACK Custom Scenery/zOrtho4XP_+17-067/
SCENERY_PACK Custom Scenery/zOrtho4XP_+17-068/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-067/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-068/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-108/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-107/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-108/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-106/
SCENERY_PACK Custom Scenery/zOrtho4XP_+60+011/
SCENERY_PACK Custom Scenery/zOrtho4XP_+62+006/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-069/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-070/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-071/
SCENERY_PACK Custom Scenery/zOrtho4XP_+19-070/
SCENERY_PACK Custom Scenery/zOrtho4XP_+19-071/
SCENERY_PACK Custom Scenery/zOrtho4XP_+45-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+45-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+63-161/
SCENERY_PACK Custom Scenery/zOrtho4XP_+64-161/
SCENERY_PACK Custom Scenery/zOrtho4XP_+64-162/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-105/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-104/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-105/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-102/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-103/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-104/
SCENERY_PACK Custom Scenery/zOrtho4XP_+42-108/
SCENERY_PACK Custom Scenery/zOrtho4XP_+42-109/
SCENERY_PACK Custom Scenery/zOrtho4XP_+43-115/
SCENERY_PACK Custom Scenery/zOrtho4XP_+43-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+43-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-120/
SCENERY_PACK Custom Scenery/zOrtho4XP_+40-120/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-066/
SCENERY_PACK Custom Scenery/zOrtho4XP_+17-063/
SCENERY_PACK Custom Scenery/zOrtho4XP_+43-109/
SCENERY_PACK Custom Scenery/zOrtho4XP_+43-110/
SCENERY_PACK Custom Scenery/zOrtho4XP_+44-109/
SCENERY_PACK Custom Scenery/zOrtho4XP_+43-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+44-110/
SCENERY_PACK Custom Scenery/zOrtho4XP_+44-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+45-110/
SCENERY_PACK Custom Scenery/zOrtho4XP_+45-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+38-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+39-120/
SCENERY_PACK Custom Scenery/zOrtho4XP_+39-121/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-114/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-115/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_-09+140/
SCENERY_PACK Custom Scenery/zOrtho4XP_-17+128/
SCENERY_PACK Custom Scenery/zOrtho4XP_+36-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+37-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+63-143/
SCENERY_PACK Custom Scenery/zOrtho4XP_+63-144/
SCENERY_PACK Custom Scenery/zOrtho4XP_+38-122/
SCENERY_PACK Custom Scenery/zOrtho4XP_+45-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+45-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+37-121/
SCENERY_PACK Custom Scenery/zOrtho4XP_+38-120/
SCENERY_PACK Custom Scenery/zOrtho4XP_+38-121/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-121/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-122/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-124/
SCENERY_PACK Custom Scenery/zOrtho4XP_+17-064/
SCENERY_PACK Custom Scenery/zOrtho4XP_+17-065/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-064/
SCENERY_PACK Custom Scenery/zOrtho4XP_+18-065/
SCENERY_PACK Custom Scenery/zOrtho4XP_+30-082/
SCENERY_PACK Custom Scenery/zOrtho4XP_+37-120/
SCENERY_PACK Custom Scenery/zOrtho4XP_+38-078/
SCENERY_PACK Custom Scenery/zOrtho4XP_+39-077/
SCENERY_PACK Custom Scenery/zOrtho4XP_+39-078/
SCENERY_PACK Custom Scenery/zOrtho4XP_+41-123/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-119/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-120/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-121/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-122/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-123/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-124/
SCENERY_PACK Custom Scenery/zOrtho4XP_+46-125/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-123/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-124/
SCENERY_PACK Custom Scenery/zOrtho4XP_+47-125/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-103/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-104/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-105/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-106/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-107/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-108/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-109/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-110/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-111/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-112/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-113/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-114/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-115/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-116/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-117/
SCENERY_PACK Custom Scenery/zOrtho4XP_+48-118/
SCENERY_PACK Custom Scenery/zOrtho4XP_+63+009/
SCENERY_PACK Custom Scenery/zOrtho4XP_+63+010/
SCENERY_PACK Custom Scenery/zOrtho4XP_-35+172/
SCENERY_PACK Custom Scenery/zOrtho4XP_-35+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-35+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-36+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-36+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-37+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-37+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-37+175/
SCENERY_PACK Custom Scenery/zOrtho4XP_-38+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-38+175/
SCENERY_PACK Custom Scenery/zOrtho4XP_-38+176/
SCENERY_PACK Custom Scenery/zOrtho4XP_-38+177/
SCENERY_PACK Custom Scenery/zOrtho4XP_-38+178/
SCENERY_PACK Custom Scenery/zOrtho4XP_-39+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-39+175/
SCENERY_PACK Custom Scenery/zOrtho4XP_-39+176/
SCENERY_PACK Custom Scenery/zOrtho4XP_-39+177/
SCENERY_PACK Custom Scenery/zOrtho4XP_-39+178/
SCENERY_PACK Custom Scenery/zOrtho4XP_-40+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-40+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-40+175/
SCENERY_PACK Custom Scenery/zOrtho4XP_-40+176/
SCENERY_PACK Custom Scenery/zOrtho4XP_-40+177/
SCENERY_PACK Custom Scenery/zOrtho4XP_-41+172/
SCENERY_PACK Custom Scenery/zOrtho4XP_-41+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-41+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-41+175/
SCENERY_PACK Custom Scenery/zOrtho4XP_-41+176/
SCENERY_PACK Custom Scenery/zOrtho4XP_-42+171/
SCENERY_PACK Custom Scenery/zOrtho4XP_-42+172/
SCENERY_PACK Custom Scenery/zOrtho4XP_-42+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-42+174/
SCENERY_PACK Custom Scenery/zOrtho4XP_-42+175/
SCENERY_PACK Custom Scenery/zOrtho4XP_-42+176/
SCENERY_PACK Custom Scenery/zOrtho4XP_-43+170/
SCENERY_PACK Custom Scenery/zOrtho4XP_-43+171/
SCENERY_PACK Custom Scenery/zOrtho4XP_-43+172/
SCENERY_PACK Custom Scenery/zOrtho4XP_-43+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-44+168/
SCENERY_PACK Custom Scenery/zOrtho4XP_-44+169/
SCENERY_PACK Custom Scenery/zOrtho4XP_-44+170/
SCENERY_PACK Custom Scenery/zOrtho4XP_-44+171/
SCENERY_PACK Custom Scenery/zOrtho4XP_-44+172/
SCENERY_PACK Custom Scenery/zOrtho4XP_-44+173/
SCENERY_PACK Custom Scenery/zOrtho4XP_-45+167/
SCENERY_PACK Custom Scenery/zOrtho4XP_-45+168/
SCENERY_PACK Custom Scenery/zOrtho4XP_-45+169/
SCENERY_PACK Custom Scenery/zOrtho4XP_-45+170/
SCENERY_PACK Custom Scenery/zOrtho4XP_-45+171/
SCENERY_PACK Custom Scenery/zOrtho4XP_-46+166/
SCENERY_PACK Custom Scenery/zOrtho4XP_-46+167/
SCENERY_PACK Custom Scenery/zOrtho4XP_-46+168/
SCENERY_PACK Custom Scenery/zOrtho4XP_-46+169/
SCENERY_PACK Custom Scenery/zOrtho4XP_-46+170/
SCENERY_PACK Custom Scenery/zOrtho4XP_-46+171/
SCENERY_PACK Custom Scenery/zOrtho4XP_-47+166/
SCENERY_PACK Custom Scenery/zOrtho4XP_-47+167/
SCENERY_PACK Custom Scenery/zOrtho4XP_-47+168/
SCENERY_PACK Custom Scenery/zOrtho4XP_-47+169/
SCENERY_PACK Custom Scenery/zOrtho4XP_-47+170/
SCENERY_PACK Custom Scenery/zOrtho4XP_-48+167/
SCENERY_PACK Custom Scenery/zOrtho4XP_-48+168/
SCENERY_PACK Custom Scenery/zzz_hd_global_scenery3/

[rinkerbuck]

Any update? Anything else to try? Am I just out of luck here and this product does not work as advertised? 

[Flappy]

Mine's still absent as well.

 

    Going to try the fix and the scenery pack .ini ordering. I DO have Washington HD so I'll make sure it is ABOVE Oregon in the load order. Sucks as I live right by Stark's Twin Oaks and I ride to Tillamook almost weekly when the weather cooperates.

[Flappy]

Mine's still absent as well.

 

    Going to try the fix and the scenery pack .ini ordering. I DO have Washington HD so I'll make sure it is ABOVE Oregon in the load order. Sucks as I live right by Stark's Twin Oaks and I ride to Tillamook almost weekly when the weather cooperates.  ANNND that was a quick fix. Put the fix in the addon scenery folder and checked my scenery pack ini.- sure enough, Washington was BELOW Oregon so I changed that and now THIS is the result.......

[Jon Clarke]

That's good news. Now you can bike there in the real world or fly there in your sim!! Nice dirt bike by the way Also nice to see that a plane from the UK Channel Islands managed to make it to Tillamook on one tank of gas

[Sentry11]

Hello Jon,

 

As you can see in the attached "Tillamook Museum.obj" and it's texture files  are in both in "Orbx_A_US_Washington_TE_Custom" and "Orbx_A_US_Oregon_TE_Custom" folders.

Since Tillamook, OR is so near the demarcation line between Oregon and Washington, this just might be what is causing the problem users are having with the "Tillamook Museum"  showing correctly.

Since "rinkerbuck" doesn't own "Orbx_A_US_Washington" yet, maybe this is the reason he cannot see the museum even with "mauricecohen's" modification file installed.

 

 

[Sentry11]

On 1/9/2020 at 6:12 PM, rinkerbuck said:

Any update? Anything else to try? Am I just out of luck here and this product does not work as advertised? 

@rinkerbuck  -  Try the attached and see if it works for you.

 

Link removed on the instructions of the developer

 

[Jon Clarke]

8 hours ago, Sentry11 said:

@rinkerbuck  -  Try the attached and see if it works for you.

KTMK Tillamook (Modified).zip 4.17 MB · 0 downloads

@rinkerbuck I believe Sentry11 was directing this mod to you but you weren't "tagged" correctly.

[rinkerbuck]

I don't believe it, that actually worked! At least one thing went well today! Thanks a lot.

[Jon Clarke]

@Sentry11 Many thanks from me for your help in resolving this issue for those that don't both TE Washington and Oregon.

[mauricecohen]

On 11/21/2019 at 10:15 PM, mauricecohen said:

I will say it again, if the developers want to add a custom object within an airport, I think that to be safe they should provide the whole airport in the package, placed above the global ones, as is the case for WA56_IsraelsFarm in the TE_WA set.

That is what @Sentry11 in effect has done by incorporating the Orbx Tillamook Museum object and textures in the X-Plane default airport.  I would not distribute it anywhere outside this forum without explicit permission from Orbx.

Edited January 17, 2020 by mauricecohen

[Jon Clarke]

Here is an official and approved Orbx fix for the missing Tillmook Air Museum when having the TE Oregon addon installed;

Unzip and place the file into Custom Scenery and in the highest priority in your scenery_packs.ini.

Orbx_A_US_Oregon_TE_Tillamook.zip

@Nick Cooper Maybe a good idea to pin this FIX as a separate post on the support forum and mark the Bug Report as Resolved?

[Nick Cooper]

Thanks, it remains a fix until incorporated into the product download, I have amended the title to reflect that

and pinned the topic as requested.