DAZ Studio Pro BETA [Release Candidate] - version 4.7.0.11! [UPDATED]

DAZ 3D is pleased to announce the next public version of the DAZ Studio Pro BETA - version 4.7.0.11! [UPDATED]

What is a Release Candidate?

A Release Candidate is a BETA version that has the potential to replace the current General Release, unless significant "show-stopper" caliber bugs emerge. A Release Candidate suggests that a General Release is relatively close.

What is a BETA?

Despite our best efforts, DAZ 3D cannot possibly test the software under all possible conditions. So, we are providing a version of the application to the general public in order to uncover problems that were not discovered during internal/private testing. We expect that there will still be problems and we hope that when users encounter any problems, they will report them to the Bug Tracker so that they can be validated, prioritized and fixed.

As with any software classified as being in the BETA phase of development, you should expect to encounter bugs. Any bugs you do encounter while using BETA software can vary in terms of severity, from minor features that do not work correctly to problems that cause your computer to crash. Before choosing to use BETA software for production purposes, you should decide whether the benefit of new features and bug fixes provided by the BETA version outweighs the risk of instability you may encounter.

Public Build, BETA, what is the difference?

Public Build is a release channel, while BETA is a phase of development.

DAZ Studio is distributed through four separate channels:

- Production Build - This is where the General Release build is distributed and is open to the general public.

- Public Build - This is where the builds that are not considered stable yet are provided for testing by the general public; this channel typically provides a build that is in the BETA phase of development, but technically can provide a build in the ALPHA phase.

- Private Build - This is similar to the Public Build channel, except it is limited to a select group of individuals that serve as the "front line" or the "canary in a coal mine" for a time before the build is promoted to a less restricted channel; this channel is more likely to see an ALPHA build than the Public Build channel is.

- Dev Build - This is for a much smaller group of individuals; this channel provides "bleeding edge" ALPHA builds; sometimes referred to as "nightly", although the builds are not limited to one per night nor to strictly occurring at night.

Will this Public Build replace the General Release?

While builds in the Public Build channel do eventually replace the build in the Production Build channel, the existence of a public build does not preclude builds that are currently in the Private Build channel from replacing the General Release before one in the Public Build channel does. One of the reasons we provide a Public Build channel is to gain broader coverage of the various fixes/additions. Sometimes fixes/additions in the Public Build channel are validated more quickly than others and can be integrated into the Production Build channel while the remaining, more risky, changes are allowed to "bake" a while longer.

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

The 4.7.0.11 version resolves many issues and implements many improvements since the 4.6.3.52 General Release. More detail on specific fixes/changes/improvements can be found in the Change Log, which can be viewed online within the Documentation Center portion of our site. All new downloads of the DAZ Studio Pro BETA product (SKU: 12000) will be of this version.

Public BETA - Release Candidate highlights are:
1) Environment Pane - Moved setting of the Backdrop for the scene to a new pane that is poised for future environment related settings. Note: The color of the Backdrop for a scene is now separate from the background color of a viewport; viewport colors can be set in "Window > Style > Customize Colors..."
2) Center Dock Area - The area previously reserved for the viewport(s) is now its own dockable area, which can be used to stack panes that consume more space; i.e. Viewport, Render Library, Shader Mixer, Shader Builder, Script IDE, etc.
3) Viewport Pane - The viewport(s) that previously consumed the remaining space between the left, right, top and bottom dock areas is now its own pane
4) Aux Viewport Pane - A separate, singular, auxiliary viewport in its own pane that can be used as a convenient, independently sized, alternate view of the scene with IPR capabilities (for renderers that provide it)
5) Interactive Progressive Rendering (IPR) - Interactively and progressively preview the final render of your scene as you work on it. IPR allows for realtime camera, light and material modifications.
6) Keyboard Scene Navigation - Navigate your scene the way you would a video game. Using the W, A, S, D, Q, and E keys, you can now navigate left, forward, right, backward, up, and down (in order). You can also look around by using I, J, K, L, U, O, and P (for leveling).
7) Scene Navigator Tool - Video game style 'mouse look' control by clicking and dragging in the viewport to orient the active view/camera/light.
8) Back to Base - Selecting the "Currently Used" filter in parameter based panes now displays properties with a value that differs from the base figure value, instead of the properties that are different than their memorized values. For example, loading the Victoria 6 Character Preset will now show the Victoria 6 shape(s) as "Currently Used" because the morph property has a value that is different than the Genesis 2 Female base. In addition, properties that are driven to a value by another property can now be adjusted to override the driven value.
9) Truly Transparent Backgrounds - When no backdrop or background color is used (optional in the Environment Pane) transparency is shown as a checkerboard pattern, similar to other graphics applications. Also, the issue where anti-aliasing against the background color of a viewport generated a 'halo' of that background color has been fixed.
10) Camera Local Dimension Override - The ability to override the global render dimensions/aspect ratio with camera specific settings has been added.
11) Render Settings Pane - Completely revamped this pane to be consistent with other parameter based panes. Adjustments to render settings are now undo-able as a result.
12) Script IDE Pane - Improvements have been made to areas like syntax highlighting, auto-indent, context menus, find/replace and the debugger. Features have been added; code folding, line numbering, bracket matching and word marking (among others). Configuration preferences have been extended.
13) Extended Texture Format Support - Added support for using .EXR, .HDR, .PSD, and various others directly as textures.
14) Photoshop CC 3D Bridge Support - Added support for Photoshop CC to the 3D Bridge
15) Render Engine Update - Updated the 3Delight render engine to 11.0.105; see change log.
16) City Limits Layout - Updated this layout to incorporate the additions/changes mentioned above (and in the change log).
17) City Limits Lite Layout - Added a new default layout; a slightly modified subset of the City Limits layout
18) Darkside Style Default - The Darkside style has been set as the default for all new installations of DAZ Studio.
19) Scene Builder Redesign - Now uses a 'wizard' style workflow, based on metadata (categories, compatibility), that you can easily extend directly within the user interface (full functionality is dependent on the update to the Starter Essentials and Default Lights and Shaders packages).

