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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
..never remember having to do that before.
In the 4.12 beta Update and Merge Menus is under the Window/Workspace menu but in 4.15 the only selection under Workspace is "Select Layout". None of the other options are there.
Wow, it sounds like your installation is really messed up. I'm still running 4.15.0.30 Public Beta. I see the menus in the attached screenshot.
I haven't updated to the latest Daz Studio, because there have been no updates to the Highlights thread to explain what has changed. What bugs were fixed? What features were added? What was changed? I find the highlights thread much more accessible than the change log. Most of the change log looks like low level internal software or script stuff that I don't comprehend. I want to know from a Daz Studio user perspective, what I will see and how I will benefit from the new version. I'll wait. No rush. Let it settle. Wait for the hot fixes.What I have works.
...yeah, I see that in the 4.12 0.47 beta, just not int the 4.15.0.30 General Release. Not going to install the 4.15 beta as it would replace the 4.12 one I am currently using as it's been rock steady ever since I installed it.
I can't understand why this happened a second time. Using the IM, I uninstalled, then deleted the .zip package from the Ready To Install tab, after which I closed the IM, reopened it, downloaded a fresh copy of the .zip, and reinstalled it. Unless the 4.15 General .zip file itself somehow became corrupted before the download, I would think a new fresh copy would have worked the way it should.
Did you try selecting a different Workspace and/or Style?
...no because I was afraid somnething else would get messed up I use the Darkside as it is the easiest on the eyes and doesn't distract form the viewport. After I first opened it last night, I closed the Content Library and Surfaces panes on the left display to access a few other folders, I then closed the programme down to open 4.12 to make sure it wasn't messed up, and afterwards when I restarted the 4.15 they were gone for good with no way to them back because the here was no way to access the Pane's selection (old hardware here and didn't want to have two instances of Daz open while I was on Chrome with the forums and Google up for troubleshooting purposes)
I have the manual download installer but holding back on that as a last resort as it will install a full clean default copy and I'd have to go through to set up all my custom settings all over again.
I think you should select a different workspace and see if that works. Maybe your previous workspace file got corrupted, or is so old it is incompatible with the latest Daz version.
...on the 4.12 beta it's fine. As this was the General Release, it replaced the 4.10 General Release I previously had which I have been concurrently running with the 4.12 beta. As I mentioned there should have been a prompt asking if I wanted it to uninstall 4.10 but that never appeared, it just went right into the installation routine and finished. There were couple times i looked like a message box flashed on he screen but it was for only a fraction of a second so I couldn't read what was going on.
I uninstalled 4.15 for now.
Maybe you are on to something about 4.10 being too old as a several major changes occurred between it and 4.12 (which included support for RTX GPUs). Yeah I could just go the manual install route but don't look forward to rebuilding my custom UI setup from scratch again. along with the directory paths in the Content Directory Manager (a real pain with a custom library/runtime setup).
The really silly aspect of this is that I was intending simply to check 4.15 out and see of it was as bad as people say given all the complaints I've read. I was wondring if possibly some of these instabilities and other issues may not be due to certain W10 updates as I'm still on W7 Pro.
ETA
Ok reinstalled and gritted my teeth when I selected Layout and then City Limits Lite. which opened the rest of the menus. Again never had to go through this before. It also cluttered the window with a number of tabs and panes some I never saw before and others I just never bothered to use. Ended up having to reconfigure the entire workspace all over again.
After about 45 min I finally got it looking like the 4.12 UI with the addition of the Simulation Settings and Render Library tabs on the same pane with the Scene and Render Settings tabs. Still can't find the Render Tone Mapping and Environment options.
That DS will create as soon as you do an Iray Preview or render, or you can create them yourself.
....just noticed that during a test render I'm running. Both also show up in the Scene tab as properties of the file.
I do like the new way the render progress window works as it actually presents the file stats more clearly at the beginning. Also rendering seems to be a somewhat faster. On the scene I'm testing it's reached 88% convergence at about 89 samples in about 40 min. Rendering the same scene in 4.10 with the exact same settings, it took about two hours and 40 min at 25,000 samples to reach that point.
@ Kioto Kid
To avoid the interface to be messed up again doing installations or uninstallations, just do this:
Arrange your interface as you prefere and then go to Users\YOURNAME\AppData\Roaming\DAZ 3D\Studio4 (where DAZ Studio stores its stuff) and Right-click the Layout.dsx file and select "Read Only" option. From that moment even the worst crash or the worst installation process will not affect your interface.
When you decide to change it, just go again to the file and unlock the writing, do the changes and lock it again.
I suggest to do the same with customactions.dsx, where your custom actions and scripts shortcuts are stored, so you don't have to redo that too.
Or backup the whole set of files. This is a quote from Richard Haseltine"
As I don't have a C drive, being on a Macintosh, will this script work on a Macintosh version of DS also?
Probably not as written. It is a sample script and has the C drive temp folder coded into the script. Is is a sample, which you can modify to do what you want it to do. I don't know how hard it would be to accommodate Macintosh.
OK. Thanks.
The relevant line is 248, setting var sTargetPath - I tried to paste it but Cloudflare thought I was trying to hack the site.
OK. Thanks for trying, Richard.
Yes, me too, YOU ARE BLOCKED in gigantic font size, and everything I typed was thrown away.
Thank you both, barbult and Richard, for your efforts.
...thank you.for that information. Done.
Glad to be helpful!
DazStudio Pro 4.15.0.30 on my new iMac 2020 27" 3.8GHz 8 core works well for images and image sequences but gives an error when I try to make a .mov movie.
I approved all the access prompts during installation via DIM. The error is shown for a 2 frame basic movie.
I gave DazStudio permission to access the drives and files.
How can this be fixed?
Hi, I tried this on my M1Mini running latest build running 4.15.0.30 and I can replicate it. I'll write a bug on it.
Thank you for your help.
I haven't been able to generate .mov files to Catalina or Big Sur regardless of the D|S vesion, while even the latest version of D|S generates them fine under Mojave. I believe the QT library D|S is using is most likely trying to generate a 32-bit codec to the 64-bit OS that for whatever reason just won't go (similar to trying to open an AVI file that's more than 2 GB in size under many Windows programs -- I had to go a few version back in Premiere, for example, just to open it under /Windows).
I would love for D|S to support a more modern MPG, or something similar, rather than having to gererate movies as frames and stitching them together and synching with sound (useful for other things, I don't want to lose that either).
-- Walt Sterdan
That is not as simple as it sounds, as you may know. The libraries need to be rebuilt from the ground up, but do put a feature request in.
I honestly don’t know what I know anymore. I’m told that D|S cannot run under Big Sur until QT is updated and the libraries are mostly rewritten from the ground up. I ask if it’s possible to add Filament to the Mac version, and I’m told that it can’t be added for the same reason that it won’t run under Big Sur and needs to wait for D|S 5.
Then — plot twist — with help from Apple D|S can run under Big Sur. I ask if Filament might now work and I’m pretty much laughed at and told that Filament “isn’t suddenly going to start working” even though, to the untrained eye, D|S did, even though I was told that Filament needs the same update that D|S needs to run under Big Sur.
As the libraries are already being rewritten for D|S 5, I’ll put in a suggestion to add an output format for animation that supports video and audio but seriously, you would think that would already be on the drawing board for a software that does animation.
— Walt Sterdan
...well ran into the first issue. Was doing a dForce Sim when both screens screen went black and then a windows dialogue box appeared up that said the display driver stopped working but was reset. Everything came back except for the Daz UO which was nothing but three white squares (one for the viewport window and another for the two tab panes I had on the other display
After that another Dialogue popped up which read:
It was like that for about ten minutes and Task Manager listed the Daz programme as "Not Responding" in its Applications Tab. Odd, as jsut a few days ago I was able to perform several hair sims (which take more horsepower) and this didn't occur at all. After a few more moments windows closed the programme losing all the changes I made.even though I made an intermittent save after applying a hair shader and adjusting the colour.
Also getting white "flickers" and momentary "whiteouts" of the main viewport window when loading a scene (even a simple one) which shouldn't be happening with 12 GB of VRAM.
Was running the sim on Nirvy's Kid's Daily Leisure outfit when it occurred about midway through.
I've been having an issue recently where Daz will crash to desktop within 30 seconds of hitting the render button. It's not a terribly complex scene, infact I have already done a dozen other renders using this set u p with no change other than the pose, What used to work fine, now just goes POOF! I have been now trying to get a render to START for 2 days now with the same results every time.
Has anyone else had this issue since the last update? and if so, has anyone found a work-around?
...is this the 4.15 General release?