Did Daz remove the ability to have 2 windows open at the same time?
darinsar
Posts: 29
So did Daz remove the ability to have 2 windows open at the same time?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Do you mean two windows to see two views at the same time in Studio?
Daz changed the way to open multiple instances of DS as just opening 2 instances directly could cause technical problems.
There are informations on the new process here: https://www.daz3d.com/forums/discussion/comment/5112696/#Comment_5112696
No. I mean to have 2 instances of DAZ Studio open at the same time.
It's changed
You now have to use a script to open a second, third, fourth etc.
"C:/Program Files/DAZ 3D/!DAZStudio4 Public Build 4.12.X.XX/DAZStudio" -instanceName # -copyAppSettings PublicBuild -copySessionUI "Public Build" "E:\Documents\Daz 3D All Libraries\Default Scene.duf"
You'll notice, I load a default scene. I've also placed Xs, which you'll need to insert the relevant numbers for.
My advice, paste it in a text file, then rename the .txt entension to .bat and you can start the script like you would an executable file.
If you download the script available in the beta thread, you can set up your own - or manually change the command I've inserted above
Damn! I really depend on opening multiple instances! Luckily my set up computer is running a solid version of 4.10, which doesn't have that problem. The rendering computer runs 4.12, which seems to render faster. The need to address that, and not with some cumbersome script.
Run the script, create as many shortcuts as you need/the system will support, use them to launch DS instances in future. It's a one-time thing unless you suddenly want an extra instance over those you created. The old methodf was an exploit, not a feature, and the new is what we are going to have going forward as it stops people running into problems as they did formerly (and they did, Daz has the support tickets to see that).
I'll give it a try Richard.
so they newest version of 4.12 has been castrated, as it were?
---
guess, I'll have to tell my computer it hasn't been following protocol and dieing all the time when multiples are open.
--
right now only three open .. one rendering a scene, one running a script to convert outfits, and other one where I'm fitting some of the transformed outfits.
--
I wish I could say that my daz crashes seem to happen when multiples are open.
But crashes when trying to delete something from the scene list happen with only one instance open.
---
but the only difference is using the script, right?
And does this apply to running older versions?
Yesterday, I was being bugged by cubes scaling from the center rather than the base so I went back to 4.9 and it worked the way I expected it to.. which let me trouble shoot to somehow the cubes were opening with object space not world space (don't have a clue how it happened) since I build in feet, I am constantly creating cubes and make them 3, 7, 10 feet high.
---
I'm not doubting that daz has tickets to prove it's a problem but I would wonder if this is to keep people who don't have the equipment to run multiple applications open from doing it.
I often have 3 daz, photoshop, 3dmax, VLC media player, 20 facebook windows, the daz installer, etc open all the time. (okay, if I get sloppy and 60 g of the ram is being used it gets a little moggy)
---
so basically we open the new instances from inside the instance we have running?
fwiw, I'm as much of a DAZ skeptic as I think frequents the forums lately (actually really disgusted), and this week is the worst ever... (ra ra dazville)
but... the issue they are addressing here is a real problem, as each of your open sessions is operating (read and write) on the same configuration files in your DAZ AppData folder, meaning that without some coordination (semaphores/locks/etc.), these sessions can and will play the 'last guy wins' game with your DAZ config files and if you have a problem with one of your windows and it stomps on your configs - it's really impossible to know what state your start-up/operating settings will be in.
The script/CLI opts simply create and manage separate config file collections for each session, so they aren't stomping on each other.
If you never have need to tweak your layouts or shortcut keys, or actions, or other DS settings, you can probably get away without issue for literally years. But... As I do/did the same thing, last month my whole layout config - with lots of customizations went poof - but I knew about the issue (before the fix/script), so I knew it was my own doing to not zip up that AppData DAZ folder when I liked it, etc.
Anyway, I am hardly impressed with much anything DAZ devs are doing (Q/A-wise - the new features are exciting if they work) in this 4.12 series, but I have to say that I *really* don't think they are smuggling in a usage constraint of some sort in this case. The complaints were probably numerous and irritating for folks that are new users and messing with their environments with multiple instances running. lord alone knows what kinds of things were going on with their config files 8^p
also - with this capability, you can set up separately named instances that have completely different task-related layouts (w different mapped runtimes/libs, etc.) and call them up when you are in that mode. E.g. you could have a figure creation instance that maps the figures with all shaping morphs and your tabs set up with GenX2, powerpose, etc. all ready for your morphing work, then use an alternate instance in another window to load, test, and animate that figure with your optimized animation layout setup. Each instance (many of 'em) could be setup to be both custom and persistent. It's a one-time pain for each one, but it is potentially safer and kind of handy if you segment your workflow. I haven't done this yet, but the design model should support and encourage this.
Question for the devs - how many versions back do those CLI options work - e.g. can I set up instance-based sessions for 4.8->4.11?, or is this whole setup a 4.12 enhancement?
best,
--ms
OK, it should be obvious but I feel I have to write it anyway ... some strange people seem to think it could be ok like that ...
This behaviour is not OK at all ! No other 3d program i've ever used behaves in this way ! It seriously [messes] up the workflow ! It has to be changed back to the way it was before ! Getting around it with weird workarounds, scripts and additional shortcuts is not a solution, wtf ?!? Please stop [messing] up the program; I really thought it was getting better otherwise !
I consider this a bug that should be fixed in the next release. Of course I won't buy anything from DAZ anymore until it is fixed (should be obvious, we should all do that) because this is a really big problem for me !
One more thing: In the older versions of DAZ studio, almost all the time, I had multiple instances open (e.g. try out and set up something in one instance then moving it over to the main scene using a scene subset). I guess most users do that. (Closing and opening the main scene all the time is a shitty solution because of loading times!). This was never a problem for me, it doesn't crash or anything. I do this in other 3d programs too, like blender, houdini and substance.
I'M CONFIDENT THAT THIS ANNOYING BUG WILL BE FIXED ASAP.
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.
I can't recall when, but the Create New Primitive dialogue was given options for configuring things like orientation, so the primitives could be created in the desired way instead of only one way and having to be transformed afterwards. It may be you are seeing the before/after of those additions - in which case review the options in the create dialogue.
1) I wanted to point out that the problems with multiple instances are not caused by the fact that there are multiple instances but the causes lie deeper. Either the program was not properly designed for that (memory management etc.) or there might be some bugs that are triggered more likely when there are multiple instances. I don't accuse anyone of anything! Every software has limitations and bugs. But maybe it would be better to improve Daz Studio over time so that it properly supports multiple instances instead of just disabling that option. Many people rely on this in their workflow. It makes us more productive.
2) A preliminary fix for this issue would be to enable multiple instances again but pop-up a warning message. This way users will know that it can trigger problems in some situations.
The problem with the previous method of launching multiple instances of Daz Studio was that all instances were using the same folders, including the temp folders. For example, if two instances tried to render at the same time, they would write over each others' files. This was a bug which has now been fixed. As a result, you can only run multiple instances if you do it in a way which ensures each instance uses separate temp and settings folders.
All you need to do is set up shortcuts which properly launch separate instances which will not interfere with each other. This is a simple one-time step. A solution which actually fixes the problem is, IMO, superior to a pop-up warning which then allows you to perform the unsafe procedure. Creating a new shortcut that works correctly seems like less trouble to me than having to respond to a pop-up every time and still getting an unstable result.
Well, every instance should automatically create its own memory and disk cache. There is a proper way to do things and there are many wrong ways. Also, I of course want the instances to load the settings from the same location. I don't want to get in a situation where multiple instances load different settings. That would be totally confusing. Every other 3d software can do this no problem. I'm sure Daz can too ;)
I guess the reason, I didn't have the problem for years is that I don't render in multiple instances at the same time. No idea why anyone would do that. I'm happy when my computer can do one render at a time at acceptable speed.
Setting up shortcuts is not a solution for me. I will wait until they remove this new limitation. Until then, I will just use 4.11 and of course I will boycott the DAZ store.
Indeed they can - and have. You can tell any non-default instance to copy settings and UI from any other instance from any release channel via switches, which the script will set up for you.
Doing a File>New in one instance would remove the temproary files (including compiled shaders and the render-in-progress) from the others.
Why do you object to shortcuts? If you explain your reasons that may suggest ways the feature set could be adapted to meet your requirements while still addressing the main concerns - assuming that it hasn't already addressed them.
I just expect that double-clicking the (one!) shortcut of the program that I have will open a new window (no matter how many are open). This is what my currently (re-) installed version of DAZ Studio does, and its just fine.
Secondly, I still didn't understand what the 'main concerns' are supposed to be. I've worked with this for years, opening Daz windows just like that, as many as I want without setting up anything extra. It worked just fine. The new version doesn't work for me anymore. I will wait until it works again :D simple.
I think, I've explained precisely enough how this is supposed to work. Check out how all other (good) programs work. If you don't want to get it, I can't make you.
One more thought: If this script is needed somehow, its code should just be integraded in the executable of Daz studio, obviously. Just do whatever it does invisibly under the hood, so to the user nothing changes.
are these CLI/instance options available on previous DS versions, and if so, how far back, please.
--ms
Ability to launch multiple instances directly was removed in version 4.12.1.16, new system was added in 4.12.1.40.
thanks for the reply - While I knew the multi-instance 'feature' removal was recent, it occurred to me that the multiple instance and context idea might have been made available earlier, even if most of us who were told about it might have ignored it at the time.
I suppose I could toss the older EXEs in an editor and see if any of those CLI options are in there.
cheers,
--ms
i'm also getting problems closing DAZ with this new version. It doesn't seem to close properly anymore and I have to end task from the task manager. Sometimes it gives an error on close.
Yea extremely annoying.
Do you have the Octane plug-in?
How do I get the new instance to have the same layout and configuration as my normal daz instance?
This is not a good solution. In the new instance none of my settings get saved at all. I have to reconfigure the new daz every time from having to put in my daz credentials on daz connect, reauthorizing plugins, having to load up my previous workspace, having to re-add all the missing directories.
This is worse than before. Whatever problem they think they solved, it created a bigger one.
I've got some bat-files that I can use for starting these instances, but that script is giving me an error (cannot find file). Is the script 4.12.1.x+ specifi? I'm using 4.12.0.86 and it doesn't load (log error is 'failed to load' and popup is error finding file' or sum-such).
fwiw, I can describe this problem, but that doesn't mean i like it or that it impresses me. No other software I use does/requires this, so here we are.
@Rodrij, there are some cli parameters that seem to indicate that you can either always draw new configs from your base instance and cleanup/forget everything when you exit, or, you can create a new dedicated instance folder(s) by using the specific CLI options. I'm guessing the way you are using it is probably a default, and probably generating a temp context and cleaning it up each time you run it.
(again, i'm not endorsing this, just describing it.)
--ms (NOT affliliated with DAZ in any way)
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...
Does the script you'd grab from the release-notes page start for you (or anyone)? I try opening DS with it (double-click on it in WinExplorer), and/or try to open it up from an open DS session (copied into my Content Lib). The error messages (popup and log) are one-liners with no detail, as mentioned above.
tnx,
--ms
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.