- This topic has 54 replies, 25 voices, and was last updated 4 years, 2 months ago by
.
-
Posts
-
Has anyone installed the Daz Studio 4.16 update?, is it only available through the Daz Central install file? Anyone has experience with it?
/Felicia.
DAZStudio_4.16.0.3_Win32.exe
Link(s):
https://workupload.com/file/x8sk5p3Fvq5
DAZStudio_4.16.0.3_Win64.exe
Link(s):
https://workupload.com/file/cyRk8wGB8Xe
key.txt
Link(s):
https://workupload.com/file/AcfPEwf3W45
PS,
Works very wellIs it worth a download ? It does not seem they have improved anything (just added useless morph mixers).
Updates often clear bugs/program errors out of the way. That is the main reason why I update. And as griyar claims, DS works very well hereafter, with this update.
/Felicia.
Well, I found the previous beta had introduced a few nasty bugs.
The current one 4.16.1.2 seems to have fixed them again.
I really don't see the point of the morph mixer though.
@ethiopia
I don't know about what conversation here, but I just know that this new update fixed many bugs in studio, at least, for me ( stopped freezing, runs faster, stopped falling in middle of process, and many other bugs......)One thing I've noticed with the latest beta is that when the rendering status window pops up it no longer lists which device(s) it's rendering on. Previous versions stated if the GPU was in use or not but the current one doesn't. It was handy feature when starting to renders to see if DS had forgotten you had a GPU installed and had fallen back to CPU rendering without having to either monitor how quickly it was updating the iterations or keeping and eye on GPU load with an external application.
@ethiopia Instead of ACDSee try Xnview - it's free, and a fab. image browser.
I can say with certainty that 4.16 did fix the memory leakage issue I had, and a quick run with a few recent scenes I'd previously done also shows that it renders just a little faster (not by a lot - maybe 5-10% at most?)
I'll have to check and see if it shuts off decently (forgot to check that), but otherwise it is an improvement over what I had before.
No idea what the morph mixer thing is. IMHO I think it's just a lazy man's way of dial-spinning. I believe I can get the same results if I just fiddle with morph dials, TBH.
PS: Instead of ACDSee, I stick with the tried-and-true Irfanview. It stayed light and fast for the 15 years+ that I've been using it, and it still comes in at only 5 MB (plugins are another 22MB, and worth installing as well): https://www.irfanview.com/
I use the 4.12.1.40 all the time and I tried all the update till the most recent one. Also all the beta´s I have try And I can say, that all this updates where just shit for me. Okay long story short.... Never change a runnin system...
Thanks @griyar for the DAZStudio 4.16.0.3.
This update is working smooth and fast.The current one, the 4.16.1.2 is even the worst update ever. Big problems with Ghost Light where the opacity is not working anymore, Shader Mixer problems, PBRSkin problems (Switching SSS mode to mono remove the transparency). And so on. you can find this all in the "Daz Studio Pro BETA - version 4.16.1.2! (*UPDATED*)" forum thread.
If you are rendering just a character, with a simple background and a simple light setup, all "out of the can" Then you do not "see" those problems. But if you are working in DaZ, working on a skin or working with illuminated planes for beautiful light setups, Then the 4.16.1.2 is totally useless.
The version from griyar, the 4.16.0.3 is the last version what is working correct and this one saved my life after using the old version 4.12.1.40 long time....
acdsee pro 2 is cool
Thank you all for this precious information. The crucial point (for me and most others by the way) is Studio's mortal lag (and poor memory handling) in morph loading (with similar constraints when posing). What is the situation in 4.16.0.3 (when you have dozens/hundreds of G8s...)?
Not sure about a scene with literal dozens of G8 figures, but they do load a little faster than previous (likely because of faster timeouts? No idea offhand.)
I forgot to answer one of the questions: I just grabbed 4.16.0.3 right off of DAZ' site. They still distribute it in .zip format, without the need for an install manager. 32 or 64 bit, and for MacOS or Windows (who still uses 32-bit?) You go to your product library and get it from there.
As for any further patching, I have no need to update/patch it for anything. I tend to keep my lighting a bit simpler than most, letting emissives and HDRI do the work, mostly to keep the render times down to something sane.
I have two GPUs (2080 TI) connected with vLink so that I should get 20+ GB VRAM. For a while I have suspected that that isn´t the case. Some more complex scenes where apparently to big to render without heavy reduction. As I am far from an expert on the more technical aspects of this hobby I didn't know how to proceed.
Anyway, today I figured I could check the temperature on both GPUs, if one was much cooler then it would mean it wasn't working. Lo and behold, one of them was really cool = not working...
After dismissing both bank robbery and suicide I figured I could try to update DAZ3D from 4.15 to 4.16 and make sure I had the latest drivers. Voila! It worked! Now big, complex scenes works like a charm again.
I'm not sure, but I suspect that when I upgraded the drivers without upgrading DAZ some time ago, one of the GPUs stopped working. But that is just a wild theory..
- You must be logged in to reply to this topic.
