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
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
Delete ds files if pz2 are present, and works.
However, the material will only work if the folder containing all the material files is located in “Content Directory Manager/Poser Formats” and not in the 'DAZ Studio formats" It will be enough to move it if necessary.
Well, I removed a large portion of the mouse tweak, delete the HIDusb service, and restored the SmoothMouseXCurve and SmoothMouseYCurve registry values, but I left the polling rate at 1000 instead of the default. Even though it’s basically more of a placebo effect in games, I don’t think that was the cause.
Thank you! I gathered up all of the .ds files and dropped them in a folder. It worked! I appreciate the help. This one would have bugged me for awhile!
I tried changing the extension to .dsa. on the Daz Studio format side of things and it generated this error when I tried to apply the texture.
2026-06-23 12:30:20.581 [INFO] :: Loading script: E:/Night Owl 3D/People/Genesis 8 Female/Converted Hair/AmberHair/Amber Materials/Amber-Blue1.dsa
2026-06-23 12:30:20.581 [WARNING] :: Script Error (E:/Night Owl 3D/People/Genesis 8 Female/Converted Hair/AmberHair/Amber Materials/Amber-Blue1.dsa): Line 19
2026-06-23 12:30:20.581 [WARNING] :: SyntaxError: Expected token `('
2026-06-23 12:30:20.582 [WARNING] :: Error in script execution: E:/Night Owl 3D/People/Genesis 8 Female/Converted Hair/AmberHair/Amber Materials/Amber-Blue1.dsa
I updated a .ds MAT file until I fixed all the errors, but it still doesn't work—it's deprecated.
2026-06-23 21:10:10.511 [WARNING] :: Global shiftPressed() is deprecated. Use DzApp::modifierKeyState() instead.
2026-06-23 21:10:10.511 [WARNING] :: Global ctrlPressed() is deprecated. Use DzApp::modifierKeyState() instead.
2026-06-23 21:10:10.520 [INFO] :: Script executed successfully:
OK, so that isn't a viable option. I wasn't sure.
It's easier to save a .duf file in DAZ 4.24 so you can use it in DAZ 2026. Remove the .dsa extension, the dynamic clothing and other features are lost.
In my logs, is there a problem accessing the “temp” folder in DAZ???
EDIT : NOPE, All the issues are related to Qt6—even the speed scroll mouse Daz to crash. Now I understand better why they were talking about my mouse...
On another PC, Windows 11 is even worse...
DAZ 2026 disappears immediately, so goodbye the crash saves... But there are still some survivors...
Lol, ah xd—it didn't crash, but I don't know that language
What is the file name for the OBJ?
Genesis 8.3.obj. If it's not the language of the pharaohs, then it's squares... But And it crashes every time I click “Create”.
As of now, Daz 2026 has are well-groomed for Mac, but for Windows 10/11, it's been a real disaster...
I rename obj "Genesis.obj'
I could reproduce the crash issue. I believe it's a bug. There's no issue with Figure Setup in DS 4.2x ~
Try to reproduce this bug "Extract Donor Figure"
Same, DS crashed on my side ~
DS 6.x...no matter general release or public build, is not a stable version at all, esp. for advanced users. Better work with DS 4.2x ~~
DAZ 2026 is faster than 4.24 in a lot of ways, but yeah, that's true. AND there are plenty of things I've forgotten because it was so frustrating to waste hours...
it runs better on the Mac than it does on Windows? Boy that's really one for the books. But don't forget, it doesn't run natively on the Mac.
Ok why not (does it crash at least once every time you use it? Yes/No), I'm going to rephrase what I said: daz 6 it has the reliability of an alpha first release, that way, no one will be jealous.
Maximize my chances without crashing, I shouldn't edit a morph's percentage, sliding a morph, avoid using the IRay preview, avoid the dforce simulation, use so-called “advanced” features, use the “disengage scroll” on my mouse—and those are the things I remember.
Since it's an access violation in dzcore, Qt6core... AND all of this with 2 PCs running Windows 10 and 11
Well, it seems like the crashes are coming from G9. With G8, I don't get any crashes when sliding a morph or editing a percentage.
I installed the update for the Beta 6.25.2026.19821 this morning on my MacMini M4 and then download the rest of my updates and purchases. I opened the Beta and after running Update and Merge all my scripts were there where I had put them under Scripts, C66Toolbox and Favorites. I then checked out my new products and did metadata adds that I do to add extra layers. No issues and I am running Content Database Maintenance>Export User Data without issues as well.
Yesterday I did a render of a Filatoon character on the regular 6.25.2026.14722 on the MacMini M4 and was happy to find Measure Metrics now available and it worked great. I did not run into any issues. I think others might call me a 'non-advanced' user, even after 10 years. But I am seeing progress and I want to thank the DAZ team for all their hard work.
This issue still persits in the latest DS 6 PB :
1) Left-click in Viewport, scroll mouse-wheel, Viewport zooms in / out as expect.
2) Now move the curse to any other pane group, e.g. Scene pane, Parameters pane, Smart Content pane or even toolbar / status bar, scroll mouse-wheel, Viewport still zooms in / out.
No such issue in DS 4.2x.
I would like to know if the following issue is specific to my system or if others are experiencing it as well.
In Daz Studio 6, when using the Geometry Sculptor, holding the Ctrl key and scrolling the mouse wheel in either direction only decreases the Falloff Radius value. It never increases.
In Daz Studio 4.24, the Geometry Sculptor works correctly—the Falloff Radius increases or decreases depending on the direction you scroll the wheel.
As a side note, the Node Weight Map Brush in Daz Studio 6 works perfectly fine; Ctrl + mouse wheel correctly increases and decreases the Inner/Outer Radius values.
On my end, this Falloff Radius bug has been happening since Daz Studio 2025 ALPHA 6.25.2025.19807 (the version where Geometry Sculptor was first released to the Public Build channel) and persists in the latest release.
Can anyone else reproduce this on their end?
Yes, the issue has been long standing there since DS 2025 was released, there's no fix up to this latest DS 6.x PB. Besides, Ctrl + PgDown / PgUp doesn't work either though the plugin states this alternative shortcut works...
I'm relieved to know it's not just my system, although it's a shame the bug hasn't been fixed yet. Good to know about the Ctrl + PgDown / PgUp issue as well.
Thank you.