DAZ Studio 4.11 Public Beta has massive speed enhancements for the viewports!
nonesuch00
Posts: 18,723
in The Commons
DAZ Studio 4.11 Public Beta has massive speed enhancements for the viewports with some types of viewport gizmos active!
So if you tend to use the latest DAZ Betas this one is worth testing!
Also, the iRay SDK version is updated to 2018.01 but since I CPU render it's not as big a thing to me.
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
Thanks for the heads up! :D
Laurie
Not to mention an update to dForce, from version 1.0.0.25 to version 1.1.0.64… Woo hoo!
4.10 is said to be about 10% slower on Iray renders than 4.9. Has anyone heard anything about speed improvements?
Cheers,
Alex.
Could you elaborate on the viewport improvements please? What is faster exactly? My main problems with speed in the viewport is posing when the figure has fibre hair - so much so that I am now avoiding using those hair products. Another problem with the viewport is not so much to do with speed but with the camera view jumping erratically which is very frustrating. Also there are issues with mouse control.
[EDIT]
It's ok ... these questions are mostly answered in the Beta Release thread in the DAZ Studio Discussion sub-forum. Well worth a look.
It's not that the Viewport speed has been deliberately changed, the target was the issue with mouse handling that caused the view to jump for some users in some situations (and also issues with remote operation).
And did you notice the new support for Polylines in OBJ import/export and (I think) in dForce? Real Dynamic hair, here we go!
The feature is listed only as enabling polylines for use as Dynamic Surface Addons - an almost literal ability to stitch things together - for which OBJ Import is required (since DS doesn't have suitable tools for creation).
Yes, an event loop a a bit of code in a program reads and acts upon the I/O event queue from your computer for devices like mouse and keyboard and it has been unusably slow in the viewport since DAZ Studio 4.10. 4.11.
I thought DS 4.11.x was almost a complete fix for the event loop code being so slow for my 1st couple of scene tests but while it really has massively improved it is still much too slow (yes it was even much worse before in 4.10.x than now in 4.11) so I will still go to activating the Geometry Editor when I want to pose figures in DAZ Studio to work around that viewport event loop lag.
Yay! If you mean operation via Remote Desktop, I'm very glad the developers are trying to improve this use case!
Yeah, better a Remote Desktop support is welcome... I think OpenGL is still a requirement and messing around when DAZ is used via RDP?
I use Splashtop on my iPad regularly because I don’t want my bedroom steaming from the heat from my laptop when it’s rendering. So I have it in my gameroom which is is big open space and the air flow is better.
I need a higher resolution as on the host desktop... this is only working with RDP well
I'm getting slower renders though, sadly;18% approx.
What I don't get any longer (knocking on wood) is the clogging up of the graphic card's vRAM, that forced me to restart DAZ Studio after every couple of aborted renders. I've done, like fifteen or so render-stop-make change-start new render cycles, and all is behaving nicely. I can't say anything about render times yet.
Isn't render noise more a lighting and/or materials setting issue than an outright renderer issue? I.e. in many cases the noise can be reduced for a given render time or number of iterations by tweaking the lights or materials.
The AI denoiser is Nvidia's new marketing push. It looks at the pixels that are already resolved and tries to predict what the rest of the image will look like. People are predicting it will render an image in 1/4 of the normal time, but we'll see how it works in practice. Logic would dictate that if these are just predictions based on existing pixels, then the image will look ok, but won't be accurate if you have a lot of reflections, refractions, translucency, SSS, caustics, etc. Each light path needs to be calculated on its own if you really want accuracy.
Tricks and gimmicks only get you so far. Some images just need lots of time and calculations. But yes, most people could speed up their images with better lighting and more efficient use of materials.
My first experience with the denoiser is, that the denoiser and DOF don't like each other. The image I testrendered looked rather psychedelic.
I have been doing some denoiser testing as well as others on the BETA thread and have posted some of my results there:
https://www.daz3d.com/forums/discussion/265581/daz-studio-pro-beta-version-4-11-0-171/p1
If anyone is interested in checking out the discussions.
Not true for me. It's a bit faster.
https://www.daz3d.com/forums/discussion/53771/iray-starter-scene-post-yourdoesn't-benchmarks/p27
Sory but the DS 4.11 rendering is about 30% slower .
and the post denoiser (very good idea) is to aggressive (need a way to be controled) so the presnt result is to plasticy.
You can reduce that, in my experience, by substantially increasing the frame at which it starts to apply (which of course means you have to wait longer for a noise-free render).
If it's anything like Blender's denoiser, it gives a much faster result. But you don't get something for nothing. From my understanding, it's more of a post-production effect, where it uses geometry data from the scene to intelligently guesstimate the render result instead of spending time doing the actual ray calculations. Which is fine if you're doing just a preview, or maybe for gaming, but for any serious professional type renders it's probably not what you'll want.
There are some nice videos as I recall for the Blender de-noiser, showing side-by-side comparisons of the actual render with the de-noiser render, and in some cases the lower quality of the de-noiser is very apparent, while in other it's not real obvious.
Does it work for CPU only? It seems to change something but as it turns out I like to see the un-denoised render and go from there. It also makes me wonder of the practical use of the Gausian/Mitchell filter & the firefly filter. Maybe I ought to turn that all off & see what renders look like.
I dig the denoiser (what I've tested of it so far). I have an image I put up as a test in the gallery with all the settings I used and how long it took. Looks really good too - the figures in the foreground are surprisingly crisp and I have just about everything turned on: caustics, bloom, spectral rendering, etc.
Laurie
It is GPU only.
Oh, because turning it on did change the way the CPU render behaved. I turned on Post Denoiser Available = On, Post Denoiser Enable = On, Post Denoiser Start Iteration = 8.
It's been a while since I tried one of these public betas. Can I try 4.11 and still have 4.10 available to use? Or will the beta overwrite my current version?
No, the beta will not overwrite the production version of 4.10. You can have a beta and a production version on the same PC at the same.
Cheers,
Alex.