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
This is a major rework of Studio, primarily updated to support the Mac platform - but the rewrite will affect all users, so the more eyes on it the better. I would hope that the pre-beta (or barring that, the first true beta) would include the text sizing changes people have been looking for.
The skin of a typical male and a typical female differ hugely. So I do not think it is really a good way to use the same skin texture for both genders for people who strive for reality. And August 8.1 looks everything but realistic or even halfway good.
...however the driver situation is still an issue. It would mean having to stay with an older version of Daz that has an older version of Iray particularly as the final general release of 5 will be after Nvidia dumps driver support for W7. Likely any new version of Iray introduced afterwards will no longer be compatible so it would be back to glacial CPU rendering.
The big question I have - will we need to "purchase" the pre-beta, or will it magically appear in our product library?
I'd put money on DS5 not supporting W7 specifically because of the iRay driver issue. nVidia may decide that's a stipulation of a newer version of the engine.
Will the new update work with intel 11 processors? There are issues with the 4.15 version and the OpenSSL coding which needs to be patched to work with the intel 11 processor.
https://www.daz3d.com/forums/discussion/256961/hexagon-beta-version-2-5-2-137-updated/p1
Doesn't seem to be promising anything
So my first impression is correct. The first release of the pre-beta is for Mac only.
I don't expect Daz to explicitly drop W7 support. True, at some point early in the DS5 release schedule it will include an Iray that no longer supports GPU rendering on W7 because the required drivers aren't available, but 3DL and Iray CPU will both still work. There may come a point where some function in DS proper will be upgraded and no longer be supported by W7 - like the upgrade to support canvases and the exr image format reduced XP to not supporting several image formats.
....that's more my thinking, just won't be able to do GPU rendering in Iray. Not about to go back to glacial render times again.
This may make me break my moratorium on subscription software and go with Octane4.
No. I believe it's Mac AND PC.
While the greatest initial benefit will be for Mac users, I would not characterize it that way. The framework update is necessary for all users, regardless of OS. The C++ libraries shipped with even the Windows version of Studio are long out of date and past mainstream support by Microsoft (If I remember correctly it's still deploying the VS 2010 runtime; end of mainstream support was in 2015). Similarly, support for QT4 ended in 2015.
Wow - haven't seen that in a while. The first 'Personal Computer' i ever used was a Heathkit H8 - and this was a very expensive option on it that we did not get. We settled for loading programs via audio cassette.
Whether it was a concern of mine didn't matter. They gave no reason to assume an additional expense would be on the way and the thought that it could be was shot down early on. I'm not going to assume what other companies may do is something DAZ3D may do.
All that addressed, we can move on now.
On a different subject - to the user who mentioned figure load times, I'm with you. I try not to complain about Studio (DAZ have enough on their plates), but if anything would truly improve my workflow, it would be improved figure (posing included) and scene loading.
Not just possible. It is already here: https://www.amd.com/en/technologies/radeon-prorender
ProRender 2.0 is free, open-source, supports Vulkan, OpenCL and Metal.
There are also three Filament-like modes. One is for pure reasterization, which is good for viewport rendering, one with baised GI on rasterization, and some ray traced effects (reflection, refraction, ambient occlusion, etc.), and one ray-traced mode, where the base rendering is still rasterization, but ray tracing is applied to achieve biased photorealistic rendering.
The easist work around for slow load times is to go into the data file and hide all of the character morphs you are not using for a given character. You will have to unhide them whenever you want to create a new character, but until there is a better fix it is a work around.
Just going to put this here, in case anyone is interested (morph hiding script freebie): https://www.daz3d.com/forums/discussion/505201/long-load-times-this-may-help#latest
I wasn't aware of that thread, good looking out and posting a link here.
So looking forward to having Daz back again.
What bothers me the most is not the announcement and its lack of clear communication regarding any future developments, aside from the support for the up-to-date iOS, but that it seems to be just a UI-overhaul with the potential to break a lot of old stuff (scripts, plugins, etc.) without bringing any new features.
If you take into account that DAZ just released Genesis 8.1 — at least for those people who do not bother a set-back in quality (plastic look due to the new skin shader) despite adding a new but still buggy expression system — I doubt that DAZ 5 will bring us any new features for Genesis figures. Softbody physics and all this would most likely require a new Genesis generation. And I doubt Genesis 9 is hiding behind the horizon.
I think the main feature of DAZ 5 is just a new UI and iOS support.
This means, as long as you are not on a Mac, it will be primarily uninteresting.
For me, this will mean that I stay on my stable 4.14 and pray to my gods that DAZ Productions Inc. will not mess up my library by updating assets that damage compatibility with DAZ 4.
Will I be able to run the Pre-beta version of DS5 on a PC?!
From what has been said, yes.
While we are glad that a rapprochement was achieved, it is in general best to leave the mods to decide what should or shouldn't be posted rather than divert the thread into a debate on the topic.
It seems likely that the new framework will require quite a bit of debugging 9which is no doubt part of the reason for the pre-beta release). Daz doesn't like to leak feature details too early, so they are probably not going to drop hints about the actual new features planned for DS 5 until they are nearer to showing them.
And me too
Nice memories. During my university studies, I have used punched paper cards to deliver program and data to the computer centre
and got results just after a week of time. Any error and another week of waiting to get another error report or results.
Imagine wait for the render 1 week and then discover, that some part of the scene you want in different place,
and since you cannot see the preview of results, you need to punch cards with different contents and process them again.
At least the corrections to the data was quite fast, if you only need to replace a couple of the cards.
Each card could carry one line of the data or program (in Fortran in my case).
Ah, it's less than two weeks old! Crazy how I hadn't seen it still. I've worked with other suggestions provided throughout various threads that were useful, but I was hoping for a more solid solution. This might be it.
From reading through this thread, the impression I get is that the initial release of DS 5 will feature nothing new other than the UI, the latest version of QT and support for the latest version of the Mac operating system and the ARM based M1 microprocessor.
As Richard has rightly highlighted, the pre beta version is likely to be extremely buggy but will be useful to show users which way DAZ is moving with regard to the UI.
Once the initial release is up and running then we will get the new stuff.
As someone who has spent almost forty years writing and maintaining manufacturing software systems, I applaud DAZ's incremental approach of "get it working properly first and then add the fancy stuff".
Cheers,
Alex.
Not sure I need the headache (without any form of compensation) to beta test a -- what is already billed as -- buggy pre-beta for the M1. Pass on that.