Daz Studio 2025 ALPHA - version 6.25.2025.32308! (Updated November 20, 2025)

Richard Haseltine · October 18

inquire said:

Yes, I know it's running in emulation. But it is not running in Tahoe, or Sequoia, or any of the OSes that actually run on the M chip. It's running in Rosetta 2, Which Apple will eventually drop. I was just wondering if there's any ETA for when DAZ Studio will actually run in, for example, Tahoe, and not in Rosetta 2.

I was further wondering if it might go the way Poser Has gone, and become "Windoes Only." (Poser version 14, soon to be released)

It says "pending" - which certainly doesn't mean no, it isn't going to be made. That is all the infromation that has been given.

acidfast22 · October 19

I just downloaded 2025 and immediately, I don't see anything in viewport in "texture shaded" mode. I cannot find a setting to make it visible in viewport - am I missing something?

DoctorJellybean · October 19

acidfast22 said:

I just downloaded 2025 and immediately, I don't see anything in viewport in "texture shaded" mode. I cannot find a setting to make it visible in viewport - am I missing something?

I'm not sure what you mean. Could you post a screen shot so we have an idea please.

acidfast22 · October 19

DoctorJellybean said:

acidfast22 said:

I just downloaded 2025 and immediately, I don't see anything in viewport in "texture shaded" mode. I cannot find a setting to make it visible in viewport - am I missing something?

I'm not sure what you mean. Could you post a screen shot so we have an idea please.

acidfast22 · October 19

The items are there in viewport, and I can select them, but they are still invisible...

Richard Haseltine · October 19

DoctorJellybean said:

acidfast22 said:

I just downloaded 2025 and immediately, I don't see anything in viewport in "texture shaded" mode. I cannot find a setting to make it visible in viewport - am I missing something?

I'm not sure what you mean. Could you post a screen shot so we have an idea please.

Also system details. Are other Drawstyles working?

acidfast22 · October 19

Richard Haseltine said:

DoctorJellybean said:

acidfast22 said:

I just downloaded 2025 and immediately, I don't see anything in viewport in "texture shaded" mode. I cannot find a setting to make it visible in viewport - am I missing something?

I'm not sure what you mean. Could you post a screen shot so we have an idea please.

Also system details. Are other Drawstyles working?

CPU: AMD Ryzen 7 5800X 8-Core Processor (3.80 GHz)

GPU AMD Radeon RX 6650 XT

Windows 11 Home

Nvidia Iray works, Filament is not showing some hair on models

Richard Haseltine · October 19

Sounds likea driver issue, then, not providing the expected features in it OpenGL. AMD can behave unexpectedly (compared to nVidia and Intel, not going to make pronouncements on which is/are correct) with some "open standards".

barbult · October 19

Richard Haseltine said:

Sounds likea driver issue, then, not providing the expected features in it OpenGL. AMD can behave unexpectedly (compared to nVidia and Intel, not going to make pronouncements on which is/are correct) with some "open standards".

Black viewport in Texture Shaded draw style is the issue we had a long long discussion about in this thread. For me it happens anytime the camera visibility is set to OFF. I was told here that that was an intentional change to correct incorrect behavior in DS4. Is it possible that camera visibility is the problem in this case, too, rather than driver issues? (My CPU is Intel.)

Richard Haseltine · October 19

barbult said:

Richard Haseltine said:

Sounds likea driver issue, then, not providing the expected features in it OpenGL. AMD can behave unexpectedly (compared to nVidia and Intel, not going to make pronouncements on which is/are correct) with some "open standards".

Black viewport in Texture Shaded draw style is the issue we had a long long discussion about in this thread. For me it happens anytime the camera visibility is set to OFF. I was told here that that was an intentional change to correct incorrect behavior in DS4. Is it possible that camera visibility is the problem in this case, too, rather than driver issues? (My CPU is Intel.)

Yes, that could be - the driver issue did sound rather specific, though not wholly impossible (and I had forgotten the hidden camera thing).

PPM_Geek · October 20

