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
Thanks for the reply.
The fireflies also disapeared, or seemed to, if I kept the environment dome visibility on but I don't want to do that for a lot of scenes.
I heard that Asus 3090s worked well with Daz 4.15. Does anybody have a similar experience with them?
I can't even install 4.15 with DIM. It says it's installed, but the app never shows up in the Win 10 start menu under DAZ 3D. And when I try to uninstall, it just sits there forever at 0%.
Where can I find older versions of DS?
I tried installing DAZ Central again, against my better judgement, and it gives all kinds of Windows and AVG Anti-virus warnings. Yes I downloaded the install module directly from DAZ.
When it finally did install, I get an error dialog over a blank window. See attached image.
Apparently if DIM is online it updates the installed package list to the new product names, even if the corresponding update has not been installed. You can find out what is really installed by launching DIM and not logging in or by looking in the corresponding "Manifest Files" directory (as configured in DIM for the package); the name of the .dsx file in there should always be correct, e.g. "IM00013176-02_DAZStudio415Win64bit.dsx". The manifest directory is configured in Settings/Installation/Manifest Archive, it contains a list of everything DIM has installed for you. If you actually have an older version installed then whatever DIM says it won't be under start menu...
If you have Windows File History (or Apple Time Machine?) set on your DIM downloads directory you can find the older versions there, though for the DAZStudio packages themselves you will have to look for the corresponding deleted files because they are renamed on major.minor updates. If you don't the way to get older versions is to ask customer service. If you are having problems uninstalling the current version of DAZStudio I suspect that a different version may not help but it might be worth just installing DAZStudio 4.15 (I'm assuming you have it downloaded) without attempting an uninstall; that's actually the way I always do it. There were upgrades to the CMS database a while back. I always update that first because everything uses it and I suspect an out-of-date version could easily cause installation hangs.
I would love to download 4.15 directly, but can't find where. It always points me to Daz Central.
One can download the installer from the Product Library in the store account:
https://www.daz3d.com/downloader/customer/files
Enter 4.x in the search box, click Filter and then click on Daz Studio 4.X Pro
Just did a manual intall of DS 4.15.0.2 for Mac. Disappointed that I can't seem to leave my old DS 4.12 installation in place, and that there's no switch to turn off CMS, which I don't use and don't want. Are there workarounds for either of these? Thanks.
You can install the Public Build (Beta) and keep a different version of the General Release.
Ok, I see how to turn off the CMS with the dedicated uninstaller. Is that public beta exactly the same as the general release?
Currently yes (although the settings are separate).
thanks for your reply, I have to wait 3 or 4 min
That is normal, if it were 15-30 minutes or more, there would be some kind of problems
Were the problems with timeline fixed in 4.15?
I Haven't tried animation since 4.9, but I have been using the timeline like additional frames to my scene, meaning if I find the ready posed character somehow lacking or not quite what I want, I have hidden everything else in the scene moved one frame forward, zeroed the character pose and made the necessary changes to the character, then I have memorized the figure, deleted the keyframes and returned to the first frame.
In DS 4.12.0.86 when I returned to the first frame, the character was still in it's previous shape and pose - I just restored the shape to one I had just memorized... Shape fixed, all is well.
Now in DS 4.15.0.2, when I did the same and returned to the first frame, the pose was reset to default, like DS had no memory of the character being posed in the first frame - Other characters were still posed, but those I had not touched.
Does DS 4.15 not save and/or remember the positions and poses in the first frame?
I've done that in the past. I've changed my technique to never changing frame 0 from the hip down; I move the actor, but leave frame 0 as, effectively, the memorized pose. Then I do all my posing in frame 30 and just dForce the animation time line. I can change frame 0 to avoid collisions/explosions without having to go back and change the memorized pose.
So far as I can see nothing has changed; I tried what you described and the pose in frame 0 is not deleted (I admit I used frame 5, not frame 1, otherwise selecting the right keys is too much for my aging hands.)
You can see exactly what it has recorded by expanding the nodes on the timeline. There should be a black up-arrow for every property; this may be why character insertion takes so long for some of us as there can be a lot of pose control properties. I know of a lot of traps that cause things to go wrong:
1) Reset of an individual property or, indeed, groups of properties (by selecting "All" in the parameters tab and, e.g. reseting all bend properties). This removes every setting of those properties on the time line then sets the properties to the memorized value on just the current frame. This is pretty much a disaster; never do a reset while using the timeline! The reset has the initial effect of setting every frame on the timeline to the reset (memorized) value, but there is only one keyframe (for the current frame), so any change to another keyframe will propogate through the whole timeline.
2) Frame selection and key selection is still broken; the mouse click on the timeline is interpreted somewhat to the right of where it actually is. On dense timelines (lots of frames visible) this makes it impossible to pick the keys on frame 0 or, indeed, frame 0 because the mouse position to hit frame 0 is actually to the left of the timeline sub-window... It might be that the redraw rectangle is similarly displayed leaving "dirty" regions of the sub-window without a redraw. This would lead to keys apparently being selected when they shouldn't be and I've had the situation where I have keys displayed as selected by "key-" is not enabled. Another observed weidness is to select the keys from frame 0 to the end then left-click to deselect them, this seems to leave the keys on the last frame selected, although maybe the weird behavior of left-click when keys are selected is by design; it seems to flip the selection state of all the keys on the closest line.
3) Pose controls are "Other" [O] properties, but the things they control are Translate or (most commonly) Rotate properties or (sometimes) Alias properties. Deleting blocks of key frames can get very confusing when all of [TROA] are not set. Deleting an Alias deletes its corresponding property, however the Alias does not show, apparently, if O is turned of, even if the Alias is of a Rotate property and R is on (try "Left Shoulder Bend"/Twist which is an alias of "Left Shoulder Twist"/Twist, a Rotate property; the former doesn't show for me when I turn off O. It's pretty much essential to keep TROA on all the time, maybe even TRSOA, to be sure of what is happening.
All of these things are what has led me to being very careful about the key frames at the ends of the timeline (not always frame 0/last frame) and the whole process of deleting keys.
Thanks, I will try again with a test scene and double check that I'm not doing anything strange.
So far this new version has been a total crashfest. Normally, maybe once a week I would see DS crash to desktop, if that. Been 4 times so far today. All I have in the scene is one girl, no hair, clothes, props, scene nothing. Just getting past preparing scene in IPR nvidia took over 5 minutes. All I am trying to do it get my dome rotation right now. Only thing I am changing is dome rotation. My 2080 seems to keep dropping out
Here is the last of the log on the 5th crash of the day using nvidia IPR
No clue what that stuff means, other than something is broken. Updated to the latest driver today, so not a driver issue I don't think.
Does it crash when you try it the first time after starting DS? HDRI 010 Spring 9am Green Fields II.hdr is quite large, 264MB.
One person bald and naked + HDRI shouldn't be enough to tap out a 2080 super. DS 4.12 handled it fine, was able to finish fine tuning rotation and render there no problem.
On the Render Settings pane, with NVIDIA Iray selected as the engine, look on the Advanced tab and see if both CPU and the 2080 are selected. If yes, try deselecting CPU for both modes.
There seems to be issues with releasing VRAM. Previously with 4.12.0.86 I could do several renders one after another, leaving the ready ones open and never dropping to CPU. Now it looks like 2-3 renders are enough for the next one to drop to CPU especially if there is a previous one still open.
DS 4.15.0.2, RTX2070Super, Nvidia 456.38 and W7
If you leave the render window open it can be resumed, that hasn't changed however it was the case in the past that the resume would start from iteration 1 in a large number of cases. The number of such cases seems to have diminished, possibly to 0. It is conceivable that earlier versions of DAZStudio did not retain the Iray state if a new render was started but that is clearly not the case now. I haven't tried leaving a large number of render windows open since moving to 4.14 so I don't know if I can still do that in the way I have before.
I suggest using a monitor program to monitor the GPU on-board RAM usage. These days I almost invariably keep something called "TechPowerUp GPU-Z" running (open on the "Sensors" tab) because I find it really does help when guessing whether I can run a dForce or another render while one is already in progress (I invariably run multiple instances of DAZStudio at once.)
It's probably worth submitting a ticket for that one. It's very unlikely you will be able to reproduce it (though if you can it is certainly worth submitting a ticket) but the repaint error suggests a problem with error recovery in DAZStudio and those problems are extremely difficult to track down because they depend on having an error in the first place. (It's like the old saw about backups; no one ever checks that the backups are working until they try to use them, and at that point it's too late.)
Just my 1070 and 2080 checked for rendering and IPR, the ryzen just slows it down so I keep CPU off.
Will see if I can get it to do it again, unfortunately deleted the scene I saved after I rendered the load icons I was making. It was not much to it, I remember which girl and HDRI I used. Will try to get that done this weekend if I get a chance.
My comment was more like a direction to look for when dropping to CPU even though the GPU should be able to handle it.
I have left previous renders open, not saving them because i'm maybe trying to find a combination of textures and/or tone that best suits what I'm after. Comparing the different results between the render windows has been a good and quick way to figure out the right combination, but now it seems that is no longer an option, or not at least for more than two windows.
4.15, "Preparations toward migration to a considerably newer version of the application framework" - I really like the sound of that. Big job I know but not intractable.
I really hope this also means some bug fixes, especially for the animation tools.
Translations ~ Be prepared for Daz Studio to break more thing as they tell you its new and improved. Adding that transferring content that works currently , that something, somewhere, in the studio app break it, so you will not e able to use said content without buying some upgrade morph set, shader's, plugin's,autofit-tool, auto-rigger's,graphic card, computer etc,etc etc. Past experience has taught has that, but there is some good examples as reminders.
My Motto. "Hope for the best, but expect the worst, and back up everything just in case."
Hoping that the 4.x family's *last version* will be solid and stable enough to allow those that have invested for years in our many many 4.x scripts and plugins to be able to continue to use them effectively as we all explore the new coming framework.
Between habits, investments, and expected functions, I really hope the migration path is well-considered.
ever forward,
--ms