Daz Studio 6.25[.0.x], General Release!

167891012»

Comments

  • Richard HaseltineRichard Haseltine Posts: 110,414

    DavidGB said:

    junkgoshere said:

    DavidGB said:

    Oh yes, keep meaning to say:

    Not a big thing, I suppose, but the kind of detail that makes software feel unfinished - DS6, as with DS4, has an option in Preferences>Interface>General to switch the Splash Screen between two images, default and alternate. As I find the default cyberpunk 'babe' distinctly unappealing, I switched to 'alternate', which is ... a completely blank black 'picture'. Which is an improvement over the default to me, but I presume there's supposed to be an actual alternate image, like the pod of leaping orcas in DS4. If it's supposed to be a 'blank' option it should say 'blank' in the preferences rather than 'alternate'.

    I wonder if you can locate that blank black picture and edit it with your own...

     

    I did actually spend a little time yesterday looking through the Program Files and AppData folders of both DS6 and DS4.24 trying to find the splash screen images, but didn't find them.

    I beleive theya re embedded, not stored as image files, so that isn't an option.

  • Richard HaseltineRichard Haseltine Posts: 110,414

    kreutzer said:

    Olo_Ordinaire said:

    I assume the difficulties with texture-shaded viewport performance and other issues will eventually be resolved.  But here's why a move to Studio v6 is not tempting, for me.

    I use Mesh Grabber, a plug-in, a lot -- in almost every render.  If I move to Studio v6, I have to throw all my investment in Mesh Grabber and a handful of other tools away.  Not only that, but if I want to have Mesh Grabber functionality, it now costs $200 PER YEAR just to continue with Mesh Grabber capability.  I have to buy the Premier subscription just to have that tool's equivalent available.

    Since I don't put vampire-ware software on my machine, DAZ Studio 6 won't be an option.  For those that suggest setting up in Studio v4 and rendering in Studio v6, that sounds like a ridiculously complex and error-prone workflow.  Not going to happen.

    I guess, mesh grabber and the other plugins will be portet to ds6?

    Not for the oens Daz purchased and made into Premier-exclusive features, as far as I am aware. Geometry Sculptor will load Mesh Grabber modifiers, but there will not be Mesh Grabber updates as such.

  • Richard HaseltineRichard Haseltine Posts: 110,414

    meaznet said:

    I'm having some issues with MikeD's Icon Creator Pro after installing Studio 6, and I understand that there may be some updates needed from them for it to work properly, but where should I be finding a related Forum?  Would that be here or is there a way to look directly at the particular Creator's Forum?

    Whata re you wanting? Icon Creator is a script rather than a plug-in, so what it requires is harder to know. I am sure the author is aware of the ssues, though he usually has a support thread in the Daz PA Commercial forum here if you want to check for other reports or add your own.

  • LeanaLeana Posts: 13,251
    edited 2:43PM

    kreutzer said:

    Olo_Ordinaire said:

    I assume the difficulties with texture-shaded viewport performance and other issues will eventually be resolved.  But here's why a move to Studio v6 is not tempting, for me.

    I use Mesh Grabber, a plug-in, a lot -- in almost every render.  If I move to Studio v6, I have to throw all my investment in Mesh Grabber and a handful of other tools away.  Not only that, but if I want to have Mesh Grabber functionality, it now costs $200 PER YEAR just to continue with Mesh Grabber capability.  I have to buy the Premier subscription just to have that tool's equivalent available.

    Since I don't put vampire-ware software on my machine, DAZ Studio 6 won't be an option.  For those that suggest setting up in Studio v4 and rendering in Studio v6, that sounds like a ridiculously complex and error-prone workflow.  Not going to happen.

    I guess, mesh grabber and the other plugins will be portet to ds6?

    Whether a plugin or script will get a DS6 version or not will depend on if the vendor creates one.
    We already know that some tools won't get a DS6 version as the PA is not active anymore (for example GenX and the other Dimension3D tools, since the PA passed away)
    In the case of Mesh Grabber and other plugins by ManFriday, since Daz bought several of them as the base to their premier plugins it's unfortunately unlikely that the previous standalone version will get a DS6 update.

    Post edited by Leana at
  • prinzeugenprinzeugen Posts: 40

    what are the system requirments for Daz 6  ? 

  • kreutzerkreutzer Posts: 14

    Leana said:

    kreutzer said:

    Olo_Ordinaire said:

    I assume the difficulties with texture-shaded viewport performance and other issues will eventually be resolved.  But here's why a move to Studio v6 is not tempting, for me.

    I use Mesh Grabber, a plug-in, a lot -- in almost every render.  If I move to Studio v6, I have to throw all my investment in Mesh Grabber and a handful of other tools away.  Not only that, but if I want to have Mesh Grabber functionality, it now costs $200 PER YEAR just to continue with Mesh Grabber capability.  I have to buy the Premier subscription just to have that tool's equivalent available.

    Since I don't put vampire-ware software on my machine, DAZ Studio 6 won't be an option.  For those that suggest setting up in Studio v4 and rendering in Studio v6, that sounds like a ridiculously complex and error-prone workflow.  Not going to happen.

    I guess, mesh grabber and the other plugins will be portet to ds6?

    Whether a plugin or script will get a DS6 version or not will depend on if the vendor creates one.
    We already know that some tools won't get a DS6 version as the PA is not active anymore (for example GenX and the other Dimension3D tools, since the PA passed away)
    In the case of Mesh Grabber and other plugins by ManFriday, since Daz bought several of them as the base to their premier plugins it's unfortunately unlikely that the previous standalone version will get a DS6 update.

    hmmm - bought meshgabber and hoped, that it will work also in ds6 some day...
    so lets hope, that someone develops a compatibility-layer for DS4 in DS6 to use the old software. :)

  • LeanaLeana Posts: 13,251

    prinzeugen said:

    what are the system requirments for Daz 6  ? 

      There is some info about requirements in the first post of the evergreen thread: https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen

  • stephenschoonstephenschoon Posts: 365

    So DIM insists that you install Daz 6 even though I only wanted to install 4.24...

    Can't see how to disable it so I guess I'll have to install it then even though I was going to wait.

    What did we all learn from Microsoft ? Never install just released software...

    S.

  • Hi all - how is iray preview on the 5XXX Series cards - is it better than DS4 on default settings, has anyone done a comparison? - considering either a 5070ti or a 5080ti (current is 4070S).  If iray was faster I would get more done!

    Thanks

  • DavidGBDavidGB Posts: 590

    kreutzer said:

    Leana said:

    kreutzer said:

    Olo_Ordinaire said:

    I assume the difficulties with texture-shaded viewport performance and other issues will eventually be resolved.  But here's why a move to Studio v6 is not tempting, for me.

    I use Mesh Grabber, a plug-in, a lot -- in almost every render.  If I move to Studio v6, I have to throw all my investment in Mesh Grabber and a handful of other tools away.  Not only that, but if I want to have Mesh Grabber functionality, it now costs $200 PER YEAR just to continue with Mesh Grabber capability.  I have to buy the Premier subscription just to have that tool's equivalent available.

    Since I don't put vampire-ware software on my machine, DAZ Studio 6 won't be an option.  For those that suggest setting up in Studio v4 and rendering in Studio v6, that sounds like a ridiculously complex and error-prone workflow.  Not going to happen.

    I guess, mesh grabber and the other plugins will be portet to ds6?

    Whether a plugin or script will get a DS6 version or not will depend on if the vendor creates one.
    We already know that some tools won't get a DS6 version as the PA is not active anymore (for example GenX and the other Dimension3D tools, since the PA passed away)
    In the case of Mesh Grabber and other plugins by ManFriday, since Daz bought several of them as the base to their premier plugins it's unfortunately unlikely that the previous standalone version will get a DS6 update.

    hmmm - bought meshgabber and hoped, that it will work also in ds6 some day...
    so lets hope, that someone develops a compatibility-layer for DS4 in DS6 to use the old software. :)

    I'm getting flashbacks to 2004-7. As soon as the very first DS - the 0.9 public beta - came out I wanted to use it and abandon Poser completely. But ended up having to keep Poser 6 on the go just because in that I could load figures and props (DAZ back then still produced Poser format cr2 figures and pp2 props, pre DS4 and .duf) into it to delete bits, break props up into parts, and define my own groups on, especially, clothes that I could then magnet/D-Form just that part of the mesh I had defined to make custom morphs in the figures that I could then load and use in DS1-3. Couldn't do any of those things in DS back then, so just had to throw things over into Poser 6, especially to make morphs affecting just the geometry I wanted, to then use in DS. I see it's going to be like that again except keeping DS4.24 to throw things into from DS6 to meshgrab and morph. Plus ça change ...

  • crashworshipcrashworship Posts: 248

    Leana said:

    mjmeyer said:

    b) Is DAZ Studio 6 only a temporary trial version and will I have to subscribe to an expensive plan to really use it?

    No, it's not. It works like DS4 did, there's a free version and if you're a Premier member you have access to more features.

    "Premier member you have access to more features" 

    Eventually, because I've discovered that even though the the Premier plugins have been installed, they are unavailable, at least on my Mac version. No auto save, no pose conversion, no face transfer, no geometry sculpting, no shape transfer. Or, all the things I upgraded to Premier to have available. Daz sure does want you to use that AI feature though. Really wants you to. Why is that? 

  • SaintSaint Posts: 80

    Anonymous Poster said:

    Hi all - how is iray preview on the 5XXX Series cards - is it better than DS4 on default settings, has anyone done a comparison? - considering either a 5070ti or a 5080ti (current is 4070S).  If iray was faster I would get more done!

    Thanks

    Other users I've spoken to have the same experience I do: trivial increases in rendering and simulation speeds, and the same viewport issues as most users have complained about. Not sure about 5090 users--don't know any of those moneybags.

  • DoctorJellybeanDoctorJellybean Posts: 9,963
    AndrewJJP said:

    chevybabe25 said:

    "Are there any known isssues with the Geometry Scultptor on strand-based hair? Basically, I cannot get it to work."

     

    For strand hair you have to select vertices.. is that what you are doing?

    Trying again. You are right, in 4.24 I was selecting the hair, and in 6.25, the base. Stupid mistake - thanks! :D

    BUT, it still doesn't work.

    • In 4.24  I can drag the hair. The machine lets me edit it no trouble at all. It's pretty much instant and completely respnsive.
    • In 6.25 a dialog appears briefly to say it' building the geometry (which is not an issue). I then click on the hair. The UI freezes completely for an extended period before it eventually recovers.

    I've done this a few tiems. The shortest freeze was 20 seconds, the longest around a minute. The operating system displays the ghost window and the Daz title bad changes to "not responding" indicating that Daz has frozen and cannot process its message queue. It's a proper freeze. Since this works well in 4.24, there is no issue with the hardware. In both cases, I am using texture shading in the viewport.

    You cannot move the hair. It is 100% reproducible for me, and I class this as a bug, not a performance issue since it completely prevents the feature from beingused. For me anyway. I wonder if anyone else sees this?

     

    Could you please report it.
  • AndrewJJPAndrewJJP Posts: 776
    edited 8:32PM

    Yes, I did report it via ticket. I posted the report above. If you would like to read it, it is the last post on page 9.

    Post edited by AndrewJJP at
  • DavidGBDavidGB Posts: 590

    So, I've finally and very belatedly figured out what to do about a problem ... but it's left me with another puzzle. As explained earlier in this thread, I re-rendered with DS6 a scene I did some months ago and rendered then in 4.24. I found DS6 rendered it in 6 minutes as compared with 48m in 4.24, which was good, but the skin of a G8F and G8M came out looking like smooth plastic, which wasn't. Same laptop, same scene, no settings changed. I hadn't realised until posts in this thread that 4.24 hadn't been able to use the laptop's RTX 5070, so the original render was CPU only, whereas the new one, with the plastic-looking skin, was a GPU render. My brain struggles through brain fog these days, so it took awhile, but it finally occurred to me to look at the 4.24 render and the 6 render at x300% magnification, when it became obvious that the DS4.24 render had lots of tiny dark dots and little lines over the skin in a kind of dither pattern, and that was what made it look 3d-skin-like at x 100% mag, whereas the DS6 GPU render had no dark dots etc and was just pure shades of colour fading into each other, giving it the flat plastic look. Which had me staring blankly at this for some time. Vague thoughts that the DS6 GPU render was being smoothed in some fashion. Then, belatedly, I remembered that some time ago I had turned on the Post Denoiser in Render Settings though back then I hadn't noticed any difference. Turned it off, did a DS6 GPU render of the same scene again, and lo and behold the dithered effect giving 3D-looking-skin reappeared, as in my DS4.24 renders, but in the 6 minutes rather than the 4.24 48 minutes. So, immediate problem solved.

    My remaining question, though, is why the Post Denoiser had no effect on the DS4.24 CPU renders. Do some of those Render Settings only affect GPU renders but not CPU renders? And if so, which settings work on GPU but not CPU renders? There's no indication in the interface.

    Oh yes, second question. I actually had 4 versions of that scene saved from DS4.24, but when I started DS6, loaded one scene, rendered it, loaded another, rendered it, then another, the first rendered using the GPU, but the subsequent ones used the CPU. Er ... I'm wondering if the first one 'filled up' the GPU card's RAM with textures, so it had to fall back to the CPU to do the others. But if that's so, how do I flush the GPU RAM short of closing then re-opening DS6?

  • Richard HaseltineRichard Haseltine Posts: 110,414

    DavidGB said:

    So, I've finally and very belatedly figured out what to do about a problem ... but it's left me with another puzzle. As explained earlier in this thread, I re-rendered with DS6 a scene I did some months ago and rendered then in 4.24. I found DS6 rendered it in 6 minutes as compared with 48m in 4.24, which was good, but the skin of a G8F and G8M came out looking like smooth plastic, which wasn't. Same laptop, same scene, no settings changed. I hadn't realised until posts in this thread that 4.24 hadn't been able to use the laptop's RTX 5070, so the original render was CPU only, whereas the new one, with the plastic-looking skin, was a GPU render. My brain struggles through brain fog these days, so it took awhile, but it finally occurred to me to look at the 4.24 render and the 6 render at x300% magnification, when it became obvious that the DS4.24 render had lots of tiny dark dots and little lines over the skin in a kind of dither pattern, and that was what made it look 3d-skin-like at x 100% mag, whereas the DS6 GPU render had no dark dots etc and was just pure shades of colour fading into each other, giving it the flat plastic look. Which had me staring blankly at this for some time. Vague thoughts that the DS6 GPU render was being smoothed in some fashion. Then, belatedly, I remembered that some time ago I had turned on the Post Denoiser in Render Settings though back then I hadn't noticed any difference. Turned it off, did a DS6 GPU render of the same scene again, and lo and behold the dithered effect giving 3D-looking-skin reappeared, as in my DS4.24 renders, but in the 6 minutes rather than the 4.24 48 minutes. So, immediate problem solved.

    My remaining question, though, is why the Post Denoiser had no effect on the DS4.24 CPU renders. Do some of those Render Settings only affect GPU renders but not CPU renders? And if so, which settings work on GPU but not CPU renders? There's no indication in the interface.

    The Post Render Denoiser uses the GPU, so it isn't available for CPU renders.

    Oh yes, second question. I actually had 4 versions of that scene saved from DS4.24, but when I started DS6, loaded one scene, rendered it, loaded another, rendered it, then another, the first rendered using the GPU, but the subsequent ones used the CPU. Er ... I'm wondering if the first one 'filled up' the GPU card's RAM with textures, so it had to fall back to the CPU to do the others. But if that's so, how do I flush the GPU RAM short of closing then re-opening DS6?

    Had you closed the previous renders? As long as they are open their data is still in GPU memory. 

  • Richard HaseltineRichard Haseltine Posts: 110,414

    stephenschoon said:

    So DIM insists that you install Daz 6 even though I only wanted to install 4.24...

    Can't see how to disable it so I guess I'll have to install it then even though I was going to wait.

    What did we all learn from Microsoft ? Never install just released software...

    S.

    Uncheck everything (or at least evereything you don't want,) make sure the box at bottom left isn't telling it to auto-run the feature, and click Accept (even if you have deselected everythiing). It then won't appear in future.

  • DavidGBDavidGB Posts: 590

    Richard Haseltine said:

    DavidGB said:

     

    My remaining question, though, is why the Post Denoiser had no effect on the DS4.24 CPU renders. Do some of those Render Settings only affect GPU renders but not CPU renders? And if so, which settings work on GPU but not CPU renders? There's no indication in the interface.

    The Post Render Denoiser uses the GPU, so it isn't available for CPU renders.

    So the last part of my question - which settings are GPU only? Is there a list somewhere? You'd think DS could not show, or fade out, options that don't apply to the selected renderer. Or group them under a 'GPU only' heading.

    Oh yes, second question. I actually had 4 versions of that scene saved from DS4.24, but when I started DS6, loaded one scene, rendered it, loaded another, rendered it, then another, the first rendered using the GPU, but the subsequent ones used the CPU. Er ... I'm wondering if the first one 'filled up' the GPU card's RAM with textures, so it had to fall back to the CPU to do the others. But if that's so, how do I flush the GPU RAM short of closing then re-opening DS6?

    Had you closed the previous renders? As long as they are open their data is still in GPU memory. 

    I ... think I'd closed them, but am not sure. As I say, I don't have memory minute to minute as a medication side-effect. I suppose I need to try that again, making sure I close them ... if I can remember what I'm doing and why I'm doing it while I'm doing it, which is not at all guaranteed. 

Sign In or Register to comment.