Loading...
> >

"V3D HDR Master Bundle" (Commercial)

1…789101113»

Comments

  • barbultbarbult Posts: 26,160
    Fortunately, the HDR Creation tools work OK. So this is no big crisis.
  • V3DigitimesV3Digitimes Posts: 3,365

    Yes, it's not a big crisis, but it's very annoying anyway.

    So I made a few tests this morning, on the 3 products HDR creator, addon tools, and manager :

    --> No crash :

    - on old versions of Daz Studio, however the products were installed

    - if the scripts are installed using Smart Content

    - if the scripts are applied NOT from the menu or the toolbar, BUT either from the script IDE (I used the dsa file I had), or by a "drag and drop" in the viewport of the "ReAdd ToolBar.dse" file (located in the data of the installed product).

    --> Crash :

    - on the latest Public Build

    - if the scripts are installed using DIM and launched from the menu and toolbar (knowing that the user has no other choice, except if he browse to the data folder to drag and drop the ReAdd).

    What I can try to do :

    - Confirm with barbult that the "ReAdd ToolBar.dse" file does its job correctly when not launched from the toolbars (I'll send you the file(s) barbult, you'll just have to drag and drop it in the viewport)

    - If it is the case, I'll ask Daz Team, but the problem may come from the fact that the file installs itself in the menu (even if I have no idea why it would work with Smart Content install in this case).

    - If it is the case, I'll have a look if I can rather redock only (I hope a file has a right to redock), or even use a hide show instead of a remove reinstall, knowing that the re-install (in case of an update) can - if I remember well - be made by the install file of the product itself (the one accessible in the content library).

  • gerd_lehndorffgerd_lehndorff Posts: 0

    Hello V3D,

    I am struggling at making a HDR from my big scene. I want to make it from viewpoint, where usually house is. I delete it and put there the v3d cam. But the result is to big. So placing the house back on leaves empty places. How can I adjust

    the size of the HDR to the orginal one?

    First pic the house the 2nd one view down the street.

    Thank you in advance

    Gerhard

     

     

    Classy HouseNew.jpg
    3840 x 2160 - 5M
    Vorm Haus3.jpg
    3840 x 2160 - 3M
  • V3DigitimesV3Digitimes Posts: 3,365
    edited October 2024

    Hi, maube you can try to play with Render Settings, in the environment properties, choose a finite sphere as the dome mode and scale it down? You can also move the env camera closer to the area you want to focus on so that it takes a larger space in the final HDR. Let me know if it is better. edit : another thing you can try is to "scale down" your environement before you create the HDR. This way each element could enventually use a wider solid angle in your final HDR.  Sorry I just saw your message right now, I did not see the notificaiton in my mail...

    Post edited by V3Digitimes on
  • V3DigitimesV3Digitimes Posts: 3,365

    I ask Daz Team help about the "redock button" or "redock menu" leading to DS crash after the recent updates, because after testing a few things, I must recognize I was clueless. This will anyway be solved in mid-term (in the worse case update would prevent the scripts from re-installing during the redock, and the full reinstall would automatically have to come from the content library/smart content).

  • RaynesinderRaynesinder Posts: 12

    I have had V3D HDR Creator for some time. All of the sudden, I can not get to render the .exr creator. I hit the render button, but it will not do anything. I need help. Currently using Daz Studio version 4.23.

  • DoctorJellybeanDoctorJellybean Posts: 9,585

    Raynesinder said:

    I have had V3D HDR Creator for some time. All of the sudden, I can not get to render the .exr creator. I hit the render button, but it will not do anything. I need help. Currently using Daz Studio version 4.23.

    What does the log (Help - Troubleshooting - View Log File) say after you click the render button?

  • RaynesinderRaynesinder Posts: 12

    I think this the line.

    2025-02-08 15:14:48.591 [DEBUG] :: V3D Application settings options found for path options and its value is NO

    2025-02-08 15:22:41.039 [DEBUG] :: oElement.name General Render

    2025-02-08 15:22:41.041 [DEBUG] :: oElement.name General Render

    2025-02-08 15:22:41.041 [DEBUG] :: oElement.name General Render

    2025-02-08 15:22:41.042 [DEBUG] :: oElement.name General Render

    2025-02-08 15:22:44.760 [WARNING] :: Script Error: Line 3174

    2025-02-08 15:22:44.760 [WARNING] :: TypeError: Result of expression 'oMyRSProp' [null] is not an object.

    2025-02-08 15:22:44.760 [WARNING] :: Stack Trace:

    <anonymous>()@C:/Users/Public/Documents/My DAZ 3D Library/scripts/v3digitimes/hdr creator/v3dhdrc 04 exr creator.dse:3174

    2025-02-08 15:22:44.763 [INFO] :: Error in script execution: C:/Users/Public/Documents/My DAZ 3D Library/scripts/v3digitimes/hdr creator/v3dhdrc 04 exr creator.dse

  • DoctorJellybeanDoctorJellybean Posts: 9,585

    That's for @V3Digitimes to help you out there, I'm afraid. Her support is very good, you should get help either tomorrow or Monday.

  • V3DigitimesV3Digitimes Posts: 3,365
    edited February 9
    I just saw your PM and post right now. Thanks a lot for the log file. I am going to have a look at it tomorrow or monday. I don’t remember what this variable is right now, but it rings a bell. Can you confirm that you have the iray Environment node (too late here to remember the exact name) in your scene when you launch the render? And that the render engine is set to iray? Edit : i have not played with it with the last DS versions, did anyone eLse had such an issue?
    Post edited by V3Digitimes on
  • V3DigitimesV3Digitimes Posts: 3,365

    @Raynesinder

    I think I might have solved your issue. I hope so anyway. Here is my global analysis process and the conclusion to solve it :

    • Step 1 : Launched base tests on one of the latest 4.23 : no crash, does not seem to directly come from DS version on a basic use of the script (good news for me).
    • Step 2 : Log file + script visual analysis (no tests) : The reason of the crash is that the script cannot find the “Post Denoiser Available” property of the Render Settings, in a function which is launched only when you check the "Set Denoiser to ON" box.  It is confirmed by the fact that : oElement.name should be : NVIDIA Iray Render Options and NOT General as you have. Seems the render engine is not set to NVIDIA Iray.
    • Step 3 : checking the existence of the “Post Denoiser Available” option in the current Daz Studio version : Yes, property still exists under “filtering”.
    • Step 4 : Testing the script with the “Set Denoiser to ON” function. No error message if render engine is 3Delight, scripted 3Delight, or NvidiaIray. The Tonemapper and environment options are automatically created in those cases.
    • Step 5 : Testing the script with “Viewport” render engine, “Multipass OPEN GL” render engine, and NO ToneMapper and NO environment options node in the scene : I have the exact same script crash and debug messages as you have.

    The exr creator is an Iray product, and requires the "NVIDIA IRay (MDL)" render engine to be selected before you launch the script. It also requires to be able to read the environment and tonemapping options, and for this, the nodes must be added in your scene.

    Conclusion : what you have to do :

    1. Set the render engine (at the “top top” of render settings, in the dropdown menu right to “Engine”) to “NVIDIA Iray (MDL)”
    2. Make sure that an “Environment Options” and a “ToneMapper Options” node are in your scene. You can load them from the “Create” Daz Studio Menu (they are near the bottom of the list), or if you are lazy, you just have to set the Viewport Style (near where you control your cameras to NVidia Iray).
    3. Test (launch the exr creator, with denoiser option on)
    4. In  since the only conditions I managed to replicate your issue was when the render engine was “viewport” and that there was no ToneMapper and Environment node in your scene, your issue should be solved. If not, come back here, with screen captures of your scene tab and your render settings tab, and with the log file if different from what you already posted.

    Remark : your render configuration (with issues : no environment, no tonemapper node, render engine probably on viewport) is typical from what you would have when you were working with a filament scene just before. Maybe it could explain when you have this issue now whereas everything was fine before (when people where always on Iray with the environment/tonemapper nodes here). So just choose Iray render engines and make sure environment and tone mapper nodes are in the scene.

    Let me know if it solved your issue, and feel free to come back here if not. If your problem is solved, I'll  add a note in the first thread so that people don't face the same issue.

  • RaynesinderRaynesinder Posts: 12

    THANK YOU SO MUCH FOR THE HELP. I WAS WORKING WITH FILAMENT. I DID NOTICE THAT AND WAS FINALLY ABLE TO GET IT TO WORK. THANK YOU VERY MUCH.

  • V3DigitimesV3Digitimes Posts: 3,365

    No problem, glad the issue was that easy to solve :)

  • barbultbarbult Posts: 26,160

    I haven't posted here lately. Yesterday I made an HDRI with Grassy Grove. It came out great. I used it to render this quick image of a girl walking along the path. I'm using DS 4.24 now, and the HDR Creator still works great.

    Mira 9 Young Shape Grassy Grove HDRI_001_Default Camera.jpg
    2600 x 2000 - 6M
  • V3DigitimesV3Digitimes Posts: 3,365

    Geeee... Don't tell me I had not answered your post because in my memory, I had... My Mandela effect? Really sorry about that!
    Well, thanks a lot for sharing and for letting me know Barbult, and sorry for the delay. I remember answering from my phone in bed, and yet, nothing here...
    I am in contact with Daz concerning the "redock menu button" which crashed Daz Studio, I mean, they re-contacted me on the subject to know if it still was an issue, but I have another product to submit before we go further on the subject.

    It looks really great, I think you're doing an amazing work with this HDRI... Probably better than me!... I would not have guessed it was one... 

  • barbultbarbult Posts: 26,160

    The V3D HDR Add-On Tools ReDock menu button crashes Daz Studio in DS 4.24.0 3. I attached the crash log and the related part of the DS log.

    Just for fun, I tried to run the script to install the V3D HDR Add-On Tools toolbar(Install First script) in the DS 6 Alpha. There, installing the toolbar crashed. The DS 6 log file references a script line number. Maybe that will help you debug the problem. That log excerpt is also attached.

    zip
    zip
    DAZStudio_error_report_250909-150243 ReDock Tools crash.zip
    92K
    txt
    txt
    DS 4.24.0.3 ReDock Tools crash - DS4 log file.txt
    15K
    txt
    txt
    DS 6 Alpha Install HDR Add-On tool bar crash - DS6 log file.txt
    15K
  • V3DigitimesV3Digitimes Posts: 3,365
    edited September 9
    I am more afraid by the toolbar redocking issue than by the compatibility with DS 6. This product is not updated yet because of this issue. For now i updated 7 or 8 products (on my computer not submitted) to be bi-compatible Daz Studio 4 and 6. 3 if them should be submitted very soon because also updated for a new product i am finishing. Then i will have a look at the toolbar redocking issue... and when solved i will use the update to add DS 6 compatibility for this HDRI bundle.
    Post edited by V3Digitimes on
  • barbultbarbult Posts: 26,160

    V3Digitimes said:

    I am more afraid by the toolbar redocking issue than by the compatibility with DS 6. This product is not updated yet because of this issue. For now i updated 7 or 8 products (on my computer not submitted) to be bi-compatible Daz Studio 4 and 6. 3 if them should be submitted very soon because also updated for a new product i am finishing. Then i will have a look at the toolbar redocking issue... and when solved i will use the update to add DS 6 compatibility for this HDRI bundle.

    I didn't expect it to work in DS 6. I just thought it might give you an additional clue to the DS4 problem. But maybe it is unrelated.

  • V3DigitimesV3Digitimes Posts: 3,365
    Ah ok! Sorry I over interpreted! Maybe ot could give a clue. i think the problem may be that for an unkown reason scripts became not allowed to install or call themselves from the toolbar... and it will require a work around. Thanks for the inputs!
  • V3DigitimesV3Digitimes Posts: 3,365

    While detailing the crash conditions linked to redocking/readding menus to the support, an idea came to my head.
    I tested it on two products and it worked so far : no more crash when redocking toolbars.
    Anybody willing to beta test ? (anyway I still have work to investigate DS 6 compatibility, so not a hurry).
     

  • ElorElor Posts: 3,135

    I don't have any of your HDR products but maybe I have one of the other two products you're speaking about (if necessary to test with them too)?

  • V3DigitimesV3Digitimes Posts: 3,365

    Arg sorry I was not clear!!!
    I patched on my computer two of the HDR Bundle products to check if my "patch theory" worked fine (and it was the case). But it's always better if a user can confirm. 
    That was nice from you Elor to propose your help, but I will focus first on this bundle first before generalising to all potential products with removable menus and toolbars if everything is ok.
    Anyway I'll come back here to share more information when I have some (such as other products involved - in case you have one -, and how PA support tells me to proceed... because my patch is a "dirty trick")...

  • DoctorJellybeanDoctorJellybean Posts: 9,585

    V3Digitimes said:

    While detailing the crash conditions linked to redocking/readding menus to the support, an idea came to my head.
    I tested it on two products and it worked so far : no more crash when redocking toolbars.
    Anybody willing to beta test ? (anyway I still have work to investigate DS 6 compatibility, so not a hurry).

    Sure. 

  • V3DigitimesV3Digitimes Posts: 3,365

    DoctorJellybean said:

    V3Digitimes said:

    While detailing the crash conditions linked to redocking/readding menus to the support, an idea came to my head.
    I tested it on two products and it worked so far : no more crash when redocking toolbars.
    Anybody willing to beta test ? (anyway I still have work to investigate DS 6 compatibility, so not a hurry).

    Sure. 

    Wonderful! I'm just waiting for PA support’s input to see if there’s a better workaround. If not, I'll get back to you so you can check that the new version works fine for you too. Thanks so much for offering to help!

  • ZoZo Posts: 386

    Title: V3D HDR Master Bundle – persistent issue with .prev.png thumbnails not showing in DAZ

    Hi everyone,

    I’m running into a recurring issue with the V3D HDR Master Bundle, and I’m wondering if others have found a workaround — or if I’ve missed something.

     My workflow:

        I generate thumbnails using V3D Add-On Tools 3 for Images → this creates HDRname.prev.png files
        Then I create .duf files using V3D HDR Manager
        The .duf expects a thumbnail named HDRname.png, but since only a .prev.png exists, the icon doesn’t show up in DAZ Studio

    Result:

        Broken icons in the content library
        Manual renaming of every .prev.png to .png is required for previews to work
        No automation or option in the bundle to handle this

    Questions:

        Did I miss a setting or a recommended workflow?
        Is this something planned for a future update?
        If not, could the thumbnail script include an automatic rename step?

    It’s frustrating to have to manually fix something that should work out of the box. Any help or insight would be appreciated!

    Thanks,
    Zo

     

  • barbultbarbult Posts: 26,160

    Zo said:

    Title: V3D HDR Master Bundle – persistent issue with .prev.png thumbnails not showing in DAZ

    Hi everyone,

    I’m running into a recurring issue with the V3D HDR Master Bundle, and I’m wondering if others have found a workaround — or if I’ve missed something.

     My workflow:

        I generate thumbnails using V3D Add-On Tools 3 for Images → this creates HDRname.prev.png files
        Then I create .duf files using V3D HDR Manager
        The .duf expects a thumbnail named HDRname.png, but since only a .prev.png exists, the icon doesn’t show up in DAZ Studio

    Result:

        Broken icons in the content library
        Manual renaming of every .prev.png to .png is required for previews to work
        No automation or option in the bundle to handle this

    Questions:

        Did I miss a setting or a recommended workflow?
        Is this something planned for a future update?
        If not, could the thumbnail script include an automatic rename step?

    It’s frustrating to have to manually fix something that should work out of the box. Any help or insight would be appreciated!

    Thanks,
    Zo

     

    Check the product's documentation. Perhaps your order of operations is incorrect. Why do you create the thumbnail first, before creating the file it is supposed to be a thumbnail for? 

  • V3DigitimesV3Digitimes Posts: 3,365

    I'll have a look at this since it is not my usual worflow.

    "No automation or option in the bundle to handle this"... In case it is required, I mean in case I don't find an easy solution for it, I can include a script for this specific case of figure, so that people can do it automatically.
    "It’s frustrating to have to manually fix something that should work out of the box. Any help or insight would be appreciated!" .... I totally agree with you... A future update is anyway planned, in order to fix another issue, but your specific issue will also be taken into account (plus I'll try to add full or partial but max compatibility with DS 6). I am in a long set of updates anyway, so yes, this is planned.

Sign In or Register to comment.