When using the Universal Tool (I cannot rule out that other tools may also have issues), dragging a geometry object has a high probability of triggering this BUG. (Null objects or objects with bones may also trigger it to some extent, but the issue is less pronounced.) If I adjust parameters directly in the Parameters tab instead of using the Universal Tool, the BUG does not seem to occur.

BUG Description: Suddenly, the camera resets to a specific coordinate, and the coordinates of the manipulated object(s) (possibly more than one) undergo significant changes. In this state, the Undo operation is ineffective and may cause the coordinates of many items to become even more disordered. Saving the file, closing DAZ, and reloading restores normal functionality.

I have communicated with multiple users, and they have also encountered this issue.

nemesis10 · October 20

Grrr... ijust lost the nvidia iray preview on my mac...no updates or any other obvious changes..

memcneil70 · October 21

nemesis10 said:

Grrr... ijust lost the nvidia iray preview on my mac...no updates or any other obvious changes..

I opened my MacMini M4 with Tahoe 26.0.1 and DS6.25.2025.27507, then opened a file I had rendered previously and went to Iray Preview and had no issues.

Mary

a_gus · October 22

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

Imago · October 22

a_gus said:

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

That's just a "code name" for the Alpha, the final release will be named DAZ Studio 6, as I can see.

Like for Genesis jumping from 3 to 8, DAZ Studio will jump from 4 to 6.

crosswind · October 22

Imago said:

a_gus said:

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

That's just a "code name" for the Alpha, the final release will be named DAZ Studio 6, as I can see.

Like for Genesis jumping from 3 to 8, DAZ Studio will jump from 4 to 6.

I know 4, 5, 6, 7 are used for Victoria... but I wonder if 5.x has been used for any DS applications ? Why does it jump from 4 to 6 ?

DoctorJellybean · October 22

crosswind said:

Imago said:

a_gus said:

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

That's just a "code name" for the Alpha, the final release will be named DAZ Studio 6, as I can see.

Like for Genesis jumping from 3 to 8, DAZ Studio will jump from 4 to 6.

I know 4, 5, 6, 7 are used for Victoria... but I wonder if 5.x has been used for any DS applications ? Why does it jump from 4 to 6 ?

I believe it refers to the QT versions used.

crosswind · October 22

DoctorJellybean said:

crosswind said:

Imago said:

a_gus said:

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

That's just a "code name" for the Alpha, the final release will be named DAZ Studio 6, as I can see.

Like for Genesis jumping from 3 to 8, DAZ Studio will jump from 4 to 6.

I know 4, 5, 6, 7 are used for Victoria... but I wonder if 5.x has been used for any DS applications ? Why does it jump from 4 to 6 ?

I believe it refers to the QT versions used.

Ah, I overlooked Qt ... Thanks !

But I personally prefer to the way that Marvelous Designer (Win) adopted, which has been developed with Qt but never binded its versions to Qt ~~

Leana · October 22

DoctorJellybean said:

crosswind said:

Imago said:

a_gus said:

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

That's just a "code name" for the Alpha, the final release will be named DAZ Studio 6, as I can see.

Like for Genesis jumping from 3 to 8, DAZ Studio will jump from 4 to 6.

I know 4, 5, 6, 7 are used for Victoria... but I wonder if 5.x has been used for any DS applications ? Why does it jump from 4 to 6 ?

I believe it refers to the QT versions used.

Yes, we've seen 5.x used in discussion about the development builds and SDK versions based on Qt5. They switched to 6 when they upgraded to Qt6.

DoctorJellybean · October 22

@crosswind & @Leana More info about versioning:

https://www.daz3d.com/forums/discussion/comment/9137741/#Comment_9137741

crosswind · October 22

DoctorJellybean said:

@crosswind & @Leana More info about versioning:

https://www.daz3d.com/forums/discussion/comment/9137741/#Comment_9137741

Thank you, Doctor!

Richard Haseltine · October 22

Imago said:

a_gus said:

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

That's just a "code name" for the Alpha, the final release will be named DAZ Studio 6, as I can see.

Like for Genesis jumping from 3 to 8, DAZ Studio will jump from 4 to 6.

See https://www.daz3d.com/forums/discussion/comment/9137741/#Comment_9137741

NudeFan · October 22

