Loading...
> >

Daz Studio 4.24[.0.x], General Release!

1235»

Comments

  • barbultbarbult Posts: 26,156

    crosswind said:

    barbult said:

    I saved a scene in DS 4.24.0.3 and I unchecked all of the options in the popup dialog, including Render Settings. When I reloaded the scene, it changed my Render Settings. I looked in the scene DUF file, and it did indeed save a Render Settings section. Why? Is this a bug I need to report? Will Daz even fix 4.24 bugs anymore, if I did submit a help request?

    This was in the saved scene file. There was also a Tone Mapper section.

                {
                    "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" : "/All%20HDRI/HDRI%20Haven/All%20Free/Studio%20Small%2005/studio_small_05_2k.hdr"
                                    }
                                }
                            ]
                        }
                    ]
                },

     

    As far as I understand, the option of "Include Render Settings" doesn't include the nodes of Tonemapper Options and Environment Options, i.e. since they're Nodes, they'll be always saved within a Scene file ~~ (sb. pls correct me if I'm wrong ...)

    Then, if you want to keep the default values of Tonemapping & Env. in Render Settings, you can set a Render Settings Preset of those two nodes only in F2 > Scene > On Load > Post Open. Or, set a Script there to remove those two nodes ~~

    Hmmm, nodes seems like a plausible explanation. But Tone Mapping and Environment also appear in the Render Settings pane, so it seems somewhat ambiguous and confusing. Are they, or are they not, "Render Settings"? If not, why are they included and can be modified from the Render Settings pane?
    I wouldn't very often want to exclude those settings, but I would like to be able to sometimes exclude them via the list of items in the popup dialog. I thought by excluding Render Settings, I would exclude everything in the Render Settings pane. That seems like a logical assumption to me. That is not how it is implemented evidently. So I assumed it was a bug.

    (@crosswind I don't expect you to answer these questions. But it would be nice if someone from Daz could explain the logic behind this implementation.)

  • crosswindcrosswind Posts: 9,537

    barbult said:

    crosswind said:

    barbult said:

    I saved a scene in DS 4.24.0.3 and I unchecked all of the options in the popup dialog, including Render Settings. When I reloaded the scene, it changed my Render Settings. I looked in the scene DUF file, and it did indeed save a Render Settings section. Why? Is this a bug I need to report? Will Daz even fix 4.24 bugs anymore, if I did submit a help request?

    This was in the saved scene file. There was also a Tone Mapper section.

                {
                    "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" : "/All%20HDRI/HDRI%20Haven/All%20Free/Studio%20Small%2005/studio_small_05_2k.hdr"
                                    }
                                }
                            ]
                        }
                    ]
                },

     

    As far as I understand, the option of "Include Render Settings" doesn't include the nodes of Tonemapper Options and Environment Options, i.e. since they're Nodes, they'll be always saved within a Scene file ~~ (sb. pls correct me if I'm wrong ...)

    Then, if you want to keep the default values of Tonemapping & Env. in Render Settings, you can set a Render Settings Preset of those two nodes only in F2 > Scene > On Load > Post Open. Or, set a Script there to remove those two nodes ~~

    Hmmm, nodes seems like a plausible explanation. But Tone Mapping and Environment also appear in the Render Settings pane, so it seems somewhat ambiguous and confusing. Are they, or are they not, "Render Settings"? If not, why are they included and can be modified from the Render Settings pane?
    I wouldn't very often want to exclude those settings, but I would like to be able to sometimes exclude them via the list of items in the popup dialog. I thought by excluding Render Settings, I would exclude everything in the Render Settings pane. That seems like a logical assumption to me. That is not how it is implemented evidently. So I assumed it was a bug.

    (@crosswind I don't expect you to answer these questions. But it would be nice if someone from Daz could explain the logic behind this implementation.)

    Actually I agree with you, and I also think there needs to be an explanation from Daz for this issue. 

  • colongraphics colongraphics Posts: 83
    edited September 20

    Lev_c said:

    The update has bricked Daz for me:

    image

    Anyone got any solutions?

    Similar problem, with multiple crashes during a work session. I even went so far as re-installing windows 11 to ensure the drivers were up to date and a clean version of Daz 4.24 to try to fix the problem, to no avail. The access violation notification indicates that the program is is trying to access memory allocated to the operating system, so the program is shut down to avoid a computer crash. This might be a hardware problem with either the installed  RAM or the video card, a driver problem with the video card, or a bug in the Daz application. Neither Daz support or I have been able to isolate the problem, so I wish you better luck.

    Post edited by Richard Haseltine on
  • ImagoImago Posts: 5,650

    colongraphics said:

    Similar problem, with multiple crashes during a work session. I even went so far as re-installing windows 11 to ensure the drivers were up to date and a clean version of Daz 4.24 to try to fix the problem, to no avail. The access violation notification indicates that the program is is trying to access memory allocated to the operating system, so the program is shut down to avoid a computer crash. This might be a hardware problem with either the installed  RAM or the video card, a driver problem with the video card, or a bug in the Daz application. Neither Daz support or I have been able to isolate the problem, so I wish you better luck.

    This happens on any scene or just some of them?
    I had a similar crash in the past months.

  • colongraphics colongraphics Posts: 83
    edited September 20

    Imago said:

    colongraphics said:

    Similar problem, with multiple crashes during a work session. I even went so far as re-installing windows 11 to ensure the drivers were up to date and a clean version of Daz 4.24 to try to fix the problem, to no avail. The access violation notification indicates that the program is is trying to access memory allocated to the operating system, so the program is shut down to avoid a computer crash. This might be a hardware problem with either the installed  RAM or the video card, a driver problem with the video card, or a bug in the Daz application. Neither Daz support or I have been able to isolate the problem, so I wish you better luck.

    This happens on any scene or just some of them?
    I had a similar crash in the past months.

    Other than having a Genesis 8 based character in the scene, no. That doesn't really narrow it down very much. Maybe it would happen with Genesis 3 or Genesis 9 , but I don't use those characters as often so I don't see it. I can go through a few sessions without problems, but the scene I attached below crashed five times before I could render it. There doesn't seems to be enough consistency so I can isolate the problem. It is frustrating, not being able to have a consistant user experience.

    DwarfRangerForestEdit.png
    1920 x 1536 - 5M
    Post edited by Richard Haseltine on
  • ElorElor Posts: 3,133

    Due to the scripting bug with Daz Studio 4.23 on MacOS, I switched to the public beta, but now I would like to go back to the general release.

    I was able to transfert the UI using the script shared by Daz (here : http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/general_ui/copy_ui_from_channel/start ) but is there an easy way to copy the list of all the directory I mapped in the beta version?

  • Richard HaseltineRichard Haseltine Posts: 107,863

    http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/file_io/save_mapped_paths/start

  • colongraphics colongraphics Posts: 83
    edited September 21

    colongraphics said:

    Imago said:

    colongraphics said:

    Similar problem, with multiple crashes during a work session. I even went so far as re-installing windows 11 to ensure the drivers were up to date and a clean version of Daz 4.24 to try to fix the problem, to no avail. The access violation notification indicates that the program is is trying to access memory allocated to the operating system, so the program is shut down to avoid a computer crash. This might be a hardware problem with either the installed  RAM or the video card, a driver problem with the video card, or a bug in the Daz application. Neither Daz support or I have been able to isolate the problem, so I wish you better luck.

    This happens on any scene or just some of them?
    I had a similar crash in the past months.

    Other than having a Genesis 8 based character in the scene, no. That doesn't really narrow it down very much. Maybe it would happen with Genesis 3 or Genesis 9 , but I don't use those characters as often so I don't see it. I can go through a few sessions without problems, but the scene I attached below crashed five times before I could render it. There doesn't seems to be enough consistency so I can isolate the problem. It is frustrating, not being able to have a consistant user experience.

    I can confirm that the access violation error did occur when using Genesis 3 figures. I am starting to suspect that a Windows 11 update in August is the root of the problem.

    Post edited by Richard Haseltine on
  • ElorElor Posts: 3,133

    Richard Haseltine said:

    http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/file_io/save_mapped_paths/start

    Thank you :)

  • plarffplarff Posts: 279
    edited October 25

    I have to say, I finally installed 24.3 version and I LOVE the dark UI with light green look so much. 

    ps. I LOOOOVE the improved Spot Render options. Just so much better functionality. I think next for the Spot Render eveolution should be a Lasso type tool function similar to Photoshop if possible.

    Richard Haseltine said:

    Masterstroke said:

    In Darkside-Midnight UI mode, Transforms sliders in the Parameter tab don't have color background anymore?
    They are just grey now.
    Is this intended?

    Window>Style>Customise Style, in the 2D Axis group alt-opt click the colour pickers to reset them. It is intentional, but the default colours are unchanged.

    Post edited by plarff on
  • khasdannyakhasdannya Posts: 4
    edited October 28

    why genesis 9 load so slow work so bad (freezes all!) and why ruin the genesis 1 morphs?!!! exist a way for delete all genesis 9 [stuff] and make genesis 1 useful again and yo udont care anymore???? 

    Post edited by Richard Haseltine on
  • LeanaLeana Posts: 12,735

    I'm not sure what problem you have but Genesis 9 does not impact Genesis 1 morphs, they're completely separate figures.

  • ImagoImago Posts: 5,650

    khasdannya said:

    why genesis 9 load so slow work so bad (freezes all!) and why ruin the genesis 1 morphs?!!! exist a way for delete all genesis 9 [stuff] and make genesis 1 useful again and yo udont care anymore???? 

    I use almost exclusively Genesis 1 and didn't notice any issues until now. What exactly happens in your installation? 

Sign In or Register to comment.