Fixed issues with messaging on failed connections to be more accurate (some occurances incorrectly stated that the username or password were incorrect)

Fixed the “Update Metadata” action in context menus for products so that it now forces an update to the metadata cache rather than refreshing from the local cache

Fixed the LOCAL USER product image (./resources/images/local-user-product.png was missing)

Fixed an issue that could cause multiple unending connection attempts (prevented the application from successfully closing)

Fixed an issue where account credentials were not being converted before being handed to Daz Connect (caused login to fail when non-ASCII characters were used)

Fixed migration triggers for products where the StoreId is not “DAZ 3D” and/or where the ProductToken is empty

*Note:A "Configuration Changed" message is expected to display for all users that have logged into Daz Connect upon launching this build; until said user has logged into Daz Connect a minimum of one more time; the system configuration detection algorithm changed to resolve differences as noted above, so everyone is impacted. Note that switching between builds provided by the General Release channel and the Public Build channel (and the Private Build channel for those involved in that endeavor) will cause this message to display; until such time that the builds offered through all channels are using the same algorithm.

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.

General Release Thread:

Previous 4.9 Beta Threads:

Comments

If you had an issue where migration from Daz Studio 4.8 to Daz Studio 4.9 did not migrate your custom categories, or custom data please file a support ticket and explain that this happened to you. We do have a script that we will be handing out on a case by case basis to help recover that data, but it is not for everyone.

I installed the recently released BETA 4.9.1.21 hoping that it would have fixed the bugs in the previous Betas. Sadly I am still getting the same problems as before.

Still getting 'Configuration of the system has changed. To use content installed using Daz Connect, the content owner must re-authenticate.' message when I start the new Beta. It seemed like that was fixed but popped up when I ran 4.9.1.21 for the first time, which seemed sort of ok, cause it was a new version. But no, not fixed.
Don't have any problem logging on though.

Smart Content is a meta mess since 4.9 (altho I never found it that useful), but I won't go into that because everybody else is screaming about it.

Still getting 'Configuration of the system has changed. To use content installed using Daz Connect, the content owner must re-authenticate.' message when I start the new Beta. It seemed like that was fixed but popped up when I ran 4.9.1.21 for the first time, which seemed sort of ok, cause it was a new version. But no, not fixed.

Had you run the release build between sessions of the beta? That will cause the system configuration changed message, just as on first launch of the beta.

Still getting 'Configuration of the system has changed. To use content installed using Daz Connect, the content owner must re-authenticate.' message when I start the new Beta. It seemed like that was fixed but popped up when I ran 4.9.1.21 for the first time, which seemed sort of ok, cause it was a new version. But no, not fixed.

Had you run the release build between sessions of the beta? That will cause the system configuration changed message, just as on first launch of the beta.

Of course, I ran both, as I was testing them, looking for changes, improvements. I don't understand why that would change the configuration as they were in isolated locations. Previously, I had searched through the Registry to see if there were any conflicts and didn't find any, and now none. And what configuration exactly has changed? Or is this some DazConnect / database thing?

So, anyhow what can I do to fix this nuisance, or is it, wait for the next bug fix to come out?
Thanks dear.

Still getting 'Configuration of the system has changed. To use content installed using Daz Connect, the content owner must re-authenticate.' message when I start the new Beta. It seemed like that was fixed but popped up when I ran 4.9.1.21 for the first time, which seemed sort of ok, cause it was a new version. But no, not fixed.

Had you run the release build between sessions of the beta? That will cause the system configuration changed message, just as on first launch of the beta.

Of course, I ran both, as I was testing them, looking for changes, improvements. I don't understand why that would change the configuration as they were in isolated locations. Previously, I had searched through the Registry to see if there were any conflicts and didn't find any, and now none. And what configuration exactly has changed? Or is this some DazConnect / database thing?

So, anyhow what can I do to fix this nuisance, or is it, wait for the next bug fix to come out?
Thanks dear.

