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
Not a bug but an observation on normals (on models that I made, not any other content so far)
I noticed the interface is behaving differently with some normals on some models that I have made in Blender. I have to seen this anywhere else at this time. but these models which I've used before displayed without these inversions prior to this.
To correct this I had to recalculate the normals on the surfaces that were getting inverted (just flipping them did not seem to do anything.) Using Studio prior to this version you would generally see an area on or close to where a normal had been flipped as inverted but I was seeing the entire surface as being the problem. Again, not a bug, just different behavior.
@ Richard H
Yes, from the content, no warning, I'll try and validate later, I need to get out of my house and walk a dog the size of Clifford who is the biggest dog in the whole wide world.
@Vaskania
I'm going to try to use the V4 and Injections that were loaded into the default location by DIM, my runtime or duplicates of it, or the fact it's on an alternative internal drive could all be the culprits.
@anyone else
Has anyone else seen the select two or more nodes and only the last one selected is adjustable in the parameters tab or am I experiencing this one on my own as well?
What I've been experiencing is the viewport screen freezing once in a while, it rarely happened before, but it happens more with the Beta. It gets fixed when selecting a new camera, but its a bit annoying.
the FBX exporter seems to be broken. Is there an update for that or is it part and parcel of the Beta release?
When I go to the export dialog box, all the morphs are missing, and yet when I try it in the General release, I see the morphs when I got to Morph export rules.
I liked the FBX exporter in Daz Stduio 3.1 a lot more because it made every available morph right there in a drop down format next to the morphs under the morph rules . it was way easier to choose either to Bake or Export at the top level.
I tend to export models to 3DS max, and Max has a morph limit so it would be nice to control the morphs in a more structured way... has anyone else encountered what I am talking about, any solutions?
Greetings,
It's probably unrelated, but I'm getting a 'duplicate formula' warning whenever I load something Genesis based.
-- Morgan
Only in the beta? Is it possible that you have two copies of the Genesis morphs, and the folders containing them are listed in a different order in the beta and the release versions? DS will grab the first file with the right path and name that it finds - if the release version is finding updated morphs first it will be happy, if the beta is finding old morphs first it will throw the error.
What is your setting for Display Separate items in the Parameter pane option menu?
What is your setting for Display Separate items in the Parameter pane option menu?
two things so far:
Eyes on V4 (and any other combination of limb nodes)
Select both in the content pane
move to the parameters Up/down or Left/Right
only the last eye I selected wants to move.
or
Import two props
Select both in the content pane
move the x,y,z translate or rotate
only the last item selected moves.
2nd
Select an item of clothing's body nodes (to adjust a morph target not at the root of the item)
say I select the neck, abdomen, chest and hips on an outfit.
I adjust a single morph value that is present in all nodes; like heavy or athlete.
Only the last item node I selected reacts to the adjustments in the parameters.
for what it's worth I have a dual monitor setup, a 27" set to portrait, and a 25" set to landscape all off the same video card which is an updated but old Nvidia GTS 250 with 1GB of DDR3
the rest of the rig: i7 920 2.6GHz (not OC'd), two (2) 500GB SATA 3/GBs drives (one for OS, the other content), 12GB Corsair DDR3 1.6GHz RAM
@Strat- the scene load issue shouldn't be related to what drive your content is on. I have both the general release and beta on E, but all of my content is on F. Judging by the errors, I'd assume it's likely an issue with your Aiko 4 install. All of my Gen4 girls are installed to the same runtime (as they need to be to work right).
Hmmmm... don't know what to think yet. Installing this beta version removed CMS from my services. Reinstalled both the beta and the latest official release. CMS is not back. Studio is unusable for me without CMS running. No errors related to CMS in event viewer.
Any suggestions here?
Installing the beta shouldn't have done anything with your CMS. Until you can find a fix though, you can still get to your content through the Content Library pane (window > panes > content library).
That is what I am doing right now but it is a real mess.
two things so far:
Eyes on V4 (and any other combination of limb nodes)
Select both in the content pane
move to the parameters Up/down or Left/Right
only the last eye I selected wants to move.
or
Import two props
Select both in the content pane
move the x,y,z translate or rotate
only the last item selected moves.
2nd
Select an item of clothing's body nodes (to adjust a morph target not at the root of the item)
say I select the neck, abdomen, chest and hips on an outfit.
I adjust a single morph value that is present in all nodes; like heavy or athlete.
Only the last item node I selected reacts to the adjustments in the parameters.
for what it's worth I have a dual monitor setup, a 27" set to portrait, and a 25" set to landscape all off the same video card which is an updated but old Nvidia GTS 250 with 1GB of DDR3
the rest of the rig: i7 920 2.6GHz (not OC'd), two (2) 500GB SATA 3/GBs drives (one for OS, the other content), 12GB Corsair DDR3 1.6GHz RAM
That didn't answer my question - and I should also have asked about the Consolidate properties option. You want that on and Display Separate Items off to affect multiple items with a single slider. I'm not entirely convinced the behaviour is logical, but it does seem to work.
I misread.
Where do I check to see what you're asking me to verify?
Parameters pane option menu - right-click on the tab, or click the button in the top corner.
https://helpdaz.zendesk.com/entries/22523891-Trouble-shooting-the-Smart-Content-Pane
https://helpdaz.zendesk.com/entries/22523891-Trouble-shooting-the-Smart-Content-Pane
I solved the problem. I suspect it was the upgrade from Windows 8 to 8.1 that made the service completely disappear from the services manager. I played with Studio after that but with an existing scene, so I may not have noticed the missing CMS. Dim couldn't reinstall it. I had to manually download the latest official release to reinstall the CMS. Lost some of my categories in this process, which I expected anyway. As for the database being corrupt, not sure at all since I regularly maintain it. Sadly I didn't export it.
Sorry but the suspicion the Beta was involved was too strong to be ignored. After all I don't know how the installer behaves. :roll:
I solved the problem. I suspect it was the upgrade from Windows 8 to 8.1 that made the service completely disappear from the services manager. I played with Studio after that but with an existing scene, so I may not have noticed the missing CMS. Dim couldn't reinstall it. I had to manually download the latest official release to reinstall the CMS. Lost some of my categories in this process, which I expected anyway. As for the database being corrupt, not sure at all since I regularly maintain it. Sadly I didn't export it.
Sorry but the suspicion the Beta was involved was too strong to be ignored. After all I don't know how the installer behaves. :roll:
That also makes sense.
@ SpottedKitty
they need to be consistent with the naming conventions, this isn't consistent at all
"_" goes before "a", not "_" goes after "z"
@Vaskania
I'll check were Aiko is installed, previously I was getting this with Morphs++ and Base as well, maybe this narrows this down.
@ Richard H.
Just tried on my mac and it worked, thanks!
I know it's inconsistent, that's why it took me so long to work out what was going wrong and how I could work around it. If the non-alpha character order has changed again, I should be able to adapt quicker this time. Still an unnecessary annoyance, though.
I solved the problem. I suspect it was the upgrade from Windows 8 to 8.1 that made the service completely disappear from the services manager. I played with Studio after that but with an existing scene, so I may not have noticed the missing CMS. Dim couldn't reinstall it. I had to manually download the latest official release to reinstall the CMS. Lost some of my categories in this process, which I expected anyway. As for the database being corrupt, not sure at all since I regularly maintain it. Sadly I didn't export it.
Sorry but the suspicion the Beta was involved was too strong to be ignored. After all I don't know how the installer behaves. :roll:
That also makes sense.
This is indeed the case, the windows 8.1 update is removing the CMS from the services manager, so it can't start
For me if I try to uninstall the DAZ Content Management Service an error message is displayed informing you that :
" this app can't run on your PC. To find a version for your pc, check with the software publisher "
Just file a support ticket/Submit a request. :)
How can we find what bugs are reported by other users?
can we add support, report problems, fixes to the same bug?
How can we find what bugs are reported by other users?
can we add support, report problems, fixes to the same bug?
You can't.
No, not at this time.
that 's a pitty,
it's just that now 100 users can report the same bug over & over again, and that 's creating some unnecessary workflow for those sorting the buglist.
ah well may be later...
Do I need to reinstall DIM to uninstall this Beta? It's too buggy for me to use and I hope it's not eligible for a Release Candidate the way it is now, I'm blowing out straight to the desktop with no error logged.
That would be the best way.
Installed it, set it up then tried to load projects I have been working on from the general release....but would not open properly. Half of the objects wouldn't even load with Daz showing tons of errors while trying to load them. Forget it! I uninstalled it and will wait for the next general release.
Did you map your content folders? The beta does not share settings with the general release (so as not to interfere with them).
I've had the same issue, and yes my "Display Separate Items" was turned on.
I also concur with the lack of conviction on that making any sense... these are separate items and are being happily displayed separately... *shrug* At least now I know what to change ;)
EDIT: And I'm really glad there's a solution, but someone somewhere might want to look at that. It makes hand posing basically impossible. Well, no, not really impossible, but so incredibly horrible that I was about to write off the beta and go back to the stable version >.>
Using the hair shaders that come with Sickle's new burlap doll, I get a UV not found error for the yarn shaders (I've made her aware of this already), but it causes 4.6.2.23 to crash. The error does not crash 4.6.1.17.