>And did you map the content paths as they are for DS4 in 2025 ALPHA? -- Yes I verified content paths are where I previously had them
>Install PostgreSQL and the 4.24 update and try again. Make sure there are no instances of any DS version running -- I did this but still not able to load those specific GEN 4 characters -- I do have 3 different versions of DAZ Studio now. See attached pix
wsterdan,
>One other thing you might try: click on the character you want to load into the scene and drag it from the library into the scene and see if that triggers it. -- Nothing happens, not even any error messages -- Thanks for the tip, I didn't know u could drag & drop!!
@vicster56 Assuming you have 4.24 installed, and that you are able to load Gen 4 characters in that: load a Gen 4 character in 4.24, save it as a scene and open that scene in 2025 ALPHA. Does the scene load as expected?
>Assuming you have 4.24 installed, and that you are able to load Gen 4 characters in that: load a Gen 4 character in 4.24, save it as a scene and open that scene in 2025 ALPHA. Does the scene load as expected? I'll try that!!
Is there updated scripting reference that I can check? I had to upgrade to RTX5090 but my complex script is not working anymore in alpha version.I see in the changelog that there are updates to public API documentation but I can't find it anywhere for new Daz Studio.
Is there updated scripting reference that I can check? I had to upgrade to RTX5090 but my complex script is not working anymore in alpha version.I see in the changelog that there are updates to public API documentation but I can't find it anywhere for new Daz Studio.
Is there updated scripting reference that I can check? I had to upgrade to RTX5090 but my complex script is not working anymore in alpha version.I see in the changelog that there are updates to public API documentation but I can't find it anywhere for new Daz Studio.
The API documentation is updated ready but not released until it is the current General Release, or at least more stable than an alpha buiild (if you look at the chnage log you will see some things have been listed and then struck through).
Can we please for the love of all that's holy get support for Intel or AMD cards. PLEASE!
If you mean for rendering that is a limitation of Iray. Not Daz Studio. Iray is made by Nvidia and thus requires Nvidia hardware. If you mean fo ranythign else I can;t comment on that since I'm on (resentfully) Nvidia hardware.
Can we please for the love of all that's holy get support for Intel or AMD cards. PLEASE!
AMD and Intel cards, as much as I know, works fine with Filament and 3Delight. IRay is bound to NVidia cards because it needs CUDA cores to work, that can be found only on NVidia cards.
There is some kind of special driver that emulates CUDA cores on AMD cards but IRay doesn't work on that method.
@Richard In this latest Alpha rendering a movie doesn't work -- it renders all frames but then it says:
Error saving the file: "whatever_path_and_name_you_used" The render could not be saved. Try again or choose a new file name. [Try Again][Choose new file][Cancel]
The only error I see in the log related to it is this:
2025-05-20 16:46:35.767 [WARNING] :: \src\sdksource\basictypes\dzfilefilter.cpp(277): Index out of range in DzFileFilter::getFilterDescription()
What I take from that error it seems to refer to the windows file dialog which only has All Files (*.*) option, and before that dialog you don't get any prompt to chose compression for the video like you did before that.
@Richard In this latest Alpha rendering a movie doesn't work -- it renders all frames but then it says:
Error saving the file: "whatever_path_and_name_you_used" The render could not be saved. Try again or choose a new file name. [Try Again][Choose new file][Cancel]
The only error I see in the log related to it is this:
2025-05-20 16:46:35.767 [WARNING] :: \src\sdksource\basictypes\dzfilefilter.cpp(277): Index out of range in DzFileFilter::getFilterDescription()
What I take from that error it seems to refer to the windows file dialog which only has All Files (*.*) option, and before that dialog you don't get any prompt to chose compression for the video like you did before that.
One possibility that was raised on a previous occasion is security software blocking /bin/ffmpeg.exe in the Daz Studio application folder, which might well disable the extension and so mean it wasn't in the list to be retrieved with the consequence being that error message. It is geenally considered better to just render the image sequence and then assemble it into a movie later.
it's the same scene but this time crashed the application after 7 hours (i was away...).
It's not a complex scene and i have a 5080 16gb.
any ideas?
No "not a complex scene" should take 7 hours on a 5080 16 GB graphics card. That would imply that you have fallen back to CPU rendering.
You had better look closely at the DS log file see what earlier error messages or warnings there may have been.
How much system RAM do you have in your computer? It is recommended to have 2-3 times as much system RAM as GPU RAM.
Is your NVIDIA graphics card driver up to date? There is a minimum driver number required for the DS 2025 Alpha. 57x, I believe.
Do you leave render windows open after the render finishes? That prevents the GPU RAM from being released for the next render.
Are you running other programs on your computer at the same time that may be hogging memory you need for the render?
it's the same scene but this time crashed the application after 7 hours (i was away...).
It's not a complex scene and i have a 5080 16gb.
any ideas?
No "not a complex scene" should take 7 hours on a 5080 16 GB graphics card. That would imply that you have fallen back to CPU rendering.
You had better look closely at the DS log file see what earlier error messages or warnings there may have been.
How much system RAM do you have in your computer? It is recommended to have 2-3 times as much system RAM as GPU RAM.
Is your NVIDIA graphics card driver up to date? There is a minimum driver number required for the DS 2025 Alpha. 57x, I believe.
Do you leave render windows open after the render finishes? That prevents the GPU RAM from being released for the next render.
Are you running other programs on your computer at the same time that may be hogging memory you need for the render?
Thank you for your answer, let's see:
No "not a complex scene" should take 7 hours on a 5080 16 GB graphics card. That would imply that you have fallen back to CPU rendering.
it's the same scene i rendered in 42 minutes before (and i lost the saved image somehow...) so i know for sure it's not a complex scene and it should be rendered under 1hr.
The cpu fallback is turned off so i guess it's not the issue here.
How much system RAM do you have in your computer? It is recommended to have 2-3 times as much system RAM as GPU RAM.
I've 32gb RAM, thinking to buy another 32. Is there any option i should check?
Is your NVIDIA graphics card driver up to date? There is a minimum driver number required for the DS 2025 Alpha. 57x, I believe.
572.83
Do you leave render windows open after the render finishes? That prevents the GPU RAM from being released for the next render.
I believe you've centered the problem: I created a script to automate renders that I point to in a specific folder, and the memory issue occurs after the second render. I should find a way to automate closing the program and directly reopening the next file. However, the previous problem (that I can't find the completed renders) makes all efforts futile...
Do you have a solution for batch rendering several scenes overnight?
it's the same scene but this time crashed the application after 7 hours (i was away...).
It's not a complex scene and i have a 5080 16gb.
any ideas?
No "not a complex scene" should take 7 hours on a 5080 16 GB graphics card. That would imply that you have fallen back to CPU rendering.
You had better look closely at the DS log file see what earlier error messages or warnings there may have been.
How much system RAM do you have in your computer? It is recommended to have 2-3 times as much system RAM as GPU RAM.
Is your NVIDIA graphics card driver up to date? There is a minimum driver number required for the DS 2025 Alpha. 57x, I believe.
Do you leave render windows open after the render finishes? That prevents the GPU RAM from being released for the next render.
Are you running other programs on your computer at the same time that may be hogging memory you need for the render?
Thank you for your answer, let's see:
No "not a complex scene" should take 7 hours on a 5080 16 GB graphics card. That would imply that you have fallen back to CPU rendering.
it's the same scene i rendered in 42 minutes before (and i lost the saved image somehow...) so i know for sure it's not a complex scene and it should be rendered under 1hr.
The cpu fallback is turned off so i guess it's not the issue here.
How much system RAM do you have in your computer? It is recommended to have 2-3 times as much system RAM as GPU RAM.
I've 32gb RAM, thinking to buy another 32. Is there any option i should check?
Is your NVIDIA graphics card driver up to date? There is a minimum driver number required for the DS 2025 Alpha. 57x, I believe.
572.83
Do you leave render windows open after the render finishes? That prevents the GPU RAM from being released for the next render.
I believe you've centered the problem: I created a script to automate renders that I point to in a specific folder, and the memory issue occurs after the second render. I should find a way to automate closing the program and directly reopening the next file. However, the previous problem (that I can't find the completed renders) makes all efforts futile...
Do you have a solution for batch rendering several scenes overnight?
Daz Premier includes a batch rnder tool. You could also take a one of sample scripts to show you how to launch rendering
@Richard In this latest Alpha rendering a movie doesn't work -- it renders all frames but then it says:
Error saving the file: "whatever_path_and_name_you_used" The render could not be saved. Try again or choose a new file name. [Try Again][Choose new file][Cancel]
The only error I see in the log related to it is this:
2025-05-20 16:46:35.767 [WARNING] :: \src\sdksource\basictypes\dzfilefilter.cpp(277): Index out of range in DzFileFilter::getFilterDescription()
What I take from that error it seems to refer to the windows file dialog which only has All Files (*.*) option, and before that dialog you don't get any prompt to chose compression for the video like you did before that.
One possibility that was raised on a previous occasion is security software blocking /bin/ffmpeg.exe in the Daz Studio application folder, which might well disable the extension and so mean it wasn't in the list to be retrieved with the consequence being that error message. It is geenally considered better to just render the image sequence and then assemble it into a movie later.
1. Antivirus is not a factor.
2. In Daz Studio 4.x you are prompted to select compression (default is Uncompressed) after the render finishes -- that dialog doesn't show in Daz Studio 2025 Alpha and I couldn't find any settings for that.
3. Daz Studio 4.x didn't use ffmpeg.exe to save animation.
4. Daz Studio 2025 ships ffmpeg.exe built by gyan.dev (version 6.1.1 release when 7.1.1 release already exists) -- on that note the maintainers say:
It is highly recommended to choose a git master build; unlike many software, releases are primarily made for the convenience of OS distributors and package managers and don't signify greater stability or maturity. For a bug report to be accepted, the issue must be reproducible using a very recent git master build.
5. Rendering series of images and merging them manually is an extra step and thus inconvenient when all you want to do is render low resolution uncompressed AVI preview. What's the point of having Render Movie option then?
@oscaricalo
According to the log file snippet you posted, your first render should be in C:/Users/bs/Documents/Renpy/asset generali/torender/rendered_1.117.png. If it is not there, perhaps One Drive moved it to the cloud. People often have that problem when they put Daz files in the User Documents folder. Try saving your file somplace else.
Your NVIDIA driver version looks like it meets the minimum requirements, so it should work OK.
Mismatched RAM can cause problems. If you buy more system RAM, be sure it is speed and timing compatible with what you have installed. Or, put the existing RAM aside and buy a pair of matched 32 GB RAM sticks.
My batch rendering solution is ManFriday's Render Queue 3 in DS 4.24. That won't work for you, because you need the DS 2025 Alpha for your 5080, and I don't think Daz sells Render Queue 3 anymore anyway. Daz bought it out from ManFriday and turned it into a Premier-Member-Only tool for DS 4.24. I don't think that tool is updated for DS 2025 yet. When/if it does get updated for DS 2025, you would have to pay for Premier membership to use it.
My batch rendering solution is ManFriday's Render Queue 3 in DS 4.24. That won't work for you, because you need the DS 2025 Alpha for your 5080, and I don't think Daz sells Render Queue 3 anymore anyway. Daz bought it out from ManFriday and turned it into a Premier-Member-Only tool for DS 4.24. I don't think that tool is updated for DS 2025 yet. When/if it does get updated for DS 2025, you would have to pay for Premier membership to use it.
My batch rendering solution is ManFriday's Render Queue 3 in DS 4.24. That won't work for you, because you need the DS 2025 Alpha for your 5080, and I don't think Daz sells Render Queue 3 anymore anyway. Daz bought it out from ManFriday and turned it into a Premier-Member-Only tool for DS 4.24. I don't think that tool is updated for DS 2025 yet. When/if it does get updated for DS 2025, you would have to pay for Premier membership to use it.
My batch rendering solution is ManFriday's Render Queue 3 in DS 4.24. That won't work for you, because you need the DS 2025 Alpha for your 5080, and I don't think Daz sells Render Queue 3 anymore anyway. Daz bought it out from ManFriday and turned it into a Premier-Member-Only tool for DS 4.24. I don't think that tool is updated for DS 2025 yet. When/if it does get updated for DS 2025, you would have to pay for Premier membership to use it.
It has been updated for DS 2025.
Was that announced someplace?
As far as I'm aware, it has been available since day 1. Some has been tweaked further, e.g. Render Queue.
Comments
Doctorjellybean,
>And did you map the content paths as they are for DS4 in 2025 ALPHA? -- Yes I verified content paths are where I previously had them
>Install PostgreSQL and the 4.24 update and try again. Make sure there are no instances of any DS version running -- I did this but still not able to load those specific GEN 4 characters -- I do have 3 different versions of DAZ Studio now. See attached pix
wsterdan,
>One other thing you might try: click on the character you want to load into the scene and drag it from the library into the scene and see if that triggers it. -- Nothing happens, not even any error messages -- Thanks for the tip, I didn't know u could drag & drop!!
Do u guys think I should just open a ticket??
Thanks!!
@vicster56 Assuming you have 4.24 installed, and that you are able to load Gen 4 characters in that: load a Gen 4 character in 4.24, save it as a scene and open that scene in 2025 ALPHA. Does the scene load as expected?
Doctorjellybean,
>Assuming you have 4.24 installed, and that you are able to load Gen 4 characters in that: load a Gen 4 character in 4.24, save it as a scene and open that scene in 2025 ALPHA. Does the scene load as expected? I'll try that!!
Thanks!!
Hey Daz Developers, is it just my impression, or is the export window completely wrong? Now it only exports armatures? Something is wrong there right?
Is there updated scripting reference that I can check? I had to upgrade to RTX5090 but my complex script is not working anymore in alpha version.I see in the changelog that there are updates to public API documentation but I can't find it anywhere for new Daz Studio.
APIs are still documented in the old location, but changes are documented here: https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen
The API documentation is updated ready but not released until it is the current General Release, or at least more stable than an alpha buiild (if you look at the chnage log you will see some things have been listed and then struck through).
Can we please for the love of all that's holy get support for Intel or AMD cards. PLEASE!
If you mean for rendering that is a limitation of Iray. Not Daz Studio. Iray is made by Nvidia and thus requires Nvidia hardware. If you mean fo ranythign else I can;t comment on that since I'm on (resentfully) Nvidia hardware.
AMD and Intel cards, as much as I know, works fine with Filament and 3Delight. IRay is bound to NVidia cards because it needs CUDA cores to work, that can be found only on NVidia cards.
There is some kind of special driver that emulates CUDA cores on AMD cards but IRay doesn't work on that method.
@Richard In this latest Alpha rendering a movie doesn't work -- it renders all frames but then it says:
Error saving the file:
"whatever_path_and_name_you_used"
The render could not be saved.
Try again or choose a new file name.
[Try Again][Choose new file][Cancel]
The only error I see in the log related to it is this:
What I take from that error it seems to refer to the windows file dialog which only has All Files (*.*) option, and before that dialog you don't get any prompt to chose compression for the video like you did before that.
Support for what features?
One possibility that was raised on a previous occasion is security software blocking /bin/ffmpeg.exe in the Daz Studio application folder, which might well disable the extension and so mean it wasn't in the list to be retrieved with the consequence being that error message. It is geenally considered better to just render the image sequence and then assemble it into a movie later.
Hello, is the RTX Pro 6000 blackwell compatible with Daz Alpha?
It's using the Blackwell family of chips, so that should be a yes.
That's what it seems to me too.
But since it's an $8,000 purchase, I wanted to be sure. Thanks.
Any news on Geometry sculptor feature support for this version?
I'm having 2 issues with this release:
[INFO] :: Saved image: C:\Users\bs\AppData\Roaming\DAZ 3D\Studio6 Public Build\temp\render\r.png
[INFO] :: Finished rendering.
[INFO] :: Total Rendering Time: 42 minutes 12.41 seconds
[DEBUG] :: Render completed: C:/Users/bs/Documents/Renpy/asset generali/torender/rendered_1.117.png
I can't find anywhere the completed render... there are no permission issues and i even started daz3d with administrator permissions.
2nd issue:
[WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(417): Iray [FATAL] - API:MEMORY :: Memory allocation failed.
it's the same scene but this time crashed the application after 7 hours (i was away...).
It's not a complex scene and i have a 5080 16gb.
any ideas?
No "not a complex scene" should take 7 hours on a 5080 16 GB graphics card. That would imply that you have fallen back to CPU rendering.
You had better look closely at the DS log file see what earlier error messages or warnings there may have been.
How much system RAM do you have in your computer? It is recommended to have 2-3 times as much system RAM as GPU RAM.
Is your NVIDIA graphics card driver up to date? There is a minimum driver number required for the DS 2025 Alpha. 57x, I believe.
Do you leave render windows open after the render finishes? That prevents the GPU RAM from being released for the next render.
Are you running other programs on your computer at the same time that may be hogging memory you need for the render?
Thank you for your answer, let's see:
it's the same scene i rendered in 42 minutes before (and i lost the saved image somehow...) so i know for sure it's not a complex scene and it should be rendered under 1hr.
The cpu fallback is turned off so i guess it's not the issue here.
I've 32gb RAM, thinking to buy another 32. Is there any option i should check?
572.83
I believe you've centered the problem: I created a script to automate renders that I point to in a specific folder, and the memory issue occurs after the second render. I should find a way to automate closing the program and directly reopening the next file. However, the previous problem (that I can't find the completed renders) makes all efforts futile...
Do you have a solution for batch rendering several scenes overnight?
Something strange is still occurring on my 5080:
2025-05-22 13:53:56.962 Iray [INFO] - IRAY:RENDER :: 1.35 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 5080): JIT-linking kernel in 2.054 s
2025-05-22 13:53:57.031 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(417): Iray [ERROR] - IRAY:RENDER :: 1.35 IRAY rend error: CUDA device 0 (NVIDIA GeForce RTX 5080): Available memory not sufficient for wavefront rendering.
2025-05-22 13:53:57.038 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(417): Iray [ERROR] - IRAY:RENDER :: 1.35 IRAY rend error: Lost master device.
2025-05-22 13:53:57.057 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(417): Iray [WARNING] - IRAY:RENDER :: 1.35 IRAY rend warn : CUDA device 0 (NVIDIA GeForce RTX 5080) ran out of memory and is temporarily unavailable for rendering.
2025-05-22 13:53:57.276 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(417): Iray [WARNING] - IRAY:RENDER :: 1.35 IRAY rend warn : All available GPUs failed.
2025-05-22 13:53:57.289 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(417): Iray [ERROR] - IRAY:RENDER :: 1.35 IRAY rend error: Fallback to CPU not allowed.
2025-05-22 13:53:57.289 Iray [INFO] - IRAY:RENDER :: 1.35 IRAY rend info : Freeing temporary rendering resources
2025-05-22 13:53:57.329 [ERROR] Iray :: Internal rendering error.
Daz Premier includes a batch rnder tool. You could also take a one of sample scripts to show you how to launch rendering
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/rendering/render_post_process/start
and combine it with the logic of the application restart script here
https://www.daz3d.com/forums/discussion/comment/9137816/#Comment_9137816
which also answers you question about restarting from script more generally.
Daz Studio is set to not start with administrator privileges (as that can cause serious issues) so you should have been able to run that way at all.
1. Antivirus is not a factor.
2. In Daz Studio 4.x you are prompted to select compression (default is Uncompressed) after the render finishes -- that dialog doesn't show in Daz Studio 2025 Alpha and I couldn't find any settings for that.
3. Daz Studio 4.x didn't use ffmpeg.exe to save animation.
It is highly recommended to choose a git master build; unlike many software, releases are primarily made for the convenience of OS distributors and package managers and don't signify greater stability or maturity. For a bug report to be accepted, the issue must be reproducible using a very recent git master build.
5. Rendering series of images and merging them manually is an extra step and thus inconvenient when all you want to do is render low resolution uncompressed AVI preview. What's the point of having Render Movie option then?
@oscaricalo
According to the log file snippet you posted, your first render should be in C:/Users/bs/Documents/Renpy/asset generali/torender/rendered_1.117.png. If it is not there, perhaps One Drive moved it to the cloud. People often have that problem when they put Daz files in the User Documents folder. Try saving your file somplace else.
Your NVIDIA driver version looks like it meets the minimum requirements, so it should work OK.
Mismatched RAM can cause problems. If you buy more system RAM, be sure it is speed and timing compatible with what you have installed. Or, put the existing RAM aside and buy a pair of matched 32 GB RAM sticks.
My batch rendering solution is ManFriday's Render Queue 3 in DS 4.24. That won't work for you, because you need the DS 2025 Alpha for your 5080, and I don't think Daz sells Render Queue 3 anymore anyway. Daz bought it out from ManFriday and turned it into a Premier-Member-Only tool for DS 4.24. I don't think that tool is updated for DS 2025 yet. When/if it does get updated for DS 2025, you would have to pay for Premier membership to use it.
Richard, he is using the DS 2025 Alpha with an RTX5080. Do your suggestions work in that environment?
It has been updated for DS 2025.
The restart is a 2025 feature. The suggestion comes from a little bird, so it should all work.
Was that announced someplace?
As far as I'm aware, it has been available since day 1. Some has been tweaked further, e.g. Render Queue.