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
DAZ has to wait for NVIDIA to supply them with the latest Iray, which then needs to be incorporated and tested.
They've had it integrated since the end of August.
There's more in the last update than Ampere support. Better to make the VERY FEW people who bought 30X0 cards wait than screw up rendering for everyone.
None said that you need to upgrade your version of DAZ immediately after the release. It's called BETA for this very reason. More and more people are getting the new cards and if those user wouldn't report that it doesn't work none would know about it, because DAZ haven't made any statement on this matter, at least I don't know.
It's in private-build testing. If it was ready for beta, it would be in the public build. Obviously it isn't.
+1
Rushing a new version of DS that supports Ampere would only potentially affect very few users positively. Rushing a new version that has significant bugs could affect a large number of users, those of us who use the public and release builds, negatively. My guess is that more people would benefit from long-standing animation bugs being properly squashed than would benefit from Ampere support, and Daz is demonstrably interested in establishing DS as a viable animation platform.
There have been nearly 20 updates to DS since Ampere support was first added. By the time it's done, it may well be 4.13, but the number doesn't matter.
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log
Sorry, but no. If you are using a beta release, then you kinda forfeit your right to complain when a new one breaks something you care about. The whole point of beta releases is to see what they broke and report it so they can fix it.
That's true, but one usually avoids releasing a public beta when it still has known critical bugs, because if the beta testers can't get it to work at all then they can't really do any useful testing.
All we know is what is in the change log, which isn't necessarily everything that is happening (Iray and dForce did not show in the chnage log before their first public appearance). I understand that people with the new GPUs, especially people with only the new cards, are very anxious for a release they can use with them but there's really nothing to be gained by speculating on what is holding the releases back or when we will see them.
Does this version crash when loading IBL master from the scripts menu?
Please provide more details, e.g. what scripts menu?
I have created a custom action to load the IBL master, its in Scripts from the menu bar I've been doing this for years, I have several things there for speed, when I updated to the recent public build version of DS now DS crashes when I try to launch IBL master from the menu rather than negiotiating to where it sits in the runtime.
Ok, it doesn't crash for me (Windows 10 x64).
So are you saying this version doesn't crash it?
No. I created a custom action for the IBL Master prop, clicked the script entry in the menu and it loaded the prop without crashing.
Out of curiosity, are you in Iray preview mode when it crashes?
- Greg
Nope don't use that.
So its the public build that has the problem.
The public build is the beta build, as opposed to the general release build.
Whilst beta is there to do final tests before making it general release. The clue is in Beta, it means it's gone through adequate alpha and whatever other private testing is required.
We can argue until the heat death of the universe, Daz will release it when they are ready, for when they will best benefit and best benefit most users.
General release build then, I did post in that thread but no one replied.
No crashing for me in the General Release either.
No argument from me there - they will release when the showstopper bugs are gone. My post was in response to Sevrin's implication that a new beta breaking people who run the public build would be a worse thing for them than it would be for the limited Ampere audience. My point was (and still is) that if you are silly enough to run the public build as your primary, then you get to live with whatever breaks and not blame anyone but yourself if your workflow is disrupted. That's the price of living on the bleeding edge, sometimes you get cut.
IMHO there's a difference between an end-user encountering a bug in a public beta and Daz3D releasing a public beta when they don't think it is ready.
I don't even have the release build installed, and, like many people, have been using the public build exclusively for a while. There's no point in there being a beta if people don't use it extensively. And to Daz, DS public build users are first-and-foremost customers of the Daz store whom it doesn't want to alienate with a buggy DS. That's why the private build testers are a pretty exclusive bunch of daredevils.
The bleeding edge is the private build. The public build, as people who are regular DS users can confirm, is the rarely inconveniencing edge. More importantly, the stuff that doesn't work in the public build, like some animation features, generally doesn't work in the current release build either. The current beta, for example, is so stable that it hasn't been updated since April or May.
Me too. At least I have the general release installed but use the Beta exclusively. Just have to be careful with DIM and make sure only the Public Build versions of plugins, etc., get installed. That said, it does seem an awfully long time since I installed this beta. I'm sure they came at more regular intervals previously which only raises my hopes that there will be some significant improvements/additions when we finally see it - hopefully some time before either the heat-death of the universe or, indeed, my own death.
I prefer to use both, the general release for my Zbrush'd character creation/V/G3 transfers, and the beta for the newer features... and seeing as the beta is usually pretty stable, I don't see it as too much of an issue.
Iray 2020 1.1 released on October 6. Hope Daz will stick to Iray 2020 1.0 and won't delay this any longer.