Author Topic: Installing Misty Moorings using addon.xml  (Read 104 times)

gavinc

  • New Member
  • *
  • Posts: 6
    • View Profile
Installing Misty Moorings using addon.xml
« on: February 10, 2019, 10:23:07 AM »
Hi
Has anyone had any issues using the addon.xml method?

I decided to start using this technique with the new updates to RTMM.

I started with CIRP 2.0 and created an RTMM folder in my Documents folder.

In there I created an addon.xml file that pointed to where I had CIRP 2.0 installed. (I should point out that at this point I had all the other RTMM files, except CIRP 1.0, installed using the traditional method).

Restarted P3D and it asked if I wanted to activate RTMM. I said yes but the program just sat and spun. I had to kill the process. I then deleted the addon.xml file and restarted P3D. It started fine and I added CIRP 2.0 using the traditional method with no issues.

Is this an issue that other people have seen?

Gavin

tomse

  • Jr. Member
  • **
  • Posts: 27
    • View Profile
Re: Installing Misty Moorings using addon.xml
« Reply #1 on: February 15, 2019, 07:39:52 AM »
Hi Gavinc
I added all my rtmm scenery (and others)  except one, with the xml method. Everything Works Fine.
But you Must set one scenery oldfashioned because you Need an Insertion Point for Ftx Central in the scenery. cfg! Ftxcentral doesnot read out the xml scenery folder, BTW PlanG neither. ( VFRFlight I don't know)
You don't have to create an xml folder by yourself. iHope you used LorbySI scenery manager, that Makes it much easier and you cán decide to Save the scenery in the scenery.cfg or xml method.
 And Vice versa
My Suggestion is to Save the Yukon scenery (Last rtmm scenery) to scenery.cfg and set this in FTX Central as Insertion Point for the Ftx Installation. Then you cán install all other scenery with the xml method.
It might Happen After new Installation or updating P3D v4, that the scenery used as Insertion Point is Kicked out. Then this scenery is no more present in Ftx Central and you have a big disorder !
Simple reinstahl the Yukon ( or whatever you choosed) and set the Insertion Point in Ftx Central again, mostly just done by Ftx Central itself .

gavinc

  • New Member
  • *
  • Posts: 6
    • View Profile
Re: Installing Misty Moorings using addon.xml
« Reply #2 on: February 15, 2019, 12:11:51 PM »
Hi Tomse

Glad to know that you can use the xml technique with RTMM.

I have other packages that I added using xml and created a "Addon Scenery" folder just to act as an insertion point for FTX, as you mentioned.

I will go back and re-try adding RTMM components via xml. I must have messed something up the first time.

Gavin

nbrich1

  • Misty Moorings Team
  • Hero Member
  • *
  • Posts: 1,020
  • MFC VA, Sim Troubleshooting & Help
    • View Profile
    • Misty Flying Club (MFC)
Re: Installing Misty Moorings using addon.xml
« Reply #3 on: February 15, 2019, 01:37:10 PM »
Need to reference the scenery folders as well as the effects and sounds - but in doing so your paths have to be perfect so just be careful.

Set up your own folders outside the sim then the xml to reference those folders. FTX insertion points are a bit trickier but it works.

At Thomas mentioned you can also use the cfg files to set up the parameters for which your sim can use. (Found in C:\ProgramData\Lockheed Martin\Prepar3D v4)
 
IE: Effects.cfg  - as default uses Your sim path Effects folder but you can create a entry and put all your RTMM Effects there : IE:


Effects.cfg
[Entry.0]
Title=Default Effects
Path=Effects
Required=True
Active=True
////////////////////////////////////////////////////////////
[Entry.1]
Title=Addon RTMM Effects
Path=D:\Addons\RTMM\Effects
Required=False
Active=True
////////////////////////////////////////////////////////////

So all of the RTMM are on D: in Folder Addons\RTMM Effects  and when the sim is started it will read not only the default Effects fold but the RTMM Effects as well or you can do it via xml

    <AddOn.Component>
        <Category>RTMM Effects</Category>
        <Path>D:\Addons\RTMM\Effects\</Path>
    </AddOn.Component>

Lots of ways to make it work but the full paths used in either the cfg files or xml files have to be dead on.
« Last Edit: February 15, 2019, 01:49:54 PM by nbrich1 »
Regards from Toronto, Canada - Misty Flying Club