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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Yeah, glad that worked.
I was having the same issues you were, including in other programs. Very frustrating not to be able to fix the issue, on a brand new machine.
So am I nutz ... it seems the latest build for the General Release is 4.15.0.14, however where do you get it? I have 4.15.0.2 installed and it looks like there have been several updates since then. I tried both DIM and Daz Central (latest versions) and no joy. What am I missing?
I think you have to start up DIM, and go to Download Filters, on the top left side. You can download DS 4.5 +, and you can also download tags such as Public Build, etc. Then, in Filters, labeled Sort Order, on the top right side, try pulling down Package Date -- Recent First. You should see things in there such as DS 4.15 + Beta, or something like that.
Like I said I tried all that. I can't find any direct links to the latest version either. The only thing showing is version 4.15.0.2. I even uninstalled Studio and tried to download from the DAZ main page (as well as DIM and DAZ Central) and they downloaded xx.0.2, so I am at a loss. I can download the Beta, but that's not what I want. I want the most recent Release 4.15.0.14, not beta. I know that x.0.15 hasn't been released yet, but 4.15.0.14 has. Just can't find it anywhere.
BTW, I downloaded the most recent versions of DIM and DAZ Central also, thinking it may be that. Again, no joy.
For me the issue is I have Iray Server on a different node, and it has updated to the latest version of Iray, the same Iray build that is in Studio 4.15.0.14, and I am running into errors when I connect with Iray Server via the DAZ bridge using the x.0.2 build. It's telling me the local node (DAZ workstation) needs to upgrade to the latest version of Iray. I can render, but I keep getting error messages on Server.
4.15.0.2 is still the latest non-beta
Not according to DAZ. On the "highlights page" General Release 4.15.0.14 was released on or around March 18, 2021, with other previos versions released prior, such as 4.15.0.9 thru 4.15.0.13 . Version 4.15.0.25 (as of August) has "updates pending" and hasn't been released as of today and is the current Beta. What I need is "Iray 2020.1.5" (v334300.8936) which has been integrated into version 4.15.0.14 and is the minimum version of Iray fully compatible with the current version of Iray Server. Daz 4.15.0.2 is two versions behind on Iray. Iray Server keeps logging errors during rendering (when using both nodes simultaneously or in viewport mode) and as a result, latency is present on the server node. While I can render, it has slowed somewhat statistically.
If you check the first post of this thread, you will find the version number of current non-beta, which is the same as is mentioned on https://www.daz3d.com/downloader/customer/files#prod_13176
Latest beta is 4.15.0.28, which was released on Friday
OK ... now I see it. The highlights page is showing various versions of the beta. I see it now. That's aggravating. Not being a regular user of this forum means I have to play catch-up sometimes. Daz should just release a General Release version with the latest Iray build, since version 4.15.0.2 is not fully compatible with other current Iray products nor fully leverages current nVidia hardware; such as Iray Server and 30xx series. It functions with the latest Iray Server build, but is actually slower than previous versions of Iray solely due to continuous error logging server side as well as not being able to fully leverage current hardware client side, which is all counter intuitive. I guess I will have to revert to a previous version of Iray Server that is compatible with 4.15.0.2 and just wait till whenever DAZ gets its act together on integration.
I shouldn't have to wait on them to create "feature sets" in DAZ, which have nothing to do with Iray, before getting the latest Iray build. This is not the case with other competing products integrating Iray, which do so via patches. DAZ doesn't seem to know about patches I guess. nVidia has made significant changes to Iray over the last 9 months to leverage the latest generation of RTX products, such as the 3090 (as well as improve performance on older generations). Actually, the Iray build integrated into 4.15.0.2 is over a year and a half old, predating the current generation of RTX. So I guess I have to compromise other things I use Iray Server for, simply because DAZ is slow on its integration? I never should have added DAZ to my suite of software and workflow, since these types of unnecessary delays have happened in the past as well. Shame on the mess!
As a general rule I do not run Beta versions (on anything), which has been problematic in the past and has impacted productivity when problems arise. I guess for now I'm stuck waiting for DAZ feature sets I do not need, just to get proper integration of Iray.
4.15.0.2 does suport 30x0 cards.
"Supporting" a GPU and fully leveraging it (as the latest Iray build does) are two different things. Not to mention not being fully compatible with other Iray products such as Server, which is part of the DAZ/Iray integration, is problematic. If you would like me to be specific about 4.15.0.2, one part of the problem lies in it not being able to leverage or to properly support both CUDA 11 and OptiX 7.1 when just using say ... a 3090 on your DAZ machine using the latest "Studio" GPU driver for instance (without using Iray Server). That's just one example. There are also problems with certain current libraries and how handlers work in the Iray integration of the General Release (4.14.0.2), but that's getting too technical for this discussion.
As I said DAZ works with Iray Server, but not like it should. When older versions of Server run faster with DAZ than current Server builds shows how "supporting" something is simply word play, unrelated to proof of performance. This is especially true when you consider how on a local machine, (not running an Iray Server), is still not fully leveraging things like CUDA 11 with Optix 7.1, Iray PhotoReal and Iray Interative handlers regardless of hardware driver. I understand my case, since I use Server, is a bit specialized; however, I do not have this issue with competing products all of which use the most current Iray build integration. I certainly when not using Iray Server can fully leverage things like Optix 7.1, and all the benefits of current versions of PhotoReal and Interactive in competing software builds. I just do not understand why DAZ holds off on things like the latest rendering solutions espeicailly when paying for the licensing; while working on other unrelated features in Daz Studio.
Look I do understand Daz and their market. I understand the size of the company as well. So it's not inconceivable that they are not setup to make patches for just one aspect of an overall product that is offered free. I get that. However, nVidia makes it relatively painless to integrate Iray via its API, and Daz has already fully integrated and tested the latest Iray version into several beta versions. It's time to patch it into the General Release and not wait for other features to be finished before doing so. Besides we are already two versions (going on three) behind on Iray builds in 4.15.0.2. What is more ironic is we are not even going to mention Optix 7.3, which is the most current version.
We all know the old phrase, "Don't put off till tomorrow what you can do today" because the bills just keep piling up. Daz is so far behind, both from a rendering software perspective as well as hardware leveraging they will find it difficult to keep current and competetive, even for its content market.
I recall reading somewhere in the forums that they were just about to release an updated 4.15.x BUT a last minute glitch was discovered, serious enough to delay said release until that is mended.
Not that I recall.
i find this to be a common phenomena in this department.
--ms
I think that was related to the announcement when they were going to release the Big Sur update a while back?
The latest beta has been refusing to install, and now the general release is doing the same thing.
Latest beta 4.15.0.30 installed fine for me on Windows 10.
The latest general release needs the current PostgreSQL. I hid the release because I always use the beta.
FINALLY Daz3D is compatible with Big Sur... just in time for macOS Monterery to come out. XD
Hopefully Daz3D will be compatible with that new OS when it rolls out.
Which Nvidia Studio driver is needed with this release?
Before dealing with this release, someone could tell me if the timeline has been finally fixed?
Sorry for asking, but I'm confused: Is there an update of DAZ Studio 4.15 Pro (General Release) now to 4.15.0.30 or is this update for the Beta-Version?
Both are now at 4.15.0.30
PostgreSQL has not changed for some time, and should not need reinstalling for a new version of DS.
Thank you, Richard.
So an update on my end; testing a render on my Big Sur'ed Daz and for some reason I can't drag the Rendering Image notification on top so I can see my render actually rendering. I have to split screen the Windows side by side to actually see what's going on.
A minor nitpick but hey, at least it's working for me finally.
Are Daz staggering the rollout of 4.15 by user name? I'm running Windows 10 Pro and I've got 4.14 release and 4.15 beta installed. I've had lots of updates to the beta and it's plugins recently. Today DIM is showing me updates for several release plugins to 4.15 but not for the Daz Studio application. I've decided not to update the plugins until I get an update for the application. I suppose having a name near the end of the alphabet I should expect to be among the last to get the update.
4.15.0.26 did not appear for me because I had rolled back 4.15.0.25 by replacing the .zip and the .dsx with those for 4.15.0.14. You can force an update by copying all the files for product13176 (General Release) or 12000 (Public Build) from Downloads to somewhere safe (just in case) then deleting the corresponding .dsx files (you can use hard links to avoid the copy; DIM doesn't overwrite existing files.) DIM should then show you the out-of-date files in "Ready to Download"; it recreates the "Downloads" .dsx files from the store server. Don't delete the Manifest Files .dsx files; they record where the product is installed on your system.
Sorry if this has been answered somewhere back in the mists of this long thread but is there any point in updating to this latest release for Windows users?
Still no fix for not saving the environment setting properly. Ugh. I mean, come on, that's a fix that should have been implemented as soon as the bug was pointed out.
If saving the file doesn't save the file accurately, then it's not really saving, now, is it?
Yes, it's a regular update - see the chnage log or highlights post
https://www.daz3d.com/forums/discussion/463926/daz-studio-pro-4-15-highlights#latest
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log