Has the Content Management Service (CMS) been improved?
If you are already using the PostgreSQL based service, no.

If you are still using the Valentina based service, yes it has. The existing Valentina based service is still included and supported, however a new PostgreSQL based service is proving itself to be much more stable and much less prone to the data corruption issues that many have experienced in the past. The new PostgreSQL based service has also proven to be somewhat faster.

With this new solution, there is no longer a need to start a service that runs in the background. Normally, the PostgreSQL server starts when the application starts and stops when the application stops; unless another application, like Install Manager, is connected to it - in which case it will stop when the last application connected to it closes. Explicit control to start the service is provided via an action [in the Content Library pane option menu] and a button [in the Smart Content pane] without ever needing to leave the application. Explicit control to stop the service is also provided via an action [in the Content Library pane option menu].

To help get you up and running with the new PostgreSQL service, we've added a separate package in Install Manager that will automatically migrate any existing data from your Valentina database; you simply install it after the PostgreSQL server is installed. We've also included an "Import Metadata from Valentina" script with the Built-In content. The amount of time required to migrate the data will vary depending on the amount of data you have and your system specs.

*Note: While the PostgreSQL server is installed, Install Manager will not install any data to the Valentina database.

What is the Application Improvement Program about?
It's about improving the DAZ Studio user experience. Support tickets and bug reports provide important clues as to the needs of you the customer, but they are only hints. This improvement program will allow us to to "see" how the features of DAZ Studio are actually performing and where users are getting hung up.

If you choose to participate in the program, the statistics we will collect are anonymous and contain no personally identifiable information. We respect your right to privacy. That said, if you choose not to participate, we respect that too.

We encourage you to participate. In doing so, your use of the application will have a greater influence on where we focus our efforts.

Has the Genesis Starter Essentials, the Genesis 2 Starter Essentials (Male/Female), or the Default Lights and Shaders packages been updated too?

Yes, the "Genesis Starter Essentials", "Genesis 2 Starter Essentials" and "Default Lights and Shaders" packages have all been updated.

*Note: Install Manager users are notified of product updates when they occur.

How do I get the latest version?

If you have previously added the DAZ Studio Pro BETA product to your account, launch Install Manager, log into your account and type "DAZ Studio * Public Build" into the filter field to filter out anything else. Then simply download and install as you would normally.

*Note: The current version of Install Manager has a new Public Build download filter that is disabled by default. You must enable this download filter to see packages in your Ready to Download list that are tagged PublicBuild.

Optionally, you can locate, download and install the BETA from the Product Library [once you are logged into your account] by entering "DAZ Studio Pro BETA" into the text field near the top left of the page and clicking the "Filter" button, or by clicking here. Then, simply click the "download & install" button.

If this is your first time downloading DAZ Studio Pro BETA, simply follow this link, click the "Add to Cart" button on the page and then follow the checkout process.

*Note: This BETA version is not available as a standalone installer. It must be downloaded and installed using Install Manager. This does not impact the General Release, which will be made available through Install Manager as well as a standalone installer.

Can I have the General Release and the BETA installed at the same time?

Yes! You can have both the General Release and a Public Build (as well as a Private Build, for those involved in that endeavor), of the same major version, installed at the same time. Please be aware that the settings for each of the builds are stored independent of each other. This includes mapped content directories, layout, style and style colors, among many others.

What about the plugins I have?

The DAZ Studio 4.5 SDK has not changed in any way that causes it to be binary incompatible, which means that any plugins created for a previous version of DAZ Studio (4.5.0.114+) should continue to load and function with this build. That said, as with any new release, there is always the possibility that a plugin has had bugs fixed or features added, so the latest versions should be downloaded and installed if they are provided.

Plugins that are currently built/produced by DAZ 3D will provide a separate package specifically intended for the Public Build. 3rd party plugins that DAZ 3D creates install packages for will be updated to allow simultaneous installation into the General Release and the Public/Private builds. These packages will display as "Product Updates" within Install Manager once they have been updated.

Is there any documentation?

Yes. Check out the User Guide and QuickStart Guide that we've posted in the DAZ Studio 4.x Documentation section.