Loading...
> >

Daz Studio Pro BETA - version 4.9.4.122! (UPDATED)

Daz SoftwareDaz Software Posts: 33
edited July 2017 in Daz Studio Discussion

Daz 3D is pleased to announce Daz Studio Pro BETA - version 4.9.4.122! (*UPDATED*)

 

 

 

!! IF YOU HAVE NOT UPGRADED TO THE 4.9 GENERAL RELEASE, IT IS HIGHLY RECOMMENDED THAT YOU BACKUP YOUR CONTENT DATABASE IN DAZ STUDIO 4.x BEFORE LAUNCHING THIS VERSION !!

How do I backup my User Data in Daz Studio?

 

!! IF YOU HAVE NOT ALREADY MIGRATED FROM THE VALENTINA DB BASED CMS, IT IS HIGHLY RECOMMENDED THAT YOU MIGRATE TO THE POSTGRESQL BASED CMS BEFORE LAUNCHING THIS VERSION !!

Has the Content Management Service (CMS) changed?

 

Highlights:

 

4.9.4.122 (June 30, 2017) *UPDATED*

  • Auto-Fit / Transfer Utility
    • Fixed a crash when using Auto-Fit or Transfer Utility

4.9.4.121 (June 23, 2017)

  • PowerPose
    • Fixed a crash on OS X when clicking a node point that controls a property with a range of zero; e.g., Genesis 3 & Genesis 8 twist bones, where the min and max of cetain transform properties are both set to 0
    • Fixed an issue where the right-click drag vertical control label for a node point could incorrectly display the label for the left-click drag vertical control
    • Fixed an issue where a change in the size/scale of a given node point's effect was not being signaled (and therefore not being applied)
    • Fixed an issue where deselecting a property point did not cause all of the potential properties to be deselected; this could result in properties that should not be affected by a given property point being affected
    • Fixed an issue where mapping of property points did not correctly initialize; this could result in unintended results when manipulating property ponts
  • Content Loading
    • Fixed an issue where holding the AltModifier key while drag-n-drop loading a Character Preset that executes a post-load script (e.g., Genesis 8) would not respect the offset defined by the load target

4.9.4.117 (June 14, 2017)

  • PowerPose
    • Fixed an issue where right-click drag horizontal on a property point was flipping the effect of the drag direction based on data for the left-click drag
    • Fixed an issue where the left-click drag vertical size on a node point was using the size data for the right-click drag vertical

4.9.4.115 (June 13, 2017)

  • PowerPose
    • Now restores the specified properties of nodes in a node group point if the AltModifier is pressed when clicking a selected node group point
    • No longer deselects the selected node(s) of a figure when clicking an “empty” area of the template
    • No longer forces deselect of a given point in order to click and drag the same point again
    • Updated styling of points
    • Updated tips to reflect style changes
    • Added support for enabling version 3+ templates for specific geometries
    • Fixed a crash when the selected figure is missing a template node
    • Fixed an issue where clicking and dragging a node group point would zero the values of properties of each node in the group before beginning to manipulate them; causing it to “pop” with each use
    • Fixed an issue where holding the AltModifier while clicking a node point did not restore the properties of the node
    • Fixed an issue where holding the AltModifier while clicking a point of a given type would restore the properties associated with the selected point even if the clicked point was not the selected point
    • Fixed an issue when selecting a prop; selecting a prop in the hierarchy of a skeleton should NOT cause the template for the figure to be deselected; selecting a prop NOT in the hierarchy of a skeleton should cause the template for the figure to be deselected
    • Fixed a crash when the 'current' node was missing
    • Fixed pixelMetric (log) warnings
    • Fixed paint (log) warning

