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

17810121332

Comments

  • SpottedKittySpottedKitty Posts: 7,232

    What's up with this thread? Two days in a row I've got a forum e-mail, and both of them gave me a "page not found".

  • AndySAndyS Posts: 1,438
    AndyS said:
    has the inconsistance between diffuse and sss texture of the G8M been solved?

    That would be a content issue, not a DS issue, presumably - have you reproted the problem? I don't recall seeing discussions or mentions on the forum.

    The problem has been reported really some time ago.
    Since G8M Essentials comes as fixed part included the DAZ builds, one can expect those corrections to be included.

  • AndySAndyS Posts: 1,438

    For Iray you'ds probably need to look at the Iray chnage logs, psoted in edited form below the main announcement post at the ehad of this thread. The link does include the 4.11 changes, including those in builds later than the Public beta - once you scroll past the links to previous, now released, versions (which may take up the first screen or so, depending on window size and zoom factor) you will see the first entry is for 4.11.0.1

    Pardon, but the link only takes me here (pl see attachment). As you see: Current Build: 10.0  -> earlier builds ...
    Why doesn't it point to the very current entry?

    DAZ_Rel_Notes.jpg
    554 x 542 - 70K
  • AndyS said:
    AndyS said:
    has the inconsistance between diffuse and sss texture of the G8M been solved?

    That would be a content issue, not a DS issue, presumably - have you reproted the problem? I don't recall seeing discussions or mentions on the forum.

    The problem has been reported really some time ago.
    Since G8M Essentials comes as fixed part included the DAZ builds, one can expect those corrections to be included.

    Sure, if there's a bug it should be fixed - but content bug fixes are not tied or linked to application updates, the topic of this thread. The same, really, would be true of a bug in the shader code if that is the root of your reported refraction issue.

  • AndyS said:

    For Iray you'ds probably need to look at the Iray chnage logs, psoted in edited form below the main announcement post at the ehad of this thread. The link does include the 4.11 changes, including those in builds later than the Public beta - once you scroll past the links to previous, now released, versions (which may take up the first screen or so, depending on window size and zoom factor) you will see the first entry is for 4.11.0.1

    Pardon, but the link only takes me here (pl see attachment). As you see: Current Build: 10.0  -> earlier builds ...
    Why doesn't it point to the very current entry?

    It has links to the previous version changelogs, since that is the main change log landing page. As I said in the quoted text, just scroll past those to get to the actual change entries starting at 4.11.0.1

  • I updated to 4.11.0.196 and was able to pose and setup a scene from start to finish with no noticeable issue. The denoising for rendering out to tif/png worked very well even with lower iteration start (100). I am now confident with setting up my scenes for most cases in this build. I did not try dforce.

    I decided to try rendering to a beauty canvas and as soon as the denoiser kicked in everything went great for the room but something about the figure and hair turns it into abstract art on the figure. I started the denoiser at 250th iteration and set for 1200 total iterations. It did not clear up and all detail was lost on the figure and hair. I will have to attach a sample later. The rest of the room looked perfect though. Not sure if it is just the settings for hair and skin that are causing the issue but for me canvases are still not an option in this iteration but I will absolutely use it for rendering without canvases!

    I'm very happy that AI denoising is making it into DAZ.

  • VisuimagVisuimag Posts: 570

    I still have trouble with mouse mvement, even after the latest update. Sticking by 4.10 until that's sorted (even if it seems like I'm the only one having said issue). 

  • marblemarble Posts: 7,500
    Visuimag said:

    I still have trouble with mouse mvement, even after the latest update. Sticking by 4.10 until that's sorted (even if it seems like I'm the only one having said issue). 

    I'm using the latest build almost exculsively now and I haven't noticed much of a problem with the mouse other than the occasional multi-select in the Scene tab tree (one click selects multiple nodes rather than the one I wanted). Another mouse issue that has always been there (and still is) is, when using the parameter sliders to move or pose something, the movement will jump back slightly as I let go of the mouse button (maybe my old fingers though?).  The mouse is not good for delicate movements so I tend to use the plus/minus operators with adjusted values in the Properties.

    The problem I had in 4.10 where the camera jumped to a different part of the scene seems to have been fixed in the beta. However, there is still a bug with Active Pose which I reported to Tech Support a few weeks ago.

     

  • RAMWolffRAMWolff Posts: 10,228

    By the way, just asking... when I was using the General release the Import and Export dialog would remember the last settings I had but this is not the case with this beta.  I use the Cinema 4D setting as it's compatible with ZBrush but it doesn't stick, have to select that one every time.  Just wondering if there is a setting in the Registry or what to get that fixed up?  

  • MattB123MattB123 Posts: 36

    Still no word on the leg warping issue? Not wanting to sound like a whinger but even keeping limits enabled it still occurs a lot and pretty much makes it impossible to render a a lot of scenes. I'd have thought this particular bug would have been higher on the priority list than quite a few listed in the change log

  • Thundorn said:

    Still no word on the leg warping issue? Not wanting to sound like a whinger but even keeping limits enabled it still occurs a lot and pretty much makes it impossible to render a a lot of scenes. I'd have thought this particular bug would have been higher on the priority list than quite a few listed in the change log

    That has been fixed in this release.

  • MattB123MattB123 Posts: 36
    Thundorn said:

    Still no word on the leg warping issue? Not wanting to sound like a whinger but even keeping limits enabled it still occurs a lot and pretty much makes it impossible to render a a lot of scenes. I'd have thought this particular bug would have been higher on the priority list than quite a few listed in the change log

    That has been fixed in this release.

    Hmm. I'll have to try reloading all my figures. Thanks for getting back to me. 

  • Thundorn said:
    Thundorn said:

    Still no word on the leg warping issue? Not wanting to sound like a whinger but even keeping limits enabled it still occurs a lot and pretty much makes it impossible to render a a lot of scenes. I'd have thought this particular bug would have been higher on the priority list than quite a few listed in the change log

    That has been fixed in this release.

    Hmm. I'll have to try reloading all my figures. Thanks for getting back to me. 

     The chnage is listed in http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_11_0_174

    Reverted changes to limit unlocking on DSON file load; was causing products that depend on compund property limits and ERC driven values to behave other than intended

  • Has a solution to this problem been worked out yet in the current beta?

  • barbultbarbult Posts: 24,755
    edited August 2018

    Changes in DS 4.11 broke tools that show/hide instances in the viewport. I have found multiple products that no longer work correctly because of this, including (V3Digitimes) Scene Optimizer SKU 41479, (Stonemason) Willow Creek SKU 38095, and (Stonemason) The Private Garden SKU 47735. The problem seems to be related to removing Instance Preview from the list of parameters for an object. In all cases, these products work correctly in DS 4.10.0.123 but not 4.11.0.196. I have submitted a help request.

    Post edited by barbult on
  • Richard HaseltineRichard Haseltine Posts: 102,344
    edited August 2018
    barbult said:

    Changes in DS 4.11 broke tools that show/hide instances in the viewport. I have found multiple products that no longer work correctly because of this, including (V3Digitimes) Scene Optimizer SKU 41479, (Stonemason) Willow Creek SKU 38095, and (Stonemason) The Private Garden SKU 47735. The problem seems to be related to removing Instance Preview from the list of parameters for an object. In all cases, these products work correctly in DS 4.10.0.123 but not 4.11.0.196. I have submitted a help request.

    I think these are scripts - if they used one method to get the control DS can fix the commands to work in 4.11.x.x (or should be able to) - however it's possible that the scripts were written using different calls for which the auto-fix doesn't apply. Hopefully support will be able to provide the creators with an explanation of what they need to do.

    Post edited by Richard Haseltine on
  • barbultbarbult Posts: 24,755
    barbult said:

    Changes in DS 4.11 broke tools that show/hide instances in the viewport. I have found multiple products that no longer work correctly because of this, including (V3Digitimes) Scene Optimizer SKU 41479, (Stonemason) Willow Creek SKU 38095, and (Stonemason) The Private Garden SKU 47735. The problem seems to be related to removing Instance Preview from the list of parameters for an object. In all cases, these products work correctly in DS 4.10.0.123 but not 4.11.0.196. I have submitted a help request.

    I think these are scripts - if they used one method to get the control DS can fix the commands to work in 4.11.x.x (or should be able to) - however it's possible that the scripts were written using different calls for which the auto-fix doesn't apply. Hopefully support will be able to provide the creators with an explanation of what they need to do.

    Yes, they are scripts. The Stonemason scripts aren't even encrypted, so if you happen to own those products, you can take a look, if you are curious. 

  • barbultbarbult Posts: 24,755
    edited September 2018

    When I create a primitive, I get errors in the log file. I submitted a help request #279608.

    2018-09-01 14:00:41.006 WARNING: Script Error: Line 476

    2018-09-01 14:00:41.006 WARNING: Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.006 WARNING: Stack Trace:

    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476

    2018-09-01 14:00:41.007 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():

    2018-09-01 14:00:41.007 Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.007 

    Screenshot 2018-09-01 14.00.38.png
    244 x 310 - 17K
    Post edited by barbult on
  • barbult said:

    When I create a primitive, I get errors in the log file. I submitted a help request #279608.

    2018-09-01 14:00:41.006 WARNING: Script Error: Line 476

    2018-09-01 14:00:41.006 WARNING: Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.006 WARNING: Stack Trace:

    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476

    2018-09-01 14:00:41.007 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():

    2018-09-01 14:00:41.007 Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.007 

    Not getting an errro with those settings here.

  • barbultbarbult Posts: 24,755
    barbult said:

    When I create a primitive, I get errors in the log file. I submitted a help request #279608.

    2018-09-01 14:00:41.006 WARNING: Script Error: Line 476

    2018-09-01 14:00:41.006 WARNING: Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.006 WARNING: Stack Trace:

    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476

    2018-09-01 14:00:41.007 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():

    2018-09-01 14:00:41.007 Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.007 

    Not getting an errro with those settings here.

    Interesting. I closed DS 4.11.0.196 and opened it again. I did nothing other than create a primitive and I still get the errors.

  • nicsttnicstt Posts: 11,715
    edited September 2018

    I get errors:

    2018-09-01 20:22:41.430 WARNING: Script Error: Line 476
    2018-09-01 20:22:41.430 WARNING: Error: cannot access member `select' of deleted QObject
    2018-09-01 20:22:41.430 WARNING: Stack Trace:
        <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476
    2018-09-01 20:22:41.430 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():
    2018-09-01 20:22:41.431 Error: cannot access member `select' of deleted QObject
    2018-09-01 20:22:41.431

    ... And it doesn't seem to matter what primitive I create either.

    Post edited by nicstt on
  • barbultbarbult Posts: 24,755
    nicstt said:

    I get errors:

    2018-09-01 20:22:41.430 WARNING: Script Error: Line 476
    2018-09-01 20:22:41.430 WARNING: Error: cannot access member `select' of deleted QObject
    2018-09-01 20:22:41.430 WARNING: Stack Trace:
        <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476
    2018-09-01 20:22:41.430 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():
    2018-09-01 20:22:41.431 Error: cannot access member `select' of deleted QObject
    2018-09-01 20:22:41.431

    ... And it doesn't seem to matter what primitive I create either.

    Thank you for confirming that it isn't just me! What is different about Richard's installation?

  • I don't know - mine was a straight launch and create primitive too.

  • barbultbarbult Posts: 24,755

    I don't know - mine was a straight launch and create primitive too.

    Are you running 4.11.0.196, or do you have a newer private beta? Can you get any visibility into what the failing script does?

  • barbult said:

    I don't know - mine was a straight launch and create primitive too.

    Are you running 4.11.0.196, or do you have a newer private beta? Can you get any visibility into what the failing script does?

    Yes, I am using 4.11.0.196 - and the script, if you look at the log, is in the application folder so it is specific to that version (4.10..0.123 would have its own version of the file in its own folder, and we may assume the same would be true for other versions). The script is .dse, which means it's encrypted.

  • DoctorJellybeanDoctorJellybean Posts: 8,654
    edited September 2018
    barbult said:

    When I create a primitive, I get errors in the log file. I submitted a help request #279608.

    2018-09-01 14:00:41.006 WARNING: Script Error: Line 476

    2018-09-01 14:00:41.006 WARNING: Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.006 WARNING: Stack Trace:

    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476

    2018-09-01 14:00:41.007 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():

    2018-09-01 14:00:41.007 Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.007 

    The actual plane does get created, right? The errors only appear in the log?

    Post edited by DoctorJellybean on
  • Oops, sorry - I thought it was failing in DS and the log file was just for info. Yes, I do see the same messages in the log.

  • barbultbarbult Posts: 24,755
    barbult said:

    When I create a primitive, I get errors in the log file. I submitted a help request #279608.

    2018-09-01 14:00:41.006 WARNING: Script Error: Line 476

    2018-09-01 14:00:41.006 WARNING: Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.006 WARNING: Stack Trace:

    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476

    2018-09-01 14:00:41.007 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():

    2018-09-01 14:00:41.007 Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.007 

    The actual plane does get created, right? The errors only appear in the log?

    Yes. That is correct.
  • barbult said:
    barbult said:

    When I create a primitive, I get errors in the log file. I submitted a help request #279608.

    2018-09-01 14:00:41.006 WARNING: Script Error: Line 476

    2018-09-01 14:00:41.006 WARNING: Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.006 WARNING: Stack Trace:

    <anonymous>()@C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse:476

    2018-09-01 14:00:41.007 WARNING: ..\..\..\..\..\src\pluginsource\DzPrimitives\dzprimitivedlg.cpp(346): Error executing script file: C:/Program Files/DAZ 3D/DAZStudio4 Public Build/scripts/support/DAZ/dzNodePostCreate.dse in DzPrimitiveDlg::executePostCreateScript():

    2018-09-01 14:00:41.007 Error: cannot access member `select' of deleted QObject

    2018-09-01 14:00:41.007 

    The actual plane does get created, right? The errors only appear in the log?

     

    Yes. That is correct.

    This is marked as fixed in the most recent build http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_11_0_213

    Fixed an issue in the dzNodePostLoadCreate script that caused an error message to appear in the log when “Create > New Primitive…” was used; the list being used to restore material selection state was stale and needed to be updated post application of the Material(s) Preset

  • You beat me to it, Richard.

This discussion has been closed.