The verification code has been altered to avoid the issues that some people (including me) were having with false change detections, however because it has changed it is no longer compatible with the code in the release version and running one will cause the other to report a change. This will end when the release version is updated to use the new code (assuming no bugs are found requiring further changes, I suppose). Getting a change alert in the public beta after runing the release version is expected and doesn't need a report - getting an alert in the beta without having run the release version, and without having made any system changes, would be unexpected and should be reported.

Still getting 'Configuration of the system has changed. To use content installed using Daz Connect, the content owner must re-authenticate.' message when I start the new Beta. It seemed like that was fixed but popped up when I ran 4.9.1.21 for the first time, which seemed sort of ok, cause it was a new version. But no, not fixed.

Had you run the release build between sessions of the beta? That will cause the system configuration changed message, just as on first launch of the beta.

Of course, I ran both, as I was testing them, looking for changes, improvements. I don't understand why that would change the configuration as they were in isolated locations. Previously, I had searched through the Registry to see if there were any conflicts and didn't find any, and now none. And what configuration exactly has changed? Or is this some DazConnect / database thing?

So, anyhow what can I do to fix this nuisance, or is it, wait for the next bug fix to come out?
Thanks dear.

The verification code has been altered to avoid the issues that some people (including me) were having with false change detections, however because it has changed it is no longer compatible with the code in the release version and running one will cause the other to report a change. This will end when the release version is updated to use the new code (assuming no bugs are found requiring further changes, I suppose). Getting a change alert in the public beta after runing the release version is expected and doesn't need a report - getting an alert in the beta without having run the release version, and without having made any system changes, would be unexpected and should be reported.

Will the blue highlight for new content in the Content Library be reinstated with this fix? I installed a pile of Freebies yesterday and that would be sheer hell without that feature to help catagorise them. I'm not moving to 4.9 until Content Library has the functionality (or improved) of 4.8.

Still getting 'Configuration of the system has changed. To use content installed using Daz Connect, the content owner must re-authenticate.' message when I start the new Beta. It seemed like that was fixed but popped up when I ran 4.9.1.21 for the first time, which seemed sort of ok, cause it was a new version. But no, not fixed.

Had you run the release build between sessions of the beta? That will cause the system configuration changed message, just as on first launch of the beta.

Of course, I ran both, as I was testing them, looking for changes, improvements. I don't understand why that would change the configuration as they were in isolated locations. Previously, I had searched through the Registry to see if there were any conflicts and didn't find any, and now none. And what configuration exactly has changed? Or is this some DazConnect / database thing?

Highlights:

*Note:A "Configuration Changed" message is expected to display for all users that have logged into Daz Connect upon launching this build; until said user has logged into Daz Connect a minimum of one more time; the system configuration detection algorithm changed to resolve differences as noted above, so everyone is impacted. Note that switching between builds provided by the General Release channel and the Public Build channel (and the Private Build channel for those involved in that endeavor) will cause this message to display; until such time that the builds offered through all channels are using the same algorithm.

Is there a Daz Studio "Next" feature request list or something? Maybe a Poll? What's coming, at least? :)

The Change Log is the closest to what you're asking for. It doesn't always contain everything that has been worked on (because sometimes we are not ready for a thing to be public knowledge yet), but it does typically contain quite a bit of information. Advance warning... it can be cryptic and technical.

Is it too much to ask that I not have to install software updates via Connect? I'll use it for products if I have to, but the software? Really?

Not quite sure what you're referring to. Daz Studio does not currently support installation of plugins (or products that install like plugins) or updates to itself (like Install Manager) via Daz Connect.

Highlights:

" message is expected to display for all users that have logged into Daz Connect upon launching this build; until said user has logged into Daz Connect a minimum of one more time; the system configuration detection algorithm changed to resolve differences as noted above, so everyone is impacted. Note that switching between builds provided by the General Release channel and the Public Build channel (and the Private Build channel for those involved in that endeavor) will cause this message to display; until such time that the builds offered through all channels are using the same algorithm.

