Loading...
> >

Daz Studio Pro BETA - version 4.22.0.15! (*UPDATED*)

1…2425262729

Comments

  • barbultbarbult Posts: 23,274

    trebor_gb_37ba5b8bb6 said:

    Hi

    Does anybody know where/how I download 4.22.0.14, please?

    If you have never installed a beta (Public Build) version before, you need to purchase it for free n the Daz store. Then it should appear in the Daz Install Manager (DIM) as described above. It is not available for manual download.

  • jbowlerjbowler Posts: 748

    Richard Haseltine said:

    I see this too, please report it to Daz via a ticket.

    No need; it's fixed in 4.22.0.14:

    2023-12-17 20:10:25.471 [INFO] :: Scanning Content folders...
    2023-12-17 20:10:25.567 [INFO] :: Creating Render Manager...

    John Bowler

     

  • jbowlerjbowler Posts: 748

    The FT2 "missing content" bug is fixed in 4.22.0.14, or at least it is if the new "Genesis9StarterEssentials" are also installed.  I verified by removing CMS directory I had created to contain the contents of the previously documented .zip fixup file.  These various WARNINGs some of which I had previously reported are still present:

    2023-12-17 20:11:30.665 [WARNING] :: QFile::flush: No file engine. Is IODevice open?
    2023-12-17 20:11:30.950 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSBaseAction::getPane()
    2023-12-17 20:11:30.951 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSShowHiddenAction::init()
    2023-12-17 20:11:30.951 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSBaseAction::getPane()
    2023-12-17 20:11:30.951 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSSyncWithSceneAction::init()


    2023-12-17 20:11:32.011 [WARNING] :: Script Error: Line 90
    2023-12-17 20:11:32.011 [WARNING] :: TypeError: Result of expression 'oPane.getInfoDivider' [undefined] is not a function.
    2023-12-17 20:11:32.011 [WARNING] :: Stack Trace:
    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/resources/tip pages/Common/PanePage.dsa:90

     

    2023-12-17 20:12:20.522 [WARNING] :: QColor::setRgb: RGB parameters out of range

    Apart from those the only warnings I see are the "Formula output property not found" ones.

     

     

     

  • Richard HaseltineRichard Haseltine Posts: 97,479

    jbowler said:

    Richard Haseltine said:

    I see this too, please report it to Daz via a ticket.

    No need; it's fixed in 4.22.0.14:

    2023-12-17 20:10:25.471 [INFO] :: Scanning Content folders...
    2023-12-17 20:10:25.567 [INFO] :: Creating Render Manager...

    John Bowler

    Thanks for confirming that.

  • Richard HaseltineRichard Haseltine Posts: 97,479

    jbowler said:

    The FT2 "missing content" bug is fixed in 4.22.0.14, or at least it is if the new "Genesis9StarterEssentials" are also installed.  I verified by removing CMS directory I had created to contain the contents of the previously documented .zip fixup file.  These various WARNINGs some of which I had previously reported are still present:

    2023-12-17 20:11:30.665 [WARNING] :: QFile::flush: No file engine. Is IODevice open?
    2023-12-17 20:11:30.950 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSBaseAction::getPane()
    2023-12-17 20:11:30.951 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSShowHiddenAction::init()
    2023-12-17 20:11:30.951 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSBaseAction::getPane()
    2023-12-17 20:11:30.951 [WARNING] :: No DzLightsPane instance could be found in DzLGHTSSyncWithSceneAction::init()

    See the change log for 4.22.0.15, it looks as if there was an issue with the pane's being identified which will be fixed in that build.


    2023-12-17 20:11:32.011 [WARNING] :: Script Error: Line 90
    2023-12-17 20:11:32.011 [WARNING] :: TypeError: Result of expression 'oPane.getInfoDivider' [undefined] is not a function.
    2023-12-17 20:11:32.011 [WARNING] :: Stack Trace:
    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/resources/tip pages/Common/PanePage.dsa:90

     

    2023-12-17 20:12:20.522 [WARNING] :: QColor::setRgb: RGB parameters out of range

    Apart from those the only warnings I see are the "Formula output property not found" ones.

     

     

     

  • jbowlerjbowler Posts: 748

    Richard Haseltine said:

    See the change log for 4.22.0.15, it looks as if there was an issue with the pane's being identified which will be fixed in that build.

    Fast and furious, that's the way to do a Beta :-)

    All WARNINGS on the simple start up have gone except for:

    2023-12-18 17:30:15.953 [INFO] :: Creating Script Engine...
    2023-12-18 17:30:15.971 [WARNING] :: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
    2023-12-18 17:30:15.971 [INFO] :: 3D mouse support library could not be loaded.
    2023-12-18 17:30:15.972 [INFO] :: Creating Main Window...
    2023-12-18 17:30:15.973 [INFO] :: Creating Viewport Manager...
    2023-12-18 17:30:16.190 [INFO] :: Successfully created OpenGL viewport for Viewport1.
    2023-12-18 17:30:16.800 [INFO] :: Successfully created OpenGL viewport for Viewport2.
    2023-12-18 17:30:17.202 [INFO] :: Successfully created OpenGL viewport for Viewport3.
    2023-12-18 17:30:17.628 [INFO] :: Successfully created OpenGL viewport for Viewport4.
    2023-12-18 17:30:17.913 [INFO] :: Creating Action Manager...
    2023-12-18 17:30:17.966 [INFO] :: Creating Pane Manager...
    2023-12-18 17:30:18.368 [INFO] :: Successfully created OpenGL viewport for AuxViewportView.
    2023-12-18 17:31:16.649 [WARNING] :: QFile::flush: No file engine. Is IODevice open?
    2023-12-18 17:31:16.995 [INFO] :: RenderQueue: we_restarted_DS: FALSE

     

    The first may have been present before; this time I did search in the log file for "WARNING".  The second was before the DzPain warnings, so those have gone.  The QColor warning is scene specific and may, indeed, be "correct" since I had been experimenting with the spectral rendering settings with the scene in question and may have managed to produce a scene with out-of-gamut sRGB (e.g. arguments to QColor::setRgbF outside the range 0..1).

  • Richard HaseltineRichard Haseltine Posts: 97,479

    The 3D Connexxion warning has been there for a long time, as I recall. If you don't hae a 3D Mouse connected then it will of course not be able to find it, so it is an  expected message for most of us. I am not sure about the QFlush message.

  • PerttiAPerttiA Posts: 9,605

    Richard Haseltine said:

    The 3D Connexxion warning has been there for a long time, as I recall. If you don't hae a 3D Mouse connected then it will of course not be able to find it, so it is an  expected message for most of us. I am not sure about the QFlush message.

    The 3D Connexion is a plugin that can be disabled if one doesn't have such mouse. 

  • Richard HaseltineRichard Haseltine Posts: 97,479

    PerttiA said:

    Richard Haseltine said:

    The 3D Connexxion warning has been there for a long time, as I recall. If you don't hae a 3D Mouse connected then it will of course not be able to find it, so it is an  expected message for most of us. I am not sure about the QFlush message.

    The 3D Connexion is a plugin that can be disabled if one doesn't have such mouse. 

    True. The message has been there for so long that I don't even think about it, but that is probably a good diea.

  • barbultbarbult Posts: 23,274

    My scene was rendering with CPU, because it was too big for GPU. I stopped the render and saved my scene. I closed Daz Studio 4.22.0.15 PB with the red X in the upper right corner. After a short while, DS stopped responding. I eventually had to kill it with the Task Manager (Windows 10). The end of the log file said:

    2023-12-19 23:20:18.855 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CPU: Scene processed in 1.929s
    2023-12-19 23:20:18.856 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : CPU: Allocated 3.239 MiB for frame buffer
    2023-12-19 23:20:19.106 Iray [INFO] - IRAY:RENDER ::   1.2   IRAY   rend info : Allocating 1-layer frame buffer
    2023-12-19 23:20:19.143 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00001 iteration after 4.615 s.
    2023-12-19 23:20:19.384 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00002 iterations after 4.854 s.
    2023-12-19 23:20:19.643 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00003 iterations after 5.114 s.
    2023-12-19 23:20:19.910 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00004 iterations after 5.381 s.
    2023-12-19 23:20:20.189 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00005 iterations after 5.660 s.
    2023-12-19 23:20:20.459 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00006 iterations after 5.929 s.
    2023-12-19 23:20:20.713 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00007 iterations after 6.184 s.
    2023-12-19 23:20:20.948 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00008 iterations after 6.419 s.
    2023-12-19 23:20:21.206 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00009 iterations after 6.676 s.
    2023-12-19 23:20:21.480 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00010 iterations after 6.951 s.
    2023-12-19 23:20:21.777 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00011 iterations after 7.248 s.
    2023-12-19 23:20:22.028 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00012 iterations after 7.498 s.
    2023-12-19 23:20:22.514 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00014 iterations after 7.985 s.
    2023-12-19 23:20:23.048 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00016 iterations after 8.518 s.
    2023-12-19 23:20:23.578 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00018 iterations after 9.049 s.
    2023-12-19 23:20:24.372 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00021 iterations after 9.843 s.
    2023-12-19 23:20:25.130 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00024 iterations after 10.601 s.
    2023-12-19 23:20:26.115 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00028 iterations after 11.585 s.
    2023-12-19 23:20:27.120 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00032 iterations after 12.591 s.
    2023-12-19 23:20:28.416 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00037 iterations after 13.887 s.
    2023-12-19 23:20:29.904 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00043 iterations after 15.376 s.
    2023-12-19 23:20:31.642 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00050 iterations after 17.113 s.
    2023-12-19 23:20:33.731 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00058 iterations after 19.202 s.
    2023-12-19 23:20:36.045 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00067 iterations after 21.516 s.
    2023-12-19 23:20:36.320 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:
    2023-12-19 23:20:36.320 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CPU: 67 iterations, 1.932s init, 17.455s render
    2023-12-19 23:20:38.994 [INFO] :: Finished Rendering
    2023-12-19 23:20:45.955 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:
    2023-12-19 23:20:45.955 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3080): 0 iterations, 0.001s init, 0.000s render
    2023-12-19 23:21:06.409 [INFO] :: Saved image: N:\DAZ 3D\Scenes\G9F and M Unionsuit.tip.png
    2023-12-19 23:21:26.008 [INFO] :: Closing main window...
    2023-12-19 23:21:26.008 [INFO] :: Saving Layout: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio4 Public Build/layout.dsx
    2023-12-19 23:21:26.014 [INFO] :: Clearing the scene...
    2023-12-19 23:21:26.470 [INFO] :: Stop following: KOO Seth << Genesis 9 Eyelashes
    2023-12-19 23:21:26.471 [INFO] :: Following stopped: KOO Seth << Genesis 9 Eyelashes
    2023-12-19 23:21:26.474 [INFO] :: Stop following: KOO Seth << Genesis 9 Eyes
    2023-12-19 23:21:26.475 [INFO] :: Following stopped: KOO Seth << Genesis 9 Eyes
    2023-12-19 23:21:26.482 [INFO] :: Stop following: KOO Seth << Genesis 9 Tear
    2023-12-19 23:21:26.482 [INFO] :: Following stopped: KOO Seth << Genesis 9 Tear
    2023-12-19 23:21:26.489 [INFO] :: Stop following: KOO Seth << Genesis 9 Mouth
    2023-12-19 23:21:26.489 [INFO] :: Following stopped: KOO Seth << Genesis 9 Mouth
    2023-12-19 23:21:26.495 [INFO] :: Stop following: KOO Seth << KOO Seth Eyebrows
    2023-12-19 23:21:26.496 [INFO] :: Following stopped: KOO Seth << KOO Seth Eyebrows
    2023-12-19 23:21:26.500 [INFO] :: Stop following: KOO Seth << Unionsuit
    2023-12-19 23:21:26.500 [INFO] :: Following stopped: KOO Seth << Unionsuit
    2023-12-19 23:21:26.506 [INFO] :: Stop following: KOO Seth << M3D SemiBald Hair
    2023-12-19 23:21:26.506 [INFO] :: Following stopped: KOO Seth << M3D SemiBald Hair
    2023-12-19 23:21:26.510 [INFO] :: Stop following: KOO Seth << NG Ankle Socks (Xmas)
    2023-12-19 23:21:26.510 [INFO] :: Following stopped: KOO Seth << NG Ankle Socks (Xmas)
    2023-12-19 23:21:27.071 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Eyelashes (2)
    2023-12-19 23:21:27.072 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Eyelashes (2)
    2023-12-19 23:21:27.076 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Tear (2)
    2023-12-19 23:21:27.076 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Tear (2)
    2023-12-19 23:21:27.083 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Eyes (2)
    2023-12-19 23:21:27.083 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Eyes (2)
    2023-12-19 23:21:27.090 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Mouth (2)
    2023-12-19 23:21:27.091 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Mouth (2)
    2023-12-19 23:21:27.098 [INFO] :: Stop following: FN Eleanor HD << G9 Eyebrows Fiber Style 01
    2023-12-19 23:21:27.099 [INFO] :: Following stopped: FN Eleanor HD << G9 Eyebrows Fiber Style 01
    2023-12-19 23:21:27.103 [INFO] :: Stop following: FN Eleanor HD << Unionsuit (2)
    2023-12-19 23:21:27.103 [INFO] :: Following stopped: FN Eleanor HD << Unionsuit (2)
    2023-12-19 23:21:27.110 [INFO] :: Stop following: FN Eleanor HD << NG Ankle Socks (Xmas) (2)

    There are a lot more items in my scene that the few listed in the log above.

     

     

    Not Responding when closing DS 4.22.0.15 PB.jpg
    342 x 328 - 13K
  • barbultbarbult Posts: 23,274

    The problem above with DS becoming Not Responding for many minutes repeated itself when I restarted DS and rendered the same scene with GPU and Render Queue 3. When the render finished, and I closed DS, it never finished closing. I killed it again finally.

  • crosswindcrosswind Posts: 4,893

    barbult said:

    The problem above with DS becoming Not Responding for many minutes repeated itself when I restarted DS and rendered the same scene with GPU and Render Queue 3. When the render finished, and I closed DS, it never finished closing. I killed it again finally.

    What if you just Ctrl + N to clear this big scene ?  

  • barbultbarbult Posts: 23,274
    edited December 2023

    crosswind said:

    barbult said:

    The problem above with DS becoming Not Responding for many minutes repeated itself when I restarted DS and rendered the same scene with GPU and Render Queue 3. When the render finished, and I closed DS, it never finished closing. I killed it again finally.

    What if you just Ctrl + N to clear this big scene ?  

    I haven't tried that yet. Currently, I just opened the scene and when it was displayed in the viewport, I closed DS with the red X. ( I didn't even render or Iray preview, just open the scene and close DS. ) As before, it DS is stuck in Clearing the scene... and  Not Responding, I'm going to go do something else and give it 15 minutes or so to see if it ever progresses. Then it not, I'll kill it again and try Ctrl+N. Thanks for the suggestion.

    Post edited by barbult on
  • crosswindcrosswind Posts: 4,893

    barbult said:

    crosswind said:

    barbult said:

    The problem above with DS becoming Not Responding for many minutes repeated itself when I restarted DS and rendered the same scene with GPU and Render Queue 3. When the render finished, and I closed DS, it never finished closing. I killed it again finally.

    What if you just Ctrl + N to clear this big scene ?  

    I haven't tried that yet. Currently, I just opened the scene and when it was displayed in the viewport, I closed DS with the red X. ( I didn't even render or Iray preview, just open the scene and close DS. ) As before, it DS is stuck in Clearing the scene... and  Not Responding, I'm going to go do something else and give it 15 minutes or so to see if it ever progresses. Then it not, I'll kill it again and try Ctrl+N. Thanks for the suggestion.

    I'll try one of my big scenes later. I'm not sure but I presume it might be related to the "new way of fast closing" because the process of "Clearing scene" has been brought to front-end rather than background as before... then the session of DS is hung there when closing big scene(s)...

  • barbultbarbult Posts: 23,274
    edited December 2023

    Hey, I guess I was too impatient. It took 15 minutes, but DS finally closed! The log has a warning about Unexpected null parameter.

    What is happening between the over 14 minute gap in these sequential log messages?

    2023-12-20 02:24:17.282 [INFO] :: Following stopped: FN Eleanor HD << Voss Hair Genesis 9
    2023-12-20 02:38:52.636 [INFO] :: *** Scene Cleared ***

    This is the end of the log:

    2023-12-20 02:24:16.327 [INFO] :: Clearing the scene...
    2023-12-20 02:24:16.616 [INFO] :: Stop following: KOO Seth << Genesis 9 Eyelashes
    2023-12-20 02:24:16.616 [INFO] :: Following stopped: KOO Seth << Genesis 9 Eyelashes
    2023-12-20 02:24:16.621 [INFO] :: Stop following: KOO Seth << Genesis 9 Eyes
    2023-12-20 02:24:16.621 [INFO] :: Following stopped: KOO Seth << Genesis 9 Eyes
    2023-12-20 02:24:16.628 [INFO] :: Stop following: KOO Seth << Genesis 9 Tear
    2023-12-20 02:24:16.628 [INFO] :: Following stopped: KOO Seth << Genesis 9 Tear
    2023-12-20 02:24:16.635 [INFO] :: Stop following: KOO Seth << Genesis 9 Mouth
    2023-12-20 02:24:16.635 [INFO] :: Following stopped: KOO Seth << Genesis 9 Mouth
    2023-12-20 02:24:16.642 [INFO] :: Stop following: KOO Seth << KOO Seth Eyebrows
    2023-12-20 02:24:16.642 [INFO] :: Following stopped: KOO Seth << KOO Seth Eyebrows
    2023-12-20 02:24:16.645 [INFO] :: Stop following: KOO Seth << Unionsuit
    2023-12-20 02:24:16.646 [INFO] :: Following stopped: KOO Seth << Unionsuit
    2023-12-20 02:24:16.652 [INFO] :: Stop following: KOO Seth << M3D SemiBald Hair
    2023-12-20 02:24:16.652 [INFO] :: Following stopped: KOO Seth << M3D SemiBald Hair
    2023-12-20 02:24:16.656 [INFO] :: Stop following: KOO Seth << NG Ankle Socks (Xmas)
    2023-12-20 02:24:16.656 [INFO] :: Following stopped: KOO Seth << NG Ankle Socks (Xmas)
    2023-12-20 02:24:17.219 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Eyelashes (2)
    2023-12-20 02:24:17.220 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Eyelashes (2)
    2023-12-20 02:24:17.224 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Tear (2)
    2023-12-20 02:24:17.224 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Tear (2)
    2023-12-20 02:24:17.231 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Eyes (2)
    2023-12-20 02:24:17.231 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Eyes (2)
    2023-12-20 02:24:17.238 [INFO] :: Stop following: FN Eleanor HD << Genesis 9 Mouth (2)
    2023-12-20 02:24:17.238 [INFO] :: Following stopped: FN Eleanor HD << Genesis 9 Mouth (2)
    2023-12-20 02:24:17.246 [INFO] :: Stop following: FN Eleanor HD << G9 Eyebrows Fiber Style 01
    2023-12-20 02:24:17.246 [INFO] :: Following stopped: FN Eleanor HD << G9 Eyebrows Fiber Style 01
    2023-12-20 02:24:17.250 [INFO] :: Stop following: FN Eleanor HD << Unionsuit (2)
    2023-12-20 02:24:17.250 [INFO] :: Following stopped: FN Eleanor HD << Unionsuit (2)
    2023-12-20 02:24:17.256 [INFO] :: Stop following: FN Eleanor HD << NG Ankle Socks (Xmas) (2)
    2023-12-20 02:24:17.256 [INFO] :: Following stopped: FN Eleanor HD << NG Ankle Socks (Xmas) (2)
    2023-12-20 02:24:17.282 [INFO] :: Stop following: FN Eleanor HD << Voss Hair Genesis 9
    2023-12-20 02:24:17.282 [INFO] :: Following stopped: FN Eleanor HD << Voss Hair Genesis 9
    2023-12-20 02:38:52.636 [INFO] :: *** Scene Cleared ***
    2023-12-20 02:38:52.738 [INFO] :: Saving Custom Actions: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio4 Public Build/customactions.dsx
    2023-12-20 02:38:52.776 [INFO] :: Saving Actions: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio4 Public Build/actions.dsx
    2023-12-20 02:38:52.787 [INFO] :: Saving Menus: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio4 Public Build/menus.dsx
    2023-12-20 02:38:52.807 [INFO] :: Saving ToolBars: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio4 Public Build/toolbars.dsx
    2023-12-20 02:38:52.817 [WARNING] :: Object::disconnect: Unexpected null parameter
    2023-12-20 02:38:52.818 [INFO] :: Begin Application cleanup...
    2023-12-20 02:38:52.819 [INFO] :: Shutting down Asset Manager...
    2023-12-20 02:38:52.891 [INFO] :: Clearing Delayed Delete Stack...
    2023-12-20 02:38:52.892 [INFO] :: Shutting down Plugin Manager...
    2023-12-20 02:38:53.030 Iray [INFO] - IRT:RENDER ::   1.1   IRT    rend info : Shutting down irt render plugin.
    2023-12-20 02:38:53.135 [INFO] :: Cleaning up Thread Pool...
    2023-12-20 02:38:53.135 [INFO] :: Deleting Inverse Kinematics Manager...
    2023-12-20 02:38:53.135 [INFO] :: Deleting OpenGL Manager...
    2023-12-20 02:38:53.158 [INFO] :: Deleting Script Engine...
    2023-12-20 02:38:53.160 [INFO] :: Deleting Importer Manager...
    2023-12-20 02:38:53.161 [INFO] :: Deleting Exporter Manager...
    2023-12-20 02:38:53.161 [INFO] :: Deleting File IO Preset Manager...
    2023-12-20 02:38:53.161 [INFO] :: Deleting Save Filter Manager...
    2023-12-20 02:38:53.161 [INFO] :: Deleting Asset IO Manager...
    2023-12-20 02:38:53.161 [INFO] :: Deleting Image Manager...
    2023-12-20 02:38:53.161 [INFO] :: Deleting Help Manager...
    2023-12-20 02:38:53.162 [INFO] :: Deleting Multimedia Manager...
    2023-12-20 02:38:53.162 [INFO] :: Deleting Cloud Manager...
    2023-12-20 02:38:53.162 [INFO] :: Deleting Asset Manager...
    2023-12-20 02:38:53.162 [INFO] :: Shutting down Content Manager...
    2023-12-20 02:38:53.163 [INFO] :: Deleting Content Manager...
    2023-12-20 02:38:53.163 [INFO] :: Shutting down Render Manager...
    2023-12-20 02:38:53.163 [INFO] :: Deleting Render Manager...
    2023-12-20 02:38:53.169 [INFO] :: Shutting down Simulation Manager...
    2023-12-20 02:38:53.169 [INFO] :: Deleting Simulation Manager...
    2023-12-20 02:38:53.169 [INFO] :: Deleting Texture Converter Manager...
    2023-12-20 02:38:53.170 [INFO] :: Deleting Texture Baker Manager...
    2023-12-20 02:38:53.170 [INFO] :: Deleting Device Manager...
    2023-12-20 02:38:53.170 [INFO] :: Deleting CallBack Manager...
    2023-12-20 02:38:53.170 [INFO] :: Clearing Undo Stack...
    2023-12-20 02:38:53.170 [INFO] :: Deleting Scene...
    2023-12-20 02:38:53.170 [INFO] :: Clearing the scene...
    2023-12-20 02:38:53.171 [INFO] :: *** Scene Cleared ***
    2023-12-20 02:38:53.171 [INFO] :: Deleting Undo Stack...
    2023-12-20 02:38:53.171 [INFO] :: Deleting Authentication Manager...
    2023-12-20 02:38:53.171 [INFO] :: Deleting Main Window...
    2023-12-20 02:38:53.305 [INFO] :: Deleting Viewport Manager...
    2023-12-20 02:38:53.335 [INFO] :: Deleting Action Manager...
    2023-12-20 02:38:53.336 [INFO] :: Hexagon Bridge : End logging.
    2023-12-20 02:38:53.342 [INFO] :: Deleting Pane Manager...
    2023-12-20 02:38:53.776 [INFO] :: Performing cleanup...
    2023-12-20 02:38:53.826 [INFO] :: Deleting Plugin Manager...
    2023-12-20 02:38:53.826 [INFO] :: Deleting Application Settings Manager...
    2023-12-20 02:39:02.820 --------------- DAZ Studio 4.22.0.15 exited ------------------
    2023-12-20 02:39:02.821 ~

    This is the scene.

    Post edited by barbult on
  • crosswindcrosswind Posts: 4,893
    edited December 2023

    barbult said:

    Hey, I guess I was too impatient. It took 15 minutes, but DS finally closed! The log has a warning about Unexpected null parameter.

    This is the end of the log:

    ....

    OK, that's it ~ the scene could be closed eventually but only "a hung session of DS" was in front of your eyes. So it seems there's no problem in terms of Clearing Scene.

    If the closing session was in background, it could be still closed after 15 mins, I believe... I really don't like the new way...

    Post edited by crosswind on
  • barbultbarbult Posts: 23,274

    crosswind said:

    barbult said:

    Hey, I guess I was too impatient. It took 15 minutes, but DS finally closed! The log has a warning about Unexpected null parameter.

    This is the end of the log:

    ....

    OK, that's it ~ the scene could be closed eventually but only "a hung session of DS" was in front of your eyes. So it seems there's no problem in terms of Clearing Scene.

    If the closing session was in background, it could be still closed after 15 mins, I believe... I really don't like the new way...

    Ctrl+N seems to be acting the same way as closing DS. I've never had to wait 15 minutes to restart DS after closing it. When the Ctrl+N finally finishes, I'm going to see what happens with DS 4.21. I sstill have that version as my general release.

  • crosswindcrosswind Posts: 4,893

    barbult said:

    crosswind said:

    barbult said:

    Hey, I guess I was too impatient. It took 15 minutes, but DS finally closed! The log has a warning about Unexpected null parameter.

    This is the end of the log:

    ....

    OK, that's it ~ the scene could be closed eventually but only "a hung session of DS" was in front of your eyes. So it seems there's no problem in terms of Clearing Scene.

    If the closing session was in background, it could be still closed after 15 mins, I believe... I really don't like the new way...

    Ctrl+N seems to be acting the same way as closing DS. I've never had to wait 15 minutes to restart DS after closing it. When the Ctrl+N finally finishes, I'm going to see what happens with DS 4.21. I sstill have that version as my general release.

    Me too ~ 4.21 is still with me. Let's compare the time...

  • barbultbarbult Posts: 23,274

    crosswind said:

    barbult said:

    crosswind said:

    barbult said:

    Hey, I guess I was too impatient. It took 15 minutes, but DS finally closed! The log has a warning about Unexpected null parameter.

    This is the end of the log:

    ....

    OK, that's it ~ the scene could be closed eventually but only "a hung session of DS" was in front of your eyes. So it seems there's no problem in terms of Clearing Scene.

    If the closing session was in background, it could be still closed after 15 mins, I believe... I really don't like the new way...

    Ctrl+N seems to be acting the same way as closing DS. I've never had to wait 15 minutes to restart DS after closing it. When the Ctrl+N finally finishes, I'm going to see what happens with DS 4.21. I sstill have that version as my general release.

    Me too ~ 4.21 is still with me. Let's compare the time...

    I loaded the scene in DS 4.21.0.5 and then closed DS. It is still running in the background after 30 minutes! I'm not sure how much longer I am willing to wait for this. I see now why people were complaining so much about shutdown time! This long delay has never happened to me before. It usually takes a minute or two. What is wrong with this scene? The only thing simulated is the sweater on the couch. It is not an animated sim. The scene file is 24,321 KB, not terribly large, I think; I have scenes much larger than that.

    Task Manager still shows Daz Studio Application running. I'm up to 37 minutes now.

  • barbultbarbult Posts: 23,274

    I give up. DS 4.21.0.5 has been running in the background for 51 minutes now. I am going to kill it and go to bed.

  • PerttiAPerttiA Posts: 9,605

    barbult said:

    crosswind said:

    barbult said:

    crosswind said:

    barbult said:

    Hey, I guess I was too impatient. It took 15 minutes, but DS finally closed! The log has a warning about Unexpected null parameter.

    This is the end of the log:

    ....

    OK, that's it ~ the scene could be closed eventually but only "a hung session of DS" was in front of your eyes. So it seems there's no problem in terms of Clearing Scene.

    If the closing session was in background, it could be still closed after 15 mins, I believe... I really don't like the new way...

    Ctrl+N seems to be acting the same way as closing DS. I've never had to wait 15 minutes to restart DS after closing it. When the Ctrl+N finally finishes, I'm going to see what happens with DS 4.21. I sstill have that version as my general release.

    Me too ~ 4.21 is still with me. Let's compare the time...

    I loaded the scene in DS 4.21.0.5 and then closed DS. It is still running in the background after 30 minutes! I'm not sure how much longer I am willing to wait for this. I see now why people were complaining so much about shutdown time! This long delay has never happened to me before. It usually takes a minute or two. What is wrong with this scene? The only thing simulated is the sweater on the couch. It is not an animated sim. The scene file is 24,321 KB, not terribly large, I think; I have scenes much larger than that.

    Task Manager still shows Daz Studio Application running. I'm up to 37 minutes now.

    How big is the memory footprint? The filesize of the savefile tells nothing about how much RAM does the scene take when loaded. 

  • barbultbarbult Posts: 23,274

    PerttiA said:

    barbult said:

    crosswind said:

    barbult said:

    crosswind said:

    barbult said:

    Hey, I guess I was too impatient. It took 15 minutes, but DS finally closed! The log has a warning about Unexpected null parameter.

    This is the end of the log:

    ....

    OK, that's it ~ the scene could be closed eventually but only "a hung session of DS" was in front of your eyes. So it seems there's no problem in terms of Clearing Scene.

    If the closing session was in background, it could be still closed after 15 mins, I believe... I really don't like the new way...

    Ctrl+N seems to be acting the same way as closing DS. I've never had to wait 15 minutes to restart DS after closing it. When the Ctrl+N finally finishes, I'm going to see what happens with DS 4.21. I sstill have that version as my general release.

    Me too ~ 4.21 is still with me. Let's compare the time...

    I loaded the scene in DS 4.21.0.5 and then closed DS. It is still running in the background after 30 minutes! I'm not sure how much longer I am willing to wait for this. I see now why people were complaining so much about shutdown time! This long delay has never happened to me before. It usually takes a minute or two. What is wrong with this scene? The only thing simulated is the sweater on the couch. It is not an animated sim. The scene file is 24,321 KB, not terribly large, I think; I have scenes much larger than that.

    Task Manager still shows Daz Studio Application running. I'm up to 37 minutes now.

    How big is the memory footprint? The filesize of the savefile tells nothing about how much RAM does the scene take when loaded. 

    Less than 5 MB. I have 32 MB in my computer. Here is a screenshot of the Task Manager when the scene was fully loaded, right before I closed Daz Studio.

     

    Screenshot 2023-12-20 043931.jpg
    882 x 175 - 30K
  • barbultbarbult Posts: 23,274

    I have determined that the white Christmas tree in the scene must be the problem. I deleted it (which took a long time in itself), saved the scene and closed DS. It took less than 15 seconds to close in DS 4.22.0.15 PB.

     

  • Richard HaseltineRichard Haseltine Posts: 97,479

    Which tree is that? Does it use a lot of instances? Is it a single complex object?

  • no__nameno__name Posts: 88

    Richard Haseltine said:

    What shape had you given the spotlight? The others would still be planar, and would have a dark area between the areas lit by the opposing sides just as the plane woulkd by my reasoning.

    Alright got it to work, looks like it's because even if "Iray Visible to primary rays" is set to off, surface still has refraction. Not sure the reason.

    -Create new primitive.

    -Set Glossy layered weith and Glossy reflection to 0

    -Set Refraction weight to 1

    -Make mesh emit light, keet it thin walled.

    -Create Advanced Nodes proprieties (Scripts/Utilities/Create Advanced Iray Node Properties)

    -Tick all (or just Ghost light factor)

    -In parameter set Iray Ghost light factor superior to 1

    Should be a "true" ghost light that works anywhere.

    DAZStudio_DiyCTG66Pg.jpg
    3009 x 797 - 320K
  • crosswindcrosswind Posts: 4,893

    barbult said:

    I have determined that the white Christmas tree in the scene must be the problem. I deleted it (which took a long time in itself), saved the scene and closed DS. It took less than 15 seconds to close in DS 4.22.0.15 PB.

     

    The tree was the culprit ? from which product ?

  • Richard HaseltineRichard Haseltine Posts: 97,479

    no__name said:

    Richard Haseltine said:

    What shape had you given the spotlight? The others would still be planar, and would have a dark area between the areas lit by the opposing sides just as the plane woulkd by my reasoning.

    Alright got it to work, looks like it's because even if "Iray Visible to primary rays" is set to off, surface still has refraction. Not sure the reason.

    -Create new primitive.

    -Set Glossy layered weith and Glossy reflection to 0

    -Set Refraction weight to 1

    -Make mesh emit light, keet it thin walled.

    -Create Advanced Nodes proprieties (Scripts/Utilities/Create Advanced Iray Node Properties)

    -Tick all (or just Ghost light factor)

    -In parameter set Iray Ghost light factor superior to 1

    Should be a "true" ghost light that works anywhere.

    Ah, I see - I think one of the earlier im,ages seemed to be showing a dark area on the ground under the plane and i thought that was what you were lookign at - or maybe that was a previous poster asking about shdows. In any event, the image on your previous post was clear and i have no idea how I missed seeing it - my apologies for being dense.

  • barbultbarbult Posts: 23,274
    edited December 2023

    Richard Haseltine said:

    Which tree is that? Does it use a lot of instances? Is it a single complex object?

    It has a lot of instances. It is from V3D Christmas Gifts and Tree. It comes with a big warning about instances that I should have heeded. The product has a tree without instances, which I have used without issue before. I wasn't concerned about instances, because I use UltraScenery with many thousand instances all the time. I don't know how many instances this tree has, but it must be a lot. I hope the developers can do further optimization on clearing instances, because this is painful. At least 4.22.0.15 took "only" 15 minutes, in comparison to 4.21.0.5, which I finally killed after almost an hour.

    White tree with instances.jpg
    583 x 790 - 127K
    Post edited by barbult on
  • barbultbarbult Posts: 23,274
    edited December 2023

    crosswind said:

    barbult said:

    I have determined that the white Christmas tree in the scene must be the problem. I deleted it (which took a long time in itself), saved the scene and closed DS. It took less than 15 seconds to close in DS 4.22.0.15 PB.

     

    The tree was the culprit ? from which product ?

    V3D Christmas Gifts and Tree. See my reply to Richard, which I just posted.

    Post edited by barbult on
  • no__nameno__name Posts: 88
    edited December 2023

    Richard Haseltine said:

    Ah, I see - I think one of the earlier im,ages seemed to be showing a dark area on the ground under the plane and i thought that was what you were lookign at - or maybe that was a previous poster asking about shdows. In any event, the image on your previous post was clear and i have no idea how I missed seeing it - my apologies for being dense.

    No need lol, I can be quite dense myself at time o/

    Imho whatever "Iray Visible to primary rays" does, it should override any refractions both for emissives and spotlights. If emissives can be fixed right now via surfaces tab, spotlights cannot (sadge). Forcing you to use your spotlights always behind your emissives ghost light or have to deal with your spotlight refractions (obviously spotlights that are not point). In fact, I don't understand why spotlights should have any kind of refraction? I must miss something (but I don't remember crossing that behavior in any engine). If Daz fixes this, the whole tricky Iray lightning is forever gone.

    I havn't time to test it yet, but another cool thing is that with 'ghost light factor' and now that G9 has separate eyes, you should probably fine tune the Iray "dead fish" eyes quite easily (and no more dirty tricks via gloss/top coat layers).

     

     

    Post edited by no__name on
Sign In or Register to comment.