4.9.4.113 (June 9, 2017)

  • Uber Iray Material
    • Added a "Dual Lobe Specular Reflectivity" property
  • PowerPose
    • Made improvements to configuration abilities; via template files
    • Dynamic scaling of template data is now supported (for version 3+ templates)
      • Supports scaling up to the dimensions of the background image; if the widget/pane is larger than the background image for the template, it will be centered
      • Supports scaling down to a minimum of 300h x 200w
    • The layout of the pane has been changed
      • The encompassing tab widget has been removed; in preparation for replacing it with a combobox that provides easy access to all templates in the set
      • The "Reset Pose" button has been removed; use actions in the pane's option menu and/or action accelerators (keyboard shortcuts)
      • Added an InfoDivider with a Tips page
    • Fixed cursor display issues
  • Preset Saving
    • Added support for setting a post-load script to the Character Preset Save Options dialog
  • Scripting
    • Made API additions and/or resolved issues in various areas; see the Change Log for more detail
  • Fixed bugs and/or made improvements in various areas; see the Change Log for details

4.9.4.110 (May 26, 2017)

  • NVIDIA Iray
    • Integrated Iray 2016.3.2 (278300.12584); see below for more details
  • Uber Iray Material
    • Added support for chromatic sub surface scattering color
    • Added a "Scatter & Transmit Intensity" option to the "Base Color Effect" property
    • Added support for dual lobe specular
    • Added support for new features in translation to Shader Mixer
  • Database Driven Asset Views
    • Dragging and dropping an asset onto a category when the "Filter By Context" option is checked and an object in the scene is selected will now ask whether or not the user would like to mark the asset(s) as being compatible with the compatibility base of the selected object
  • Database Driven Product Views
    • When the path of an icon for a product cannot be determined from a database entry (e.g., installed/imported vs created), an attempt is made to locate an icon in the mapped Daz Studio/Poser Format directories where the path/name matches the pattern ./Runtime/Support/<StoreID>_[<ProductToken>_]<Product_Name>.<Ext>; the PNG extension is attempted followed by the JPG extension if not found
  • Content DB Editor
    • Sending the "LOCAL USER" product to the Content DB Editor no longer displays the "Product" page within the dialog; the "LOCAL USER" product is a special case catch-all product of which the product specific details should not be modified
    • The "LOCAL USER" store is now explicitly listed in the store selector on the "Product" page of the Content DB Editor dialog instead of displaying an empty value
    • Content DB Editor now checks that a file is not user-facing (loadable) before it allows that file to be listed in the support files list
    • Editing a file listed in the Support File(s) list of Content DB Editor and choosing a user-facing file removes the edited entry from the list
    • Content DB Editor root categories now use a path combobox dialog instead of root categories menu; prevents the menu from becoming so large that it cannot fit on the screen
  • Auto-Fit
    • Added support for applying pose data in clones to morphs that are not removed
    • Optimized pose corrective morphs
    • Added support for clone asset ERC links
    • Auto-Fit now provides cursor feedback while busy
  • Transfer Utility
    • Transfer Utility now supports clone assets with embedded pose data
    • Added support for applying pose data in clones to morphs that are not removed
    • Optimized pose corrective morphs
    • Added support for clone asset ERC links
    • Fixed a skin binding issue with the "Replace Source With Target" option
  • Clone Asset Saving
    • Replaced the message box and node selection behavior used by Clone Asset save with a dialog that presents options for choosing which figure represents the base and which figure represents the clone
    • Clone Asset save now suggests a filename based on the clone figure name in the file save dialog
    • Clone Asset save now provides an option within the dialog to select the destination base path; this is automatically set/updated when the Base Figure is selected/updated
    • Clone Asset save now provides a property selection view within the dialog for selecting which properties to remove from the target figure when projecting using the clone via Auto-Fit or Transfer Utility
  • PowerPose
    • Fixed an issue that left selection points clickable when no figure is selected
    • Fixed an issue that caused cursor feedback when no figure is selected and no selection points are displayed
    • Updated the default male templates to match functionality provided by the default female templates
    • Templates now support relative (to the templates file) paths
    • The ability to dynamically load a template set from a figure's support asset tools folder (for non-legacy figures) has been added
    • Clicking a property selection point now causes the node associated with that property to become selected; if the node is hidden, the node hierarchy is ascended until a non-hidden parent node is reached
    • The label of a node is now used in tooltips instead of its name; matches display in other areas of the UI
    • Pane configuration has been moved to the layout file instead of the startup script
    • ActivePose tool configuration has been moved to application settings instead of the startup script
    • The pane option menu has been updated
    • Tool tips, status tips, and what's this text has been extracted to an inline help file
    • The ability to save a template set via scripting API has been added; this feature is still in the late ALPHA phase of development - format is subject to change as the feature is completed; saved templates are not compatible with earlier versions; non-legacy vs legacy figure is handled differently based on the corresponding asset loading mechanisms
    • Non-legacy figure templates can now specify a property on any node (including the skeleton) as a selection point; legacy figures are still limited to Morphforms
  • Map Transfer
    • The alpha channel of a texture is now supported when using GPU
  • Animation Saving/Loading
    • Current animation range is now saved/read to/from a scene file
    • Current play range is now saved/read to/from a scene file
    • FPS is now saved/read to/from a scene file; FPS is no longer written to the startup script
    • Clearing the scene (e.g., File > New) now resets FPS to the default (30)
  • Node
    • Fixed an issues where the "Visible in Render" property was not being respected in OpenGL renders
  • Group Node (3D Layer)
    • The "Visible in Render" property now controls whether or not child nodes are considered visible in a render
    • Fixed an issues where the "Visible in Render" property was not being respected in OpenGL renders
  • General User Interface
    • Updated default menus; recommend running the "Update and Merge Menus" script
    • Added the ability to invoke a screen color picker from any color widget by pressing the AltModifier on the keyboard while initiating a left-click + hold from the area of the color-well between the numeric values; the cursor will change to a cross and the color will update as the cursor is moved; releasing the left-click + hold commits the color of the pixel currently under the center of the cross cursor; right-clicking while the left-click + hold is still active cancels the operation
    • Added a Log Size preference (and a Default button) to the General page in the Preferences dialog
  • Scripting
    • Many API additions and/or resolved issues in various areas; see the Change Log for more detail
  • Fixed bugs and/or made improvements in various areas; see the Change Log for details

 

