Jump to content

lonewulf47

Members
  • Posts

    59
  • Joined

  • Last visited

Posts posted by lonewulf47

  1. There is no need to move the entire documents folder. Alternatively you can also create an own folder for all add-ons on any other drive. If you happen to use an installer that supports the new system, just point the install to this folder. The installers using the "new" system I have found so far are from FSDreamTeam and FlightBeam. All other "P3D V4 compatible installers" I have seen so far still use the traditional system with an entry in the scenery.cfg.

     

    Oskar

  2. The new principle of adressing/registering installed add-ons has a major flaw. The main idea was to provide the possibility to install add-ons outside the P3D root folder.

    Whenever you are using an installer of that kind your installed (Scenery) add-ons will:

     

    1) not show in the scenery.cfg

    2) be always on thop of everything else in the Scenery Library

    3) not editable/moveable (not even deselect possible)

    4) no priority layer assigned

     

    This can lead to a few unwelcome problems within the scenery administration. One example are sceneries of certain vendors (also ORBX) which have libraries installed and need all consecutive installs to be installed on a LOWER layer. With the present system - as there is no layer definition/edition for newly installed scenery - it is simply impossible to install a certain add-on at a certain layer number and thus giving it the proper priority to work with its own libraries. My guess is that this is th4e reason why ORBX still works with the "traditional" system.

     

    LM has defined a layer command within the "add-ons.XML" which is completely useless as this file is not administered by the user but only by the add-on provider. LM need definitely and desperately to come up with a possibility to define a priority layer for each scenery add-on, like it still is and was used in the scenery.cfg. I'm not giving any advice how to manually overcome this system flaw, as it cannot be the users task to tinker with the various *.cfg and *.xml files.

     

    We need a proper and working solution on this from LS's side. I definitely don't fancy suggestions of tinkering with the scenery installs.

     

    Oskar

×
×
  • Create New...