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
There is a known issue in 4.12.0.86 with some legacy figures (Poser rigs, like Star) that ahve IK chanins defined. The beta has the fix, the General Release will be fixed when this or a later beta become the new General Release.
oh! thank you so much for let me know!
olvide mi contraseña que hago
Use the "I forgot my password" link on the Home Page https://www.daz3d.com/
I'm glad i haven't updated to 4.12 yet. The horror stories i'm reading in this thread are bone chilling. Almost sounds like the Pro version is worse than the Beta. Yikes.
Well the two main goals of 4.12 would be animation and rtx support. Now the latter seems to be mined by unreliable drivers from nvidia, at least with some configurations. While the ik chains seem to have issues when saving and reloading the scene. That said, if you don't care about animation and you don't have a rtx card, then 4.12 works as fine as 4.11. My system is working fine for example.
So nothing is really worst, just it isn't better yet.
I'd disagree that the new ik chains are unusable for animation. Indeed they work fine unless you save and reload the scene. That's a bug reported to the daz team, though actually I have no news on it being fixed.
https://www.daz3d.com/forums/discussion/357776/ik-chains-explained
https://www.daz3d.com/forums/discussion/359821/ik-chains-bug-ticket-submitted
It's actually frustrating and it never works for any of my animations. On the contrary, it made my workflow worse. After spending some time posing my figure in the starting position, I activate the IK and begin animating. Then I go back to frame one and all of a sudden the original pose I created (and memorized) is gone. I clear the animation and restore the figure, but the original pose is not restored. I delete the Ik chains and restore again, the same. The result of many minutes trying to create a simple animation is a disturbing pose the IK chains created. Not to mention the sliding feet/hands during the animation no matter what you do (even after following your tutorials), or even worse when limbs explode all over the screen. I don't even dare to use IK chains anymore. Daz should fix the IK and bring it back to how it was when it was first introduced in Beta. It worked flawlessly then and then one update messed it up and hasn't been fixed since.
Had you set a key frame in the initial frame? If not then any properties that were not adjusted for the initial post will isntead have the properties set in the first frame in which they did get changed/keyed.
I reported the bug you speak of a couple of months ago, they asked for a video to prove if happens so I gave one to them & I also gave them the scene that it happens in and instructions on how to replicate it. They accepted the ticket but I don't know when they can fix the bugs.
I only experience slidings after reloading the scene. As for the exploding limbs I only get them when I forget to set limits for the ik solver. I agree though that using the ik chains is troublesome, that is, it requires a fair amount of caution and correct setup to get it working. That's probably not how a general use ik system should be.
Thanks, Richard! Yes that happens even when you create a keyframe
Thanks for doing that! I hope it will be fixed soon.
Thanks! When IK Chains feature was still new in Beta there was no need to set limits. It worked as you would expect. Mcasual pinning scripts are still more reliable and do the job more accurately with less effort.
Yeah, I've got an RTX Card and 1080 in my system. I'd love to use the RTX card to it's fullest, but with everything being mentioned here, I...just don't want to take the risk of 'upgrading/updating' only to uninstall and redo everything for 4.11. And someone here said 4.11 isn't available anymore? That's kinda dumb, especially after hearing all the bugs and problems, you'd think the developers would allow the previous version to be downloadable once more, until the current version doesn't flop around so much.
You can always install the beta, that won't affect the General Release (and has a version of Iray that addresses some of the issues that have been reported).
https://www.daz3d.com/daz-studio-beta
With all due respect, No. The beta wouldn't save for me. Why should I 'upgrade' to 4.12 and run the risk of whats been plainly spelled out here; excessive crashing, not saving, 1 iteration of iray on GPU before resorting to CPU, etc. From everything I've read so far, 4.12 is a damn disaster, regardless if it's beta or not. I'm visiting this thread to see if the developers got 4.12 to work right; ie, doesn't excessively crash, doesn't drop to CPU rendering when GPU is specified, and bloodly saves the file when told to. I mean, that's the whole point, right? Create a scene, render it, save the duf and the image file and move onto the next project.
And if the only differences between 4.11 and 4.12 are the animation timeline and RTX support; whoopie freaking do. I'll stick with 4.11.
Bear in mind, I'm an engineer and know how to install proper drivers, updates and such, much more than most people; so the issue is not the computer setup. I'm running Win10 Pro (fully updated), the most recent BIOS for the machine, and the latest nVidia drivers (as of this week).
Here's the issue ...
I have an older machine I use in another room. It's an HPz820 workstation, with 96Gb RAM and dual E5-2697v2 CPU's (12 core). I also have three Titan Xp GPU's running. I am having the same memory allocation error problems with 4.12 as described above; where with 4.11 none existed. This is rendering a single image. Now sure I render at 2K (16:9) and commonly have multiple fully clothed G3 and G8 figures and props, but I never had this issue before on 4.11 no matter how complex the scene. I've had as many as 8 figures, in a fully furnished room and using large HDRi for lighting. No issues in 4.11 in those cases. In 4.12 most scenes, even smallish ones, fallback to CPU from the get go. I'm not making animations, just single images. With the Titans and 4.11 I never really had to think about texture sizes, furnished rooms or HDRi sizes for most of my rendered images.
Once I cancel the render the memory doesn't clear, it just stays at 11.x Gb on the cards. I have to restart DAZ or sometimes reboot the machine to clear the VRAM. I suspect there is a memory leak or a badly written "memory clear" command line in the Iray manager coding or DAZ port coding. This is really making my workflow on this machine pretty much useless, not to mention my expense on three TitanXp's a waste of money. I bought them for this purpose. I don't game.
I've looked at the log files, the total size of the VRAM allocation being made by Iray manager is always about 7Gb, (scene complexity notwithstanding) which is far below the amount available regardless. Why it's always around 7Gb is a mystery to me. Yet it keeps trying to reduce allocation sizes ... over and over and over. Usually, before running a render the memory being used by the 1st Titan is at most 1Gb mostly from the viewport in shaded texture mode and the other Titans are at zero. Yet while the log says 7Gb, the actual memory usage is the full maximum on all three cards simultaneously. The Titan Xp are called a 12Gb VRAM card (give or take).
I have never run Optix, since I always have the hardware horsepower. I don't run anything in the background on the machine, no browsers or widgets or anything other than necessary Win10 services (and only those needed). I do run MSI Afterburner, but only to monitor GPU usage and custom fan curves, I use no overclocking or overvoltage on the GPU's or CPU's.
On my main machine (see my sig) I don't have this issue, but I'm running three Titan RTX's there with 24Gb VRAM each and memory sharing via NVLink.
If I can't run Iray on three Titan Xp's on a big workstation ... well ... that's a potential problem for a lot of DAZ users.
I have my theories and suspicions that the problem lies in how Iray manager may be looking to do memory sharing (or even full-on memory scaling as in the RTX Titans and Quadros). When it can't find NVLink enabled cards, such as when finding cards like the 2070 and below (and Pascal cards), it botches the memory allocation somehow, goes into an error mode and doesn't clear the VRAM memory; and then moves on to fallback CPU mode. The same would happen when rendering multiple frames of an animation after the first frame is completed; because of the manager allocating memory into some failure mode leading to the VRAM not clearing. But this is just conjecture on my part.
Tried the beta too ... no joy! Even tried reverting back to multiple older nVidia drivers ... again ... no joy.
I have a feeling I'm going to have to dust off my old Quadro VCA and renew my license for Iray Server just to use this computer with DAZ 4.12. The electric company will be happy. Me ... not so much.
@jrlaudio see this post.
The reports do not apply to all users - remember that people with problems are far more likely to post than those without. The current beta does have workarounds fopr issues with the 440 drivers, though I have found 4.12 pretty stable for still images using the 430.86 drivers.
12 GB Titan X and Titan Xp Pascal cards. (Win 10, i7-8700K. 64GB). Consistent problems with fallback to CPU using 4.12 GR and betas. Nvidia drivers 430.86, 431.86, 441.08 and 441.28 - no change. Very frustrating. Only solution was to revert back to DS 4.11.
Your words are empty with the following, from the immediate next post by MarkH.
Richard, we aren't looking for workarounds, we're looking for fixes to the problems we're describing and having. Until the problems are fixed, 4.12 is not ready for prime time.
I understand that people may be frustrated getting a rtx card just to discover it doesn't work yet. Also may be daz was a little rush putting out 4.12 with rtx support. Anyway it's just waiting for iray and nvidia drivers to get along. There's really nothing daz can do apart may be making 4.11 available for download until the issues are fixed.
I'd also stress here that not all systems are affected. Mine works fine for example.
New NVIDIA drivers (441.66) are now available.
It is not just RTX. I'm having several problems, discussed at length here, with my GTX 1070. So are others. I may not be the expert that you are but these problems are real for those reporting them. I have no idea why your system is working fine and mine isn't... perhaps you should share your expertise with DAZ so that we can all have a working system.
I have a GTX 980 Ti (older non-RTX card).
You are correct that these are real issues and that problems are not restircted to RTX card users. Using DS 4.12.is not much fun. I have been trying to use DS 4.12.1.40. I have been keeping my Nvidia drivers up to date in hopes of fixes. I am currently on 441.41 and have not yet tried the new driver that came out today.
I'm not frustrated that my RTX titan isn't working, because it is working. Very well in-fact. It works wonders with it's older, less powerful brother GTX 1080.
What i'm frustrated at is Daz studio stating that 4.12 is a newer, better version of Daz, when it's actually a degradation. Its worse- hence the 12 pages of posts stating as such. What i'm frustrated at is Daz staff saying 'use this workaround'. No, a workaround in any environment isn't acceptable when people have funneled a great deal of money into equipment, only for the software to flip them the bird.
What the staffers need to do is allow for Daz studio 4.11 to be readily available for download and put Daz 4.12 BACK into beta and keep it there until this GPU to CPU fall-back is corrected, along with all the other show stopping issues are taken care off. Everyone that has expressed issue with the CPU fallback has posted logs.
I say again, Daz Studio 4.12 is NOT ready for prime time.
Agreed, for those whom are suffering the ill behaviors of 4.12 and can't go back to 4.11.
Has anyone heard from the staff why they do not have previous main releases available for download? I know some features are no longer supported and it may not be beneficial at all to have back to inception but even the past few main releases might be good to have available for users to download. I am not having any issues preventing my work currently but curious, nonetheless, about it.
The main issue, aside from the additional meory footprint, seems to be with the 440 drivers (not only, but they do seem to be an issue). And as i said above, not everyone is experiencing the same issues. It is apparently the case that there are substantial changes in the reent drivers - hence the workarounds in the Iray update in the 4.12.1 beta, which is nVidia's own work - and those happened after 4.12.0.86 - which, as noted on the release notes, requires driver 430.86 (stipulated by nVidia).
When there are changes that cause issues, but which are apparently needed elsewhere (do bear in mind that the games that need these updates probably have more users than DS) then I'm afraid workarounds are the order of the day - even making 4.11.x.x available would be a workaround.
Thankfully, I still have 4.11 so I do use that workaround when I need to render an image series or a still scene that requires more VRAM. I feel sorry for those who don't have that option though. It is also inconvenient because some of the plugins will not load in both the General Release and the Beta. I'd much rather have a stable General Release than this kind of workaround.
There are good things about 4.12 which is why I use the Beta whenever possible. When it does render a scene it seems faster than 4.11. The viewport also seems more responsive and quicker to work with. I hope that DAZ & NVidia can come up with a solution soon and I hope that solution does not mean that GTX card users need to go out and buy a 24GB monster GPU just to render scenes that were no problem before 4.12.
By the way, DAZ must be aware that people will stop buying product which look like they might need a lot of VRAM. I have stopped buying just on that assumption because product descriptions hardly ever mention VRAM requirements.
Have you tried reinstaling the older drivers, the minimum required - 430.86 - after uninstalling the current set?