I am hitting an error with almost all material copy scripts from one popular vendor (3rd party store) -- they all worked in 4.x just fine.
Error in log is:
TypeError: Property 'setLabel' of object QVariant(DzTSharedPointer<DzElement>, DzUberIrayMaterial(0x1c21611c860, name = "Torso")) is not a function
Is this something that has changed in Daz Studio 2025 and will no longer work so they have to update the script, or is it a bug in Daz Studio?
Please advise.
There are some quite significant changes to the way the Qt script engine, on which Daz Studio scripting is built, works so yes, it is likely that the script is doing something unsupported or changed. One thing that has changed is the way arrays of objects work, so if for example the script is getting a list of surfaces it may not have the sort of thing it was written to expect - without seeing the source code I can't do more than guess (and even with the source code I might not do much better).
I installed this for my 5060 video card, mainly to help bug test it. I may not be able to use DAZ at the moment but I am more than willing to help bug test future releases. I don't mind being proactive.
With that said, I tested it out, managed to get a render of a single character done without problem. So I tested a larger scene with three characters and an asset in a kitchen etc... and that crashed, which didn't surprise me. I wanted to know where I can send the bug report, which I saved in order to contribute to getting this version fixed and out there? I made certain to save it anyhow.
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
Thanks.
What were you doing at that point? Can you get it to happen consistently?
Just loaded Daz 6 and for an Alpha version is surprisingly good. I have some issues which is to be expected. One rather annoying bug is the blurry viewport in texture view mode. Switching to iRay preview works fine. I've attached examples of the issue.
Another issue occurs when opening a scene that has missing files. In version 4 you could click a button to find the files. The button is missing in version 6
Is there anywhere that lists the bugs reported so far? I don't want to repeat reporting issues that have already been raised.
I'm using an RTX5090 and the Nvidia studio driver version 576.80
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
Thanks.
What were you doing at that point? Can you get it to happen consistently?
It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
Thanks.
What were you doing at that point? Can you get it to happen consistently?
It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.
How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
Thanks.
What were you doing at that point? Can you get it to happen consistently?
It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.
How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in
%appdata%/daz 3d/Studio6 Public Build/
will have the information.
I didn't alter the defaults in the Alpha 6 or the layout file.
I have two paths, with only one file each for Studio6:
a) C:\ProgramData\DAZ 3D\Studio6\dazstudio.dat
b) C:\ProgramData\DAZ 3D\Studio6 Public Build\dazstudio.dat
They are in binary and I don't have a hex editor installed, but those are the only two files in those directories.
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
Thanks.
What were you doing at that point? Can you get it to happen consistently?
It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.
How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in
%appdata%/daz 3d/Studio6 Public Build/
will have the information.
I didn't alter the defaults in the Alpha 6 or the layout file.
I have two paths, with only one file each for Studio6:
a) C:\ProgramData\DAZ 3D\Studio6\dazstudio.dat
b) C:\ProgramData\DAZ 3D\Studio6 Public Build\dazstudio.dat
They are in binary and I don't have a hex editor installed, but those are the only two files in those directories.
%appdata% is C:/users/you/appdata/roaming/, not Program Data - if you paste the path I gave above into a file browser address bar it will take you to the right folder, but the %appdata% is not a folder name in itself.
I have 6.25.2025.17807 and an RTX 5070. The main viewport was black, although mousing over things showed they were there. Toggling the Preview Lights had no effect. The icon in the display options for the active pane toggles, but the actual viewport remains completely dark. This is in a pre-existing file.
FYI, Draw Settings->Dome->Environment intensityy was 0. Setting it to 1.0 made the scene visible again.
I have 6.25.2025.17807 and an RTX 5070. The main viewport was black, although mousing over things showed they were there. Toggling the Preview Lights had no effect. The icon in the display options for the active pane toggles, but the actual viewport remains completely dark. This is in a pre-existing file.
FYI, Draw Settings->Dome->Environment intensityy was 0. Setting it to 1.0 made the scene visible again.
Cheers!
I would do a clean install of your Nvidia studio driver (just a thought). If that does not work, try using the game driver.
After I load a simple scene, two characters, after a while when I move the mouse over the viewport and highlights the object Daz stops responding and I have to force close it.
Tested with default chars, different enviroments and I get the same crash.
Updated or rolled back diffrent nvidia studio drivers.
Nothing in the log file.
Not sure if this has been talked about before - searching for .daz file format did not bring up anything.
Trying to load some of the props from the product https://www.daz3d.com/it-s-a-crime comes up with the message - An importer for the "daz" file format cannot be found.". It opens fine in the stable release versions. The props for this have a file extension of .daz.
Not sure if this has been talked about before - searching for .daz file format did not bring up anything.
Trying to load some of the props from the product https://www.daz3d.com/it-s-a-crime comes up with the message - An importer for the "daz" file format cannot be found.". It opens fine in the stable release versions. The props for this have a file extension of .daz.
Daz Studio 2025 ALPHA doesn't support the .daz format. Load it in 4.x and resave as a .duf, or use Legacy Set Converter in 4.x (available in the store).
Not sure if this has been talked about before - searching for .daz file format did not bring up anything.
Trying to load some of the props from the product https://www.daz3d.com/it-s-a-crime comes up with the message - An importer for the "daz" file format cannot be found.". It opens fine in the stable release versions. The props for this have a file extension of .daz.
Daz Studio 2025 ALPHA doesn't support the .daz format. Load it in 4.x and resave as a .duf, or use Legacy Set Converter in 4.x (available in the store).
Not sure if this has been talked about before - searching for .daz file format did not bring up anything.
Trying to load some of the props from the product https://www.daz3d.com/it-s-a-crime comes up with the message - An importer for the "daz" file format cannot be found.". It opens fine in the stable release versions. The props for this have a file extension of .daz.
Daz Studio 2025 ALPHA doesn't support the .daz format. Load it in 4.x and resave as a .duf, or use Legacy Set Converter in 4.x (available in the store).
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
Thanks.
What were you doing at that point? Can you get it to happen consistently?
It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.
How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in
%appdata%/daz 3d/Studio6 Public Build/
will have the information.
I didn't alter the defaults in the Alpha 6 or the layout file.
I have two paths, with only one file each for Studio6:
a) C:\ProgramData\DAZ 3D\Studio6\dazstudio.dat
b) C:\ProgramData\DAZ 3D\Studio6 Public Build\dazstudio.dat
They are in binary and I don't have a hex editor installed, but those are the only two files in those directories.
%appdata% is C:/users/you/appdata/roaming/, not Program Data - if you paste the path I gave above into a file browser address bar it will take you to the right folder, but the %appdata% is not a folder name in itself.
I'm not sure what was going on before but I bought some Outlet Store products today and so needed to install them, once I went to the Install tab in DIM the DAZ Studio Alpha 6 Jun 25 and plugins were on still in the Install Tab listed so I went again and installed them (again, I think) and now it works. So I'm not even sure what was crashing because if it was the prior Alpha version, then that had been already working prior to all the crashing I reported here. Anyway, it works. Sorry for the inconvenience.
Something that I've noticed has showed up in the 6 Alpha and the others, 4 Release, & 4 Beta are my top level Smart Content icons in the top right hand corner now mostly have a white symetric and vertiically bisected circle with a small white triangle pointed down at the bottom gap in the circle. What does that mean? Is this a icon telling me I have content available in that DAZ Connect again even though I've installed it via DIM? If so, I wish it wouldn't do that with the same product has already been installed via DIM. Or is that just notice that the meta data has been updated, example: data to better sort by genre, fashion, and other data, or that tells me I own the interactive license for that product. If so, how to I get DAZ Studio to update all of those metadata at once, but of if it's not wanting me to installs all of those products a second time, which would be a huge time wasting, space wasting, organizational disaster?
Also, while I'm asking that why is it that each time I start up DS 4.X Release, DS 4.X Public Beta, or DS 6 Alpha I get a dialogue messague before the DAZ Studio proper is on the screen that I am going to need to restart DS for the plugins changes and such to take effect. They haven't changed and restarting will just show that message again. When will that be fixed?
Something that I've noticed has showed up in the 6 Alpha and the others, 4 Release, & 4 Beta are my top level Smart Content icons in the top right hand corner now mostly have a white symetric and vertiically bisected circle with a small white triangle pointed down at the bottom gap in the circle. What does that mean? Is this a icon telling me I have content available in that DAZ Connect again even though I've installed it via DIM? If so, I wish it wouldn't do that with the same product has already been installed via DIM. Or is that just notice that the meta data has been updated, example: data to better sort by genre, fashion, and other data, or that tells me I own the interactive license for that product. If so, how to I get DAZ Studio to update all of those metadata at once, but of if it's not wanting me to installs all of those products a second time, which would be a huge time wasting, space wasting, organizational disaster?
That does sound like the avaiualble for install through Connect con. In the latests builds of DS 4 and in DS 2025 it should be hidden on products that are nstalled through DIM (or manually installed and their metadata imported).
Also, while I'm asking that why is it that each time I start up DS 4.X Release, DS 4.X Public Beta, or DS 6 Alpha I get a dialogue messague before the DAZ Studio proper is on the screen that I am going to need to restart DS for the plugins changes and such to take effect. They haven't changed and restarting will just show that message again. When will that be fixed?
It was fixed some time ago.
The two issues together do sound as if something (security software, system utilty) is getting in the way of DS' and/or DIM's ability to update certain data.
Something that I've noticed has showed up in the 6 Alpha and the others, 4 Release, & 4 Beta are my top level Smart Content icons in the top right hand corner now mostly have a white symetric and vertiically bisected circle with a small white triangle pointed down at the bottom gap in the circle. What does that mean? Is this a icon telling me I have content available in that DAZ Connect again even though I've installed it via DIM? If so, I wish it wouldn't do that with the same product has already been installed via DIM. Or is that just notice that the meta data has been updated, example: data to better sort by genre, fashion, and other data, or that tells me I own the interactive license for that product. If so, how to I get DAZ Studio to update all of those metadata at once, but of if it's not wanting me to installs all of those products a second time, which would be a huge time wasting, space wasting, organizational disaster?
That does sound like the avaiualble for install through Connect con. In the latests builds of DS 4 and in DS 2025 it should be hidden on products that are nstalled through DIM (or manually installed and their metadata imported).
Also, while I'm asking that why is it that each time I start up DS 4.X Release, DS 4.X Public Beta, or DS 6 Alpha I get a dialogue messague before the DAZ Studio proper is on the screen that I am going to need to restart DS for the plugins changes and such to take effect. They haven't changed and restarting will just show that message again. When will that be fixed?
It was fixed some time ago.
The two issues together do sound as if something (security software, system utilty) is getting in the way of DS' and/or DIM's ability to update certain data.
I stumbled on another labeling issue today. I opened the Alpha, 6.25.2025.17807 and had sorted my Wardrobe by Product ID: Lowest First and as I reviewed them, I noticed files with .duf and .dsf extensions were missing their labels. My first reaction was I had forgotten to add them when I did the metadata as these were V4/M4 and G1 files, but I opened the Beta, 6.24.0.3 and looked at those files and they did have their labels, indicating if they were Wardrobe, Accessory, or Prop... See the snip I took of the two desktops with the Alpha behind the Beta showing the same outfit. I did a scan of other type of files in the Alpha that are old enough that I would have had to assign metadata or in the case of DAZ+ had it, and they were fine. I did open Content DB Manager and added the Type of file (label) and it did show up at that time.
I have done a random sample of my wardrobe from G1, G2, G3, G8, G8.1 and G9 and it appears that only the label ‘Wearables’ is appearing. All other categories are blank in the Alpha. I have not seen this in the Beta at all. And I check all new products.
In a few cases of old Poser environment files the thumbnails were showing the 'grey image with the exclamation point in a box', even though it is there in the Beta. But this is not consistent for all Poser files, I can't seem to find a pattern for that. And in one case, Castleguarde, SKU 2419, it loaded okay.
I stumbled on another labeling issue today. I opened the Alpha, 6.25.2025.17807 and had sorted my Wardrobe by Product ID: Lowest First and as I reviewed them, I noticed files with .duf and .dsf extensions were missing their labels. My first reaction was I had forgotten to add them when I did the metadata as these were V4/M4 and G1 files, but I opened the Beta, 6.24.0.3 and looked at those files and they did have their labels, indicating if they were Wardrobe, Accessory, or Prop... See the snip I took of the two desktops with the Alpha behind the Beta showing the same outfit. I did a scan of other type of files in the Alpha that are old enough that I would have had to assign metadata or in the case of DAZ+ had it, and they were fine. I did open Content DB Manager and added the Type of file (label) and it did show up at that time.
I have done a random sample of my wardrobe from G1, G2, G3, G8, G8.1 and G9 and it appears that only the label ‘Wearables’ is appearing. All other categories are blank in the Alpha. I have not seen this in the Beta at all. And I check all new products.
In a few cases of old Poser environment files the thumbnails were showing the 'grey image with the exclamation point in a box', even though it is there in the Beta. But this is not consistent for all Poser files, I can't seem to find a pattern for that. And in one case, Castleguarde, SKU 2419, it loaded okay.
I would recommend that people do NOT use the STUDIO drivers! The Game Ready drivers are more up to date and have fixed issues which cause Windows to crash, where as, for some strange reason, the Studio drivers have not been updated.
Otherwise, it would be nice if there was a way I would submit my bug reports, my crash reports generated by Daz, otherwise, what in [Heaven's name] is the sense of testing an alpha?!
Comments
There are some quite significant changes to the way the Qt script engine, on which Daz Studio scripting is built, works so yes, it is likely that the script is doing something unsupported or changed. One thing that has changed is the way arrays of objects work, so if for example the script is getting a list of surfaces it may not have the sort of thing it was written to expect - without seeing the source code I can't do more than guess (and even with the source code I might not do much better).
@Richard
Also, scene tab doesn't update selectable/unselectable checkbox when you change the selectable in viewport toggle.
Yes, a number of people have run into that and I believe it is on the list.
It would be nice to see "the list" so we can stop harping about things Daz developers have already acknowledged need to be fixed.
I installed this for my 5060 video card, mainly to help bug test it. I may not be able to use DAZ at the moment but I am more than willing to help bug test future releases. I don't mind being proactive.
With that said, I tested it out, managed to get a render of a single character done without problem. So I tested a larger scene with three characters and an asset in a kitchen etc... and that crashed, which didn't surprise me. I wanted to know where I can send the bug report, which I saved in order to contribute to getting this version fixed and out there? I made certain to save it anyhow.
Okay, I decided to attach my bug report to this message. I hope someone gets it.
If I can test anything, let me know.
I am getting a crach on the latest Alpha.
AMD Ryzen 7 5700G
96GB RAM
PNY GeForce 4070 12GB
2 TB m.2 nvme PCIe Gen 3 System Disk.
2TB external USB m.2 nvme Gen3 DAZ Content Library Disk
Thanks.
What were you doing at that point? Can you get it to happen consistently?
Just loaded Daz 6 and for an Alpha version is surprisingly good. I have some issues which is to be expected. One rather annoying bug is the blurry viewport in texture view mode. Switching to iRay preview works fine. I've attached examples of the issue.
Another issue occurs when opening a scene that has missing files. In version 4 you could click a button to find the files. The button is missing in version 6
Is there anywhere that lists the bugs reported so far? I don't want to repeat reporting issues that have already been raised.
I'm using an RTX5090 and the Nvidia studio driver version 576.80
So Any news when we will get access to Geometry Sculptor?
It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.
No dates, but there has been a fair bit of actiivity relating to it in the Change Log which is somewhat encouraging.
How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in
%appdata%/daz 3d/Studio6 Public Build/
will have the information.
I didn't alter the defaults in the Alpha 6 or the layout file.
I have two paths, with only one file each for Studio6:
a) C:\ProgramData\DAZ 3D\Studio6\dazstudio.dat
b) C:\ProgramData\DAZ 3D\Studio6 Public Build\dazstudio.dat
They are in binary and I don't have a hex editor installed, but those are the only two files in those directories.
%appdata% is C:/users/you/appdata/roaming/, not Program Data - if you paste the path I gave above into a file browser address bar it will take you to the right folder, but the %appdata% is not a folder name in itself.
I have 6.25.2025.17807 and an RTX 5070. The main viewport was black, although mousing over things showed they were there. Toggling the Preview Lights had no effect. The icon in the display options for the active pane toggles, but the actual viewport remains completely dark. This is in a pre-existing file.
FYI, Draw Settings->Dome->Environment intensityy was 0. Setting it to 1.0 made the scene visible again.
Cheers!
I would do a clean install of your Nvidia studio driver (just a thought). If that does not work, try using the game driver.
Is it a common problem or just me?
After I load a simple scene, two characters, after a while when I move the mouse over the viewport and highlights the object Daz stops responding and I have to force close it.
Tested with default chars, different enviroments and I get the same crash.
Updated or rolled back diffrent nvidia studio drivers.
Nothing in the log file.
6.25.2025.17807
Not sure if this has been talked about before - searching for .daz file format did not bring up anything.
Trying to load some of the props from the product https://www.daz3d.com/it-s-a-crime comes up with the message - An importer for the "daz" file format cannot be found.". It opens fine in the stable release versions. The props for this have a file extension of .daz.
Daz Studio 2025 ALPHA doesn't support the .daz format. Load it in 4.x and resave as a .duf, or use Legacy Set Converter in 4.x (available in the store).
Thank you!
See File Formats : Retired
https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen
I'm not sure what was going on before but I bought some Outlet Store products today and so needed to install them, once I went to the Install tab in DIM the DAZ Studio Alpha 6 Jun 25 and plugins were on still in the Install Tab listed so I went again and installed them (again, I think) and now it works. So I'm not even sure what was crashing because if it was the prior Alpha version, then that had been already working prior to all the crashing I reported here. Anyway, it works. Sorry for the inconvenience.
Something that I've noticed has showed up in the 6 Alpha and the others, 4 Release, & 4 Beta are my top level Smart Content icons in the top right hand corner now mostly have a white symetric and vertiically bisected circle with a small white triangle pointed down at the bottom gap in the circle. What does that mean? Is this a icon telling me I have content available in that DAZ Connect again even though I've installed it via DIM? If so, I wish it wouldn't do that with the same product has already been installed via DIM. Or is that just notice that the meta data has been updated, example: data to better sort by genre, fashion, and other data, or that tells me I own the interactive license for that product. If so, how to I get DAZ Studio to update all of those metadata at once, but of if it's not wanting me to installs all of those products a second time, which would be a huge time wasting, space wasting, organizational disaster?
Also, while I'm asking that why is it that each time I start up DS 4.X Release, DS 4.X Public Beta, or DS 6 Alpha I get a dialogue messague before the DAZ Studio proper is on the screen that I am going to need to restart DS for the plugins changes and such to take effect. They haven't changed and restarting will just show that message again. When will that be fixed?
That does sound like the avaiualble for install through Connect con. In the latests builds of DS 4 and in DS 2025 it should be hidden on products that are nstalled through DIM (or manually installed and their metadata imported).
It was fixed some time ago.
The two issues together do sound as if something (security software, system utilty) is getting in the way of DS' and/or DIM's ability to update certain data.
OK, thanks, I'll look around.
I stumbled on another labeling issue today. I opened the Alpha, 6.25.2025.17807 and had sorted my Wardrobe by Product ID: Lowest First and as I reviewed them, I noticed files with .duf and .dsf extensions were missing their labels. My first reaction was I had forgotten to add them when I did the metadata as these were V4/M4 and G1 files, but I opened the Beta, 6.24.0.3 and looked at those files and they did have their labels, indicating if they were Wardrobe, Accessory, or Prop... See the snip I took of the two desktops with the Alpha behind the Beta showing the same outfit. I did a scan of other type of files in the Alpha that are old enough that I would have had to assign metadata or in the case of DAZ+ had it, and they were fine. I did open Content DB Manager and added the Type of file (label) and it did show up at that time.
I have done a random sample of my wardrobe from G1, G2, G3, G8, G8.1 and G9 and it appears that only the label ‘Wearables’ is appearing. All other categories are blank in the Alpha. I have not seen this in the Beta at all. And I check all new products.
In a few cases of old Poser environment files the thumbnails were showing the 'grey image with the exclamation point in a box', even though it is there in the Beta. But this is not consistent for all Poser files, I can't seem to find a pattern for that. And in one case, Castleguarde, SKU 2419, it loaded okay.
Fixed in 6.25.2025.18018, we are told.
Thanks Richard I will look for it.
I would recommend that people do NOT use the STUDIO drivers! The Game Ready drivers are more up to date and have fixed issues which cause Windows to crash, where as, for some strange reason, the Studio drivers have not been updated.
Otherwise, it would be nice if there was a way I would submit my bug reports, my crash reports generated by Daz, otherwise, what in [Heaven's name] is the sense of testing an alpha?!