Any idea why I get this warning every time I open Daz Studio?

Comments

• felis Posts: 6,274

  May 12

  The only SSLongitude I can think of is in Render Settings > Environment, either with Dome and Scene (or Done Only) if you don't have a image in Environment map, or with Sun-Sky.

  Are you having a customized scene when starting?
• Jumbotron Posts: 270

  May 12 edited May 12

  Hi felis,

  Thank you. Yes, I agree, the only SSLongitude parameter I can think of is the one that appears under Render settings>Environment when there's dome lighting in the scene but there's not any environment map (HDRI) loaded. By doing that, the Sun-Sky system manages the environmental lighting as far as I know. In fact, I think that the 'SS' in SSLongitude stands for Sun-Sky.

  What puzzles me is that I don't see anything in my preferences that seems out of the normal. (I've attached two screenshots).

  Quite some time ago, I saw this post by crosswind and I remember that I created custom startup conditions with the information provided there. But considering the current settings I have in Daz Studio (in the screenshots), I believe that whatever changes I may have done in the past to the way the program behaves when it launches shouldn't have any effect now.

  P. S. In any case, the good news is that it's just a warning that seems to have no real effect when using the program.

  

  

  startup.jpg

  1258 x 1221 - 104K

  

  

  scene.jpg

  1259 x 1220 - 164K

  Post edited by Jumbotron on May 12
• WendyLuvsCatz Posts: 40,822

  May 12

  it's possibly looking for a path to something you changed

  if custom startup, was there an environment map you moved?

  or a different version of DAZ studio ie Beta

  I get similar messages saving scenes in other versions about the DTHruins HDR sometimes that lives in the program files, apparently one version doesn't look for the path in another
• Jumbotron Posts: 270

  May 12 edited May 12

  Hello Wendy,

  Thank you. You see, that's part of the problem, that I can't remember what changes I exactly made back when I customized the Studio's startup conditions after following crosswind's indications in the post I linked above (something that I believe I did like a complete year ago or so). It doesn't help that I've barely opened the application for the last 8 months or so either. I've only started to use it again like a couple of weeks ago.

  But considering that I really liked playing with the Sun-Sky settings (like testing different latitudes and longitudes, different time zones, different part of the year, different part of the day and so on), my hunch is that I set the startup so that no environment map would load upon opening the application, so that it was the Sun-Sky environment system which managed the dome lighting.

  As for using different versions of Daz Studio (like the beta branch of 4.24 or the latest 2026 version), while I have both installed, I stick to using the latest stable release.

  Post edited by Jumbotron on May 12
• WendyLuvsCatz Posts: 40,822

  May 12

  did you save a sun node or something such as a null or light or that sundial object?

  resaving a new startup scene may fix it
• Jumbotron Posts: 270

  May 12 edited May 12

  Thank you. I can't really remember the details (I wish I could), but no, I don't think I did something like that. I'm more inclined to believe that I saved the environment part of the render settings without an image map (HDRI) and with fixed values for certain parameters (latitude, longitude, time offset, etc.).

  As long as I don't find real issues for using the application, I think I'll leave it like this. It's a warning, but I can use the Studio with normality after all. 

  Post edited by Jumbotron on May 12