Important Notes:

 

  • The first time you launch Daz Studio 4.9, any data that exists in the content database is migrated so that it can be used in Daz Studio 4.9.
  • The amount of time the database migration operation takes is proportional to the amount of data to be migrated.
  • The database migration operation does not delete the data that it migrates from the previous location so that it remains accessible by earlier versions and other applications, such as Carrara.
  • Daz Studio 4.9 uses the same PostgreSQL database as Daz Studio 4.6 and later, and/or other applications, such as Carrara.
  • A portion of the data contained within the database is shared amongst versions but not entirely. For example:
    • Creating a category in either Daz Studio 4.9 or 4.8 will cause that category to exist in the other version
    • Assigning a file to that category in Daz Studio 4.9 will NOT cause that file to be assigned to that category in Daz Studio 4.8
    • Assigning a file to that category in Daz Studio 4.8 WILL cause the file to be assigned to the category in Daz Studio 4.9
  • Reseting the database in any version of Daz Studio that uses PostgreSQL (e.g., 4.6 or later) will purge all of data in the database, including any data that may be used by earlier versions or other applications, such as Carrara.
  • After the initial migration operation, edited metadata in Daz Studio 4.8 will not be migrated to Daz Studio 4.9.
    • A workaround is to export User Data from Daz Studio 4.8 and reimport User Data in Daz Studio 4.9.

 

Frequently Asked Questions:

 

 

General Release Threads:

 

 

Previous 4.9 Beta Threads:

 

  • 4.9.3.166 (RC5)
  • 4.9.3.153 (RC4)
  • 4.9.3.128 (RC3)
  • 4.9.3.117 (RC2)
  • 4.9.3.71 (RC)
  • 4.9.3.56
  • 4.9.3.37
  • 4.9.3.25
  • 4.9.2.70
  • 4.9.2.67 (RC)
  • 4.9.2.60
  • 4.9.2.55
  • 4.9.2.44
Post edited by rbtwhiz on
«1345678