I have created a G8F Figure with anatomical elements and attached to it pubes (Tempesta3d\Realistic Strips 1\RS05.Duf).

When I load the figure in DAZ Studio 6.25.2025.27507 (Why I can’t select, copy and paste this version number from the ‘About…’-Window?), activate the universal tool and move with the mouse e.g. over the left upper arm I see ‘Left shoulder bend’. When I click on it, the entire figure is selected. I can do this with almost all body parts, in the upper most cases the entire figure is selected. But when I click on the ‘Left tight bend’ - depending on the location there - different items (mainly on the right side) are selected.

If I load the same figure in DAZ Studio 4.24.0.3 and click on different body parts, the expected parts are selected, means: When I click e.g. on the right shoulder, I can easily modify the parameter to adjust the figures pose.

When I select in Studio 6 the pubes and remove it’s ‘Smoothing modifier’, the behaviour is like expected, when I click on e.g. the left shin, I can adapt it’s pose afterwards.

DoctorJellybean · October 22

NudeFan said:

I have created a G8F Figure with anatomical elements and attached to it pubes (Tempesta3d\Realistic Strips 1\RS05.Duf).

When I load the figure in DAZ Studio 6.25.2025.27507 (Why I can’t select, copy and paste this version number from the ‘About…’-Window?), activate the universal tool and move with the mouse e.g. over the left upper arm I see ‘Left shoulder bend’. When I click on it, the entire figure is selected. I can do this with almost all body parts, in the upper most cases the entire figure is selected. But when I click on the ‘Left tight bend’ - depending on the location there - different items (mainly on the right side) are selected.

If I load the same figure in DAZ Studio 4.24.0.3 and click on different body parts, the expected parts are selected, means: When I click e.g. on the right shoulder, I can easily modify the parameter to adjust the figures pose.

When I select in Studio 6 the pubes and remove it’s ‘Smoothing modifier’, the behaviour is like expected, when I click on e.g. the left shin, I can adapt it’s pose afterwards.

There is no difference between how this works in 4.x and 6.x - but configuration of 4.x (intentionally) does not automatically carry over to 6.x. In the Tool Settings pane, when the Universal (or derivative) tool is active, is a "Node Selection Mode" setting.

The "Node" option will cause the node you click (or the corresponding bone of the follow target in the case of a follower) to become selected.

The "Root Node First" option will cause the root node of a figure (where the majority of properties are presented) to be selected when switching between different objects, but the node you click (or the corresponding bone of the follow target in the case of a follower) to become selected if you click within the same object.

The "Root Node Only" option will always cause the root node of a figure to be selected, regardless of which object is currently selected.

Regardless of which of these options is chosen, right-clicking a node in the scene provides a context menu with selection actions that are based on what is under the cursor at the point where you clicked.

NudeFan · October 22

DoctorJellybean said:

NudeFan said:

I have created a G8F Figure with anatomical elements and attached to it pubes (Tempesta3d\Realistic Strips 1\RS05.Duf).

When I load the figure in DAZ Studio 6.25.2025.27507 (Why I can’t select, copy and paste this version number from the ‘About…’-Window?), activate the universal tool and move with the mouse e.g. over the left upper arm I see ‘Left shoulder bend’. When I click on it, the entire figure is selected. I can do this with almost all body parts, in the upper most cases the entire figure is selected. But when I click on the ‘Left tight bend’ - depending on the location there - different items (mainly on the right side) are selected.

If I load the same figure in DAZ Studio 4.24.0.3 and click on different body parts, the expected parts are selected, means: When I click e.g. on the right shoulder, I can easily modify the parameter to adjust the figures pose.

When I select in Studio 6 the pubes and remove it’s ‘Smoothing modifier’, the behaviour is like expected, when I click on e.g. the left shin, I can adapt it’s pose afterwards.

There is no difference between how this works in 4.x and 6.x - but configuration of 4.x (intentionally) does not automatically carry over to 6.x. In the Tool Settings pane, when the Universal (or derivative) tool is active, is a "Node Selection Mode" setting.

The "Node" option will cause the node you click (or the corresponding bone of the follow target in the case of a follower) to become selected.

