It seems that I am not the only one who experiences this, but this issue obviously does not apply to everyone. After I have updated to the latest DAZ Studio version, the Iray preview doesn't work properly, it flickers. In the first few seconds it still shows a few glimpses of Iray view but after like 10 seconds it's only smooth shaded view (grey scale). Only when I change something it starts to flicker again and sometimes shows the Iray preview in between the permanent smooth shaded view.
I have updated my Nvidia drivers. I have a 2080Ti.
It probably is no use to complain about the fact that the color option on the dials has been removed (is "dial" the proper term? I mean the sliding control knobs for translate, rotate and scale). That was such a great help in finding the right dial. Now it is all flat with the same color and it takes a lot more time to find the right dial.
It seems that I am not the only one who experiences this, but this issue obviously does not apply to everyone. After I have updated to the latest DAZ Studio version, the Iray preview doesn't work properly, it flickers. In the first few seconds it still shows a few glimpses of Iray view but after like 10 seconds it's only smooth shaded view (grey scale). Only when I change something it starts to flicker again and sometimes shows the Iray preview in between the permanent smooth shaded view.
I have updated my Nvidia drivers. I have a 2080Ti.
Do you have a GPU on the CPU (Intel or AMD)? If so, which is draswing the application UI (check nVidia Control Panel)
It probably is no use to complain about the fact that the color option on the dials has been removed (is "dial" the proper term? I mean the sliding control knobs for translate, rotate and scale). That was such a great help in finding the right dial. Now it is all flat with the same color and it takes a lot more time to find the right dial.
Today I was working on a project, by selecting a "Edit a strand-based hair" in the menu, I probably should not be doing this because I knew it won't load, and yes, it didn't load anything. But a very strainge thing happened. The Nvidia Iray preview on the viewport stopped working at all, even not creating any default environment or anything. No log in the logfile at all.
I tried re-install the program and it was not working at all, cannot fix. But eventually I fixed this issue all by myself.
The way I fixed, is cleaned up all the files in the my user roaming folders. Then startup the program fresh and the iray preview worked again. So I tried to narrow down what caused the issue by replacing the backup files one by one. At last I found out it was the file "layout.dsx" caused this problem. But I cannot understand why.
Is there a way to rename managed pages to a single letter? H for Hair, S for Shape, F for Figures, so they can be ganged up in a single workspace without too much clutter and we will know what is preferably in each managed page. The tab label names are really long and the UI does not abbreviate them when stacked together.
It would be nice to be able to layer a long bar of managed pages horizontally up "above" the viewport area.
UPDATE:
Okay, I found a way to use one managed page and drop others into it to create an independent workspace that can be dropped above the viewport and smart content etc. workspaces for a horizontal display of custom content. What is nice is it can be completely hidden and unhidden with one click on the tab edge button. The only lingering problem is the Managed Pages, their names are too long and a one letter name or number would be preferable with tabs that resize to tiny tabs. It would be helpful to have like 20 "tiny" tabs as a hideable horizontal row along the top above all other workspaces. These Managed Pages are a great replacement for Visual Menus which would not allow you to click scene elements while the script was open. Managed Pages are MUCH easier to customize and use as well.
Is there a way to rename managed pages to a single letter? H for Hair, S for Shape, F for Figures, so they can be ganged up in a single workspace without too much clutter and we will know what is preferably in each managed page. The tab label names are really long and the UI does not abbreviate them when stacked together.
It would be nice to be able to layer a long bar of managed pages horizontally up "above" the viewport area.
UPDATE:
Okay, I found a way to use one managed page and drop others into it to create an independent workspace that can be dropped above the viewport and smart content etc. workspaces for a horizontal display of custom content. What is nice is it can be completely hidden and unhidden with one click on the tab edge button. The only lingering problem is the Managed Pages, their names are too long and a one letter name or number would be preferable with tabs that resize to tiny tabs. It would be helpful to have like 20 "tiny" tabs as a hideable horizontal row along the top above all other workspaces. These Managed Pages are a great replacement for Visual Menus which would not allow you to click scene elements while the script was open. Managed Pages are MUCH easier to customize and use as well.
The duplicate pages are labelled Manage (#) because they the content management pane, rather than because they are "managed". It isn't currently possible to relabel them, whether that will be supported in future is not kown. Don't forget that each page is still fully navigable, so for geenral users such a renaming system would just be confusing, though of course if we do get some kind of relabel feature in future you could use it as you wished.
Is there a way to rename managed pages to a single letter? H for Hair, S for Shape, F for Figures, so they can be ganged up in a single workspace without too much clutter and we will know what is preferably in each managed page. The tab label names are really long and the UI does not abbreviate them when stacked together.
It would be nice to be able to layer a long bar of managed pages horizontally up "above" the viewport area.
UPDATE:
Okay, I found a way to use one managed page and drop others into it to create an independent workspace that can be dropped above the viewport and smart content etc. workspaces for a horizontal display of custom content. What is nice is it can be completely hidden and unhidden with one click on the tab edge button. The only lingering problem is the Managed Pages, their names are too long and a one letter name or number would be preferable with tabs that resize to tiny tabs. It would be helpful to have like 20 "tiny" tabs as a hideable horizontal row along the top above all other workspaces. These Managed Pages are a great replacement for Visual Menus which would not allow you to click scene elements while the script was open. Managed Pages are MUCH easier to customize and use as well.
The duplicate pages are labelled Manage (#) because they the content management pane, rather than because they are "managed". It isn't currently possible to relabel them, whether that will be supported in future is not kown. Don't forget that each page is still fully navigable, so for geenral users such a renaming system would just be confusing, though of course if we do get some kind of relabel feature in future you could use it as you wished.
I am very excited about the new Manage Pages feature, though each page is fully navigable, naming them and using them in a semi-static way is very appealing as well. I hope naming them is something the developers can add. Manage Pages (tabbed pages) is a very useful feature! Thx!
I do have an issue with the custom assets added to the pages showing up duplicated in the manage pages. Often, one has a label and one does not. If I delete either one, the other dissappears as well. Only certain assets duplicate. I would like to understad why as eliminating this problem would make the page less cluttered.
If I could suggest another feature for V6, when you are in the content library and you type a search word in the search bar above. The search bar should search in the selected folder below and not always default to a global search of the entire library.
(maybe i am interpreting how the search works wrong)
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Is there a way to rename managed pages to a single letter? H for Hair, S for Shape, F for Figures, so they can be ganged up in a single workspace without too much clutter and we will know what is preferably in each managed page. The tab label names are really long and the UI does not abbreviate them when stacked together.
It would be nice to be able to layer a long bar of managed pages horizontally up "above" the viewport area.
UPDATE:
Okay, I found a way to use one managed page and drop others into it to create an independent workspace that can be dropped above the viewport and smart content etc. workspaces for a horizontal display of custom content. What is nice is it can be completely hidden and unhidden with one click on the tab edge button. The only lingering problem is the Managed Pages, their names are too long and a one letter name or number would be preferable with tabs that resize to tiny tabs. It would be helpful to have like 20 "tiny" tabs as a hideable horizontal row along the top above all other workspaces. These Managed Pages are a great replacement for Visual Menus which would not allow you to click scene elements while the script was open. Managed Pages are MUCH easier to customize and use as well.
The duplicate pages are labelled Manage (#) because they the content management pane, rather than because they are "managed". It isn't currently possible to relabel them, whether that will be supported in future is not kown. Don't forget that each page is still fully navigable, so for geenral users such a renaming system would just be confusing, though of course if we do get some kind of relabel feature in future you could use it as you wished.
I am very excited about the new Manage Pages feature, though each page is fully navigable, naming them and using them in a semi-static way is very appealing as well. I hope naming them is something the developers can add. Manage Pages (tabbed pages) is a very useful feature! Thx!
I do have an issue with the custom assets added to the pages showing up duplicated in the manage pages. Often, one has a label and one does not. If I delete either one, the other dissappears as well. Only certain assets duplicate. I would like to understad why as eliminating this problem would make the page less cluttered.
I don't know why you are getting those duplicates - though the lack of type tags (the bit at top-right saying what kind of content they are) does suggest some oddities or issues with the content management system's data.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Richard, the installed Intel UHD630 driver is OpenGL 4.5, but I cannot find any information about what GLSL version it is, but I would presume that it is also 4.5.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Richard, the installed Intel UHD630 driver is OpenGL 4.5, but I cannot find any information about what GLSL version it is, but I would presume that it is also 4.5.
The screenshot on your post shows the OpeGL version as 4.1
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Richard, the installed Intel UHD630 driver is OpenGL 4.5, but I cannot find any information about what GLSL version it is, but I would presume that it is also 4.5.
The screenshot on your post shows the OpeGL version as 4.1
These are the specs for UHD630, it clearly states OpenGL as 4..5. Now I know next to nothing about how Intel drivers work but OpenGL 4.5 has been supported in Intel drivers since Build version 25.20.100.6861. Does one have to jump through any specific "hoops" in order to get the 4.5 driver to be installed or recognised?
GPU Specifications
GPU Name‡ Intel® UHD Graphics 630
Graphics Base Frequency 350 MHz
Graphics Max Dynamic Frequency 1.05 GHz
Graphics Video Max Memory 64 GB
4K Support Yes, at 60Hz
Max Resolution (HDMI)‡ 4096 x 2304@24Hz
Max Resolution (DP)‡ 4096 x 2304@60Hz
Max Resolution (eDP - Integrated Flat Panel)‡ 4096 x 2304@60Hz
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Richard, the installed Intel UHD630 driver is OpenGL 4.5, but I cannot find any information about what GLSL version it is, but I would presume that it is also 4.5.
The screenshot on your post shows the OpeGL version as 4.1
These are the specs for UHD630, it clearly states OpenGL as 4..5. Now I know next to nothing about how Intel drivers work but OpenGL 4.5 has been supported in Intel drivers since Build version 25.20.100.6861. Does one have to jump through any specific "hoops" in order to get the 4.5 driver to be installed or recognised?
In a hope of further investigating the Intel graphics assue, i have downloaded and run the GLview Extensions Viewer, and it appears to confirm that the insalled driver is indeed OpenGL 4.5 compliant.
As DS2025 is not showing any OpenGL , and DS4.24 is showing OpenGL as only 4.1, is it all possible that DS historically has not been reading/setting the correct OpenGL version from/in the Intel driver?
I would be very interested to hear from other users with Intel integrated grachics that are experiencing the Grey Viewport issue, if they get similar results from GLview Extensions Viewer.
Now as I said above, this area is completely foreign to me, so I could be totaly missunderstanding the situation, and would therefore appreciate the input of those who know more about the subject than I do.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Is this why the viewport in 2025 is so laggy? I tested both version 4.24 and 2025 on the same computer (5090 & 9950X3D), opening the same scene. The FPS in 4.24 was perfect (above 60), but in 2025, it was completely lag, with FPS dropping to around 1~5.
Is there any way to fix this issue? I know 2025 is still in testing, but I’m really worried that this might be an unfixable problem. It’s a serious issue — working in this state is almost unbearable.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Is this why the viewport in 2025 is so laggy? I tested both version 4.24 and 2025 on the same computer (5090 & 9950X3D), opening the same scene. The FPS in 4.24 was perfect (above 60), but in 2025, it was completely lag, with FPS dropping to around 1~5.
Is there any way to fix this issue? I know 2025 is still in testing, but I’m really worried that this might be an unfixable problem. It’s a serious issue — working in this state is almost unbearable.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Is this why the viewport in 2025 is so laggy? I tested both version 4.24 and 2025 on the same computer (5090 & 9950X3D), opening the same scene. The FPS in 4.24 was perfect (above 60), but in 2025, it was completely lag, with FPS dropping to around 1~5.
Is there any way to fix this issue? I know 2025 is still in testing, but I’m really worried that this might be an unfixable problem. It’s a serious issue — working in this state is almost unbearable.
It is still a W.I.P.
Surely you realize how unacceptable this is, even for an alpha. Especially since these people intentionally didn't work on supporting 50 series GPUs with 4.24, putting a lot of creators in a difficult place.
Hi Sorry if this has been answered already, but is anyone else having issues with making movies in the Alpha?
I make a lot of animations and have recently upgraded to a RTX5070ti. So I've downloaded alpha 6.25 as it supports this card (and it works fantastivally by the way. Render times are WAY faster)
However whenever I try to render a Movie, it goes through the full render process, and then gives me an error message saying it cannot save the file (I tried to attach the screenshot but it jjust gets stuck on UPLOADING). The mesage says:
"Error Saving File
The Render could not be saved.
Try again ro choose a new file name"
It wont let me save the file anywhere. All my drives have room and I'm using the same download folders I always have for my animations (The standard Render Library loacation). However it just gives the error message. I've tried all different names with no special characters, and still nothing.
It wont let me choose the type of fie it saves as, it jst says "all files" and then says it cannot save. The message just keeps repeating every time I try.
So I couldn't even save the file as a random thing then convert to .avi, as it just won't let me save.
I've tried going back to Daz 4.24 and that works fine (but much, much, slower as it doesn't use my graphics card to render). So the issue definately seems to be the Daz Alpha.
I know that Animate isn't integrated yet, but it should still be able to render movies right? The option is still there.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Is this why the viewport in 2025 is so laggy? I tested both version 4.24 and 2025 on the same computer (5090 & 9950X3D), opening the same scene. The FPS in 4.24 was perfect (above 60), but in 2025, it was completely lag, with FPS dropping to around 1~5.
Is there any way to fix this issue? I know 2025 is still in testing, but I’m really worried that this might be an unfixable problem. It’s a serious issue — working in this state is almost unbearable.
It is still a W.I.P.
Surely you realize how unacceptable this is, even for an alpha. Especially since these people intentionally didn't work on supporting 50 series GPUs with 4.24, putting a lot of creators in a difficult place.
I know it's still a W.I.P., but I smell "structural problem." If it's something that can be fixed in a few months, then that would be ideal—and maybe even a good reason to subscribe to Premium. But if it's something that might never be fixed, or could take years, then starting to learn Blender early on might be the better choice.
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
Is this why the viewport in 2025 is so laggy? I tested both version 4.24 and 2025 on the same computer (5090 & 9950X3D), opening the same scene. The FPS in 4.24 was perfect (above 60), but in 2025, it was completely lag, with FPS dropping to around 1~5.
Is there any way to fix this issue? I know 2025 is still in testing, but I’m really worried that this might be an unfixable problem. It’s a serious issue — working in this state is almost unbearable.
It is still a W.I.P.
Surely you realize how unacceptable this is, even for an alpha. Especially since these people intentionally didn't work on supporting 50 series GPUs with 4.24, putting a lot of creators in a difficult place.
If by "these people" you mean Daz then it wasn't their choice - as has been explained in various places, the only version of Iray that supported 50x0 cards and was potentially compatible with DS 4.x.x.x (Iray version 2024.0) had bugs and after testing was reverted to a previous build. iray version 2024.1 fixed the issues, but is not compatible with DS 4.x.x.x and cannot be made compatible - it requires changes that would give the same broken plug-ins as DS 2025.
Hi Sorry if this has been answered already, but is anyone else having issues with making movies in the Alpha?
I make a lot of animations and have recently upgraded to a RTX5070ti. So I've downloaded alpha 6.25 as it supports this card (and it works fantastivally by the way. Render times are WAY faster)
However whenever I try to render a Movie, it goes through the full render process, and then gives me an error message saying it cannot save the file (I tried to attach the screenshot but it jjust gets stuck on UPLOADING). The mesage says:
"Error Saving File
The Render could not be saved.
Try again ro choose a new file name"
It wont let me save the file anywhere. All my drives have room and I'm using the same download folders I always have for my animations (The standard Render Library loacation). However it just gives the error message. I've tried all different names with no special characters, and still nothing.
It wont let me choose the type of fie it saves as, it jst says "all files" and then says it cannot save. The message just keeps repeating every time I try.
So I couldn't even save the file as a random thing then convert to .avi, as it just won't let me save.
I've tried going back to Daz 4.24 and that works fine (but much, much, slower as it doesn't use my graphics card to render). So the issue definately seems to be the Daz Alpha.
I know that Animate isn't integrated yet, but it should still be able to render movies right? The option is still there.
Thank you.
Have you tried rendering to an image sequence instead of a movie, then assembling the images in a dedicated video application? This is an issue affecting at least some users, though I thought there had been changes relating to this in the log - make sure you are using the current build.
Hi Sorry if this has been answered already, but is anyone else having issues with making movies in the Alpha?
I make a lot of animations and have recently upgraded to a RTX5070ti. So I've downloaded alpha 6.25 as it supports this card (and it works fantastivally by the way. Render times are WAY faster)
However whenever I try to render a Movie, it goes through the full render process, and then gives me an error message saying it cannot save the file (I tried to attach the screenshot but it jjust gets stuck on UPLOADING). The mesage says:
"Error Saving File
The Render could not be saved.
Try again ro choose a new file name"
It wont let me save the file anywhere. All my drives have room and I'm using the same download folders I always have for my animations (The standard Render Library loacation). However it just gives the error message. I've tried all different names with no special characters, and still nothing.
It wont let me choose the type of fie it saves as, it jst says "all files" and then says it cannot save. The message just keeps repeating every time I try.
So I couldn't even save the file as a random thing then convert to .avi, as it just won't let me save.
I've tried going back to Daz 4.24 and that works fine (but much, much, slower as it doesn't use my graphics card to render). So the issue definately seems to be the Daz Alpha.
I know that Animate isn't integrated yet, but it should still be able to render movies right? The option is still there.
Thank you.
Have you tried rendering to an image sequence instead of a movie, then assembling the images in a dedicated video application? This is an issue affecting at least some users, though I thought there had been changes relating to this in the log - make sure you are using the current build.
Thanks for the response! I can't see a newer version come up in the DAZ installer. What's the latest version? Mine is 6.25.2025 14115 (According to the About DAZ option under help).
I will try the still image render. Do you know what programmeas would be good for putting tem together easily?
Comments
It seems that I am not the only one who experiences this, but this issue obviously does not apply to everyone. After I have updated to the latest DAZ Studio version, the Iray preview doesn't work properly, it flickers. In the first few seconds it still shows a few glimpses of Iray view but after like 10 seconds it's only smooth shaded view (grey scale). Only when I change something it starts to flicker again and sometimes shows the Iray preview in between the permanent smooth shaded view.
I have updated my Nvidia drivers. I have a 2080Ti.
It probably is no use to complain about the fact that the color option on the dials has been removed (is "dial" the proper term? I mean the sliding control knobs for translate, rotate and scale). That was such a great help in finding the right dial. Now it is all flat with the same color and it takes a lot more time to find the right dial.
Hello all. I just installed 2025 ALPHA and note that I cannot export MDD files. Has this capability been dropped? THANK YOU FOR ANY INFO YOU HAVE.
Do you have a GPU on the CPU (Intel or AMD)? If so, which is draswing the application UI (check nVidia Control Panel)
https://www.daz3d.com/forums/discussion/comment/9155256/#Comment_9155256
According to this https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen#latest
Animate is still pending update.
Note that Animate 2 has not (yet) been updated to work with the Alpha. See https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen#latest
At least it means they will bring it to DAZ Studio 6.
I don't know that that is certain, though it is possible that the original wording was more qualiified than merely pending so perhaps a good sign.
I'd like to report an issue for studio 6 alpha.
Today I was working on a project, by selecting a "Edit a strand-based hair" in the menu, I probably should not be doing this because I knew it won't load, and yes, it didn't load anything. But a very strainge thing happened. The Nvidia Iray preview on the viewport stopped working at all, even not creating any default environment or anything. No log in the logfile at all.
I tried re-install the program and it was not working at all, cannot fix. But eventually I fixed this issue all by myself.
The way I fixed, is cleaned up all the files in the my user roaming folders. Then startup the program fresh and the iray preview worked again. So I tried to narrow down what caused the issue by replacing the backup files one by one. At last I found out it was the file "layout.dsx" caused this problem. But I cannot understand why.
Are you sure the Viewport pane was not simply closed?
I don't think so. I don't think I ever knew how to close it on my own...
Is there a way to rename managed pages to a single letter? H for Hair, S for Shape, F for Figures, so they can be ganged up in a single workspace without too much clutter and we will know what is preferably in each managed page. The tab label names are really long and the UI does not abbreviate them when stacked together.
It would be nice to be able to layer a long bar of managed pages horizontally up "above" the viewport area.
UPDATE:
Okay, I found a way to use one managed page and drop others into it to create an independent workspace that can be dropped above the viewport and smart content etc. workspaces for a horizontal display of custom content. What is nice is it can be completely hidden and unhidden with one click on the tab edge button. The only lingering problem is the Managed Pages, their names are too long and a one letter name or number would be preferable with tabs that resize to tiny tabs. It would be helpful to have like 20 "tiny" tabs as a hideable horizontal row along the top above all other workspaces. These Managed Pages are a great replacement for Visual Menus which would not allow you to click scene elements while the script was open. Managed Pages are MUCH easier to customize and use as well.
The duplicate pages are labelled Manage (#) because they the content management pane, rather than because they are "managed". It isn't currently possible to relabel them, whether that will be supported in future is not kown. Don't forget that each page is still fully navigable, so for geenral users such a renaming system would just be confusing, though of course if we do get some kind of relabel feature in future you could use it as you wished.
I am very excited about the new Manage Pages feature, though each page is fully navigable, naming them and using them in a semi-static way is very appealing as well. I hope naming them is something the developers can add. Manage Pages (tabbed pages) is a very useful feature! Thx!
I do have an issue with the custom assets added to the pages showing up duplicated in the manage pages. Often, one has a label and one does not. If I delete either one, the other dissappears as well. Only certain assets duplicate. I would like to understad why as eliminating this problem would make the page less cluttered.
If I could suggest another feature for V6, when you are in the content library and you type a search word in the search bar above. The search bar should search in the selected folder below and not always default to a global search of the entire library.
(maybe i am interpreting how the search works wrong)
I am experiencing the grey viewport issue in DS 2025 latest version (Windows 11 Home on Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz 2.90 GHz with integrated Intel UHD Graphics 630, and Installed RAM 16.0 GB (15.8 GB usable)), and I think that I have identified the probable cause of the issue.
As you can see from the attached screenshot, DS2025 is not reading /processing the Intel driver in the same way that DS4.24 General & DS4.24 Beta are. Both DS4.24 versions are showing full support for the Intel Hardware features, whereas DS2025 is only showing Hardware Anti-Aliasing as being supported.
Hopefully this information will assist the developers in resolving the issue with using Intel integrated graphics with DS2025.
I don't know why you are getting those duplicates - though the lack of type tags (the bit at top-right saying what kind of content they are) does suggest some oddities or issues with the content management system's data.
The Viewport code has been rewritten entirely, and as a result now has higher requirements - for OpenGL Shading Language (GLSL). See https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen#latest
Richard, the installed Intel UHD630 driver is OpenGL 4.5, but I cannot find any information about what GLSL version it is, but I would presume that it is also 4.5.
The screenshot on your post shows the OpeGL version as 4.1
Well according to https://www.intel.com/content/www/us/en/products/sku/134898/intel-core-i59400-processor-9m-cache-up-to-4-10-ghz/specifications.html?wapkw=i5-9400
These are the specs for UHD630, it clearly states OpenGL as 4..5. Now I know next to nothing about how Intel drivers work but OpenGL 4.5 has been supported in Intel drivers since Build version 25.20.100.6861. Does one have to jump through any specific "hoops" in order to get the 4.5 driver to be installed or recognised?
GPU Specifications
GPU Name‡ Intel® UHD Graphics 630
Graphics Base Frequency 350 MHz
Graphics Max Dynamic Frequency 1.05 GHz
Graphics Video Max Memory 64 GB
4K Support Yes, at 60Hz
Max Resolution (HDMI)‡ 4096 x 2304@24Hz
Max Resolution (DP)‡ 4096 x 2304@60Hz
Max Resolution (eDP - Integrated Flat Panel)‡ 4096 x 2304@60Hz
DirectX* Support 12
OpenGL* Support 4.5
Intel® Quick Sync Video Yes
Intel® InTru™ 3D Technology Yes
Intel® Clear Video HD Technology Yes
Intel® Clear Video Technology Yes
# of Displays Supported ‡3
Device ID 0X3E98/x92
In a hope of further investigating the Intel graphics assue, i have downloaded and run the GLview Extensions Viewer, and it appears to confirm that the insalled driver is indeed OpenGL 4.5 compliant.
As DS2025 is not showing any OpenGL , and DS4.24 is showing OpenGL as only 4.1, is it all possible that DS historically has not been reading/setting the correct OpenGL version from/in the Intel driver?
I would be very interested to hear from other users with Intel integrated grachics that are experiencing the Grey Viewport issue, if they get similar results from GLview Extensions Viewer.
Now as I said above, this area is completely foreign to me, so I could be totaly missunderstanding the situation, and would therefore appreciate the input of those who know more about the subject than I do.
Is this why the viewport in 2025 is so laggy? I tested both version 4.24 and 2025 on the same computer (5090 & 9950X3D), opening the same scene. The FPS in 4.24 was perfect (above 60), but in 2025, it was completely lag, with FPS dropping to around 1~5.
Is there any way to fix this issue? I know 2025 is still in testing, but I’m really worried that this might be an unfixable problem. It’s a serious issue — working in this state is almost unbearable.
It is still a W.I.P.
Surely you realize how unacceptable this is, even for an alpha. Especially since these people intentionally didn't work on supporting 50 series GPUs with 4.24, putting a lot of creators in a difficult place.
Hi Sorry if this has been answered already, but is anyone else having issues with making movies in the Alpha?
I make a lot of animations and have recently upgraded to a RTX5070ti. So I've downloaded alpha 6.25 as it supports this card (and it works fantastivally by the way. Render times are WAY faster)
However whenever I try to render a Movie, it goes through the full render process, and then gives me an error message saying it cannot save the file (I tried to attach the screenshot but it jjust gets stuck on UPLOADING). The mesage says:
"Error Saving File
The Render could not be saved.
Try again ro choose a new file name"
It wont let me save the file anywhere. All my drives have room and I'm using the same download folders I always have for my animations (The standard Render Library loacation). However it just gives the error message. I've tried all different names with no special characters, and still nothing.
It wont let me choose the type of fie it saves as, it jst says "all files" and then says it cannot save. The message just keeps repeating every time I try.
So I couldn't even save the file as a random thing then convert to .avi, as it just won't let me save.
I've tried going back to Daz 4.24 and that works fine (but much, much, slower as it doesn't use my graphics card to render). So the issue definately seems to be the Daz Alpha.
I know that Animate isn't integrated yet, but it should still be able to render movies right? The option is still there.
Thank you.
I know it's still a W.I.P., but I smell "structural problem." If it's something that can be fixed in a few months, then that would be ideal—and maybe even a good reason to subscribe to Premium. But if it's something that might never be fixed, or could take years, then starting to learn Blender early on might be the better choice.
If by "these people" you mean Daz then it wasn't their choice - as has been explained in various places, the only version of Iray that supported 50x0 cards and was potentially compatible with DS 4.x.x.x (Iray version 2024.0) had bugs and after testing was reverted to a previous build. iray version 2024.1 fixed the issues, but is not compatible with DS 4.x.x.x and cannot be made compatible - it requires changes that would give the same broken plug-ins as DS 2025.
Have you tried rendering to an image sequence instead of a movie, then assembling the images in a dedicated video application? This is an issue affecting at least some users, though I thought there had been changes relating to this in the log - make sure you are using the current build.
Thanks for the response! I can't see a newer version come up in the DAZ installer. What's the latest version? Mine is 6.25.2025 14115 (According to the About DAZ option under help).
I will try the still image render. Do you know what programmeas would be good for putting tem together easily?
Thank you again.
II don't do much aniamting, but I beleive Blender can do it and I am sure there are other free/open source options.