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
Can someone explain to me the fundamental concepts of the 3 release channels: Private, Public and General Release? I always thought that if a build pass the tests in the Private build, it will be push to the Public channel, then after that the general release. However since the current public beta hasn't been updated since May ?!, and some people even using the beta as their only software for using Daz Store Content, what is the concept of these 3 release channels? Can't imagine that after nearly 5 months, they can't push any features in the private build to the public beta build ...
Yes it is really anxious because I sold my old card, but now I understand that I can't push this upcoming update no matter what I write on this forum. However if Daz was kind enough and gave us a expecting time, they could ease my anxiety a bit as well as help me with my situation. For example, if I knew I have to wait more than 1 month then I would bought another GPU to use with my work in the mean time.
There's a difference between "I/they can do nothing" and "nothing can be done"
That would depend, it may well be that - especially with new features - things have to go through multiple iterations in one channel before they are ready to be moved on to the next.
See https://www.daz3d.com/forums/discussion/comment/990671/#Comment_990671 for the actual definitions.
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_12_2_50
They're up to 45 private builds since the last public build update. 20 since Ampere support was added. Not sure what the holdup is. At least one of those has to be stable enough for us peons.
Well... Hope it's not gonna delay the release by another two weeks on top of the currenlty planned date.
Hold up is called Google Filament...
Probably. Based on the changelog, it appears that Daz is looking to update the DS preview with a PBR engine. Maybe we'll get closer to a realtime PBR preview? That and the animation fixes would be nice to see, as long as Filament plays nice with Iray materials.
If the preview speed will be similar to iray's preview mode with all the recompiling, then I don't see it as viable option,rather waste of time. Will turbo fast change it back to gl as soon as I see the first hickup.
They had best take all the time they need and get it right then!
I'll keep an open mind about Filament, but the fact that it's designed for mobile devices is worth noting. For those interested in more info:
https://google.github.io/filament/Filament.md.html
- Greg
If it was better if they used Cycles Render instead of Filements .
I'm expecting it to be somewhat between Eevee and Radeon ProRender. I expect it won't be half bad actually, even with intel integrated GPUs or 3 year old AMD Radeon GPUs. I haven't actually tried to find an app to install on my Windows 10 PC that renders using Filament already though.
Well, it's here now.
How can we find out what is new/fixed, etc. The change log is cryptic and full of "Source maintenance" that means nothing to users reading the log. The highlights thread hasn't been updated since April 2020 (version 4.12.1.109) and doesn't even cover the previous beta 4.12.2.6. Is there some other thread that explains what this beta provides?
Well... there are interesting things to look at and comments which suggest obvious fixes to annoying behaviors; like not being able to undo adding something to the scene other than by deleting it (which totally messes up the undo stack itself!)
The recent SSIM changes seem particularly interesting to me. (The link I gave is to a headline description of a talk from 2018). I find Render Quality to be a PITA; sometimes I get adequate subjective quality around RQ 0.1 (I don't much care about noise in hair) and now the horrible image size (PNG can't compress noise) can be fixed by the "de-noiser".
The Iray thread has been updated, the general highlights are to come
Thanks. I guess you mean this thread: https://www.daz3d.com/forums/discussion/335016/daz-studio-pro-4-12-nvidia-iray#latest
Note the minimum driver requirement mentioned in the update previous to the latest.
Where on earth did Tone Mapping and Environment settings go? They're gone from the Render Settings Tab.
I have to give credit when credit is due so... THANK YOU, to everyone working at/for Daz Production and all the private build testers, for working hard to give us this update less than one month after the Ampere cards are released!
Thanks ALOT Daz Team for Filament render option.
Still don't have alot time ATM, but did a quick test, in filament posing quick with IK by dragging body parts and rendering out a test anim with an image series. Went fast with tons of morphs and 4 characters in scene. 10 frames took like 30 seconds I think. Nice big step for creating animations in DazStudio. Well at least the design for now. Made my day!
I don't know if it's been reported but if anything in the scene has the Oso Blendy Shader applied to it Daz Studio crashes as soon as you hit "render" in Iray Render.
Either start a render or use the Iray Viewport Drawstyle for a sec, Tone Mapping and Environments will appear as as well as nodes in the Scene pane.
Ha! That's certainly true.
... And I'm silly enough
, although I keep backups of previous betas and have been known to revert.
Latest beta crashes on start up - nothing in the log file but event viewer shows:
This is on my old desktop (4790k + ATI 7950 display + GTX 1070 iray only). Installs fine on my laptop though (8850H + GTX 1070 display + iray)
Also, how is one supposed to manually change the environment hdr without having to resort to changing the viewport preview to iray? A rather unnecessary change methinks... and not user-friendly. Those short on vram will probably find it necessary to close down DS between setting the environment map in iray preview before initiating a final render - to flush vram properly.
Note: Bugs
I have a scene that caused the 'Tone Mapping Settings' and the 'Environment Settings' to cause nodes to be created in the scene tab. I deleted those nodes but the Enviromental and Tone Mapping Settings stayed in the renderer pane.
I tried to render in iRay Sun-Sky or Dome & Scene with Draw Dome on and in both case the iRay renderer drew the alpha channel for the sky (a grey & black checkerboard).
However, I saved the scene, exited, start DAZ, over the same scene but DS crash without generating a crash dump. So I open DAZ again, open the same scene again, and this time the 'Enviroment Settings' and 'Tone Settings' are complete missing.
There are conflicts in state I think in switching between Viewport and iRay to render and in Filament Preview and iRay Preview in the Viewport. Currently I have my scene set to iRay for render and Filament for Viewport.
Hmm, I see those too. Similar to Octane render setting nodes.
Oh Thank thank you! That did the trick! :)
Slight problem with all this automated adding and removing of settings as 'Nodes'.
I saved a scene with the Beta and it removed the SSIM stop condition from the menu. It was doing this every time I opened that particular file.
I had to open and save the file in the General Release to get the option back.
(...then, of course, the Beta added the added the Environment and tonemapping nodes again, giving me duplicates.)