Loading...
> >

New Runtime(s)

Geoffrey_WoodgetGeoffrey_Woodget Posts: 98
in New Users

I'm completely starting over.

So I'll have Gen1, 2, 3 and Poser.

Is there a reason(s) I just don't want to make 1 oganized (organised for Dson portion & Poser) Runtime with everything in it?

Thank you

Comments

  • LeanaLeana Posts: 12,826

    The main reason I see to use multiple Runtimes is to separate the content you have into smaller libraries, so you can choose to load only some of them if you don't need the others.
    That can be pretty useful when you have tons of content ;)

    It can also be useful to separate non-commercial freebies from the rest of your content if you make commercial work.

     

  • dracorndracorn Posts: 2,363
    Leana said:

    The main reason I see to use multiple Runtimes is to separate the content you have into smaller libraries, so you can choose to load only some of them if you don't need the others.
    That can be pretty useful when you have tons of content ;)

    It can also be useful to separate non-commercial freebies from the rest of your content if you make commercial work.

     

    I'd like to know how you separate out your runtime, especially if you use DIM. Do you have to uninstall and then reinstall? I have extensive categories and want to preserve them.
  • LeanaLeana Posts: 12,826

    If content is already installed then yes, I would uninstall and reinstall.

  • SixDsSixDs Posts: 2,384

    Unless something has changed more recently, the advice that has always been given by the DAZ folks is not to create too many content libraries. Although the CMS database can handle more than one, I suspect that the problem lies in the resource overhead involved in having the database keep track of multiple repositories, but I am simply guessing at that.

  • Geoffrey_WoodgetGeoffrey_Woodget Posts: 98
    edited December 2016
    SixDs said:

    Unless something has changed more recently, the advice that has always been given by the DAZ folks is not to create too many content libraries. Although the CMS database can handle more than one, I suspect that the problem lies in the resource overhead involved in having the database keep track of multiple repositories, but I am simply guessing at that.

    Support recommended using only one to me.

    You people were my 2nd opinion(s). :) 

    Post edited by Geoffrey_Woodget on
Sign In or Register to comment.