SODE Installation Path

Home › Forums › Support › SODE Installation Path

Topic Resolution: Resolved
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 22. April 2020 at 13:47 #4248
    Hanky.Panky
    Participant

    Am I right, that the default installation path for SODE is also hardcoded within the program and – at the moment – cannot be changed by the user?

    When trying to move the SODE installatin to a different drive all SODE objects in all sceneries disappear, but no red X.

    After editing the addon.xml SODE is still shown under Tools and DLL connection active. All appearances of SODE in the registry have been changed to the new path. Also add-on.cfg is changed

    What else needs to be modified? And is it possible to add a choice for installation path during setup with one of the next releases?

     

    Thanks a lot in advance – Dieter

    24. April 2020 at 14:46 #4252
    12bPilot
    Keymaster

    Hello Dieter,

    Depends on which installation path you refer to. The executables are installed to the path specified during the install process (default Program Files (x86)).

    I think you mean the path for the SODE related data like xmls, SimObjects, ini files in C:\ProgramData\12bPilot\SODE? Yes, that is hard-coded and cannot be changed. I needed a common, shared place where all the devs can install their data into, and this location is easily accessible to their installers.

    As you might have done already, the SimObjects can be moved manually when you change the add-on.xml path to this new location. But the sdx/xml files need to be in the ProgramData location, that one is hardcoded.

    Changing this location would break dozens of add-on installers.

    24. April 2020 at 15:12 #4255
    Hanky.Panky
    Participant

    Ok, I see and understand. Changing the location of the SimObjects would do the job, as this is the folder with GB of data, which I like to remove from my backup jobs.

    Thanks a lot, keep up your great job and stay healthy!

    24. April 2020 at 16:11 #4257
    12bPilot
    Keymaster

    Thanks, you as well.

    24. April 2020 at 17:12 #4261
    12bPilot
    Keymaster

    Follow up: You can also create an own addon.xml just defining an external path to a folder that hold SimObjects.

    Then you move all the SODE SimObjects to your folder.

    I am doing this myself on my machine for the same reason…limited space on C:

    18. August 2020 at 10:57 #4896
    arslanturegun
    Participant

    Hi 🙂
    Can you post an example addon.xml ?
    I too have very limited space on my windows installation disk .
    Cheers,

    Arslan Turegun

    18. August 2020 at 20:42 #4899
    12bPilot
    Keymaster
    arslanturegun wrote:

    Hi ? Can you post an example addon.xml ? I too have very limited space on my windows installation disk . Cheers, Arslan Turegun

    Hi, sure!

    This is what my add-on.xml looks like:

    <?xml version=”1.0″ encoding=”utf-8″?>

    <SimBase.Document Type=”AddOnXml” version=”4,0″ id=”add-on”>

    <AddOn.Name>My Additional SODE SimObject Folder</AddOn.Name>

    <AddOn.Description>Additional Folder for SODE SimObjects</AddOn.Description>

    <AddOn.Component>

    <Category>SimObjects</Category>

    <Path>D:\FSAddons\SODE_Additional\SimObjects</Path>

    </AddOn.Component>

    </SimBase.Document>

    Note that you can name the AddOn.Name and AddOn.Description as you like. Put the add-on.xml file in to the C:\Users\<YourUserName>\Documents\Prepar3D v4 Add-ons folder and P3D should detect it automatically. P3D then knows about this new SimObject path and it (and SODE) will be able to find the SimObject containers in there.

    19. August 2020 at 11:46 #4900
    arslanturegun
    Participant

    Thank you so much 🙂

    Cheers,

    Arslan

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.