Loading...
> >

DS 4.22 No Longer Supports .EXR

warlordnikwarlordnik Posts: 41
edited November 2023 in Daz Studio Discussion

After upgrading to DS 4.22, I was about to render a scene with Flipmode's (vendor) HDRI products and it just gave me the whole scene lit in a pink light.  I discovered that all of Flipmode's HDRIs are in .EXR format, as opposed to the more common .HDR.

Are .EXR formated HDRI no longer supported?  If so, then ALL of Flipmode's products are useless!  They were definitely supported by DS 4.21.

 

I submitted a ticket, but seeing how it's the weekend, I probably won't hear back for a few days.

 

Does anybody have a workaround this issue?  I tried using GIMP to convert the .EXR to .HDR but the conversion didn't take.

Post edited by warlordnik on

Comments

  • GordigGordig Posts: 10,072

    It seems to be a known issue: https://www.daz3d.com/forums/discussion/comment/8430651/#Comment_8430651

  • warlordnikwarlordnik Posts: 41

    Gordig said:

    It seems to be a known issue: https://www.daz3d.com/forums/discussion/comment/8430651/#Comment_8430651

    Excellent!  Thanks so very much!  I'll go check out that thread for potential solutions!  Cheers! 

  • Richard HaseltineRichard Haseltine Posts: 101,032

    To be clear, .exr is supported but the new image-handling library that nVidia has switched to for Iray (Open Image IO, I think, instead of FreeImage) has problems with a few files in that format - whether it is the application used to create them or some particular setting we don't know, but it looks as if one of the colour channels is dropped or mis-interpreted (I wonder if it is related to a compression algorithm).

  • warlordnikwarlordnik Posts: 41

    Richard Haseltine said:

    To be clear, .exr is supported but the new image-handling library that nVidia has switched to for Iray (Open Image IO, I think, instead of FreeImage) has problems with a few files in that format - whether it is the application used to create them or some particular setting we don't know, but it looks as if one of the colour channels is dropped or mis-interpreted (I wonder if it is related to a compression algorithm).

    Thanks, Richard.  Yeah, I read the other forum post where Flipmode says he'll wait a few days for Daz, but you chime in to say this is an Iray issue.  Hopefully he just recompiles his .EXR files to a more updated version, or just converts them to .HDR.

    Cheers! 

  • Richard HaseltineRichard Haseltine Posts: 101,032

    warlordnik said:

    Richard Haseltine said:

    To be clear, .exr is supported but the new image-handling library that nVidia has switched to for Iray (Open Image IO, I think, instead of FreeImage) has problems with a few files in that format - whether it is the application used to create them or some particular setting we don't know, but it looks as if one of the colour channels is dropped or mis-interpreted (I wonder if it is related to a compression algorithm).

    Thanks, Richard.  Yeah, I read the other forum post where Flipmode says he'll wait a few days for Daz, but you chime in to say this is an Iray issue.  Hopefully he just recompiles his .EXR files to a more updated version, or just converts them to .HDR.

    Cheers! 

    he's posted to say that he has now done so, and sent in an update. (smug And apparently it was the compression algorithm /smug)

  • warlordnikwarlordnik Posts: 41

    Richard Haseltine said:

    warlordnik said:

    Richard Haseltine said:

    To be clear, .exr is supported but the new image-handling library that nVidia has switched to for Iray (Open Image IO, I think, instead of FreeImage) has problems with a few files in that format - whether it is the application used to create them or some particular setting we don't know, but it looks as if one of the colour channels is dropped or mis-interpreted (I wonder if it is related to a compression algorithm).

    Thanks, Richard.  Yeah, I read the other forum post where Flipmode says he'll wait a few days for Daz, but you chime in to say this is an Iray issue.  Hopefully he just recompiles his .EXR files to a more updated version, or just converts them to .HDR.

    Cheers! 

    he's posted to say that he has now done so, and sent in an update. (smug And apparently it was the compression algorithm /smug)

    Awesome!  Incidentally, I did so manually using Photoshop.  Yeah, it was definitely a compression thing.  Flipmode's .EXRs were in the double digit MBs, while the best PS could do was compress them down to the hundreds of MBs.  Not sure what black magic sacrifice he made to Eldrich gods to get it down that small in the first place! 

  • FlipmodeFlipmode Posts: 909

    warlordnik said:

    Awesome!  Incidentally, I did so manually using Photoshop.  Yeah, it was definitely a compression thing.  Flipmode's .EXRs were in the double digit MBs, while the best PS could do was compress them down to the hundreds of MBs.  Not sure what black magic sacrifice he made to Eldrich gods to get it down that small in the first place! 

    Photoshop > ProEXR Plugin > Luminance/Chroma compression. wink

    Took me a while to figure that out back then, trying to make the HDRIs more useable on low-end systems.
    Like Richard said, I submitted the updates ... across 30+ products the files grew from about 5GB to 15GB of data.
    I´d still prefer if Daz could add that compression support back in tbh..
    Anyway, I am sorry for the trouble you guys are having right now with those sets.

     

    Richard Haseltine said:

    To be clear, .exr is supported but the new image-handling library that nVidia has switched to for Iray (Open Image IO, I think, instead of FreeImage) has problems with a few files in that format - whether it is the application used to create them or some particular setting we don't know, but it looks as if one of the colour channels is dropped or mis-interpreted (I wonder if it is related to a compression algorithm).

    Good guess Richard, and thanks for helping keeping everyone informed!

    Don´t you think Daz has Coders capable of making changes to Iray related stuff if they need it?
    E.g. in this case add compatibility to OpenImage, or use FreeImage as fallback.

     

     

  • Richard HaseltineRichard Haseltine Posts: 101,032

    Flipmode said:

    warlordnik said:

    Awesome!  Incidentally, I did so manually using Photoshop.  Yeah, it was definitely a compression thing.  Flipmode's .EXRs were in the double digit MBs, while the best PS could do was compress them down to the hundreds of MBs.  Not sure what black magic sacrifice he made to Eldrich gods to get it down that small in the first place! 

    Photoshop > ProEXR Plugin > Luminance/Chroma compression. wink

    Took me a while to figure that out back then, trying to make the HDRIs more useable on low-end systems.
    Like Richard said, I submitted the updates ... across 30+ products the files grew from about 5GB to 15GB of data.
    I´d still prefer if Daz could add that compression support back in tbh..
    Anyway, I am sorry for the trouble you guys are having right now with those sets.

     

    Richard Haseltine said:

    To be clear, .exr is supported but the new image-handling library that nVidia has switched to for Iray (Open Image IO, I think, instead of FreeImage) has problems with a few files in that format - whether it is the application used to create them or some particular setting we don't know, but it looks as if one of the colour channels is dropped or mis-interpreted (I wonder if it is related to a compression algorithm).

    Good guess Richard, and thanks for helping keeping everyone informed!

    Don´t you think Daz has Coders capable of making changes to Iray related stuff if they need it?
    E.g. in this case add compatibility to OpenImage, or use FreeImage as fallback.

    Daz get Iray as a black box (well, pre-compiled .dll..dylib) with hooks for communication - they don't have any way to edit its actual working, including the image handling code which is the problem here.

  • FlipmodeFlipmode Posts: 909

    Richard Haseltine said:

    Daz get Iray as a black box (well, pre-compiled .dll..dylib) with hooks for communication - they don't have any way to edit its actual working, including the image handling code which is the problem here.

    That´s ... a bit unfortunate.
    Well, I hear the issue has finally been passed down the line, it may or may not be fixed in the future.
    It doesn´t matter much anymore though, I hope the updates I made will start showing up soon.

Sign In or Register to comment.