-Rob

Thanks for clairifying that, Rob, Spooky and Richard.

I may not have actually read it completely, as it seemed to me, to be the same stuff y'all have said before. And as you have mentioned, some of it can be cryptic and technical.

I really do appreciate that y'all respond on the Forums to our issues.

Still getting Crash to Desktop on DAZ Studio exit. Seems to be related with Iray cleanup routine. The problem occurs just when I render something using Iray. If I do not render or render with 3Delight the error doesn't shows.

Still getting Crash to Desktop on DAZ Studio exit. Seems to be related with Iray cleanup routine. The problem occurs just when I render something using Iray. If I do not render or render with 3Delight the error doesn't shows.

Doing a quick look...there seems to be 2 common causes for that error. Bad RAM and software. If it's Iray related (which it seems to be) and most other Mac users aren't having that particular crash, then it's time to suspect RAM.

Still getting Crash to Desktop on DAZ Studio exit. Seems to be related with Iray cleanup routine. The problem occurs just when I render something using Iray. If I do not render or render with 3Delight the error doesn't shows.

Doing a quick look...there seems to be 2 common causes for that error. Bad RAM and software. If it's Iray related (which it seems to be) and most other Mac users aren't having that particular crash, then it's time to suspect RAM.

Maybe, but before version 4.9.x it was working fine. None other application is presenting errors. I tested RAM with TechTool Pro and it doesn't point any problem, while I know taht is not the best indicator. Anyway, all seems working fine. My renders are finishing as expected, and apart from some problems with the database, DAZ Studio on overall is working fine. As the crash just occurs at the end of the exit process, and just when I worked with Iray, my clue is that it is something with the cleanup procedure. I will make a test witout plug-ins, which is something I think can be the issue.