The "Root Node First" option will cause the root node of a figure (where the majority of properties are presented) to be selected when switching between different objects, but the node you click (or the corresponding bone of the follow target in the case of a follower) to become selected if you click within the same object.

The "Root Node Only" option will always cause the root node of a figure to be selected, regardless of which object is currently selected.

Regardless of which of these options is chosen, right-clicking a node in the scene provides a context menu with selection actions that are based on what is under the cursor at the point where you clicked.

I have copied the settings from DS4, but no changes. The image shows the menu I get with a right click on the upper right arm.

IceCrMn · October 22

here's another crash report

this happened while I was moving an item around the viewport.

I was positioning a pack of cigarettes in the scene.

Seems like moving things is whats causing/triggering the crash.

Doesn't seem to be any specific character or item as I've had this happen 3 times now in completely different scenes with completely different assets in them.

IceCrMn · October 22

I see several of these lines in the log

2025-10-22 15:56:17.295 [WARNING] :: \src\sdksource\interface\viewtools\dztransformtool.cpp(444): Undo Stack hold already started in DzTransformTool::mousePress()!

IceCrMn · October 22

opening the dmp file in WinDB and clicking the !analyze -v option I get this...

For analysis of this file, run !analyze -v

ntdll!NtGetContextThread+0x14:

