Jump to content

Default objects issues monument valley


Recommended Posts

Hi Martin,

probably this is the usual "issue" with XPlane priority scenery and mesh integration. Models are floats because you have other mesh, probably Ortho4XP or similar, with high priority respect Monument Valley mesh. To solve this problem it's necessary an integration and I have prepared it for Ortho4XP (only). Monument Valley have the exclusions area, if an building appear close to the Hotel View probably it is a priority issue. Only in one case you can see an unexpected building but not in this position, but at the border between degrees where is not possible manage properly the exclusion areas. To solve this issue I have prepared a specific OSM data for W2XP integration, deleting the buildings on the critical scenery area.

Link for patch integration https://1drv.ms/u/s!Av9rxLyBi20agQzLGxk8132uRbqd

Link for the video tutorial Ortho4XP https://youtu.be/raAvUDw6zJw

Link for the video tutorial W2XP https://youtu.be/yrlOp_OWefo

I remember that the videos shown Matterhorn Park integration but the important is the concept, change the degrees and some particulars.

In the manual of integration the *ini files in example are without the prefix "Orbx" because I wrote the manual before Orbx asked to rename the folders.

 

I hope that it is clear and I hope that you can solve the problem... in XPlane when mesh are custom many problems arise and developers have a simple instrument, Meshtool, to compile mesh. It is stable but very limiting.

Link to comment
Share on other sites

Hello Fabio

 

Yeah, I remember your patch of the Matterhorn Park. While i compiled the O4Xp in Switzerland myself, the DSF files of MV which are currently installed are coming from the US Orthophotos project, which probably all XP11 users do use.

https://forums.x-plane.org/index.php?/files/file/36327-us-orthophotos/

 

If you and Forkboy could align and to bring our a DSF which is already complied, this would probably help a lot of people. More convenient for the less skilled. Aerosoft adds usually a precompiled set of DSF for the few variations us get. O4XP users, HD4 users and default XP users. This way you only got to copy over the right DSF file.

 

In CH, I have done it with a blank exclusion layer, to get rid of buildings on my scenery. This is just plain exclusion rectangles, which in the end will be higher in priority than w2xp or o4xp. I do strictly follow the layer order. The example below. Which leads me to a side comment. By default ORBX MV installer installs the  Monument_Valley_Lib below the UHD Mesh  and the the ORBX MV_Mesh at the top of the scenery_pack.ini. Little detail that should be fixed too

 

Quote
  1. Airports / Regionale Szenerien (zum Beispiel New Zealand von Alpilotx), oder Flugplatzsammlungen...
  2. Global Airports, Standard X-Plane Airports welche von LR selbst publiziert werden
  3. OSM Daten (z.B. World2XPlane)
  4. Bibliotheken (Libraries), andere addons. Wobei der Ort der Libraries in der scenery_packs.ini nicht relevant ist.
  5. Fotoszenerien
  6. Mesh Daten (z.B. HD Scenery Mesh v4 von alpilotx)...

scenery_pack.ini

I

1000 version

SCENERY

 

SCENERY_PACK Custom Scenery/LOWW 1.0/

SCENERY_PACK Custom Scenery/LOAV 1.1/

SCENERY_PACK Custom Scenery/LOAN 1.1/

SCENERY_PACK Custom Scenery/Aerosoft - EBBR Brussels/

SCENERY_PACK Custom Scenery/Aerosoft - EDDF Frankfurt/

SCENERY_PACK Custom Scenery/Aerosoft - EDDK Cologne/

SCENERY_PACK Custom Scenery/Aerosoft - EDDM Munich/

SCENERY_PACK Custom Scenery/Aerosoft - EDDS Stuttgart/

SCENERY_PACK Custom Scenery/Aerosoft - EDDT Berlin Tegel/

SCENERY_PACK Custom Scenery/Aerosoft - EDLP Paderborn-Lippstadt/

SCENERY_PACK Custom Scenery/Aerosoft - EGBB Birmingham/

SCENERY_PACK Custom Scenery/Aerosoft - EGKK London-Gatwick/

SCENERY_PACK Custom Scenery/Aerosoft - EGLL Heathrow/

SCENERY_PACK Custom Scenery/Aerosoft - EGPF Glasgow/

SCENERY_PACK Custom Scenery/Aerosoft - EGSS London-Stansted/

SCENERY_PACK Custom Scenery/Aerosoft - EIDW Dublin/

SCENERY_PACK Custom Scenery/Aerosoft - LEBL Barcelona/

SCENERY_PACK Custom Scenery/Aerosoft - LEMD Madrid/

SCENERY_PACK Custom Scenery/Aerosoft - LFMN Nice Cote d Azur X/

SCENERY_PACK Custom Scenery/Aerosoft - LFPG Paris CDG/

SCENERY_PACK Custom Scenery/Aerosoft - LFPO Paris Orly/

SCENERY_PACK Custom Scenery/Aerosoft - LPFR Faro/

SCENERY_PACK Custom Scenery/Aerosoft - LSGG Genf/

SCENERY_PACK Custom Scenery/Global Airports/

SCENERY_PACK Custom Scenery/w2xp_Austria_beta6.0-hd/

...

SCENERY_PACK Custom Scenery/Osm_Europe/

SCENERY_PACK Custom Scenery/world-models/

SCENERY_PACK Custom Scenery/OpenSceneryX/

SCENERY_PACK Custom Scenery/Europe_Library/

SCENERY_PACK Custom Scenery/R2_Library/

SCENERY_PACK Custom Scenery/FF_Library/

SCENERY_PACK Custom Scenery/zPhotoXP_+45+006_16_Albertville_XP10_2012-10/

SCENERY_PACK Custom Scenery/zzz_uhd_global_scenery_V1/

SCENERY_PACK Custom Scenery/zzz_hd_global_scenery_V4/

 

 

 

 

 

Link to comment
Share on other sites

An example what Aerosoft does whith their own airports - could help you too with object conflicts. Not with elevation errors, of course

 

Quote
SCENERY_PACK Custom Scenery/Aerosoft - LFBO Toulouse Airport/
SCENERY_PACK Custom Scenery/Aerosoft - LFBO Toulouse Scenery/
SCENERY_PACK Custom Scenery/Aerosoft - LFBO Toulouse zExclusions/

 

As this will be higher than Global Airports and the W2XP Libs, the objects will be gone and your airport will be clear of conflicts

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...