Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
Okay, sooooo...
Daz3D 4.23.0.1
Windows 10 Pro
nVidia driver: Studio Driver 566.14 (2024-11-12)
Environment: FG School with all other surfaces disabled except the Gymnasium, plus 6 Genesis 8/8.1 (F) figures
I'm having difficulty with lighting. Specifically, if I create 7 lights, whether individually or via object duplication, they produce light, but not as extensive as I'd like. The 8th and further lights, whether created individually or by object duplication , do not light, in spite of the properties being set identically.
Additionally, I cannot seem to get the light aura to extend its distance. These are all point lights, 5000K temperature, intensity x2.00, Lumen output at 30000, diameter 1000 (1m).
What in the world am I doing wrong? I do not have this problem with one of the coffee-house environments in which I am creating many lights as well.
Texture shaded is limited, at least on most cards, to 8 lights - one of which is the headlamp/no preview light. texture Shaded is very limited as a preview of actual renders, in 3Delight or Iray.
Good information! Thank you!
I am a bit confused. I have some LAMH models, the DS free 4.23 release, and the free LAMH player. The tabs for the player options do not show up, but when I was looking for info it says I need "DS Pro"?
I found it. Apparently, I have to load the tab manually even though it is installed.
That's normal. There are a lot of possible panes (tabs) that can be included in your DS interface. There are some Workspace selections available that include certain panes, but you can customize your workspace to include whatever panes you want to use and position and dock them wherever your want - even on a second monitor. It is a useful feature of Daz Studio.
Skin Builder 8 Seems to be broken in 4.23. It will run initiailly but then I get errors whenever I do any task, for example, just trying to add eyebrows to a figure, I will get errors that it cannot locate files. I am unable to find the files they want manually, and so I have to hit skip. And then I am forced to quit Daz to get out because it just hang after that. Then after force quiting, in task manager Daz will still be running. so I have to force quit there as well. This was not a problem until 4.23. I can't find the commercial thread for Skin Builder 8, if there is one. the search function for the forums is useless. The search brings up nothing. This is a serious issue though, I use Skin Builder 8 for nearly every character this needs to be fixed. I can't beleive no one else is complaining about this yet.
https://www.daz3d.com/help/download-content
I use another search engine to search the forums. The one here doesn't seem to work well. I don't have the product so can't check further.
There is a little search program for windows called everything. It is really fast for finding files.
I found the commercial thread and saw that several other people have made the same complaint about using SB8 with DS4.23, but there has been no response by the PA to anyone in that thread going back to Dec 2024, when the first complaint was made, so I opened a ticket. It is definitely broken in 4.23, anyone who owns it and is running DS 4.23 can easily verify this.
Bought a brand new PC with a 5090, got my whole setup and library moved over, and it seems that Daz still doesn't support the 50 series?
Whenever I try to render, it just ends immediately with a blank image (not black).
Any updates on when the this issue with the 50 series will be resolved? Or has it been resolved, and I'm having a separate issue?
You need to install the Daz Studio 2025 Alpha to get support for the 5000 series GPUs. DS 4.X will never support to 5000 series GPUs. Unfortunately the Daz Studio 2025 Alpha is bare bones at this point. Almost no plugins work and many scripts fail. As named, it is an Alpha release, with a ways to go before being even a Beta. You can install it along side your other Daz Studio release(s) with DIM.
Wow! Thank you so much! I'm back on the road and rendering, just like that.
I had spent so long trying to figure out that issue.
I hadn't even considered that Daz' public software wouldn't work with the biggest graphic card company's newest cards
Also, luckily, I don't even know what a script is, in a Daz context, so maybe I won't be too burdened by the Alpha's state.
Again, thank you!
Here are some forum threads that offer some information about the DS 2025 Alpha:
https://www.daz3d.com/forums/discussion/728111/daz-studio-2025-alpha-version-6-25-2025-12207-updated-may-2-2025/p1
https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen
Is there any way to still download 4.23 for use on my laptop? I don't have an Iray compatible GPU and 4.24 keeps resetting the workspace to the default
No, there is no way to download older versions of DS.
Well that's a bit of a bummer.
They do not have a license to ship the 3DLight engine, built into 4.23.
I'm not interested in 3DL (which I have in my 4.24 anyway). 4.23 was a lot better in many ways. I wish I'd never upgraded on my main machine to 4.24.
Legally, they cannot ship 4.23. And I have no idea how 4.23 is better than 4.24. I've never wanted to go back.
3DL automatically converts to IRAY in 4.24. But rendering with 3DL does not happen.
The main reason I find 4.23 better is the fact that when changing selection from a G8M to G8F, the asset selection tab doesn't minimise itself like it does in 4.24.
Example. In 4.24 I select G8M and then scroll through the list to add a hair asset. If I then select a G8F character, that expanded drop down asset list collapses itself and I have to scroll through everything again. In 4.23, it stays on the hair tab and just changes the shown assets for compatible ones. This is a much quicker way to work. 4.24 is a major step backwards in terms of workflow efficiency.
I've learned to live with the content library tree view sucking. ;)