Render-/Environment-Settings ignored by 4.15

Hi,

first effect on the new DAZ 4.15: The entries for Tonemappping and Environment (Dome-Settings) are missing in the "Render Settings" Tab.
OK - no problem, there are corresponding "presets" in the Content Library, which add the missing setting parameters.

But:
For a scene, I changed the dome setting to sun-sky. My preferences are set to store those settings (see attachment).
But opening the saved scene again, the environment setting for render again is the default HDRI, instead of the stored sun-sky setting. Not allways, but in most cases.

So what's wrong? Or what did I misunderstood?

Andy

Scene-Options 4-15.jpg
416 x 495 - 27K

Comments

  • margravemargrave Posts: 1,822

    Tonemapping and Environment were changed to be nodes in the scene tree. You need to add them from the "Create" menu and then save them as part of your scene. Yes, it's hideous and clutters up the scene tree, but Daz aren't changing it back.

  • AndreaswbAndreaswb Posts: 25

    margrave said:

    Tonemapping and Environment were changed to be nodes in the scene tree. You need to add them from the "Create" menu and then save them as part of your scene. Yes, it's hideous and clutters up the scene tree, but Daz aren't changing it back.

    no Problem if they don't. But sometimes the original "Environment Mode" parameter of the saved scene is not considered opening an existing scene. Instead it has the default "Dome and Scene" value with the DAZ-default HDRI map.
    Is this a kind of bug or didn't I understand the related preferences setting?

  • margravemargrave Posts: 1,822

    Andreaswb said:

    no Problem if they don't. But sometimes the original "Environment Mode" parameter of the saved scene is not considered opening an existing scene. Instead it has the default "Dome and Scene" value with the DAZ-default HDRI map.
    Is this a kind of bug or didn't I understand the related preferences setting?

    Those settings predate Daz changing the Tonemapper and Environment into scene nodes. So in past versions, IIRC, it did what you're asking. But now it doesn't. You just need to save the Tonemapper and Environment as nodes and merge them into your scene.

  • AndreaswbAndreaswb Posts: 25

    Pardon margrave,

    margrave said:

    Andreaswb said:

    no Problem if they don't. But sometimes the original "Environment Mode" parameter of the saved scene is not considered opening an existing scene. Instead it has the default "Dome and Scene" value with the DAZ-default HDRI map.
    Is this a kind of bug or didn't I understand the related preferences setting?

    Those settings predate Daz changing the Tonemapper and Environment into scene nodes. So in past versions, IIRC, it did what you're asking. But now it doesn't. You just need to save the Tonemapper and Environment as nodes and merge them into your scene.

    what is this with "... into scene nodes."? I saved a new scene including dome- and Environment-Settings in 4.15. Envi- and ToneMapper-Settings appear in the scene items list. See attachment.
    Although they seem not to be considered with the next opening of this scene (sometimes).
    Preferences as documented in the first post.

    Andy

    Render Envi Settings 4-15.jpg
    389 x 216 - 14K
  • AndreaswbAndreaswb Posts: 25

    btw:

    Who removed my attachment of the first post ??

    Here the preference setting again:

    Scene-Options 4-15.jpg
    416 x 495 - 27K
  • AndreaswbAndreaswb Posts: 25

    ... And:

    If 4.15 overwrites the old envi-settings, how shall I get the original settings of scenes from older versions back (to transform them into those scene nodes)? no

  • ioonrxoonioonrxoon Posts: 893
    edited July 2021

    I'm not sure this is entirely accurate and applies every time, but from what I've noticed the settings are saved, but on reloading a scene after a restart, the basic hdri map is added... if you remove it, you should have your settings as they were initially.

    Post edited by ioonrxoon on
  • barbultbarbult Posts: 24,233
    I reported this as a bug months ago. It was acknowledged as a known problem, but there hasn't been any fix released yet.
Sign In or Register to comment.