00007ffe`2bfe3b44 c3 ret

0:187> !analyze -v

................................................................

................

************* Symbol Loading Error Summary **************

Module name Error

SharedUserData No error - symbol load deferred

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.

You should also verify that your symbol search path (.sympath) is correct.

*******************************************************************************

* *

* Exception Analysis *

* *

*******************************************************************************

*** WARNING: Unable to verify checksum for DAZStudio.exe

KEY_VALUES_STRING: 1

Key : AV.Type

Value: Read

Key : Analysis.CPU.mSec

Value: 812

Key : Analysis.Elapsed.mSec

Value: 11085

Key : Analysis.IO.Other.Mb

Value: 0

Key : Analysis.IO.Read.Mb

Value: 1

Key : Analysis.IO.Write.Mb

Value: 20

Key : Analysis.Init.CPU.mSec

Value: 890

Key : Analysis.Init.Elapsed.mSec

Value: 18607

Key : Analysis.Memory.CommitPeak.Mb

Value: 229

Key : Analysis.Version.DbgEng

Value: 10.0.27871.1001

Key : Analysis.Version.Description

Value: 10.2505.01.02 amd64fre

Key : Analysis.Version.Ext

Value: 1.2505.1.2

Key : Failure.Bucket

Value: INVALID_POINTER_READ_c0000005_DzCore.dll!Unknown

Key : Failure.Exception.Code

Value: 0xc0000005

Key : Failure.Exception.IP.Address

Value: 0x7ffda5b89d16

Key : Failure.Exception.IP.Module

Value: DzCore

Key : Failure.Exception.IP.Offset

Value: 0x849d16

Key : Failure.Hash

Value: {d637a19e-0e83-b0de-06d0-f6996c785da7}

Key : Failure.ProblemClass.Primary

Value: INVALID_POINTER_READ

Key : Timeline.OS.Boot.DeltaSec

Value: 29695

Key : Timeline.Process.Start.DeltaSec

Value: 3650

Key : WER.OS.Branch

Value: ge_release

Key : WER.OS.Version

Value: 10.0.26100.1

Key : WER.Process.Version

Value: 6.25.2025.27507

FILE_IN_CAB: crashdump.dmp

CONTEXT: (.ecxr)

rax=00007ffda53d7262 rbx=0000000000000000 rcx=0000026c396742c0

rdx=0000000000000000 rsi=0000026b9230b720 rdi=0000026b9230b730

rip=00007ffda5b89d16 rsp=0000009fe17fae50 rbp=0000026b9230b720

r8=0000009fe17faea0 r9=0000026b9230b730 r10=0000026b920fd950

r11=0000009fe17fb710 r12=0000026b91eb6f60 r13=0000009fe17fc070

r14=0000026b9226a670 r15=0000000000000000

iopl=0 nv up ei pl nz na po nc

cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206

DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x77e011:

00007ffd`a5b89d16 488b9358010000 mov rdx,qword ptr [rbx+158h] ds:00000000`00000158=????????????????

Resetting default scope

EXCEPTION_RECORD: (.exr -1)

ExceptionAddress: 00007ffda5b89d16 (DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x000000000077e011)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: 0000000000000158

Attempt to read from address 0000000000000158

PROCESS_NAME: DAZStudio.exe

READ_ADDRESS: 0000000000000158

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000158

STACK_TEXT:

0000009f`e17fae50 00007ffd`a5b89c9a : 0000009f`e17faf40 0000026c`396742c0 0000026b`9230b720 0000026b`9230b730 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x77e011

0000009f`e17faed0 00007ffd`a695fe60 : 0000026b`9226a670 0000009f`e17fb0b0 0000026b`9230b020 0000026b`00000002 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x77df95

0000009f`e17faf10 00007ffd`a695971a : 00000000`00000000 0000026c`396742c0 00000000`00000000 0000026b`eb641301 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x155415b

0000009f`e17fafb0 00007ffd`a65e7254 : 0000009f`e17fb770 0000026b`91d6c720 0000009f`e17fb770 0000026b`91eb6f60 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x154da15

0000009f`e17fb720 00007ffd`a65e75a8 : 0000026b`eda97360 00007ffd`a65e360d 0000026b`91eb7120 0000039c`000002b7 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x11db54f

0000009f`e17fb7b0 00007ffd`a9e17256 : 0000026b`91eb7120 00007ffd`aa6fb017 00000000`00000002 0000026b`91eb7120 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x11db8a3

0000009f`e17fb7e0 00007ffd`bf1f3b01 : 0000026b`ed8a9300 0000009f`e17fc070 0000009f`e17fc070 0000026b`91eb7120 : Qt6Gui!QWindow::event+0x56

0000009f`e17fb850 00007ffd`bf1f2bf9 : 0000026b`ed8a9300 0000009f`e17fb980 0000026b`eb63b4f0 00000000`00000000 : Qt6Widgets!QApplicationPrivate::notify_helper+0x151

0000009f`e17fb880 00007ffd`a662dd27 : 0000009f`e17ff748 0000026b`91eb7120 0000009f`e17fc070 0000009f`00000000 : Qt6Widgets!QApplication::notify+0x1669

0000009f`e17fbd50 00007ffd`aa6f8621 : 0000026b`91eb7120 00000000`00000001 0000009f`e17fc070 0000009f`e17fc070 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x1222022

0000009f`e17fbd80 00007ffd`a9dcb904 : 00000000`00000000 0000026b`9d979260 00000000`00000000 0000026b`edb08e50 : Qt6Core!QCoreApplication::notifyInternal2+0x101

0000009f`e17fbdf0 00007ffd`a9e2a08b : 0000026b`ed96d1c0 00000000`00000001 0000026b`dc54f170 0000026b`eb666e60 : Qt6Gui!QGuiApplicationPrivate::processMouseEvent+0x7d4

0000009f`e17fc300 00007ffd`aa88f210 : 0000026b`c8da6970 00000000`000000a4 0000009f`e17fc430 00000000`000000a4 : Qt6Gui!QWindowSystemInterface::sendWindowSystemEvents+0xfb

0000009f`e17fc330 00007ffd`aa0e7679 : 00000000`00000000 00000000`00000000 0000026b`c8da6970 0000026b`ed96d1c0 : Qt6Core!QEventDispatcherWin32::processEvents+0x90

0000009f`e17ff490 00007ffd`aa6ff244 : 00000000`000000a4 0000026b`c8da6970 0000026b`ed8a9300 00000000`00000001 : Qt6Gui!QWindowsGuiEventDispatcher::processEvents+0x19

0000009f`e17ff4c0 00007ffd`aa6f6cba : 0000009f`e17ff580 0000026b`eb641340 0000026b`eb641340 0000009f`e17ff748 : Qt6Core!QEventLoop::exec+0x1c4

0000009f`e17ff560 00007ffd`a6615a82 : 0000026b`beabcc30 0000026b`beabcc30 00000000`00000000 00000000`00000000 : Qt6Core!QCoreApplication::exec+0x16a

0000009f`e17ff5c0 00007ffd`a663394b : 00000000`00000002 0000026b`beabcc30 0000026b`bf31e5a0 00000000`00000000 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x1209d7d

0000009f`e17ff5f0 00007ff6`f33c1740 : 0000026b`ed9750e0 0000009f`e17ff7b0 00000000`00000001 00000000`00000000 : DzCore!DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt+0x1227c46

0000009f`e17ff6b0 00007ff6`f33c1d2e : ffffffff`80000002 00007ff6`f33c4830 00000000`00000000 0000009f`e17ff908 : DAZStudio+0x1740

0000009f`e17ff850 00007ff6`f33c2ef0 : 00000000`00000004 00000000`00000001 ffffffff`00000000 00000000`00000238 : DAZStudio+0x1d2e

0000009f`e17ff8f0 00007ff6`f33c2436 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : DAZStudio+0x2ef0

0000009f`e17ff980 00007ffe`2b82e8d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : DAZStudio+0x2436

0000009f`e17ff9c0 00007ffe`2bf0c53c : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17

0000009f`e17ff9f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c