Comments

  • rbtwhizrbtwhiz Posts: 1,992
    edited May 2017

    What is new in this build? Do I need to update my copy?

    Daz Studio 4.9.4.x resolves several issues and implements several improvements since the 4.9.3.166 General Release. The first post contains highlights and more detail on specific fixes/changes/improvements can be found in the Change Log. All new downloads of the Daz Studio Pro BETA product (SKU: 12000) will be of this version.

    Post edited by rbtwhiz on
  • rbtwhizrbtwhiz Posts: 1,992
    edited May 2017

    Has the NVIDIA Iray renderer been updated?

    Yes, it has.

    *Note: The entries below come directly from the NVIDIA Iray 2016.3.2/2016.3.1 release notes. Some entries, such as the mention of Iray Realtime, Linux, etc, currently have no bearing on Daz Studio itself but are included for completeness.

    Iray 2016.3.2, build 278300.12584

    Added and Changed Features

    • General
      • Timestamps in log messages have been changed to include now the time zone offset.
      • Timestamps in HTTP headers have been changed to conform to RFC 2616.

    Fixed Bugs

    • General
      • A problem with degenerate polys where the hole equals the outer loop has been fixed. A vdebug message is printed if poly loops are ignored. Bug #18097.
      • A crash on a degenerate poly with lots of duplicate vertices and a 0-area hole has been fixed. Bug #18097.
      • The node manager now prints the IP address rather than the hostname for nodes joining the group.
      • In the node manager, a potential deadlock has been fixed when get_property was called from a property callback. Bug #17951.
    • .mi File Exporter
      • The export of the trace depth parameters depth reflect, depth refract and depth are now handled independently, whenever given. Bug #17881.
      • The export of bsdf measurements has been fixed. The filename was not quoted and hence caused a syntax error. Bug #17873.
      • A crash during export of multiple tex spaces has been fixed. The exporter tried to access multiple tex spaces using the same connectivity, which failed. Later on, the tex spaces were accessed unconditionally, even though they were 0. Bug #18118.
    • Iray Bridge
      • A rare hang bug when calling cancel render on an Iray Cloud render context has been fixed.
      • A missing check that the provided scene name to Iray_bridge_client_api_component::create_snapshot_context() indeed names an IScene element has been added. Before, this would succeed for any valid database element and the error would not be spotted until trying to import the .cb snapshot.
      • A bug has been fixed where additional video streams created when rendering in stereo would not be closed properly when switching back to mono. The streams remained open and hogged bandwidth that should be assigned to other streams.
    • Iray Photoreal
      • Potential crashes with motion blur and batch rendering when using auto instancing mode have been fixed. Bug #18214.
      • Crashes from wrong internal data versioning have been fixed. Bug #18146.
      • Accessing empty geometry instances/groups has been fixed. Bug #18116.
    • Iray Interactive
      • Global Illumination for planar light sources with single sided EDF (local EDF on the front side and no EDF on the back side) has been fixed and improved.
    • Material Definition Language (MDL)
      • Previously, cycles in material graphs led to a crash during rendering. Now such cycles are recognized during rendering and materials with such cycles will be ignored. Bug #18078.
      • The JIT compiled implementation of math::sign() has been fixed.
      • The module name is now being used instead of an empty filename when reporting an exception location in the JIT backend.
      • Built-in modules like ::base do not have a file name in current Iray versions. The module name is now reported in case an exception is fired there inside jitted code.
      • A crash when evaluating the MDL environment has been fixed. Bug #18057.
      • A rare crash has been fixed that occurred when an array constructor was used inside a uniform expression. Bug #18184.
      • Archive version information is now handled correctly. Bug #17930.
      • The handling of the color(float) converter when used inside the fixed function pipeline of Iray has been fixed. Bug #18206.
      • Zero sized arrays in MDL's spectral color constructor no longer cause a crash.
    Post edited by rbtwhiz on
  • rbtwhizrbtwhiz Posts: 1,992
    edited June 2017

    Iray 2016.3.1, build 278300.6408

    Added and Changed Features

    • General
      • Both .mi importer and .mi exporter now correctly handle multiple shader attributes attached to MDL material instances or MDL function calls.
      • The detection whether stderr is connected to a console on Windows has been fixed. This lead to missing log output when the default logger was used.
    • Iray Bridge
      • irt_cloud now supports the option "scheduler_mode" which can be set to "batch", "synchronous", or "interactive".

    Fixed Bugs

    • Iray Bridge
      • A bug has been fixed where passing a NULL progress callback to the render() method of Iray Bridge render contexts could cause a crash.
    • Iray Photoreal & Iray Interactive
      • An issue where JIT-compiled MDL expressions evalauted incorrectly in combination with base.mdl has been fixed.
    • Iray Photoreal
      • Potential crashes when using section planes featuring invalid normal vectors have been fixed.
      • Potential issues with invalid geometry and shading normals (resulting for example in NaNs in the auxiliary buffers/render elements) have been fixed.
      • Brightness differences between Linux and Windows versions in very specific corner cases of the sun & sky environment settings have been fixed.
      • Banding artifacts in fake shadows on matte objects are now avoided.
      • Wrong alpha values during internal RGB->RGBA texture conversion have been fixed.
      • Cases where the result of some light path expressions (LPEs) in combination with matte objects depended on other LPEs have been fixed.
      • Banding artifacts of matte objects shadows on curved geometry have been fixed.
      • Potential crashes with textured emission and light updates on Linux have been fixed.
      • A crash happening with two sided emitting materials has been fixed.
    • Iray Interactive
      • A bug causing a finite environment dome to occlude geometry located outside the dome has been fixed.
      • A bug has been fixed that caused screen-space image-based lighting to produce erroneous shadows when rendering using an orthographic camera.
      • A crash has been fixed that showed if a textured area light was rendered with Iray Interactive.
      • A crash when rendering stereo images using multiple hosts has been fixed.
    • Material Definition Language (MDL)
      • The comparison of semantic version numbers in the manifest of MDL archives has been fixed.
      • The MDL compiler now issues a warning for modules in MDL archives that import another module outside the archive without declaring that dependency in the MANIFEST.
    Post edited by rbtwhiz on
  • AndySAndyS Posts: 1,432

    Hi Folks,

    I hope it is allowed to post some critics over here ...

    The new 4.9.4.110 isn't an improvement. All old (now even over 1.5 ago reported) bug aren't solved still.

    • fatally wrong light transition into refractive media,
    • SubD for displacement of surfaces still auto-limited.

    These facts got reported to the devs and discussed over here in the forums including detailed and qualified analysis by me.

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    I now cannot get access to Content Library.

    I really need that to do anything!

     

    :(

     

  • DoctorJellybeanDoctorJellybean Posts: 6,826
    captainklutz_a2ec859073 said:

    I now cannot get access to Content Library.

    I really need that to do anything!

     

    :(

     

    Is PostgreSQL running when DS is active?

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    Not sure. It works OK when I run the 4.9.2 general release.

  • DoctorJellybeanDoctorJellybean Posts: 6,826

    Open DS Beta and check the specified paths in Content Directory Manager, make sure that they match the ones in your General Release.

  • Richard HaseltineRichard Haseltine Posts: 90,095
    AndyS said:

    Hi Folks,

    I hope it is allowed to post some critics over here ...

    The new 4.9.4.110 isn't an improvement. All old (now even over 1.5 ago reported) bug aren't solved still.

    • fatally wrong light transition into refractive media,
    • SubD for displacement of surfaces still auto-limited.

    These facts got reported to the devs and discussed over here in the forums including detailed and qualified analysis by me.

    Both of which are aspects of Iray, not soemthing daz has any direct power over.

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192
    DoctorJellybean said:

    Open DS Beta and check the specified paths in Content Directory Manager, make sure that they match the ones in your General Release.

    OK I'll check that out...Thanks. :)

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    It shows up the same, but is not available it the pane / tab drop down. :(

  • DoctorJellybeanDoctorJellybean Posts: 6,826

    Could you please attach a screenshot.

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    I'll try...

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

     

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    When I go to Windows Panes tabs Content Library is not listed in drop down.

  • AndySAndyS Posts: 1,432

    Hi Richard,

    Richard Haseltine said:
    AndyS said:

    Hi Folks,

    I hope it is allowed to post some critics over here ...

    The new 4.9.4.110 isn't an improvement. All old (now even over 1.5 ago reported) bug aren't solved still.

    • fatally wrong light transition into refractive media,
    • SubD for displacement of surfaces still auto-limited.

    These facts got reported to the devs and discussed over here in the forums including detailed and qualified analysis by me.

    Both of which are aspects of Iray, not soemthing daz has any direct power over.

    possibly,

    But why is such a really still not properly working software included as plugin without forcing nVidia to improve it?
    For a long time I worked as a software architect for big companies and believe me - we would never ever had this status accepted.

  • DoctorJellybeanDoctorJellybean Posts: 6,826
    captainklutz_a2ec859073 said:

    When I go to Windows Panes tabs Content Library is not listed in drop down.

    Did you by any chance install it while DS was running? Try uninstalling and reinstalling it.

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    Not that I am aware of. I'll try it though. Thanks for your help. :)

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    No, that didn't help. I wonder if anyone else is able to access the Content Library in this build? :/

  • barbultbarbult Posts: 20,938

    Did you update and merge menus as recommended in the first post? (Updated default menus; recommend running the “Update and Merge Menus” script)

  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    Hmmm... Can't pick up on the reference to that...Can't see a merge menu script?

    It is the first time I have seen this behaviour & I have been successfully installing & using 4.8 through 4.92 both in beta & general release.

    :/

  • Richard HaseltineRichard Haseltine Posts: 90,095

    If you look in Help>About Installed Plug-ins what is the status of the Content Library Pane?

  • barbultbarbult Posts: 20,938
    captainklutz_a2ec859073 said:

    Hmmm... Can't pick up on the reference to that...Can't see a merge menu script?

    It is the first time I have seen this behaviour & I have been successfully installing & using 4.8 through 4.92 both in beta & general release.

    :/

    Since you can't see the Content Library, maybe you can find the script in the Smart Content pane under Scripts/Utilities/Workspace.

     

    Update and Merge Menus.JPG
    528 x 982 - 69K
  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    @ Richard.

    Content Library is not showing as a Plug In for this beta installation. It was working fine on the 492 & 493 Betas & General Issues.

    @ Barbult

    Thanks for your efforts but I have never used Smart Content as I have always ran a custom manual installs & when I look at it, it only shows a log in page.

  • AalaAala Posts: 140

    A slight annoying thing, but CTRL+S acts like a 'Save As' command instead of just Save. Also DAZ doesn't remember the last folder I accessed when I opened a scene, which might be related to the 'Save As' bug.

  • DoctorJellybeanDoctorJellybean Posts: 6,826
    edited May 2017
    captainklutz_a2ec859073 said:

    @ Richard.

    Content Library is not showing as a Plug In for this beta installation. It was working fine on the 492 & 493 Betas & General Issues.

    Depending on your OS version, look and see if dzcontentlibrarypane.dll exists in the plugins directory of the Public Build installation

    x64 : C:\Program Files\DAZ 3D
    x32 : C:\Program Files (x86)\DAZ 3D

    Post edited by DoctorJellybean on
  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    Yes, that file is present. :/

  • barbultbarbult Posts: 20,938
    edited May 2017

    Have you tried just selecting a different Workspace Layout to see if the Content Library is visible there?

    Post edited by barbult on
  • captainklutz_a2ec859073captainklutz_a2ec859073 Posts: 192

    Yes, I had tried that ealier.

    Content Library does not appear on any layout.

  • Cris PalominoCris Palomino Posts: 10,460
    Aala said:

    A slight annoying thing, but CTRL+S acts like a 'Save As' command instead of just Save. Also DAZ doesn't remember the last folder I accessed when I opened a scene, which might be related to the 'Save As' bug.

    Enter authorship information in preferences...

Sign In or Register to comment.