What causes a product to disappear from Daz Connect? I discovered this missing product (Just Josh for G3M) when I opened a saved scene and got a missing files error. I know it used to be there, because the files are still in the Daz Connect cloud file system on my disk from a previous installation in an earlier 4.9 beta. But the product doesn't show up in my Content Library or in Smart Content at all. I carefully made sure that I have "All" selected on the left and at the bottom, I don't have Filter by Context checked, I looked in both the top colored installed list and the lower gray available list. I did Daz Connect>Update Metadata. I refreshed the J section of the Content Library. It just is not there. (I think I reset the database sometime after the original Just Josh installation, so I would expect the product to show up in Available if I hadn't reinstalled it yet.) It is still shown in My Account Product Library, so Daz knows I own it.

Prior to this, Real Hands product was missing. I wrote a help request and customer service "cleared my cache". That made Real Hands show up. Did that make Just Josh disappear? I wonder if I am missing other products now.

Still getting Crash to Desktop on DAZ Studio exit. Seems to be related with Iray cleanup routine. The problem occurs just when I render something using Iray. If I do not render or render with 3Delight the error doesn't shows.

Doing a quick look...there seems to be 2 common causes for that error. Bad RAM and software. If it's Iray related (which it seems to be) and most other Mac users aren't having that particular crash, then it's time to suspect RAM.

Maybe, but before version 4.9.x it was working fine. None other application is presenting errors. I tested RAM with TechTool Pro and it doesn't point any problem, while I know taht is not the best indicator. Anyway, all seems working fine. My renders are finishing as expected, and apart from some problems with the database, DAZ Studio on overall is working fine. As the crash just occurs at the end of the exit process, and just when I worked with Iray, my clue is that it is something with the cleanup procedure. I will make a test witout plug-ins, which is something I think can be the issue.

I'll use my machine as an example...

If I don't go in to the BIOS and manually force the RAM to run at a certain speed, half my RAM will disappear or I will get all sorts of errors only in some programs...and even that, only certain versions of some programs. But manually set to run at the slower speed, everything is perfect. RAM is a finicky thing and really is the cause of a bunch of odd/difficult to track down errors. .

I'm not interested in Cloud, Connect or DRM; discounting that, I'm not seeing any issues with 4.9. Indeed it renders very slightly faster over some. It is supposed to be slower when using Subsurface Scattering, but I can't say I'm seeing this. So for general use, is a good upgrade.

Will the blue highlight for new content in the Content Library be reinstated with this fix? I installed a pile of Freebies yesterday and that would be sheer hell without that feature to help catagorise them. I'm not moving to 4.9 until Content Library has the functionality (or improved) of 4.8.

I whole-heartedly second these sentiments. Please someone from DAZ comment on this.

Will the blue highlight for new content in the Content Library be reinstated with this fix? I installed a pile of Freebies yesterday and that would be sheer hell without that feature to help catagorise them. I'm not moving to 4.9 until Content Library has the functionality (or improved) of 4.8.

I whole-heartedly second these sentiments. Please someone from DAZ comment on this.

No, the change from the old New flagging system to the group-based system was deliberate. Though I don't understand the apaprently inconsistent results you are seeing, so that may be something that will be fixed.

Since freebies don't have metadata at all I would suggest isntalling to a separate content directory, then move them into your real content directory once you know they work and you want to keep them.

Will the blue highlight for new content in the Content Library be reinstated with this fix? I installed a pile of Freebies yesterday and that would be sheer hell without that feature to help catagorise them. I'm not moving to 4.9 until Content Library has the functionality (or improved) of 4.8.

I whole-heartedly second these sentiments. Please someone from DAZ comment on this.

No, the change from the old New flagging system to the group-based system was deliberate. Though I don't understand the apaprently inconsistent results you are seeing, so that may be something that will be fixed.

Since freebies don't have metadata at all I would suggest isntalling to a separate content directory, then move them into your real content directory once you know they work and you want to keep them.

If I understand the group-based system correctly, it works the opposite from how the old "new" tag system worked in that you yourself have to find the new items and mark them as new. That sounds so silly I know I must be misunderstanding the intent??

Will the blue highlight for new content in the Content Library be reinstated with this fix? I installed a pile of Freebies yesterday and that would be sheer hell without that feature to help catagorise them. I'm not moving to 4.9 until Content Library has the functionality (or improved) of 4.8.

I whole-heartedly second these sentiments. Please someone from DAZ comment on this.

No, the change from the old New flagging system to the group-based system was deliberate. Though I don't understand the apaprently inconsistent results you are seeing, so that may be something that will be fixed.

Since freebies don't have metadata at all I would suggest isntalling to a separate content directory, then move them into your real content directory once you know they work and you want to keep them.

If I understand the group-based system correctly, it works the opposite from how the old "new" tag system worked in that you yourself have to find the new items and mark them as new. That sounds so silly I know I must be misunderstanding the intent??

No, it hould be auto-tagging them as new AFAIK, but I'm not sure if it works the same way for all the different installation methods.

Will the blue highlight for new content in the Content Library be reinstated with this fix? I installed a pile of Freebies yesterday and that would be sheer hell without that feature to help catagorise them. I'm not moving to 4.9 until Content Library has the functionality (or improved) of 4.8.

I whole-heartedly second these sentiments. Please someone from DAZ comment on this.

No, the change from the old New flagging system to the group-based system was deliberate. Though I don't understand the apaprently inconsistent results you are seeing, so that may be something that will be fixed.

Since freebies don't have metadata at all I would suggest isntalling to a separate content directory, then move them into your real content directory once you know they work and you want to keep them.

If I understand the group-based system correctly, it works the opposite from how the old "new" tag system worked in that you yourself have to find the new items and mark them as new. That sounds so silly I know I must be misunderstanding the intent??

No, it hould be auto-tagging them as new AFAIK, but I'm not sure if it works the same way for all the different installation methods.

But if I understood Richard correctly, he just said the auto-tagging as New was not included as a feature in 4.9. Instead, the Group designation was created? I am really confused.