SYMBOL_NAME: DzCore+77e011

MODULE_NAME: DzCore

IMAGE_NAME: DzCore.dll

STACK_COMMAND: ~187s; .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_DzCore.dll!Unknown

OS_VERSION: 10.0.26100.1

BUILDLAB_STR: ge_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 6.25.2025.27507

FAILURE_ID_HASH: {d637a19e-0e83-b0de-06d0-f6996c785da7}

Followup: MachineOwner

---------

DoctorJellybean · October 23

NudeFan said:

DoctorJellybean said:

NudeFan said:

I have created a G8F Figure with anatomical elements and attached to it pubes (Tempesta3d\Realistic Strips 1\RS05.Duf).

When I load the figure in DAZ Studio 6.25.2025.27507 (Why I can’t select, copy and paste this version number from the ‘About…’-Window?), activate the universal tool and move with the mouse e.g. over the left upper arm I see ‘Left shoulder bend’. When I click on it, the entire figure is selected. I can do this with almost all body parts, in the upper most cases the entire figure is selected. But when I click on the ‘Left tight bend’ - depending on the location there - different items (mainly on the right side) are selected.

If I load the same figure in DAZ Studio 4.24.0.3 and click on different body parts, the expected parts are selected, means: When I click e.g. on the right shoulder, I can easily modify the parameter to adjust the figures pose.

When I select in Studio 6 the pubes and remove it’s ‘Smoothing modifier’, the behaviour is like expected, when I click on e.g. the left shin, I can adapt it’s pose afterwards.

There is no difference between how this works in 4.x and 6.x - but configuration of 4.x (intentionally) does not automatically carry over to 6.x. In the Tool Settings pane, when the Universal (or derivative) tool is active, is a "Node Selection Mode" setting.

The "Node" option will cause the node you click (or the corresponding bone of the follow target in the case of a follower) to become selected.

The "Root Node First" option will cause the root node of a figure (where the majority of properties are presented) to be selected when switching between different objects, but the node you click (or the corresponding bone of the follow target in the case of a follower) to become selected if you click within the same object.

The "Root Node Only" option will always cause the root node of a figure to be selected, regardless of which object is currently selected.

Regardless of which of these options is chosen, right-clicking a node in the scene provides a context menu with selection actions that are based on what is under the cursor at the point where you clicked.

I have copied the settings from DS4, but no changes. The image shows the menu I get with a right click on the upper right arm.

How did you "[create] a G8F Figure?". Is this G8F loaded using the duf from Daz, or is it exported/imported/converted/transferred/etc?

If right-clicking the mesh is not providing named groups, it suggests the groups are not there, or not associated with the bones.

a_gus · October 23

DoctorJellybean said:

a_gus said:

Hi there.
What about a final version of Daz Studio "2025"? Daz will have to rename it in "Daz 2026"...

I believe it refers to the QT versions used.

Sound more clear for me now.
Do we have an little idea when the final version will be released?

Notifications

Daz Studio 2025 ALPHA - version 6.25.2025.32308! (Updated November 20, 2025)

Comments

Adding to Cart…