Loading...
> >

Did Daz remove the ability to have 2 windows open at the same time?

2»

Comments

  • mindsongmindsong Posts: 1,761
    Leana said:
    mindsong said:
    Fixmypcmike said:
    mindsong said:
    Richard Haseltine said:

    If you use the script you can set the j sfance to copy settings and/or UI from any other version/instance. You can also manually set the command line options, of course.

    I can't get it to open/start in 4.12.0.86 - not gonna upgrade to 4.12.1.117 in the state it's in...

    It won't work with 4.12.0.86

    otay, much thanks for verifying!

    --ms

    New method of opening instances had not been introduced yet in that version, so it's not really surprising the script doesn't work.

    That was an earlier (unanswered) question.

    I was hoping it was available a few versions back, even if I wasn't aware of the value/need at that point. Users of old versions still face this risk of corruption.

    Obviously once DAZ-devs forced the issue, the capability/requirement/resolutions became more interesting.

    --ms

     

  • nicsttnicstt Posts: 11,715
    edited May 2020
    Leana said:
    NA_1234 said:
    It has to be changed back to the way it was before !

    Don't hold your breath. There's an actual reason it was changed, and I don't see them going back to a situation which was generating problems (yes, I know, not for you. Doesn't mean it wasn't creating problems for others). Especially since you can still open multiple instances, though not directly.

    It is very simple to have it as a clickable.

    The image shows my instance opener, on a secondary monitor.

    The script it runs is actually a custom folder i created but just point it to whichever you want. You'll notice that I also have it set to open my usual default scene; if that isn't required then remove the text.

    Put the script in a text file and change the extension to .bat

    If I wanted it to open the latest 'officially' installed beta, I would change the first part of the text to: "C:\Program Files\DAZ 3D\DAZStudio4 Public Build/DAZStudio"

    instance.jpg
    1149 x 366 - 57K
    Post edited by nicstt on
  • lilweeplilweep Posts: 2,831

    how do you run the new instance script?

  • Richard HaseltineRichard Haseltine Posts: 110,349
    lilweep said:

    how do you run the new instance script?

    Drag it into the Daz Studio Viewport, or place it in a content directory (e.g, in /Scripts/Utilituies) and access it throiugh the Content Library pane.

  • Rod Wise DriggoRod Wise Driggo Posts: 2,339
    edited May 2020

    Hmm, what about Mac? Actually I never had the idea of opening two instances before but it would make sense to do something in one instance while the other one does a render.

    Well tried out the following

    1. Open Studio. Try do open again. -> Does not work.

    2. Open Studio. Open the current public beta also. -> Does work.

    3. Duplicate just the App-File and optionally rename but leave it in the same folder. Open Studio. Open Studio with the copied file -> Does work.

    So with 3. and multiple copies one should have no problem running more instances at once. Anybody using this on Mac and have experienced any problems?

    Post edited by Rod Wise Driggo on
  • fixmypcmikefixmypcmike Posts: 19,718
    edited May 2020
    Rod Wise Driggo said:

    Hmm, what about Mac? Actually I never had the idea of opening two instances before but it would make sense to do something in one instance while the other one does a render.

    Well tried out the following

    1. Open Studio. Try do open again. -> Does not work.

    2. Open Studio. Open the current public beta also. -> Does work.

    3. Duplicate just the App-File and optionally rename but leave it in the same folder. Open Studio. Open Studio with the copied file -> Does work.

    So with 3. and multiple copies one should have no problem running more instances at once. Anybody using this on Mac and have experienced any problems?

    If you duplicate just the app file they will still use the same settings, so you can still run into problems.  And I don't see how it's easier than using the multiple shortcut method (although I don't know how to do it on a Mac, but I'm sure @Totte does).

    ETA: Since its a DS script I imagine you can do it the same way on a Mac.

    Post edited by fixmypcmike on
  • Richard HaseltineRichard Haseltine Posts: 110,349
    Rod Wise Driggo said:

    Hmm, what about Mac? Actually I never had the idea of opening two instances before but it would make sense to do something in one instance while the other one does a render.

    Well tried out the following

    1. Open Studio. Try do open again. -> Does not work.

    2. Open Studio. Open the current public beta also. -> Does work.

    3. Duplicate just the App-File and optionally rename but leave it in the same folder. Open Studio. Open Studio with the copied file -> Does work.

    So with 3. and multiple copies one should have no problem running more instances at once. Anybody using this on Mac and have experienced any problems?

    That sounds like a bug to me.

  • TotteTotte Posts: 15,021
    Fixmypcmike said:
    Rod Wise Driggo said:

    Hmm, what about Mac? Actually I never had the idea of opening two instances before but it would make sense to do something in one instance while the other one does a render.

    Well tried out the following

    1. Open Studio. Try do open again. -> Does not work.

    2. Open Studio. Open the current public beta also. -> Does work.

    3. Duplicate just the App-File and optionally rename but leave it in the same folder. Open Studio. Open Studio with the copied file -> Does work.

    So with 3. and multiple copies one should have no problem running more instances at once. Anybody using this on Mac and have experienced any problems?

    If you duplicate just the app file they will still use the same settings, so you can still run into problems.  And I don't see how it's easier than using the multiple shortcut method (although I don't know how to do it on a Mac, but I'm sure @Totte does).

    ETA: Since its a DS script I imagine you can do it the same way on a Mac.

    I actually never done it running two instances - I never had the need, I have several machines. And multiple instances of the same application on os x usually causes very strange issues as the prefs are the same you get collisions with .plist file updates. Generally, two windows in a Mac application are two windows, not app instances, while on windows, two windows are usually two app instances. 

    Two very different paradigms 

     

  • stgastga Posts: 27

    I'm seeing the same thing, on Windows.

    I used to be able to have 3-4 instances of DAZ Studio running, while allowed me to continue to work while rendering.

    Now any attempt to open a second instance just brings the first instance to the foreground.

    I'm going to open this as a bug, as from my PoV, this is a functional regression.

  • Richard HaseltineRichard Haseltine Posts: 110,349
    stga said:

    I'm seeing the same thing, on Windows.

    I used to be able to have 3-4 instances of DAZ Studio running, while allowed me to continue to work while rendering.

    Now any attempt to open a second instance just brings the first instance to the foreground.

    I'm going to open this as a bug, as from my PoV, this is a functional regression.

    As discussed above it is not a bug, it is new behavior which can be manged either using the script from the release notes to launch a new instance of DS or, if you can't run the script now and haven't used it to set up a shortcut previously, by creating a custom shortcut with the needed command line parameter (at least a name for the instance)

  • Richard HaseltineRichard Haseltine Posts: 110,349
    Rod Wise Driggo said:

    Hmm, what about Mac? Actually I never had the idea of opening two instances before but it would make sense to do something in one instance while the other one does a render.

    Well tried out the following

    1. Open Studio. Try do open again. -> Does not work.

    2. Open Studio. Open the current public beta also. -> Does work.

    3. Duplicate just the App-File and optionally rename but leave it in the same folder. Open Studio. Open Studio with the copied file -> Does work.

    So with 3. and multiple copies one should have no problem running more instances at once. Anybody using this on Mac and have experienced any problems?

    I am told:

    The macOS paradigm is different. It's default behavior is not to open a second instance of a running application - one must use the command line to override the default behavior and launch a second instance. Of the application instance CLI options implemented in Daz Studio, the only one that doesn't currently work on macOS (and is accounted for in the script) is the automatic gap-filling name enumeration (#).

  • Rod Wise DriggoRod Wise Driggo Posts: 2,339

    @Richard:

    Any help on how exactly the command line needs to be used to override the default?

  • Richard HaseltineRichard Haseltine Posts: 110,349
    Rod Wise Driggo said:

    @Richard:

    Any help on how exactly the command line needs to be used to override the default?

    You mean in general, to actually launch an instance via the terminal in Mac OS? No, sorry. The DS-specific stuff is here https://www.daz3d.com/forums/discussion/comment/5112696/#Comment_5112696

Sign In or Register to comment.