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
Mine generally even a bit less than that.
Reporting back on my issues. After replacing a few hardware pieces, most of my problems have gone away.
I wasn't having obvious issues with any of the things I replaced.Studio was the only program that was acting up.
I replaced my SSD, mouse, and keyboard because of good sale prices recently.
The mouse was ~8 years old wireless track ball.
The keyboard was a MS comfort curve 2000v1.0. Yep bought it when it first released, and had been using it since XP pro days.
The SSD was only a year old, but the new one was 500GB and cost half as much as the 110 GB cost.
The copy of windows I was running had actually been patched up from Vista Ultimate through the years to 10 pro today. I had moved it from a mechanical drive to an SSD drive with DD from gentoo a year or so ago without any issues. And this is the step I skipped this time. I installed Windows 10 fresh on the blank SSD drive this time. Along with all new driver and software installs. Currently I only have the beta installed as I wasn't using the release version anyway I didn't bother to put it back on.
Not sure which step fixed the Studio stalling and crashing. But it was obviously one of them because so far, I've not been able to recreate the problems.
I still get the occasional dforce explosion,but it's not stalled or crashed Studio yet.
You went from a 'patched' Windows (vista to Windows 7 to 8 to 10) to a fresh install of 10. There was likely junk code in there, muddying the waters for Daz. A clean install put only necessary code in. That's what fixed your hangs.
I have read 100's of pages of gripes/praises and pros/cons for various verions of Daz and based on those reads made some choices I believed to be best for a system like mine. I understand that RAM and CPU components can make choices more narrow or broad and may or may not have affected some viewpoints of versions. I have two issues, using Face Transfer and having two Pro versions installed, and It's been a while since I griped about Daz Studio and I really don't want to go down that road again so I am asking for advice in advance of making changes.
Recently, while trying to fix Iris & pupil issues I created a post searching for help on Iris issues. Frustrated, I decided to try face transfer and that;s when I noticed that on my 2080 rig, Pro 4.12 version was not a beta, it was a 32bit Pro version. Somehow, on my 2080 rig I accidently installed a 4.12.0.86 Pro 32bit beta and a 4.11.0.383 Pro 64bit
.
On the rig with 1080 cards I have 410.0.123 Pro 64bit and 4.11.0.366 Beta 64bit. None of these seem to work with Face Transfer Unlimited. My rig details are in my sig.
Question 1. Does anyone know which versions are actually best suited for the 2080 cards and which is better for the 1080 rig? I do have a few restore points which may or may not come in handy.
Question 2. Does Face Transfer work on 4.12 beta versions (it doesn't seem to on 4.12 32bit or 4.11 4.10 versions). I do not seem to have a beta version on the 2080 rig.
Question 3 . The 2080 stays offline. Anyone know best way to install all components for curren Beta manually?
Thanks in advance.
Juanita
1) Kepler and Maxwell cards are currently supported but will probably be dropped soon; the 1080's are Pascal cards so they will still be supported in the latest DS (4.12.1.118)
2) Face Transfer requires 4.12.0.86 or higher and 64-bit Windows, which doesn't seem to be among any of the versions you have installed.
3) Install DIM on both systems. (Set any paths you want to be non-default.) Download the beta on the online system, copy it to the downloads folder on the offline system. Run DIM in offline mode on the offline system.
Thanks. You are one of my few go to's to look up posts prior to posting, so thanks for answering. I recently had to do some restores which accounts for the odd versions. Being the chicken I am, I'm going to create a restore point and download the 4.12 as a beta on the Nvidia 2080ti RTX pc but I need to do it manually. I read somewhere that the 4.12 didn't play well with the Nvidia 1080ti's so I'll probably not change that PC until it get a chance to scrutinize Jay's benchmark thread. I'm one of those users who don't allow windows 10 to update at whim. The DIM is working great on one the machine with the 1080's but on the higher end PC it refuses to update but will install data manually moved to my downloads drive on that rig. I at one point deleted everything and tried again and with the amount of items I have to install it gets horrendous. Since then I refuse to put that machine online. I am going to try to maually install the 4.12 beta, has anyone been successful at that? Also if I download to this folder on my online PC (1080's) will it overwrite the current beta installed if I have install after download unchecked? I'm thinking I could port the files to the other pc.
I have no issues with 4.12 and the 1080Ti. My Windows updates are done manually.
Appreciate that. That's good news, for me it probably means a driver update on the 1080. Just two questions.
1. Are you referring to the new beta or the pro version?
2. Are there any plugins that are being dropped in Pro 4.12 vs Pro 4.11 vs Pro 4.10? I've been trying to determine that but maybe you could share that info.
3. What drivers per machine would you recommend as stable. I heard the 430.86 was good. Is this correct?
Perfect. Thank you.
If you want to save a particular version make sure you move the zip for it (and the zips for any plugins) out of the DIM downloads folder and save them somewhere. DIM will replace the public beta or the general release with the new one (the beta won't replace the general release, and vice versa). a 64-bit version won't replace a 32-bit version.
I downloaded the Nvidia 451.77 driver before upgrading and the perfomace of alll installed versions on both PC improved. Pre the driver update, I had to exit a benchtest render (on the 4.11. 0366 beta) because after 7.5 minutes it only reached 2% but after the driver update, the same scene rendered well under 5 minutes despite an old windows version a (511 v.1511 build 10586.466) but the driver @DoctorJellybean recommend works like a charm. After installing the newest beta version, in advanced tab it initially showed 3 devicesand all plugins had green plugs. I closed it and reopened it to perform a test render only to find CPU as my only photoreal & interactive device available. It dropped the two Cuda's so I took a screenshot and closed it. Retried but same issue. Walked away for a tad, tried again and now it's showing all 3 devices again and I'm afraid to close it dowmn. LOL. Anyone have this issue? Also is the Optix Prime an option in the beta. I couldn't find it.
Edit Does the software detect the RTX and not populate Optix Prime acceleration because it should be off? And what does CPU Load at 36 mean?
Also decided to try Peer 2 for NVlink and it rendered without a hiccup. I am so glad I installed this newest beta!
My Tech Named my PC not me. I tried changing it, press buttons, but nothing works
When installing updated drivers, do a custum installation and check the clean install option. There is a discussion about Optix Prime here.
After you recommended driver 451.77, and I was on driver version 3XX, the mouse started shaking & I was about to duck & tuck, thinking California was having the big one, when I realized it was not an earthquake, it was me shaking. I have forced windows to never update years ago and shut down all updates including drivers. After a ton googling, didn't trust you, ha ha ha, (because I read every freaking page of several Daz beta releases threads and other discussions, including this 58 page thread) I found one post that made me feel comfy. It said let Nvidia decide. And I thought, why not? Obviously I can't. After much sweating,, I managed to create a Nvidia account, and let it control my machine. My only decision was Gaming ... or Studio? Okay that's a lie. They actuallly defaulted to Gaming (tried to dupe me, but I knew I had no games on the PC) so I twisted their arm with a lug wrench, and after one "Uncle", the switch to Studio was successful and they commenced with the 'Nvidia Experience', which was me wondering, what the hell is being installed, and them not cluing me in. Then came the black screen of death and momentarily, I wondered what would happen if I hit the power off button, but I was too paralyzed with fear to do anything, But after the darkness came light and my screen wallpaper manifested itself before my awing eyes. I gave my monitor a giant hug, then right clicked it, and choose Nvidia control panel. In the bottom left, I clicked the system information link and there I found the secret meaning of the 'Nvidia Experience'. They had magically empowered my crippled system with the version you suggested and apparently any cleaning needed was done by the Nvidia brownies (my guess is it was Ollie).
Iray 2020.1.0 is final. Everything sounds good. Looking forward to seeing it in Daz Studio.
Interesting, but does this mean there'll be yet another raising of the minimum NVidia driver version? It's already a lot closer to "today's latest and greatest" than it used to be when I started using Iray.
Just wanted to leave a note that DAZ Studio 4.12 Pro, 4.12 BETA, and DIM all crash on launch due to a missing dylib and dylib cache on the just released macOS BETA of Big Sur. Let me know if you need a tester for that platform. DAZ Central appears to be unaffected, but I don't use it. DAZ Central works but crashes after entering password to install anything.
In case it helps:
Process: DAZ3DIM [69409]
Path: /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM
Identifier: com.DAZ.DAZ3DIM
Version: 1.0 (1.4.0.58)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: DAZ3DIM [69409]
User ID: 501
Date/Time: 2020-08-18 20:10:34.426 -0500
OS Version: Mac OS X 10.16 (20A5343j)
Report Version: 12
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
dyld: No shared cache present
Library not loaded: /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
Referenced from: /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM
Reason: image not found
Binary Images:
0x100000000 - 0x10060efff +com.DAZ.DAZ3DIM (1.0 - 1.4.0.58) <3050F87B-9F65-2D41-B729-EB4E43EAC0ED> /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/MacOS/DAZ3DIM
0x1009ee000 - 0x100b58fff +libdzcmsconnector.dylib (1) <ADE57172-9DAD-20D7-55FF-0A42B7E226FC> /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/Frameworks/libdzcmsconnector.dylib
0x100cca000 - 0x100f7afff +QtCore (4.8.7) <4CA3C606-A089-F187-979B-7B48C41EC059> /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/Frameworks/QtCore.framework/Versions/4/QtCore
0x10100e000 - 0x1019d8fff +QtGui (4.8.7) <83428699-BE40-1D52-E6DE-D119AFD0A1B1> /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui
0x101c51000 - 0x101d7dfff +QtNetwork (4.8.7) <F29D5129-3E68-4C08-CA75-73C7E6CEA40D> /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/Frameworks/QtNetwork.framework/Versions/4/QtNetwork
0x101ddb000 - 0x101e20fff +QtXml (4.8.7) <CC4B6377-A95B-8DC7-A3E0-1A482D1531CD> /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/Frameworks/QtXml.framework/Versions/4/QtXml
0x101e38000 - 0x10200bfff +QtScript (4.8.7) <81DA01E2-08A0-7463-58A6-E4DBC275DAC0> /Applications/DAZ 3D/*/DAZ3DIM.app/Contents/Frameworks/QtScript.framework/Versions/4/QtScript
0x7fff663f2000 - 0x7fff66489fff dyld (828) <0F674766-D96E-3668-8705-324A53FA816A> /usr/lib/dyld
Library not loaded: /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
That sounds weird as that framework is what all cocoa apps use. Can be something with framework versioning maybe.
FBX export is not honouring visiblity or unticking props
From the DS change log:
Currently in Private Build Channel.
Adds support for Ampere GPUs, drops Kepler GPUs.
Cool stuff. Optix 7.1 should help with performance and denoising memory load.
RIP Kepler, though. Daz needs to highlight that.
I talked with some other developers and it's been determined, thanks to some Python gurus, that the frameworks are no longer aliased to the System/Library/Frameworks directory and must instead be called with absolute (static) pathing. That appears to be the problem with the DAZ apps. I don't know if it's the QT compiler that needs to be fixed or if you guys use some other compilation method where you specify frameworks, but this is the solve for it, at least for now. I doubt Apple is going to change it since it's been a problem for 3 beta versions now.
Hi all, any news on DAZ bug fix for daz NOT saving any morph animations? :) This has be very frustrating bug that is hindering my work tremendously..
If anyone has an older version of DAZ 4.12.0.8xx that can post for people to download and install untill this bug is fixed, that would be wonderful. That version used to save morph animations fine..
help... :)
The only way to obtain an older version is to request one from Customer Services:
https://helpdaz.zendesk.com/hc/en-us/requests/new
I requested 4.12.0.86 back because I suspect my backup got corrupted and the daz support replied they don't have old versions available. So there is no way to get it back. For the record it's request #341234. I'm now working with my 4.11 backup that seems fine, until they fix the 4.12 animation issues. Then personally I do find it unbelievable that daz doesn't care about the 4.12 animation issues it's a very long time now. Either fix it or provide an older version that works.
Then if anyone can provide a SHA 256 of the 4.12.0.86 installer I can verify my backup. Since daz doesn't provide any checksum either. My issue with 4.12.0.86 is that it only installs if 4.11 was installed first and I don't know if it's corrupted of if it's a daz bug. SInce 4.12.0.86 comes with a 4.11 system name I suspect it's a daz bug. My SHA 256: 841BDAB7001631D81389EB1517962E0124C158C5E4789AE51DFD9E7ACE98BF2F
Yeah, agreed. I don't think I've ever seen anything quite like this with any of the DCC software I've ever owned. Even iClone, which is known for being very buggy / unstable, gets critical bug fixes (and communication on upcoming fixes) on a fairly regular basis. Meanwhile, we Daz animators have been dealing with a major bug -- one that causes unrecoverable data loss -- for several months with zero communication from Daz, not even a simple, "We're working on it." It's extremely frustrating for those of us who have sunk thousands of dollars into the Daz ecosystem.
So, as of now if I can't even get the DAZ 4.12.0.86 older version, I'm stuck not being to use DAZ for morph animations? I know DAZ is not an animation program, but this makes it almosty impossible for me to do facial animations with it.. I can save shaping presets per character but that's a pretty inconvenient way to work. Funny thing is the default daz facial morphs DO save without problem.. and if you look inside parameters tab for the default daz morphs, it's named as Modifier/Pose under Posing tab... So I tried changing my morphs to Modifier/Pose (instead of Modifier/Shape) and tried saving it and still no luck.
If anyone has figured out a way to save morphs in timeline please post it here.. it would be a life saver!
thanks
@kandori07 The default daz facial "morphs" are essentially poses for the facial bones since G8 comes with a face rig. It has nothing to do with geometry morphs aka shapes.
+1
Same boat here. Luckily I have a backup of 4.12.0.86 so I can work on my projects but if they keep not fixing the animation tools (timeline and puppeteer) all the animators will be doomed on relying on an obsolete version.
And it's not just matter of animators, even "stillers" are damaged by this not being able to use the animation tools along with DForce, FluidOs and all other plugins that requires a timelapse.
@Imago May you please tell me the SHA 256 of your 4.12.0.86 installer ? So I could verify my backup. To get the SHA 256 menu it is enough to install 7-zip.