Jump to content

mauricecohen

Members
  • Posts

    122
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mauricecohen's Achievements

Senior Member

Senior Member (4/6)

36

Reputation

  1. Open the file with a text editor and delete line 5 (POINT_COUNTS 1926 0 0 1926), which is repeated in line 11, where it really belongs.
  2. 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.
  3. 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.
  4. I guess it was correct and it is only a solution for those who have the custom museum with an embedded white building.
  5. I need to reactivate the forest exclusion because now trees intrude on the custom object. Here it is again with only the object and facade exclusions removed; please try and let me know. Link removed on the instructions of the developer EDIT - Looking back at my screenshot of the museum, the intruding trees were already there, so this is not effective to remove the trees.
  6. Jon and rinkerbuck, please try the following - unzipped and above Global Airports Link removed on the instructions of the developer
  7. I believe I found the source of the randomness of the custom museum appearing or not. Take a look at this snipshot of WED with the default KTMK (with the facade removed) there is an exclusion zone (actually several stacked, each for a different category) that covers part of the museum footprint; the insertion point of the Orbx custom object must be right at the edge of the exclusion zone and since there is not an absolutely exact placement by XP of scenery elements when it loads, the exclusion can or not suppress the custom museum. It would not serve any purpose for me to remove or modify the exclusion zone in my fix, as it would still be there in Global Airports which lies between my fix and the custom Orbx. The only sure fix is for the developers to modify the insertion point of the custom museum to be far enough away from the default exclusion zone to eliminate the probability that it would be suppressed by XP's "fuzziness" in placement. The above struck-out text is wrong, I will modify the fix and re-post in a few minutes after removing the exclusion, which should work because it will SUPPRESS the default, including the exclusion.
  8. FYI, mine is the HD. There are two separate issues here: the seemingly random appearance of the Orbx custom museum; and, the embedded (or standalone if the custom object is AWOL) facade from the default airport. I think these kinds of problems will occur if Orbx relies on the XP default airports (meaning Global Airports is higher) but also places custom objects at these airports. If the default airport has an exclusion around its object/facade, the Orbx custom will be missing (this actually could explain why some people do not see the museum: their default KTMK somehow has an exclusion there), and if it does not have an exclusion, it will have an embedded default object/facade. I believe that if Orbx wishes to place a custom object at an airport, it should provide it in a “custom airport” to be placed above the global ones.
  9. What I said was If you only had the white rectangular building, this will not make the museum appear, it will just make the white building disappear, so will do nothing for you.
  10. That is exactly what I said to do You cannot attached an unzipped folder. Here are the files contained in it, you just need to reconstitute the folder structure (and i am confident you will see that it is identical to the one I zipped). +45-124.dsfapt.datearth.wed.bak.xmlearth.wed.xmlvalidation_report.txt Aha! I think my fix worked, no white rectangular building, BUT you just got the "no-custom-Tillamook-Museum" from Orbx bug.
  11. For those who have the problem of the white rectangular building embedded in the Orbx Tillamook Museum, the issue is that it is a facade in the default KTMK and that the Orbx exclusions cannot suppress it because Orbx_A_US_Oregon_TE_Custom is installed below Global Airports (as per @Jon Clarke's rearrangement of the ini file). Moving Global Airports below Orbx_A_US_Oregon_TE_Custom might solve the problem (I have not tried it) but might create new ones. I have downloaded and modified the default KTMK by deleting the facade, saving it and placing it with other airports above the Global Airports; it works: For anyone not able to use WED to do the same and would like to use the fix, here it - just unzip and place in Custom Scenery above Global Airports. Link removed on the instructions of the developer
×
×
  • Create New...