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
Here you go!
Change this in the Workspace > Customize Interface Style menu
Headlamp off, preview lighting off:
Headlamp off, preview lighting on:
Headlamp on:
I can reproduce this
I'm getting the same behavior aswell.
If I wait for the "busy" cursor it won't crash.
the crash dump is showing
error code:0x00002733
Description:A non-blocking socket operation could not be completed immediately
Googling the error code I found several discussions about it.
none that look to be done on the customers side though
0x000027330x0000273300x0x00002733000027330x000027330x00002733x00002733
Pardon my confusion. What could be considered the minimum GPU needed for DAZ Studio 2025?! Are we talking the 50XX video cards?
my RTX 3060 works just fine with it
I'm using ther newest driver from Nvidia
Cascaduer recently added Ragdoll physics as well.
Thank you, it's been so long since I set those that I forgot they even could be set in that menu. Appreciated!
I still have no idea how to get Casadeur to work with DAZ figures; the one person who offered to explain shared a file that I could not get to work. Has it gotten any easier?
I've found that since I'm going to retarget and tweak it in Blender anyway, I don't have to have an exact match of the Genesis chracter in Cascadeur. Close enough is good enough.
Not told off, just pointed to a more appropriate place. The chnage of Qt version (the framework used to build the application) means that all plug-ins are broken and scripts may or may not work - with those with UIs being obvious candidates for failure since they are using the Qt features. Once the SDK is stable we may hope that developers will be able to update their products, but the alpha stage is, almost by definition, not stable enough.
I see this too, not sure what it is - fiddling with the tool Settinmgs didn't remove it.
If I load a strand based hair, even by itself, in a scene and activate the new strand based hair editor the hair vanishes. Leaving behind only the scalp.
Theres no apparent manipulators in the view port. Just a large cursor.
Switching to the Universal Manipulation Tool
If I change either of the two the tessellation values for example "Viewport Line Tessellation Sides" from 3 to 1 the app crashes instantly
So I downloaded the Alpha out of curiosity, wondering whether it would work at all on my old Windows 10 OS.
The main interface loaded OK. I didn't log in to my account because I wasn't sure if that would mess up settings for my existing installation of DS.
We were reminded in advance that some features would be missing but I was surprised that the missing features included some of the main, most essential, things.
No camera cube, no ability to choose camera, nothing visible in the viewport, no ability to frame selected object. No plugins. No 3Delight. Export formats limited the most basic ones.
So I felt that this was, on my OS, an almost non-functional version. I mean, it boots but isn't yet able to do any work. I can't guess whether this is simply because my computer is too old or whether the beta and customer ready versions will include the backwards compatibility that I need.
I'm worried that day is coming when I won't be able to use Daz Studio at all because the system will have become so advanced that old users like me will be left in dust. I'm so worried about that that I've almost completely stopped buying the newer Daz content and my purchases are mainly of V4, M4, A4 type of things which will still work in Poser, Carrara and, to a lesser extent, Vue.
It feels like having a ticket on a train which won't be there much longer.
You need to use the Tool Settings pane to work through the stages of hair creation/editing. Is the hair you are using actually Strand-Based Hair or dForce hair?
You can just Alt-click the colour bar headers (with the label) as that restores to default, which iss till the coloured version.
3Delight and Iray may be free to us, but that doesn't mean they are free-free.
I'm not sure how this came about, but I wanted to see just how much improvement there was to character loading times so I loaded a G8.1 character I have saved as a scene subset complete with hair, goegrafts and geometry shells. In studio 2025 it took 1 minute 27 seconds to load, here is the wierd bit, in 4.23.1.27 it took 12 minutes 45 seconds to load this morning before I installed 2025. After installing 2025 the same character loads in 4.23.1.27 in 1 minute 28 seconds. It seems, although I don't see how, that simply installing 2025 and not even having it running in the background has sped up my G8 load times signifcantly.
That's definitely a bug, not an intentional limitation. What kind of GPU does your system have, and if it's an nvidia card is your driver above min version required?
We already knew the next major version would break all plugins, breaking the SDK is why it's a major version.
The others were most likely plugins.
I'm still wondering why Daz released an alpha version to the users ...
It is the only version that can render with Nvidia RTX 50xx series cards which will become common over the next few months. IMO, the launch allows focus to shift to DS 6 and reduce efforts on DS 4.
DAZ Studio 6's AI was thanking you for becoming a DS 6 Alpha tester.
Thank you, both. That was driving me crazy.
Yeah this is actually also headlamp lighting, because the render options also force it by default. This isn't the same as the preview lighting available in current and all previous versions (which seems to be just gone). The difference is you have no contrast with headlamp lighting so it makes it much harder to perceive volume and shape.
Leana said:
That's definitely a bug, not an intentional limitation. What kind of GPU does your system have, and if it's an nvidia card is your driver above min version required?
As I said, I only downloaded the Alpha out of a curiosity to see whether it would even fuction at all on my antiquated Windows 10 system. My computer isn't able to upgrade to Windows 11, the hardware won't support it. The graphics are integrated Intel, not a dedicated GPU, although some video editing software, such as Movavi, seems to be able to use a software emulation which treats the integrated graphics as a "GPU".. I'm not sure how that works but anyway Daz Studio doesn't do it.
This is why I'm so worried that poor people like me who can't afford to upgrade the hardware are going to get left behind. It feels as though there's a conflict of interests between the tech imperative of continually moving onward, ever onward, and the commercial imperative of holding onto the broadest possible customer base. From a commercial point of view the wisdom is to sell whatever customers will buy. So if some customers are buying Teslas and some customers are buying the Model-T Ford you sell some of each, yes?
In previous versions of Daz, moving around in Perspective mode with Preview Lighting turned off worked great in Textured Shaded mode. I'm not sure if this change is a bug or intentional, but now the Perspective view behaves like a camera—zooming in causes everything to go black, and zooming out makes the scene overly bright. I rely on having Preview Lighting off while working in Textured Shaded mode because it made editing scenes quick and easy. Fingers crossed it's just a bug.
Ok, other people have reported problems with Intel integrated GPU so it will likely be investigated by Daz.
Good question, I really don't know.
It's the "dforce Roxi Hair for Genesis 8 Female"
I'm assumed it was because of the tressalation options.
might just be regualr old deforce hair tho.
It's not SBH, but that's not the same as being "regular old dForce hair". The reason Richard was asking is that the SBH editor works on SBH hairs created with the SBH editor, but once a PA applies dForce to the hair, it is no longer user-editable.