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
I have recently encountered a really strange bug! When I bend the right shin, the right thigh becomes REALLY distorted! This has happened with totally different characters and so far, only happens with the right leg.
I am guessing it is a bug with how Daz is handling the bones.
I tested this with Daz 4.24 and there are no such issues with the same character.
It is more likely that you have a morph installed that is activating when it shouldn't.
I tested this on 4.24 and there are no issues at all. Though either way, it is a nasty bug not present on 4.24.
When it comes to my morphs, I actually cleared ALL of them out a couple years ago and started to move morphs I know I needed and that were not buggy back in as needed. This way I was able to pinpoint morphs which were buggy and leave them out. So I don't have problems with morphs. If there are, it is with 6.25.
You'll have to give more specific data and screenshots of the problem, if you want someone to try to reproduce and diagnose the problem. What generation of characters are you having this problem with? You say it is not morph related, so can you demonstrate the problem with the Base character of the affected generation, with no morphs applied? Specify the shin rotation(s) that causes the problem.
Also, do the content directories match (the folders and the order in which they are listed, since DS will stop when it finds the first copy of any given file - meaning that if the order of directories is different in the two versions one may be loading an old/damaged version of the files while the other gets a good version). What about the DSON Cache (Edit>Preferences, you may want to try clearing it to see if that beings the two versions into agreement).
I loaded up DAZ Alpha again today, and the problem has vanished. I tested it on the base G8F, and again on the character I had issues with last night and... nothing, all works fine. I tried out some premade poses I had been testing, poses I made and saved myself, and they all worked... no issues. This has happened in the past. I recall the same issue with the right leg on a totally different character. I noted that when I have been using DAZ Alpha for a while, it can slow down signiifcantly. Eventually, the Iray preview on the main viewport will be really low rez where you can see the blocks. I think the issue with the leg is somehow related as all these issues start to pop up after using Daz for a while. Issues I never had with 4.xx.
As a programmer myself, this is the sort of behaviour that leads me to think of a memory leak of some sort.
In any event, no matter what the ultimate cause of the problem is, IT IS A PROBLEM and NOT my fault what so ever. If others switch from older versions to this version... they WILL have the same issues which NEED to be dealt with, rather than blaming the end user.
I doubt I will waste my time reporting bugs in the future as thus far, it is an excersize in frustration. Enjoy your forums and lets hope these problems are dealt with.
Goodbye!
Your original description didn't really give mush information to go on, asking for more information/troubleshooting is not discmissing the issue or blamiong you but trying to narrow it down. Sometimes it will turn out not to be a bug, sometimes (as with the issue selecting in the Timeline) it will, and the extra steps/wquestions will help to identify it.
Currently I am using the GeForce Game Ready Driver Version 581.29 which as of September 10th is the most up to date driver.
I resorted to using custom menus and not the Favourite or Scripts so that when they are removed by updates or Merge script it is not an issue. i simply F3 and import my Utility menu again leaving the others blank (actually sometimes they are not always blank, they contain GUID information for the previous assets that were linked). Will test your toolbar issue. Usaully i can R-Click on the toolbar and uncheck the boxes, Exit Studio and they remain in the state i left them (disabled or enabled). F3 sometime override the R-Click.
Still no fixes for this issue?
Check the most recent entries to the change log - if that works out we may hpe that the next public build will have the fix.
Perhaps this has already been mentioned previously, but the volume of posts prevented me from checking.
In my case (Mac version), when I have a character selected in my scene (for example, Genesis 9), in version 4.x, when the “Filter By Content” box is checked in the “Smart Content” panel, it only shows me elements that are compatible.
In the ALPHA version, this does not work and, more often than not, the folders are displayed as empty.
I'm sure this has been asked before, but the Alpha seems to not render dforce hair at all.
Is this a known bug or do I need to enable something?
Any specific hair? What is your driver version? I can render it.
Literally any dforce hair.
Driver version is 581.29 and GPU is 5060 Ti.
Check the log the next time you try and see what it says.
So I installed an update and now the issue is this;
With Multithreading from preferences on, dforce hair freezes the whole program.
Multithreading off, the program only renders the preview hairs.
2025-09-16 22:32:06.565 [INFO] :: Begin asset load (merge): /People/Genesis 9/Characters/Oso3D/Oso Perrito for Genesis 9/Oso Perrito Base Fur.duf
2025-09-16 22:32:06.572 [INFO] :: Determining missing assets...
2025-09-16 22:32:06.735 [INFO] :: Setting textures...
2025-09-16 22:32:06.782 [INFO] :: Scanning for addons...
2025-09-16 22:32:06.783 [INFO] :: Creating node geometry...
2025-09-16 22:32:06.784 [INFO] :: Creating UV sets...
2025-09-16 22:32:06.784 [INFO] :: Creating materials...
2025-09-16 22:32:06.861 [INFO] :: Resolving legacy figures...
2025-09-16 22:32:06.861 [INFO] :: Preparing modifiers...
2025-09-16 22:32:06.861 [INFO] :: Creating modifiers...
2025-09-16 22:32:06.902 [INFO] :: Finalizing modifiers...
2025-09-16 22:32:06.902 [INFO] :: Finalizing simulation providers...
2025-09-16 22:32:06.902 [INFO] :: Sorting property groups...
This is as much the log gives me.
Which tool is active (checked in the Tools menu)?
I even failed to load Oso Perrito G9 with latest Alpha. DS freezed. But loading the fur separately worked as well as the rendering.
Is Alpha responsive, e.g. can you delete Perrito, etc? Or do you need to restart?
Alpha didn't response. CPU load went up and fans roared, lol~ I'm not able to sort it out by now.
This is not a known issue in general. Are all the CMS-related settings the same in both versions of DS? Also, do they have matching permissions?
It seems to be fixed in 6.25.2025.25616, at least I can now marquee select the top level "heart" for a character and can also click-select. I haven't checked anything else because my Smart Content appears to have been almost completely deleted; the only things left seem to be products I installed on 13 September. Probably not related to installing .25616 and the CMS is there, it's just the Smarts that have gone.
@richard, do you have any idea where the Smarts are stored?
John Bowler
Edit>Preferences>CMS Settings tab, the Content Cluster location. Though I would suspect it has been changed somehow, before the first of the installations that is still showing, so that would not be the location of your original database..
I'm having the same dForce hair problem in DS6 25616 as previously reported by others. Having seen the reports, I tried loading and rendering the AM white rabbit in the previous DS6 Alpha version before updating DS6 Alpha. It worked fine. After updating to DS 25616, loading the same figure just puts DS6 into Not Responding and I had to kill the process.It wouldn't even load. I couldn't get as far as trying to render.
One difference I noticed is that with the previous update, I was prompted to update kernels. This time I was not. I don't know if that is significant. That kernel update prompt might be related to a GPU driver update rather than a DS update. I don't know. I can't remember exactly when it happened.
Is any regression testing done before releasing an Alpha update? It seems like with each release, previously working capability is lost. I get the sense that it was not intentional. If it was intentional or was discovered during Daz testing, a heads up would be appreciated. It would save us Alpha testers a lot of wasted effort.
I realize it is an Alpha, but I'm still surprised to lose previously working functionality. I feel bad for NVIDIA 50XX users who are stuck with unpredictable functionality losses. I only have a 3080; I can just go away and use DS4 for everything, like usual.
I second the points. It seems there's been no regression test while we users are doing these...? These malfunctions make Alpha less usable.
BTW, the issue of plugins unregistered I ever reported seems gone in the latest version.
My first thought too but it hasn't been changed; it's still there and, when I load a scene which certainly contains items which are not in the very few products listed for smart content they load just fine, no "help me find" or anything. I checked with both the 6alpha and the 4beta.
That's why I say the CMS has not been deleted or reset but the smart content was zapped, maybe, in fact, before Sept 10 but I loaded scenes after that.
Hence my question; where is the smart content stored? Perhaps not in the CMS or perhaps the relevant entry in the CMS was deleted somehow (but not the whole CMS). Yeah, I can write a script to go through every .dsx in .../RunTime/Support and reload it, or I can use the Content Directory Manager option which is meant to do that but always seems to mess everything up even more but I'd really like to understand what happened.
John Bowler
We are their free labor, I guess, but I always expect that user testing should be a check to see if something was overlooked after developer testing and Private Build "canary" testing. It doesn't feel like that is how it is working.
To be fair, we're a much, much wider range of machines and configurations for them, far, far wider than they'd be able to afford to test. It does hurt a bit, as you mentioned when something that worked last version stops working in the new version. I've got a couple of projects going using the Alpha so I had to go back to the last version or stop working on them.