Loading...
> >

DAZ 3D always resets Env Map

Hurdy3DHurdy3D Posts: 1,057
in The Commons

Hey

I've a pretty anyoing problem.

When I save a file and set Enviornment Map to none, whenever I reload the file, the Environment Map is resetted to the default HDRI map.

Any idea what could cause this?

It isn't caused by my duf files, after this also happens with new files.

Comments

  • BeeMKayBeeMKay Posts: 7,019
    edited October 2021

    You have to change the settings for saving your files. Under "Edit --> Preferences". In the "Pereferences" menu, go to the "Scenes" tab. There, go the "Render settings" at the bottom of the list, and check "Record when saving file" and unckeck "Ignore when opening scene".

    Screenshot 2021-10-07 191658.jpg
    883 x 602 - 53K
    Post edited by BeeMKay on
  • Hurdy3DHurdy3D Posts: 1,057

    BeeMKay said:

    You have to change the settings for saving your files. Under "Edit --> Preferences". In the "Pereferences" menu, go to the "Scenes" tab. There, go the "Render settings" at the bottom of the list, and check "Record when saving file" and unckeck "Ignore when opening scene".

    Thank you. Good idea, but these settings are unchanged in my setup:

    Must be something different what's causing this.

    Screenshot 2021-10-07 192334.png
    814 x 735 - 118K
  • BeeMKayBeeMKay Posts: 7,019

    Do you have an environment node in the scene when you save it? Or does it load a new one when you open the scene?

  • Hurdy3DHurdy3D Posts: 1,057

    BeeMKay said:

    Do you have an environment node in the scene when you save it? Or does it load a new one when you open the scene?

    Yes and yes. And it's only the Env Map which is resettet. All other settings are untouched.

  • Hurdy3DHurdy3D Posts: 1,057
    edited October 2021

    Okay... it seems to be reseted when opening the file.

    I've a scene with a hdri env map, I've these in the duf file:

     

                {                "id" : "Environment Options-1",                "url" : "#Environment%20Options",                "name" : "Environment Options",                "label" : "Environment Options",                "extra" : [                    {                        "type" : "studio/node/environment"                    },                    {                        "type" : "studio_node_channels",                        "version" : 4,                        "channels" : [                            {                                "channel" : {                                    "id" : "Environment Map",                                    "type" : "float",                                    "current_value" : 2,                                    "image_file" : "/resources/DTHDR-RuinsB-500.hdr"                                }                            }                        ]                    }                ]            }        ],

    But if save the scene without the HDRI, it's missing in the duf file:

                {                "id" : "Environment Options-1",                "url" : "#Environment%20Options",                "name" : "Environment Options",                "label" : "Environment Options",                "extra" : [                    {                        "type" : "studio/node/environment"                    },                    {                        "type" : "studio_node_channels",                        "version" : 4                    }                ]            }
     

     

    That means, saving is working, opening the file is broken.

     

    Post edited by Hurdy3D on
  • barbultbarbult Posts: 24,829

    Yes, I reported this problem in a Help Request in April 2021. I was told it was a known problem that has been reported to the developers.

  • Hurdy3DHurdy3D Posts: 1,057

    barbult said:

    Yes, I reported this problem in a Help Request in April 2021. I was told it was a known problem that has been reported to the developers.

    Great... so we have to wait forever to have this issues fixed. This issue is blocking me from using Render Queue since months... I have to render every image manually and fix the setting.

  • barbultbarbult Posts: 24,829

    gerster said:

    barbult said:

    Yes, I reported this problem in a Help Request in April 2021. I was told it was a known problem that has been reported to the developers.

    Great... so we have to wait forever to have this issues fixed. This issue is blocking me from using Render Queue since months... I have to render every image manually and fix the setting.

    Yes, the Render Queue issue is exactly my problem, too. Many a render has been ruined by this problem, when I forget about it.

  • Hurdy3DHurdy3D Posts: 1,057

    barbult said:

    gerster said:

    barbult said:

    Yes, I reported this problem in a Help Request in April 2021. I was told it was a known problem that has been reported to the developers.

    Great... so we have to wait forever to have this issues fixed. This issue is blocking me from using Render Queue since months... I have to render every image manually and fix the setting.

    Yes, the Render Queue issue is exactly my problem, too. Many a render has been ruined by this problem, when I forget about it.

    I reported 2 years ago that Canvas Alpha maps are broken. Still buggy and unusable, but it least for there's a workaround (using Beauty, to get the Alpha maps).

    My hope that DAZ fixes their bugs is quite low.

    I mean, it needed also around two years that they fixed some meta data issues in a pose product. I had to repopen the ticket multiple times.

  • barbultbarbult Posts: 24,829

    They've been doing better with product fixes lately, but recently Daz Studio seems to only get attention on fixing Mac compatibility and preparing for QT upgrades. Daz Studio is free. We get what we get, and live with or work around the problems. With all the emphasis on bridges, I kind of expected them to drop DS development, but we were told in the forum that that is not the case.

  • Hurdy3DHurdy3D Posts: 1,057

    barbult said:

    They've been doing better with product fixes lately, but recently Daz Studio seems to only get attention on fixing Mac compatibility and preparing for QT upgrades. Daz Studio is free. We get what we get, and live with or work around the problems. With all the emphasis on bridges, I kind of expected them to drop DS development, but we were told in the forum that that is not the case.

    Blender is also free and works far better. And Daz Studio isn't really free, after you pay thousends of thousens $$$ for content.

    However, If everythings works well, I'll move to Blender after my current project and importing Genesis figures via Diffeo.

    But I don't think that they will drop DAZ Studio, they need the lock-in to sell their HD morphs and dForce hair.

  • Richard HaseltineRichard Haseltine Posts: 102,640

    The alpha issue is probably an iray thing, so out of Daz' hands.

  • Richard HaseltineRichard Haseltine Posts: 102,640

    barbult said:

    They've been doing better with product fixes lately, but recently Daz Studio seems to only get attention on fixing Mac compatibility and preparing for QT upgrades. Daz Studio is free. We get what we get, and live with or work around the problems. With all the emphasis on bridges, I kind of expected them to drop DS development, but we were told in the forum that that is not the case.

    Have you looked at the change log recently? http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log . It certainly isn't Mac/Qt-stuff only.

  • barbultbarbult Posts: 24,829

    Richard Haseltine said:

    barbult said:

    They've been doing better with product fixes lately, but recently Daz Studio seems to only get attention on fixing Mac compatibility and preparing for QT upgrades. Daz Studio is free. We get what we get, and live with or work around the problems. With all the emphasis on bridges, I kind of expected them to drop DS development, but we were told in the forum that that is not the case.

    Have you looked at the change log recently? http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log . It certainly isn't Mac/Qt-stuff only.

    I can't relate what is written there to any bug fixes. Sadly most of it is unintelligible to me at my level of understanding. Things like "Extended DzSkinBinding public API; added BlendMode enum; added getBlendMode(), setBlendMode(); added blendModeChanged() signal" are beyond my comprehension. Is there some specific thing posted there that you believe relates to the subject of this thread (the default HDRI being reloaded when the file was saved with no HDRI)? That would be very encouraging.

  • xyer0xyer0 Posts: 6,050

    This [Environment Maps changing when merging or queuing] has also been an issue for me for months. But after mentioning it in the forums and reading other people's echoes, I just dealt with it. But it's real inconvenient.

  • Richard HaseltineRichard Haseltine Posts: 102,640

    barbult said:

    Richard Haseltine said:

    barbult said:

    They've been doing better with product fixes lately, but recently Daz Studio seems to only get attention on fixing Mac compatibility and preparing for QT upgrades. Daz Studio is free. We get what we get, and live with or work around the problems. With all the emphasis on bridges, I kind of expected them to drop DS development, but we were told in the forum that that is not the case.

    Have you looked at the change log recently? http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log . It certainly isn't Mac/Qt-stuff only.

    I can't relate what is written there to any bug fixes. Sadly most of it is unintelligible to me at my level of understanding. Things like "Extended DzSkinBinding public API; added BlendMode enum; added getBlendMode(), setBlendMode(); added blendModeChanged() signal" are beyond my comprehension. Is there some specific thing posted there that you believe relates to the subject of this thread (the default HDRI being reloaded when the file was saved with no HDRI)? That would be very encouraging.

    The point was to refute the asertion that nothing was being done other than the Mac compatibility and Qt updating, but I don't think theer is any indication that this particular issue has yet been resolved.

  • Leonides02Leonides02 Posts: 1,379
    edited October 2021

    gerster said:

    barbult said:

    Yes, I reported this problem in a Help Request in April 2021. I was told it was a known problem that has been reported to the developers.

    Great... so we have to wait forever to have this issues fixed. This issue is blocking me from using Render Queue since months... I have to render every image manually and fix the setting.

    I also reported this as an issue over a year ago. As far as I am aware, it's still a problem.

    I fixed it by DELETING the default map from my system!

    Post edited by Leonides02 on
  • barbultbarbult Posts: 24,829

    Leonides02 said:

    gerster said:

    barbult said:

    Yes, I reported this problem in a Help Request in April 2021. I was told it was a known problem that has been reported to the developers.

    Great... so we have to wait forever to have this issues fixed. This issue is blocking me from using Render Queue since months... I have to render every image manually and fix the setting.

    I also reported this as an issue over a year ago. As far as I am aware, it's still a problem.

    I fixed it by DELETING the default map from my system!

    Hey, I never thought of that!

  • Hurdy3DHurdy3D Posts: 1,057

    Leonides02 said:

    gerster said:

    barbult said:

    Yes, I reported this problem in a Help Request in April 2021. I was told it was a known problem that has been reported to the developers.

    Great... so we have to wait forever to have this issues fixed. This issue is blocking me from using Render Queue since months... I have to render every image manually and fix the setting.

    I also reported this as an issue over a year ago. As far as I am aware, it's still a problem.

    I fixed it by DELETING the default map from my system!

    Good idea, this workaround seems to work.

    They just released a new Beta (4.15.72) and the env map bug is still not fixed...

  • SpaciousSpacious Posts: 481

    Workaround : use a small image that's only black as the environment map.

Sign In or Register to comment.