Loading...
> >

Daz Studio Pro BETA - version 4.11.0.335! (*UPDATED*)

1…1718202223…32

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,344
    asyd said:

    Hello,

    Since yesterday the denoiser don't work on my Beta 4.11, before I've never had any problems.  Do somebody knows a reason why ?

    I didn't change anything , so I reinstalled the Beta but always the same problem.

    Thanks if someone has an idea

    ( Sorry for my English, it's not my mother tongue....)

    Is Iray using the GPU at all? There have been reports that the latest driver from nVidia is not playing nicely with Iray, so if you updated (or the system did automatically) that may be the issue.

  • asydasyd Posts: 6

    @ Sylvie1998 and @Richard Haseltine

    Effectively I installed the latest Nvidia drivers 2 days ago, so it may be that ! I'll downgrade the driver tomorrow and test,  thanks very much !!!!!

  • marius_ifmarius_if Posts: 48

    Thank you very much Miss Chohole and Miss Sylvie1998,

    my current version is "4.11.0.236", I was interested to have the latest build.

    I am always using the latest beta version and I've never had problems so far.

    Indeed the nvidia 418.81 driver got me the same headaches so, I did a clean install to 417.71 and everything works fine as before.

    I was thinking - since nvidia physx sdk 4 has been released - some awesome goodies will be present in the next Daz Studio Beta version.

    Thank you for being such wonderful people.

    Best regards,

    marius.

  • Rev2019Rev2019 Posts: 180
    sylvie1998 said:

    @pat1
     I have no issues with my 2080 and anti-aliasing.

     

    really?

    then i must have change something or you have changed something ;)?

    the only stuff i changed is that i have put in the rendering settings from this article

    https://magazine.renderosity.com/article/4864/6-weeks-with-daz-studio-week-4-rendering-in-iray

    those should not affect AA

    and in nvidia controlpanel i use pretty much the default settings.

    any clue what causes this?

    but ok you are using 417.71 and i use 417.01

    i may try the 71 drives also

  • barbultbarbult Posts: 24,755
    If your Pixel Filter Radius is too low you can get jaggies. Try rendering with the default Gaussian 1.5. If the jaggies are gone and it looks blurry, start experimenting with lower pixel filter radius values and maybe the Mitchell filter.
  • Rev2019Rev2019 Posts: 180

    Problem solved ! :)

    Per Pixel Shader was set to OFF for some reason.

    probably a shortcut command went wrong somewhere and turned it off i dont know ;) 

     

  • asydasyd Posts: 6

    All is OK since I downgraded nvidia driver to 417.71, the denoiser works again.

    Big thanks to @ Sylvie1998 and @Richard Haseltine

  • asydasyd Posts: 6

    OK so finally it doesn't work, it seems that rendering uses my CPU instead of my GPU (RTX 2080 Ti), even if checked and I tried to check/uncheck OptiX acceleration but no effects.... any ideas ?

  • asydasyd Posts: 6

    So when I render an animation the first image is good but then rendering uses CPU. When I look the Task Manager the VRAM don't decrease after a render so the second image of an animation always switch to CPU rendering....I never had this problem before....

  • Rev2019Rev2019 Posts: 180
    edited February 2019

    Antialiasing problem NOT solved.

    it looked like it at first because the viewport looked great without jaggies

    renderers still looks like crap

    RTX 2080 with Hardware ANTIALIASING turned on LOL

    what an downgrade.

    time to go back to the trusty 1050ti ;)

     

    Edit: finally i think i have found the problem

    running scripts that copies all settings from 4.10 wasnt a great idea it seems.

    https://www.daz3d.com/forums/discussion/307381/upgrading-to-rtx-2080-question#latest

    once i pressed DEFAULTS for Rendering settings again Antialiasing is back ON wow! :)

    what caused the problem i dont know but now it works!

    jaggies.jpg
    400 x 555 - 69K
    Post edited by Rev2019 on
  • alialovedreams_df822ebdefalialovedreams_df822ebdef Posts: 0
    pat1 said:

    Antialiasing problem NOT solved.

    it looked like it at first because the viewport looked great without jaggies

    renderers still looks like crap

    RTX 2080 with Hardware ANTIALIASING turned on LOL

    what an downgrade.

    time to go back to the trusty 1050ti ;)

     

    Edit: finally i think i have found the problem

    running scripts that copies all settings from 4.10 wasnt a great idea it seems.

    https://www.daz3d.com/forums/discussion/307381/upgrading-to-rtx-2080-question#latest

    once i pressed DEFAULTS for Rendering settings again Antialiasing is back ON wow! :)

    what caused the problem i dont know but now it works!

    I had similar problem when moved from 4.10 to 4.11. All my previous scenes opened with added some settings into Draw settings.

    The problem was in Draw settings - Filtering - Noise degrain(and its parametres like Radius and Blur). So I just made Noise degrain to 0 and all is fine:)

    Just check all your scenes if they have same parametres on. 

    uiuiui.JPG
    796 x 927 - 73K
    uiuiui.JPG
    796 x 927 - 73K
    attachment.JPG
    796 x 927 - 73K
  • OstadanOstadan Posts: 1,128

    I find the 4.11 beta on my Mac routinely crashes when loading .daz file-named scenes (I recently tried to load an old Maclean product, for example); 4.10 does not.

    Is there a handy batch script for converting .daz files to .duf?  Or is this considered a 'bug', and the intention will be to restore the backward compatibility for the old files.

  • stuart.lowsley@ntlworld.comstuart.lowsley@ntlworld.com Posts: 19
    Ostadan said:

    I find the 4.11 beta on my Mac routinely crashes when loading .daz file-named scenes (I recently tried to load an old Maclean product, for example); 4.10 does not.

    Is there a handy batch script for converting .daz files to .duf?  Or is this considered a 'bug', and the intention will be to restore the backward compatibility for the old files.

    Open them in 4.10 and save them as .DUF files.

     

  • OstadanOstadan Posts: 1,128

    And when 4.11 is out of beta and I have to uninstall 4.10?  The lack of backward compatibility with products that are still in the store is a bug.

     

    '

  • Richard HaseltineRichard Haseltine Posts: 102,344
    Ostadan said:

    And when 4.11 is out of beta and I have to uninstall 4.10?  The lack of backward compatibility with products that are still in the store is a bug.

    I have had DS crash on a range of .daz files for soem time - it seems to be hit and miss. This is why, in part, the format was switched.

  • asydasyd Posts: 6

    @sylvie1998

    I checked I was in 417.71 but I uninstalled the drivers completly before install it as you said. But the problem was still here, in fact after rendering sometime the VRAM doesn't clear by itself...so I must quit DAZ3d and open it again before the rendering of an big animation. Also I checked "memory" instead of "speed" in the rendering optimization and it seems to go better now, the VRAM is not full so that the denoiser can works.

    Thanks !

  • SpottedKittySpottedKitty Posts: 7,232
    Richard Haseltine said:
    I have had DS crash on a range of .daz files for soem time - it seems to be hit and miss. This is why, in part, the format was switched.

    Would I be right in guessing that a mass conversion of all remaining .daz products in the store into proper .duf format would be a non-trivial exercise? Or could it be reserved only for .daz files confirmed to be duds? I have a few .daz format Optitex dynamic clothes (and other stuff) that don't actually crash D|S, but they do kick up error messages. I'd be very interested in knowing what DAZ has in mind to solve this situation; after all, I've paid actual £££ for these products.

    FWIW, I don't think I've noticed any increase in the frequency of glitching .daz files in recent D|S versions.

  • MelanieLMelanieL Posts: 7,464
    SpottedKitty said:
    Richard Haseltine said:
    I have had DS crash on a range of .daz files for soem time - it seems to be hit and miss. This is why, in part, the format was switched.

    Would I be right in guessing that a mass conversion of all remaining .daz products in the store into proper .duf format would be a non-trivial exercise? Or could it be reserved only for .daz files confirmed to be duds? I have a few .daz format Optitex dynamic clothes (and other stuff) that don't actually crash D|S, but they do kick up error messages. I'd be very interested in knowing what DAZ has in mind to solve this situation; after all, I've paid actual £££ for these products.

    FWIW, I don't think I've noticed any increase in the frequency of glitching .daz files in recent D|S versions.

    +1 to this!

    Are we supposed to raise a bunch of tickets for all those purchased items that no longer work, in the hope of an update?

  • barbultbarbult Posts: 24,755
    MelanieL said:
    SpottedKitty said:
    Richard Haseltine said:
    I have had DS crash on a range of .daz files for soem time - it seems to be hit and miss. This is why, in part, the format was switched.

    Would I be right in guessing that a mass conversion of all remaining .daz products in the store into proper .duf format would be a non-trivial exercise? Or could it be reserved only for .daz files confirmed to be duds? I have a few .daz format Optitex dynamic clothes (and other stuff) that don't actually crash D|S, but they do kick up error messages. I'd be very interested in knowing what DAZ has in mind to solve this situation; after all, I've paid actual £££ for these products.

    FWIW, I don't think I've noticed any increase in the frequency of glitching .daz files in recent D|S versions.

    +1 to this!

    Are we supposed to raise a bunch of tickets for all those purchased items that no longer work, in the hope of an update?

    6 months ago, I submitted a help request about a .daz file from the store that would not open in DS 4.11.0.171 (the current beta at the time). That request is still open (i.e. not fixed yet). That help request was forwarded to the bug tracker at that time. 

  • MelanieLMelanieL Posts: 7,464
    barbult said:
    MelanieL said:
    SpottedKitty said:
    Richard Haseltine said:
    I have had DS crash on a range of .daz files for soem time - it seems to be hit and miss. This is why, in part, the format was switched.

    Would I be right in guessing that a mass conversion of all remaining .daz products in the store into proper .duf format would be a non-trivial exercise? Or could it be reserved only for .daz files confirmed to be duds? I have a few .daz format Optitex dynamic clothes (and other stuff) that don't actually crash D|S, but they do kick up error messages. I'd be very interested in knowing what DAZ has in mind to solve this situation; after all, I've paid actual £££ for these products.

    FWIW, I don't think I've noticed any increase in the frequency of glitching .daz files in recent D|S versions.

    +1 to this!

    Are we supposed to raise a bunch of tickets for all those purchased items that no longer work, in the hope of an update?

    6 months ago, I submitted a help request about a .daz file from the store that would not open in DS 4.11.0.171 (the current beta at the time). That request is still open (i.e. not fixed yet). That help request was forwarded to the bug tracker at that time.

    Hmm, sounds like it's going the way of two of mine raised months (actually years in one case) ago.

  • VEGAVEGA Posts: 86

    New Nvidia driver 418.91 still falls back to CPU when trying Iray rendering.

  • DoctorJellybeanDoctorJellybean Posts: 8,654
    VEGA said:

    New Nvidia driver 418.91 still falls back to CPU when trying Iray rendering.

    What card are you using?

  • VEGAVEGA Posts: 86
    edited February 2019
    DoctorJellybean said:
    VEGA said:

    New Nvidia driver 418.91 still falls back to CPU when trying Iray rendering.

    What card are you using?

     

    RTX 2080Ti

    Post edited by VEGA on
  • nicsttnicstt Posts: 11,715
    asyd said:

    @sylvie1998

    I checked I was in 417.71 but I uninstalled the drivers completly before install it as you said. But the problem was still here, in fact after rendering sometime the VRAM doesn't clear by itself...so I must quit DAZ3d and open it again before the rendering of an big animation. Also I checked "memory" instead of "speed" in the rendering optimization and it seems to go better now, the VRAM is not full so that the denoiser can works.

    Thanks !

    What sort of uninstall did you use?

    Display Driver Uninstaller does the best job of getting rid of recalcitrant graphics card driver file remnants; (no both AMD and Nvidia suck at this).

  • DoctorJellybeanDoctorJellybean Posts: 8,654

    I usually select Custom and then check the Clean Installation option when installing an update.

  • bigtastybigtasty Posts: 7
    asyd said:

    @sylvie1998

    I checked I was in 417.71 but I uninstalled the drivers completly before install it as you said. But the problem was still here, in fact after rendering sometime the VRAM doesn't clear by itself...so I must quit DAZ3d and open it again before the rendering of an big animation. Also I checked "memory" instead of "speed" in the rendering optimization and it seems to go better now, the VRAM is not full so that the denoiser can works.

    Thanks !

     

    I noticed the same problem. Did you have any success trying other drivers?

  • nicsttnicstt Posts: 11,715
    sylvie1998 said:

    @VEGA

    From driver 418.91 release notes, known issues section, page 15:

     - [Iray][OptiX]: Iray GPU acceleration crashes and falls back to CPU acceleration. [2503738]

    So yes, still not fixed, don't update.

    @nicstt

    In Windows 10 if you don't check clean install in NVIDIA driver setup the old drivers will remain cached. Since NVIDIA drivers are now 1 GB extracted, having previous 10 versions cached will rob you of 10 GB of space and you won't even know it's there. As far as I know DDU won't clean out anything than current video drivers.

     

    That's good to know; not sure what I did on the last installation as it has been many, many months; it works, it isn't broke... So sure as hell not fixing it.

This discussion has been closed.