Daz Studio Pro BETA - version 4.11.0.335! (*UPDATED*)
This discussion has been closed.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
They should be working now.
I'm not sure I understand your problem. If you have nothing to reflect but a dark background, that's what your reflective surfaces are going to reflect. This doesn't seem unusual to me. The one with the rendered background looks better because there's something to reflect (other than a plain dark background).
Laurie
This happens even inside a room where there is something to reflect.
Ok nevermind. You were right. The last time I put her in a room, it was open on one side, and I must have caught the lack of reflection from that side.
Is the other side of the room (that will be reflected) adequately lit? Or is the light only aimed at the character with the rest of the room dark?
Gotcha ;).
I was thinking I was missing your point somehow. LOL
Laurie
Any idea of when this beta will become a General Release? I need the fixes but I don't trust betas.
No timescale, but you can run this version alongside the Reneral Release.
The beta "highlights" list is much shorter today... :-)
Well, it is only five builds.
4.11.0.196 changed the way primitives are created, so they are created with the surface shader appropriate for the active render engine. That was great! I would like to see surfaces created with the Geometry Editor tool treated the same way, i.e. the surface should use the default shader for the active render engine. So, when using Iray, the created surface would use Iray Uber instead of Daz Studio Default shader. I submitted this request as a help request.
The issue with mouse movement remains for me. So, I cannot upgrade until that is figured out. Doesn't happen on 4.10, but has happened on all of the 4.11 Betas.
You guys wanna see a magic trick ?
Left click on any view icon in the viewport and hold it and then right click at the same time.
What is a "view icon"?
Has anyone been able to get pwToon to work in the beta version? I've tried with the last couple of updates but without success. I had a quick try with Visual Style Shader and this did seem to apply to the surfaces.
Also, I had an issue with trying to shut down the new beta version today. It refused to close and I had to do a hard shut down. I'm using the Mac version.
Currently I am having an issue with DS 4.10. When I start 4.10 it gets as far as loading dforce and crashes. I submitted a bug report. With tech supports work load I don't know how long a reply will be in coming so I am going to download 4.11.0.236.
When I looked at the instillation procedure on the promo page it shows to load DS public build and scene builder public build. Here is a list of what I have in DIM.
DAZ Studio 4.11 (Win 64-bit) Public Build +Beta+
Scene Builder for DAZ Studio
GoZ for DAZ Studio 4.11+ (Win 64-bit) Public Build +Beta+
Photoshop 3D Bridge for DAZ Studio 4.11+ (Win 64-bit) Public Build +Beta+
PostgreSQL CMS (Win 64-bit) Public Build +Beta+
PostgreSQL CMS From Valentina CMS Conversion Public Build +Beta+
My questions: Scene Builder is not a public build, should I still load it. I have these other four public builds and I do not know if loading them is necessary or required. I do not have Z-Brush or Photoshop and my current SQL works fine except for the occasional hiccup.
Any help or advice would be appreciated.
deeleelaw57:
If you don't have Z-Brush or Photoshop you do NOT need to load those link plugins. You only need one copy of PostgreSQL CMS even when you have both standard and Beta versions of DAZ Studio. So you can ignore the extra version.
PostgreSQL CMS From Valentina CMS Conversion is only necessary if you have not converted from the old Valentina database to the PostgreSQL CMS. Which it seems you have already been done, so disregard it.
If you use Scene Builder, there may be some upgrade for new features such as dForce. Otherwise you can ignore it.
Hope that helps.
RainbowArtist, thank you very much. I do not use Scene Builder but may download it for potential upgrades to new features as you stated.
Why, with the latest Beta, am I rendering a simple scene on my CPU and not my TitanX?
Is the TitanX available as a device on the Advanced tab in Iray Render Settings?
Yes and it is the only thing selected. It renders once, totally black... then falls back to CPU only. Upgraded drivers, same result.
I've noticed that renders in beta take twice as long as 4.10; I know beta can add an additional cost, but doubling rendering times is surprising.
4.10 - Rendering Time: 7 minutes 25.29 seconds
Beta (4.11.0.236) Rendering Time: 14 minutes 36.38 seconds
I've been eye-balling the renders to see if a lower convergence on beta would be comparable, but it isn't obviously so.
I wonder why my images are getting rendered much more edgy in the beta version compared to the release version. It looks like someone turned off antialiasing. Does anybody know why? Did they add some new feature which is turned off as standard?
Assuming you are opening your scenes, not merging them, check Edit>Preferences>Scene that DS beta is not set to ignore render settings on load.
I transfered a 4.10 created scene to the 4.11 beta build. On the release version it looks normal but it looks slightly weird on the beta version.
There was a change to the Iray surfaces to set a new entry "Invert Tanssmission Normal" to On by default. You could try turning that Off and see it it makes a difference. Without seeing your renders, it is hard to guess what the cause is.
Beta is still slower for me on a 1080ti. At first it looked like it was going faster. Don't know what happened.
4.10
optix: 15 minutes 19.1 seconds, 8.7GB vram
no optix: 25 minutes 15.59 seconds, 7.2GB vram
4.11
optix: 26 minutes 30.39 seconds, 9.5GB vram
no optix: didn't bother
Specs: 16GB ram, i7-2600K, evga 1080ti sc2 1670MHz boost
@ 4.10.0.36 = NVIDIA Iray 2017.0.1 (287000.7672)
---
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log
@ 4.11.0.47 = NVIDIA Iray 2017.1.2 (296300.3713)
@ 4.11.0.105 = NVIDIA Iray 2017.1.4 (296300.6298)
@ 4.11.0.161 = NVIDIA Iray 2018.0.1 (302800.349
A lot has changed. Things that were not working, or were working incorrectly, were fixed. Functionality that did not exist, added.
Before I start submitting a support ticket, is anyone else experiencing complete system freezes during some renders in the beta with one of the new RTX cards? I got an RTX 2080 Ti this week which reliably freezes my system on certain renders, requiring a hard reboot. I've put the card through 3DMark and games without issues, so I suspect the problem is in the Daz beta. Since I haven't been following all the conversations about this topic, I'd just like to hear if I'm alone in this or not.
Edit: It appears I have a faulty GPU. I'll be getting it replaced.
I am having trouble that in DS Public Beta 4.11.0.236 sometimes the mouse pointer disappears. It reappears only when I move the mouse pointer outside of DAZ Studio focus to elsewhere on the desktop.
Nevermind, I had some weight sitting my my bamboo tablet!