Daz Studio Pro BETA - version 4.9.3.166! Release Candidate 5 (*UPDATED*)
Daz Software
Posts: 35
Daz 3D is pleased to announce Daz Studio Pro BETA - version 4.9.3.166 Release Candidate 5! (*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.3.166 - Release Candidate 5 (December 23, 2016) *UPDATED*
- NVIDIA Iray
- Worked around a resource pathing issue that caused the Interactive Render Mode to go missing on OS X
- Renamed the "Cloud [BETA]" sub-page, on the Advanced page of the Render Settings pane, to "Bridge [BETA]"
- Added "batch" mode (or "queueing") support for network rendering via Iray Server and/or VCA, for still images; animations are not currently supported
- Made several changes/tweaks to the "Bridge [BETA]" sub-page to support "queueing" and to clarify which settings pertain to "streaming"
- Daz Connect
- Fixed an issue with timing out before long running downloads could complete
- Added a time out for persistently slow download speeds; below 128 bytes per second
- Fixed an issue with saving (e.g., Scenes, etc.) and assets installed via Daz Connect that could cause too many dependencies to be recorded in the save file(s). This manifested itself by the loading of the saved file(s) indicating that more products are required than are actually necessary; e.g., products that provide morphs and/or UV sets that were installed at the time of save, but are not actively used.
- OpenGL
- Renders performed using the OpenGL option(s) now behave similarly to the other renderers in that they include a transparent background; saved scenes that render using one of the OpenGL options and relied on the viewport color as a background color will need to be updated by the user to include a backdrop consisting of the desired color.
- Fixed bugs and/or made improvements in various areas; see the Change Log for details
4.9.3.153 - Release Candidate 4 (December 9, 2016)
- NVIDIA Iray
- Integrated Iray 2016.3 Release build; improves support for Pascal generation (10-series) GPUs (see this post for more information)
- Addresses reported issues with OS X CUDA Compute Capability version
- Addresses reported issues with ILLEGAL_INSTRUCTION on AMD CPUs that do not support SSSE3 instructions (e.g., Phenom II, etc.)
- Integrated Iray 2016.3 Release build; improves support for Pascal generation (10-series) GPUs (see this post for more information)
- Interface
- Made adjustments to the styling of the Darkside style
- Scripting
- Several APIs have been extended
- Fixed bugs and/or made improvements in various areas; see the Change Log for details
4.9.3.128 - Release Candidate 3 (November 4, 2016)
- NVIDIA Iray
- Integrated Iray 2016.3 beta build; improves support for Pascal generation (10-series) GPUs; requires CUDA 8.0 (see this post for more information)
- Does NOT currently address reported issues with OS X CUDA Compute Capability <= 5.2
- Does NOT currently address reported issues with ILLEGAL_INSTRUCTION in libneuray.dll on AMD CPUs that do not support SSSE3 instructions (e.g., Phenom II, etc.)
- Added basic support for accessing lens and aperture settings; added a “Lens” property group to cameras when Iray is the active renderer; properties include Lens Radial Bias, Lens Shift X (mm), Lens Shift Y (mm), Lens Stereo Offset (mm), Lens Distortion Type (spherical, cylindrical, stereo, etc), Lens Distortion K1/2/3, Lens Distortion Scale, Aperture Blades, Aperture Blade Rotation
- Integrated Iray 2016.3 beta build; improves support for Pascal generation (10-series) GPUs; requires CUDA 8.0 (see this post for more information)
- Render Settings
- Fixed an issue where changing the General > Dimensions > Dimension Preset (Global) property would not result in a corresponding size/aspect image when rendered; renders would always be the size/aspect of the Active Viewport, despite all other visual indicators suggesting otherwise
- Scripting
- Numerous APIs have been extended
- Fixed bugs and/or made improvements in various areas; see the Change Log for details
4.9.3.117 - Release Candidate 2 (October 25, 2016)
- NVIDIA Iray
- Integrated Iray 2016.2 Release build; adds support for Pascal generation (10-Series) GPUs; requires CUDA 8.0 (see this post for more information)
- Exposed Iray 2016.2 "Spectral Rendering" render settings; "Spectral Rendering Enable", "Spectral Conversion Intent", and "Spectral Observer"
- Added UV clipping to Decal nodes; adds a "Clip Mode" property to the "Decal > General" group; selecting a value dynamically shows/hides additional properties
- Scripted 3Delight
- The Outline render script respects the colors set by the user again
- Content Database
- Various usability adjustments have been made to the Categorize dialog
- "Search Drives(s) for Files" no longer considers content downloaded and installed to the mapped Daz Connect Data directory
- Daz Connect
- Automatic Login will now fail after 3 attempts @ 20 sec intervals; this protects against blocking the application from launching when/if there are issues with web services and automatic login is enabled
- ERC Freeze
- Added an "Object" column to the property view; used in identifying when properties are cross-object
- The header of the property view columns can now be clicked to change sort order
- Shader Mixer
- The "Connector Color..." action has been made available from the context menu for connected inputs of a brick; allows the color to be changed from either side of the connection
- Shader Builder
- The "New Shader..." action in the Catalog is functioning properly again
- Made UI tweaks toward consistency with Shader Mixer and ultimately toward fixing the minimum size center dock issue of both panes
- Morph Loader Pro
- The geometry scale and axis conversion options are properly displayed again
- Map Transfer
- Added a "Convert By Matching Properties" option; on by default; causes conversion to occur by property instead of by map
- Removed a power of 2 requirement from transfered results
- Scripting
- Numerous APIs have been extended
- Fixed bugs and/or made improvements in various areas; see the Change Log for details
4.9.3.71 - Release Candidate 1 (August 18, 2016)
- NVIDIA Iray
- Transmitted color map in the Iray Uber Material is now ignored due to a limitation described in the Iray programmers guide; "The material's volume coefficients are varying in MDL, however, Iray Photoreal only supports uniform coefficients"
- Daz Connect
- Fixed a category syncing issue (updating metadata)
- Selecting the "Browse…" option in Edit > Preferences… > CMS Settings : Cluster Directory will now use the currently selected directory path as the initial folder when browsing for a new Cluster Directory path
- Asset Finding
- The "Scan Known Directories for Files" dialog has been reworked
- Asset Loading
- HDRI files are now being found when searching for missing files
- Viewport
- Improved bounding box framing
- Improved node selectablity in some viewport tools
- Camera, DrawStyle and Background Color are now being reset correctly when performing a hardware render
- Duplication
- Animation data is no longer being lost when an object is duplicated
- FBX Importer
- Now handles n-gons (polygons with greater than 4 sides)
- PZ3 Importer
- The last settings used for the OBJ exporter no longer have an impact on the result of the PZ3 importer
- Logging
- Timestamps in the log now indicate the correct month
- Scripting
- Numerous APIs have been extended
- Fixed bugs and/or made improvements in various areas; see the Change Log for details
4.9.3.56 (August 2, 2016)
- NVIDIA Iray
- Updated to 2016.1.2 (see this post for more information)
- Daz Connect
- Added support for automatic login; requires valid cached (encrypted) account credentials; if account credentials change, automatic login will silently fail and user must explicitly invoke login with updated credentials
- Added an option to "Automatically Login" to the Account Login dialog and the Smart Content Store page
- Added an "Automatically Login With Remembered Credentials" option to Preferences
- Content Database
- Fixed an issue that could cause a failure to upgrade the CMS database
- Properly handle vendor/user categorization when unifying categories
- Fixed a "Lost and Found" category sync issue
- The port number defined in the postgresql.conf file, found within the database cluster path, is now read (if any) on launch of the application and validated against the port number read (if any) from the application data cmscfg.json file; if the port numbers in these two files do not match, the cmscfg.json file is updated to reflect the port number read from postgresql.conf file.
- Fixed an issue in where the application data cmscfg.json would not be created if both the cluster directory and the port were changed by the user within Preferences; when the user changes the database cluster path, the port number, or both, the application data cmscfg.json file and the postgresql.conf file are now updated as appropriate; when the user changes the port number the application may need to be closed and restarted for a connection using the port number to be established.
- Smart Content pane
- Product views now use their own search thread
- Content Library pane
- Added the “Create a Product from…” action to the context menu for Search and Category containers
- Added the “Create a Product from…” action to the context menu for Asset(s)
- Surfaces pane
- Extended search types to include language specific preset/materials, preset/materials/hierarchical, and preset/shader content types (i.e., MDL, RSL, OSL, LXM, MC6, MT5)
- Transfer Utility
- Work on projection algorithms to improve results
- Added a "Closest Vertex First" option; uses Bounding Volume Hierarchy (BVH) and closest facet first when unchecked, uses Octree and closest vertex first when checked; default is unchecked, previous behavior is checked
- Made improvements to UV Space projection
- AutoFit
- Made general improvements
- Added support for pose data in clones
- ERC connections are now temporarily disconnected to avoid issues relating to pose baking
- OBJ Importer
- Refactored individual options so that they are more consistent with the OBJ Exporter individual options (in both look and feel)
- Geometry Based Tools
- Added actions to context menus that allow a user to select/deselect by geometry islands; context menu > Geometry Selection > (De)Select By > (De)Select Geometry Islands…
- Map Transfer
- Changed to render by material instead of by template
- Hexagon Bridge
- Refactored the options dialogs
- Bryce Bridge
- Now writes its messages to the log
- Fixed bugs and/or made improvements in various areas; see the Change Log for details
4.9.3.37 (July 5, 2016)
- Database Driven Content Views
- Fixed #DS-1286/#CS-221671 : Failure to Upgrade CMS database; this was the root cause of some users suddenly not seeing categories unless the "Show Hidden Vendor Categorizations" preference was enabled
- Categorizing an asset assigned to a "Lost and Found" product sub-category now automatically causes the "Lost and Found" categorization of that asset to be removed
- Categorizing the last asset assigned to a "Lost and Found" product sub-category now causes the "Lost and Found" product sub-category to be removed
- Updating metadata via Daz Connect now removes an asset from a "Lost and Found" product sub-category if that asset has been assigned to a proper category that is outside the “Lost and Found” category; if an asset's categorizations are removed and the asset has not been categorized by the user, the asset is assigned to a "Lost and Found" sub-category named after the product that provides the asset
- FBX Importer
- Improved support for pipeline automation via script
- Draw Settings
- Made various (minor) tweaks to labeling of properties and/or enumerated values
- Ongoing updates to documentation; remaining pages are actively being reviewed/edited
- Preferences
- Fixed a crash when launching the Preferences dialog if a bridge plugin that a preference referenced was not installed; e.g., GoZ
- Fixed bugs and/or made improvements in various areas; see the Change Log for details
4.9.3.25 (June 21, 2016)
- Database Driven Content Views
- Renamed the "All" filter in database driven asset/product views to "All Files" and "All Products" as appropriate; i.e., the Files and Products pages of the Smart Content pane, the Targets, Add-Ons and Product views of the Smart Content pane, the Presets pages (and their respective embedded Targets and Add-Ons views) on various property based panes
- Added support for a user persistently hiding vendor-defined categorization of assets; when a user removes an asset from a category that a vendor has assigned the asset to, the vendor-defined categorization is not actually removed, rather the categorization is marked as hidden and thus does not contribute to the category tree in the database driven asset/product views unless the "Show Hidden Vendor Categorizations" preference is enabled or the vendor-defined categorization is changed by an explicit update
- Note: The state of the new preference has no bearing on the categories or categorizations displayed in the Content Library pane, the Categorize dialog if launched from the context menu of an asset in the Content Library pane, or the Content DB Editor. These particular views are provided for managing content and as such display all categories and categorizations that exist in the database.
- Migrated assets (i.e., assets installed via Install Manager or assets created in pre-4.9 versions) are now assigned to a "Lost and Found" product sub-category if the asset has no categorization
- Removing the last user-defined categorization of an asset now causes that asset to either revert to a "Lost and Found" product sub-category (for assets that are not formalized as part of a product with proper metadata) or the vendor-defined categorization (for assets that are formally defined by a product that provides proper metadata)
- Replaced the "Remove From All Categories" checkbox in the Categorize dialog with a button bearing the same name and modified the behavior accordingly; with the checkbox a user had to check the option, accept the dialog and then relaunch the dialog in order to clear all current categorizations and start from scratch; with the button the user need only click it once to uncheck all current categories and then immediately begin categorizing without being forced to accept and relaunch the dialog
- Viewport Tools
- Added "Secondary Nodes" options to the Universal, Rotate, Translate and Scale view tools; when enabled, these options provide the ability to manipulate multiple selected nodes in the same manner as the primary (most-recent) selected node, using the manipulator displayed in the viewport for the primary selected node
- FBX Exporter
- Fixed FBX export of non-transform property animation curves
- Added support for distributing auto-follow base figure animation curves to fitted figures (i.e., clothing, hair, etc)
- Fixed a potential crash in the handling of specialized PBR materials
- Improved support for pipeline automation via script
- Transfer Utility
- Added an option for UV space projection
- Preferences
- Renamed the "Content Library" page to "Content"; the majority of options on the page are not specific to a particular pane
- Added a "Show Hidden Vendor Categorizations" option to the Content page; when checked, vendor categorizations that the user has hidden become visible again in database driven asset/product views
- Addressed crashes caused by security policy differences resulting from changing hosting providers when the Participate in Daz Studio Improvement Program preference is enabled
- Added a Bridges page; extracted bridge preferences from the Interface page
- Added an option for explicitly setting the Bryce executable location for the Bryce bridge
- Added an option for explicitly setting the Hexagon executable location for the Hexagon bridge
- Fixed bugs in various areas; see the Change Log for details
Note: Switching between builds provided via the General Release channel that are older than 4.9.1.30 and builds provided via the Public Build channel (and the Private Build channel for those involved in that endeavor) will cause a "Configuration Changed" message to display.
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.2.70
- 4.9.2.67 (RC)
- 4.9.2.60
- 4.9.2.55
- 4.9.2.44
Post edited by rbtwhiz on
Comments
What is new in this build? Do I need to update my copy?
Daz Studio 4.9.3.x resolves several issues and implements several improvements since the 4.9.2.70 General Release. The first post contains hightlights 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.
While this release does address several issues and implement several new features relating to the preservation/restoration/creation of User Data, it does not address all of the issues that we are aware of. We have identified and are actively working toward resolving some remaining issues that pertain to cleaning up the "Lost and Found" category when assets receive proper categorization, scanning for files in mapped content directories and creating assets for the found files and assigning those assets to the New group.
Is there any documentation?
Yes, there is. And we're actively working on more.
Check out the User Guide and QuickStart Guide that we've posted in the DAZ Studio 4.x Documentation section.
The Reference Guide is also in the process of being populated/updated.
Some of the areas we have been focusing on (and will be recieving updates first) are:
*Note: Some pages are still being built. If you see "permission denied" for a page, that page is not live yet.
For those of you that want to copy the Custom Actions, Actions, Menus, Toolbars, and Layout of the last session for a build in one channel (i.e., General Release) to a build in another channel (i.e., Public Build) or vice versa... I recently posted a new script sample (i.e., Copy UI from Channel) that does it for you. Simply run the script in the build you want to copy the actions/menus/layout to, select the build you want to copy from in the dialog that pops up, and click Accept.
For those of you that want to replace the mapped directories of a build in one channel (i.e., General Release) with the mapped directories for a build in another channel (i.e., Public Build), I have a script sample (i.e., Save Mapped Paths) that does that for you too. Run the script in the build that has the content directory mappings that you want in the other build. The script produces a second script with all of your content directory mappings that can then be run in another build to set it up with the same mappings.
I also have script samples posted that:
I point these out because I often see users ask how to do this manually, and/or become confused by the fact that the builds released through the various channels use independent settings. I then see others try to explain what to do in ways that are either harder or more technical than they need to be, or place the a user at risk of causing damage to sensitive areas of their computer.
I'm not quite sure I care for how this all on or all off Category view works. Need to look at it some more, but boy was I surprised to have Zero categories when I first opened up.
How do I get the Category View back on the Smart Content tab? Can't find a toggle switch anywhere...
I have a repeatable hard crash of DS 4.9.3.25 in the following scenario:
1) In the Smart Content pane, select Files tab, All Files category, sort by Last Update: Recent First, uncheck Filter by Context
2) In the Content Library pane, select a product (A Bit Boho).
3) In the Content Library pane, right click on one of the assets in the selected product (01_Stockings.duf) and select Show Asset in>Smart Content>Files. I get the error message "The chosen products could not be found with the current file options." The error message is not very specific, but I think this is because the Smart Content pane is not showing all my content files. At the top it says 1-1132+. When sorted by Last Update:Recent First, I don't think the selected file is included in the list.
4) Click OK to close the error message.
5) In the Content Library pane, click on the context menu and select Edit Preferences...
Daz Studio 4.9.3.25 crashed immediately with "Daz Studio has encountered a fatal error, and must close."
I submited Request #221543 with the crash log. I don't know whether this problem occurred in the previous beta or not. I just stumbled upon it today after updating.
What are you refering to when you say "this all on or all off Category view"? Quantify what "this" is in reference to. If you are referring to an actual Category View (hard to know for sure without a little more context), which are all populated by the CMS/database, then what you may be experiencing is a known issue that has to do with the timing of closing one application that connects to the CMS and quickly opening another.
Because Install Manager and Daz Studio (and Carrara) start PostgreSQL (if it is not already running) when they launch and stop PostgreSQL when they close (if it isn't still in use by another application), there exists a scenario where PostgreSQL is busy shutting down as a result of a command from one application and therefore cannot react to the launch of another. This is a byproduct of stepping away from a service that is always running in the background like we had with Valentina, which there were many complaints about, in favor of something that starts and stops with the application(s) (as requested).
If that is in fact what you're referring to, the way to avoid it is to launch the second application (e.g., Daz Studio) before closing the first (e.g., Install Manager).
-Rob
Knowing more about what you were doing, or what else was happening, at the time the Category View disappeared would help us pinpoint why it happened and where to look for a potential bug to fix.
To trigger events that evaluate whether or not the Category View should be displayed (it gets hidden/shown in order to facilitate the embedded Targets, Add-Ons, and Product Contents views, as well as the Basic view mode which is for an entirely different layout/workflow being investigated/developed), in the Option Menu for the pane switch to the Basic View and then back to the Standard View.
-Rob
Sorry, Rob. I was referring to the Hidden Vendor Categories. I do not yet have a full grasp of how this works. When I first launched the beta my Smart Content Files and Products views had zero categories, just: All Files and All Products. I had to go turn off the option to hide the Vendor Categories to get to see any categories at all. Hence my reference to "all on or all off". It does not seem a beneficial feature. But perhaps I still don't quite understand what the purpose/intended function of this is.
I am unable to duplicate the exact behavior on a different machine.
I just loaded the beta on my tablet. I can not duplicate the exact elements I saw: no categories, but definetly products (I could see them all unsorted). If I turn the CMS off, I see no categories and no products... which is not what I saw. I had to toggle the Vendor Categories in Prefernces to see any Categories. I will follow up when I get home and see how it is acting on that machine,.
The preference is labeled "Show Hidden Vendor Categorizations." The purpose of this option is to control whether or not categorizations of an asset that are assigned by the vendor, and which you decide do not fit in your workflow so you re-categorize to your liking (thereby "removing" [hiding] the default categorizations), are shown where the vendor categorized them in addition to wherever you may have categorized them. Its basically a way to preserve default categorizations (useful for customer support scenarios, and/or temporary reference for customization) while also allowing you to [re]categorize however you want without forcing you to always see the defaults, but having a way to see them if/when you want/need to.
-Rob
Which is how I understood it. But it did not seem to be working that way in my initial look at it. My intial look may have been a one-time abberation that confused me in how it was supposed to function.
Thanks for replying Rob. I had just installed the Beta update and re-lauched the beta and it looked like the attached pic. evilded777 had posted that "Show hidden Vendor Categories" in preferences was not checked. I enabled that option and the categories came came back. (Thanks evilded777 !) I'll be watching intently to this thread for further info.
One pet peeve is having DS files, typically materials included with Poser pz2 and sometimes mc6 materials (not speaking of pz2 mats with ds scripts). I end up removing all metadata and categorizing these "pure" Poser materials to the Lost and Found category. Is there a way to hide them from view?
Edit: Re the last paragraph, I'm a DAZ Connect to install content when available.
It sounds like maybe Lindsey and I experienced the same thing. Maybe.
Anyway., Is Lost and Found considered one of these hidable categories?
"Lost and Found" is evolving into a catch-all category (similar, in some ways, to the "Uncategorized" category of versions past), where assets are either assigned to a proper category or they end up in "Lost and Found", under a sub-category bearing the name of the "product" that provides the asset, that is itself owned by the user as well as the link between the asset and the category.
In 4.9.1 the "Lost and Found" category, and any sub-category that got installed or imported, was vendor-owned... as was the link between the asset and the category; a user did not own either record, so a user (that was not acting like a vendor) could not modify it.
In 4.9.2 that changed (in favor of the user) so that the sub-categories of "Lost and Found", as well as the link between the asset and the category, were created by processes in the vendor pipeline but explicitly created as user-owned records; so that a user (without acting like a vendor) could remove it. But that data still had the potential to come back when metadata updates were posted/retrieved and it created a situation where the possibility also became a responsibility (i.e., because you could, you had to). This is why even products that recieved updates that would otherwise remove assets from "Lost and Found" still showed the assets in "Lost and Found;" we make every attempt to preserve user-owned data.
In 4.9.3 it has changed [is changing] (in favor of the user) again, such that an asset is assigned to a "Lost and Found" sub-category only if it is not categorized elsewhere; this is one case where we will clean up "user-owned" data that we created for the user. Where this is different from "hiding" vendor categorizations is the categorization within sub-categories of "Lost and Found" are actually removed from the database (as are the sub-categories themselves if they are empty) and they are not recreated unless all user-owned categorizations for an asset are removed and the asset has no proper vendor categorizations to fall back on.
Hopefully I've explained that in a way that you can follow...
---
With regard to the empty Category View, I'm putting together a script that you'll be able to run to snapshot some raw data from the database for me (instead of messing with packaging up and sending the entire database so I can see inside); this will let me see if something went wrong with the schema/database change/update.
-Rob
Not yet... but its on the list. We know its needed.
-Rob
The issue in beta 4.9.2.44 (if I recall correctly) where making changes to a file's category isn't applying has come back for me in this beta 4.9.3.25. I also can't assign a category to a file that doesn't have any. I filed ticket 221579 reporting this.
Edit 6-24-2014: I now believe this issue is related to the failure to upgrade the CMS database when launching 4.9.3.25 as the database columns aren't what 4.9.3.25 is expecting.
Yeah... that flag for Hidden Vendor Category is working different for me on my production machine and on my tablet.
On my PC I have to have it turned on to see any categories.
@Lindsey, @evilded777
Attached is a script (category_content_info.dse). Running this script should extract some raw data about a particular table in the database and prompt you to save a JSON file named category_content_info.json. The data collected contains nothing that personally identifies you, rather it contains information about how a particular table in the database is currently setup on your machine(s). If you could run the script under the build that isn't displaying categories unless the option is checked and respond with the results (attach the category_content_info.json file) it would help in trying to track down why you are seeing what you are.
-Rob
Here you go, Rob.
I'm currently not able to access preferences in this build. I get a crash when attempting to launch Preferences with error report:
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\QtCore4.dll" at 0033:0000000064C14DC0, QObject::parent()
I don't have this problem with the general release.
Need some help, please! I don't know what happened, but I can't see all the categories from the Smart Content. All I see is "All Files" and when I click on it, only a few of the products appear on the rigth side. I recently updated from the previous version to 4.9.3.25.
(Please delete, I went back to read the comments again on this page, and by placing a check mark on "Show Hidden Vendor Categorizations" showed the content
rbtwhiz: Here's my script output from Beta 4.9.3.25
I also get a the same type crash when attempting to launch Preferences .in this beta.
I also sometimes get that crash, but only on my tablet where I do not have the database problem.
@Lindsey, @evilded777
It looks like the DB update failed for both of you, and as a result neither of you have the column in the table that holds the value used to determine whether or not a particular categorization is hidden (which is being interpreted as "yes, hide it"). There should be an error in the log and/or cloudLog that indicates what caused the update to fail.
-Rob
So I should go look for that error? And report it?
The transfer utility doesn't work in this version it deform my cloth into an unknown pose
In general release this doesn't happen