I am also a Keyshot user.
May I do some suggestions:
The first one could be an overlay displaying the real time fps in the viewport (especially in Iray render mode).
The second could be a specific tool (not necessary a complete scene to render) in order to have a reference score specifically for Daz software. That could be a precious help to compare configurations and graphic cards (even if the GPU doesn't make all) rather than a render time (on what?). That would give a precious help to choose a computer before to buy it.
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.
I have created a default G8F Figure with a default hair and anatomical elements, a default skin. This figure I loaded, changed some parameters for an individual looking, loaded a different skin, replaced the hair etc. to make an individual figure. A procedure I do since years and for a lot of figures. I reproduced the steps with the G8F-Template as well as with another modified figure in DS6: I can select the body parts like expected.
The attachment shows the right click menu in DS4, here I have the option to select the right shoulder.
Update:
I have removed the pubes, and applied it again. Since this attachment had been loaded as own item I chaged the parent to the anatomical element. With that constelation I could select the body parts like expected. So I changed the pose and noticed, that the pubes are away for the figure. So I fit it to the anatomical element. After that I have the same problem. When I load the same figure in DS4 the problem isn't there.
opening the dmp file in WinDB and clicking the !analyze -v option I get this...
...
Given the limitations of the forum formatting it would be helpful to attach the file, rather than pasting it into the body of the post - you could simply attach the whole crash-report zip file.
opening the dmp file in WinDB and clicking the !analyze -v option I get this...
...
Given the limitations of the forum formatting it would be helpful to attach the file, rather than pasting it into the body of the post - you could simply attach the whole crash-report zip file.
I really wish the next version lets us disable the "Select All" option from right click menu. Or make it work fast.
If I have a complex scene and i hit it by mistake, the app freezes for several minutes sometimes. And its usually faster just terminate daz and relaunch & load the scene again.
It is way too easy way to just freeze the whole program for an extended time by one misclick
Not sure if this is a bug, a feature that hasn't been implemented yet, or a setting I don't have correct. I attempted to render a 1 second animation at 60fps and the software can't write the file. It'll still attempt to render the entire sequence though. Log file attached.
Not sure if this is a bug, a feature that hasn't been implemented yet, or a setting I don't have correct. I attempted to render a 1 second animation at 60fps and the software can't write the file. It'll still attempt to render the entire sequence though. Log file attached.
Yeah, I've had that problem before:
2025-10-26 18:50:41.313 [INFO] :: Saved image: C:\Users\vambl\AppData\Roaming\DAZ 3D\Studio6 Public Build\temp\render\r60.png
2025-10-26 18:50:41.433 [WARNING] :: \src\sdksource\general\dzmultimediamgr.cpp(202): Exporter not found in DzMultiMediaMgr::exportVideoClip() : D:/Renders/FF Renders/./Marlene Window Test
2025-10-26 18:55:17.488 [INFO] :: Finished rendering 61 of 61 frames.
It's not very helpful. It means that you don't have a codec (an encoder in this case) for the media format you requested. The situation can be "rescued" by carefully copying the 61 frames from the first line and running them offline through an appropriate video encoder, though you will probably have to find the right Windows codec first...
Saving a scene feels slower compared to 4.x versions.
It's hard to pinpoint it, but I feel like there is a slight increase when saving simple scenes. It's not a major issue, taking forever to save. But I feel like there is something off about the ALPHA save time versus the save time for versions 4.x
Saving a scene feels slower compared to 4.x versions.
It's hard to pinpoint it, but I feel like there is a slight increase when saving simple scenes. It's not a major issue, taking forever to save. But I feel like there is something off about the ALPHA save time versus the save time for versions 4.x
I am not sure about that. I have been working recently in 4.24 recently and the initial save as is dreadfully long, and the subsequent saves take a bit. Regardless of which version 4.24 or 6.25, if I do a 'save as' I have time to go off and do something else that I have put off: trips to the bathroom, refresh my coffee cup, load laundry, stretch... But it doesn't seem longer than other versions in the past.
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
Do you mean render as a .mov file, as it should be able to?
I am also a Keyshot user.
May I do some suggestions:
The first one could be an overlay displaying the real time fps in the viewport (especially in Iray render mode).
The second could be a specific tool (not necessary a complete scene to render) in order to have a reference score specifically for Daz software. That could be a precious help to compare configurations and graphic cards (even if the GPU doesn't make all) rather than a render time (on what?). That would give a precious help to choose a computer before to buy it.
i can save a .mov file rendered with latest DS 6 on macOS 15.7.1, didn't try on macOS 26.0.1 though
Since the version "Daz Studio 2025 ALPHA - version 6.25.2025.27507! (Updated October 2, 2025)" I have the problem that DAZ crashes after a short time due to lack of system memory. In the current version "Daz Studio 2025 ALPHA - version 6.25.2025.30407! (Updated October 31, 2025)", the error is unfortunately still present. I load a simple character, move it a few times and suddenly nothing works anymore. Then an error message appears that there is no memory left. Backing up or quitting is then no longer possible. In the versions before that, I never had such a problem. Version Daz Studio 2025 ALPHA - version 6.25.2025.26119! (Updated September 19, 2025) runs without any problems.
My system: MacMini M4 with MacOS Sequoia (current release)
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?
I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.
I am also a Keyshot user.
May I do some suggestions:
The first one could be an overlay displaying the real time fps in the viewport (especially in Iray render mode).
The second could be a specific tool (not necessary a complete scene to render) in order to have a reference score specifically for Daz software. That could be a precious help to compare configurations and graphic cards (even if the GPU doesn't make all) rather than a render time (on what?). That would give a precious help to choose a computer before to buy it.
i can save a .mov file rendered with latest DS 6 on macOS 15.7.1, didn't try on macOS 26.0.1 though
Thanks for confirming that you could do it. I tried a few different paths and found that I could save successfully to my desktop, but had errors in other locations, so it might be somethng in my pathnames or other settings.
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?
I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.
Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination.
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?
I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.
Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination.
Found it: "Added camera usage description on macOS"
So, if not facial or lip sync, what might this be pertinent to?
Alpha 6.25.2025.30407 Windows not installing correctly on Win 11
The Halloween release is really scary: DIM shows an install size of -1 and as one can expect there's nothing working installed.
System:
Windows 11 Pro 24H2
AMD Ryzen 7950X
128GB RAM
Dual RTX 5090
Try uninstalling and reinstalling
Of course I tried that first
Finally it helped to manually remove the installation directory of the previous DAZ Studio 2025 version - now it's working!
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?
I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.
Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination.
Found it: "Added camera usage description on macOS"
So, if not facial or lip sync, what might this be pertinent to?
I beleive that they come as a pair, I don't hav a Mac but presumably at some point you get a permissions pop-up and I beleive that is where the usage description will come in - which may well say that this is just ancillary to the Microphone.
Since the version "Daz Studio 2025 ALPHA - version 6.25.2025.27507! (Updated October 2, 2025)" I have the problem that DAZ crashes after a short time due to lack of system memory. In the current version "Daz Studio 2025 ALPHA - version 6.25.2025.30407! (Updated October 31, 2025)", the error is unfortunately still present. I load a simple character, move it a few times and suddenly nothing works anymore. Then an error message appears that there is no memory left. Backing up or quitting is then no longer possible. In the versions before that, I never had such a problem. Version Daz Studio 2025 ALPHA - version 6.25.2025.26119! (Updated September 19, 2025) runs without any problems.
My system: MacMini M4 with MacOS Sequoia (current release)
I see the same issue - MacBook Pro M3 with MacOS Sequoia.
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?
I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.
Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination.
Found it: "Added camera usage description on macOS"
So, if not facial or lip sync, what might this be pertinent to?
I beleive that they come as a pair, I don't hav a Mac but presumably at some point you get a permissions pop-up and I beleive that is where the usage description will come in - which may well say that this is just ancillary to the Microphone.
Thanks. That could be it. No worries, I'm not getting my hopes up. I'm just glad I'm able to import video again in the latest Alpha.
Will we getting any new features like ik posing or is this more or less the same version 4 with small tweaks, updated to work with new graphic cards ?
It's a band-aid to prevent people from complaining that Daz Studio can't be used by the 50-series GPUs - why else would you release an Alpha to the general public (and it's STILL in Alpha.......)
Since the version "Daz Studio 2025 ALPHA - version 6.25.2025.27507! (Updated October 2, 2025)" I have the problem that DAZ crashes after a short time due to lack of system memory. In the current version "Daz Studio 2025 ALPHA - version 6.25.2025.30407! (Updated October 31, 2025)", the error is unfortunately still present. I load a simple character, move it a few times and suddenly nothing works anymore. Then an error message appears that there is no memory left. Backing up or quitting is then no longer possible. In the versions before that, I never had such a problem. Version Daz Studio 2025 ALPHA - version 6.25.2025.26119! (Updated September 19, 2025) runs without any problems.
My system: MacMini M4 with MacOS Sequoia (current release)
I see the same issue - MacBook Pro M3 with MacOS Sequoia.
OK, I confirmed this, the memory leak is when moving around the viewport.
Will we getting any new features like ik posing or is this more or less the same version 4 with small tweaks, updated to work with new graphic cards ?
It's a band-aid to prevent people from complaining that Daz Studio can't be used by the 50-series GPUs - why else would you release an Alpha to the general public (and it's STILL in Alpha.......)
That is not correct, the alpha build was always intended to come out around the time it did but it is a new version so there are a lot of potential clashes that need testing "in the wild" rather than on a limited number of internal or focus-group systems. Not all partsa re equally alpha, even so, but the label aplies to the whole thing for the sake of those that are.
As for new features, I am sure we will see things - but bear in mind that the later (DS 4.20+) versions of DS 4 were getting new features developed as part of the DS next-version, so there is a limit to how much new-stuff-we-haven't-already-seen Daz has ready.
Comments
It is actually Qt, my mistake.
There is no roadmap for releases.
I am also a Keyshot user.
May I do some suggestions:
I have created a default G8F Figure with a default hair and anatomical elements, a default skin. This figure I loaded, changed some parameters for an individual looking, loaded a different skin, replaced the hair etc. to make an individual figure. A procedure I do since years and for a lot of figures. I reproduced the steps with the G8F-Template as well as with another modified figure in DS6: I can select the body parts like expected.
The attachment shows the right click menu in DS4, here I have the option to select the right shoulder.
Update:
I have removed the pubes, and applied it again. Since this attachment had been loaded as own item I chaged the parent to the anatomical element. With that constelation I could select the body parts like expected. So I changed the pose and noticed, that the pubes are away for the figure. So I fit it to the anatomical element. After that I have the same problem. When I load the same figure in DS4 the problem isn't there.
Given the limitations of the forum formatting it would be helpful to attach the file, rather than pasting it into the body of the post - you could simply attach the whole crash-report zip file.
I did :)
https://www.daz3d.com/forums/discussion/comment/9339191/#Comment_9339191
It's 2 posts up from the one you quoted.
I don't see anything in the viewport... only filament and iray are working.
I know it's still alpha and I know my PC is not good(AMD - Ryzen/Radeon), but Blender 5 alpha works like a charm! So I guess the problem is not my PC.
I really wish the next version lets us disable the "Select All" option from right click menu. Or make it work fast.
If I have a complex scene and i hit it by mistake, the app freezes for several minutes sometimes. And its usually faster just terminate daz and relaunch & load the scene again.
It is way too easy way to just freeze the whole program for an extended time by one misclick
Not sure if this is a bug, a feature that hasn't been implemented yet, or a setting I don't have correct. I attempted to render a 1 second animation at 60fps and the software can't write the file. It'll still attempt to render the entire sequence though. Log file attached.
Yeah, I've had that problem before:
It's not very helpful. It means that you don't have a codec (an encoder in this case) for the media format you requested. The situation can be "rescued" by carefully copying the 61 frames from the first line and running them offline through an appropriate video encoder, though you will probably have to find the right Windows codec first...
Saving a scene feels slower compared to 4.x versions.
It's hard to pinpoint it, but I feel like there is a slight increase when saving simple scenes. It's not a major issue, taking forever to save. But I feel like there is something off about the ALPHA save time versus the save time for versions 4.x
I am not sure about that. I have been working recently in 4.24 recently and the initial save as is dreadfully long, and the subsequent saves take a bit. Regardless of which version 4.24 or 6.25, if I do a 'save as' I have time to go off and do something else that I have put off: trips to the bathroom, refresh my coffee cup, load laundry, stretch... But it doesn't seem longer than other versions in the past.
Regarding: version 6.25.2025.30407 (October 31st) Mac version:
1. I can select and import audio files again.
2. I still can't save a .mov file (as others have mentioned), so I'm back to converting multiple frames from the temp folder to a single .mov file and then add the audio to it. It's a minor irritant, but versions 6.25.2025.21707 (August 5, 2025) and 6.25.2025.22607 (August 14, 2025) saved a single .mov file that I could open in iMovie with audio and video all in one file.
I see lots of references to AI, Vicky, accents and Mac camera and microphone in the log, is this going to be for new lip sync?
Do you mean render as a .mov file, as it should be able to?
i can save a .mov file rendered with latest DS 6 on macOS 15.7.1, didn't try on macOS 26.0.1 though
Alpha 6.25.2025.30407 Windows not installing correctly on Win 11
The Halloween release is really scary: DIM shows an install size of -1 and as one can expect there's nothing working installed.
System:
Windows 11 Pro 24H2
AMD Ryzen 7950X
128GB RAM
Dual RTX 5090
Hello!
Since the version "Daz Studio 2025 ALPHA - version 6.25.2025.27507! (Updated October 2, 2025)" I have the problem that DAZ crashes after a short time due to lack of system memory. In the current version "Daz Studio 2025 ALPHA - version 6.25.2025.30407! (Updated October 31, 2025)", the error is unfortunately still present. I load a simple character, move it a few times and suddenly nothing works anymore. Then an error message appears that there is no memory left. Backing up or quitting is then no longer possible. In the versions before that, I never had such a problem. Version Daz Studio 2025 ALPHA - version 6.25.2025.26119! (Updated September 19, 2025) runs without any problems.
My system: MacMini M4 with MacOS Sequoia (current release)
I don't know about lots, but there is mention that the AI Chat pane is the Vicky Bot from the store - and that supports voice interaction which is the context for the microphone reference. I don't know anything about lip synch, but the log entries definitely don't relate to anything like that. Sorry it isn't good news.
Try uninstalling and reinstalling
Thanks for confirming that you could do it. I tried a few different paths and found that I could save successfully to my desktop, but had errors in other locations, so it might be somethng in my pathnames or other settings.
Thanks Richard; I can't seem to access the logs at the moment, but I thought I saw reference to the Mac camera last night and I'm not sure what the computer's camera would be used for other than for some sort of facial or lip sync. I'll try again later to confirm that it wasn't my (almost always) overblown imagination.
Found it:
"Added camera usage description on macOS"
So, if not facial or lip sync, what might this be pertinent to?
Of course I tried that first
Finally it helped to manually remove the installation directory of the previous DAZ Studio 2025 version - now it's working!
I beleive that they come as a pair, I don't hav a Mac but presumably at some point you get a permissions pop-up and I beleive that is where the usage description will come in - which may well say that this is just ancillary to the Microphone.
I see the same issue - MacBook Pro M3 with MacOS Sequoia.
Thanks. That could be it. No worries, I'm not getting my hopes up. I'm just glad I'm able to import video again in the latest Alpha.
Will we getting any new features like ik posing or is this more or less the same version 4 with small tweaks, updated to work with new graphic cards ?
It's a band-aid to prevent people from complaining that Daz Studio can't be used by the 50-series GPUs - why else would you release an Alpha to the general public (and it's STILL in Alpha.......)
RTX 5080 – Iray GPU dead in Daz Studio 4.24 & 6.25 ALPHA
Hi guys, stuck with a fresh RTX 5080 (desktop, Blackwell, 16 GB, Compute 12.0).
Setup:
Problem:
What I tried:
Asking 50-series users:
Just want GPU rendering back. Any “worked for me with build X + driver Y” tips would be gold. Thanks!
OK, I confirmed this, the memory leak is when moving around the viewport.
That is not correct, the alpha build was always intended to come out around the time it did but it is a new version so there are a lot of potential clashes that need testing "in the wild" rather than on a limited number of internal or focus-group systems. Not all partsa re equally alpha, even so, but the label aplies to the whole thing for the sake of those that are.
As for new features, I am sure we will see things - but bear in mind that the later (DS 4.20+) versions of DS 4 were getting new features developed as part of the DS next-version, so there is a limit to how much new-stuff-we-haven't-already-seen Daz has ready.