Update 4.14 no Iray? (Solved)

CASINCCASINC Posts: 76
edited November 2020 in The Commons

Just unfortunately downloaded update 4.14 and well, it does nothing in Iray. Renders blank screens, no viewport previews, basically nothing is happening. Anybody else? Any ideas? I'm stumped.

Post edited by Daz Jack Tomalin on

Comments

  • scorpioscorpio Posts: 8,480

    Check your graphic card drivers are currant

  • PerttiAPerttiA Posts: 10,024

    Did you read the requirements, especially the ones talking about required GPU driver version?

  • HylasHylas Posts: 5,070

    Does this mean 4.14 can't do Iray renders with CPU?

  • scorpioscorpio Posts: 8,480
    edited November 2020
    Hylas said:

    Does this mean 4.14 can't do Iray renders with CPU?

    No its just if trying to do renders using the GPU and not allowing DS to drop to CPU then Iray won't render if the drivers aren't up to date. At least thats how I think it works.

    Post edited by scorpio on
  • CASINCCASINC Posts: 76

    checked drivers, they are up to date. The computer is a 2 month old MSI i9 with a RTX 2070.

  • For reference, what drivers are you using?

  • Noah LGPNoah LGP Posts: 2,617
    edited November 2020

    The current driver version is 457.30 (2020.11.9)

    https://www.nvidia.fr/Download/index.aspx?lang=en

    Post edited by Noah LGP on
  • CASINCCASINC Posts: 76
    Noah LGP said:

    The current driver version is 457.30 (2020.11.9)

    https://www.nvidia.fr/Download/index.aspx?lang=en

    ok, ya I checked, running 442.19

  • Ghosty12Ghosty12 Posts: 2,065
    edited November 2020

    The one big change that I noticed is that the environment and tonemapper options are now in the scene pane, and no longer in the render settings tab.. The other thing to get the options to even show up you have to start a iRay render and they appear in the scene tab..

    Post edited by Ghosty12 on
  • PerttiAPerttiA Posts: 10,024
    CASINC said:
    Noah LGP said:

    The current driver version is 457.30 (2020.11.9)

    https://www.nvidia.fr/Download/index.aspx?lang=en

    ok, ya I checked, running 442.19

    https://www.daz3d.com/forums/discussion/449356

    REQUIRES NVIDIA Driver 451.48 (or newer)

  • HylasHylas Posts: 5,070
    scorpio said:
    Hylas said:

    Does this mean 4.14 can't do Iray renders with CPU?

    No its just if trying to do renders using the GPU and not allowing DS to drop to CPU then Iray won't render if the drivers aren't up to date. At least thats how I think it works.

    Thx yes

  • There we go then :)

  • CASINCCASINC Posts: 76

    Thanks Everybody, updating the nvidia driver worked.

  • So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

  • So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

    Yep, it's not Daz' fault mind you, it's Iray itself having been upgraded. I was on a GTX 760 TI before upgrading, and I was constantly getting warnings in my render logs about Iray throwing a fit that support for my GPU was ending soon. I do wonder though if the new filament renderer works on older cards. If so, that old card of mine might have a new use. lol

  • So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

    I don't think anything but the Intel newest iGPU's, the ones in laptops, are doing that. Is there a reason software decode isn't acceptable?

     

  • xyer0xyer0 Posts: 6,057
    Ghosty12 said:

    The one big change that I noticed is that the environment and tonemapper options are now in the scene pane, and no longer in the render settings tab.. The other thing to get the options to even show up you have to start a iRay render and they appear in the scene tab..

    I wonder how that works with older sessions.

  • scorpioscorpio Posts: 8,480
    Ghosty12 said:

    The one big change that I noticed is that the environment and tonemapper options are now in the scene pane, and no longer in the render settings tab.. The other thing to get the options to even show up you have to start a iRay render and they appear in the scene tab..

    Nope - you just need to add the node to the scene.

  • Noah LGPNoah LGP Posts: 2,617
    edited November 2020

    So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

     

    Same thing when the driver isn't updated. Sometimes the new driver versions damage the old graphic cards.

    Post edited by Noah LGP on
  • Ghosty12Ghosty12 Posts: 2,065
    edited November 2020
    xyer0 said:
    Ghosty12 said:

    The one big change that I noticed is that the environment and tonemapper options are now in the scene pane, and no longer in the render settings tab.. The other thing to get the options to even show up you have to start a iRay render and they appear in the scene tab..

    I wonder how that works with older sessions.

    Found out that they are now part of the create menu, seems weird to me but has me thinking that Filament may have something to do with this change..

    scorpio said:
    Ghosty12 said:

    The one big change that I noticed is that the environment and tonemapper options are now in the scene pane, and no longer in the render settings tab.. The other thing to get the options to even show up you have to start a iRay render and they appear in the scene tab..

    Nope - you just need to add the node to the scene.

    Ahh k cheers for the info, just weird that they made this change and as I said above, I am wondering if it has anything to do with Filament..

    Post edited by Ghosty12 on
  • prixatprixat Posts: 1,590
    All the Turing cards can decode h.265 4:4:4. They should manage 4:2:2 easily.
  • So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

    I don't think anything but the Intel newest iGPU's, the ones in laptops, are doing that. Is there a reason software decode isn't acceptable?

     

    A snappy and smooth editing experience. Editing a video that stutters or frozen half the time is very annoying and not fun. At 1080p it might be doable, at 4K or 8K not. A graphics card is upgradable, a processor not so. You would basically have to rebuild your whole computer.

     

    Noah LGP said:

    So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

     

    Same thing when the driver isn't updated. Sometimes the new driver versions damage the old graphic cards.

    Also something I don't like doing.

     

    prixat said:
    All the Turing cards can decode h.265 4:4:4. They should manage 4:2:2 easily.

    Stupidly enough that is true. Annoying that the only chroma subsampling they don't support is 4:2:2. It is not a new issue i believe.

  • FauvistFauvist Posts: 2,152

    Are renders on Mac CPUs still possible, or not?  

  • nonesuch00nonesuch00 Posts: 18,316
    Fauvist said:

    Are renders on Mac CPUs still possible, or not?  

    yes

  • So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

    Yep, it's not Daz' fault mind you, it's Iray itself having been upgraded. I was on a GTX 760 TI before upgrading, and I was constantly getting warnings in my render logs about Iray throwing a fit that support for my GPU was ending soon. I do wonder though if the new filament renderer works on older cards. If so, that old card of mine might have a new use. lol

    The argument about using older cards that DAZ uses was no longer valid the moment they decided to update Iray as well, essentially disabeling quality renders on old hardware. Filament does not seem to be a worthy replacement for Iray at the moment.

  • So Kepler is removed huh. I guess 4.12 will be my final version then (Geforce 770 GTX 4GB). I am not buying a new graphics card before I known which graphics card will support HEVC 10bit 4:2:2 hardware decoding (nothing supports that yet, it is necessary for videos from the Canon EOS R5)

    Yep, it's not Daz' fault mind you, it's Iray itself having been upgraded. I was on a GTX 760 TI before upgrading, and I was constantly getting warnings in my render logs about Iray throwing a fit that support for my GPU was ending soon. I do wonder though if the new filament renderer works on older cards. If so, that old card of mine might have a new use. lol

    The argument about using older cards that DAZ uses was no longer valid the moment they decided to update Iray as well, essentially disabeling quality renders on old hardware. Filament does not seem to be a worthy replacement for Iray at the moment.

    Filament isn't meant to be an Iray repalcement. Daz may well have no choice but to update Iray when they update DS, but even if they do using an older version would mean older bugs would remain.

  • That is true Richard, I wouldn't like to release software with remaining bugs myself. I am just unlucky that my graphics card is not supported anymore the moment they decide to improve the animation features (or so they claim, but I have not seen anything about what they exactly mean by that). The TS was lucky that only his drivers were the issue, not his card's microarchitecture or he might have been forced to downgrade. 

  • Ghosty12 said:

    The one big change that I noticed is that the environment and tonemapper options are now in the scene pane, and no longer in the render settings tab.. The other thing to get the options to even show up you have to start a iRay render and they appear in the scene tab..

    http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log_4_14_0_8#4_12_2_41

    "Scenes that contain render settings will automatically cause the singleton node to be created/replaced"
    "Application of a Render Settings Preset will cause the singleton node to be created/replaced"
    "The first render performed with the NVIDIA Iray renderer will cause the singleton node to be created"
    "Create > New Environment Options Node... will cause the singleton node to be created/replaced"

  • jdllareusjdllareus Posts: 1
    edited March 2021

    Hi, I have a similar issue and was hoping to get some help. My computer has an older graphics card, Geforce GTX 680M and the current driver is 425.31 (release date 4/11/2019 (my understanding the most recent driver). When I try to render the, the yellow bar at the bottom just increases over and over... Never actually renders for Iray.

    Post edited by jdllareus on
Sign In or Register to comment.