UncannyValet said:

If you dont want to make it again, you have two options:

Option 1: Export and rig using transfer utility

Dial up clone morph on G8/G9 as required so both donor and acceptor figure are same shape. Export the G8 SBH with Tesselation Sides value =1. On obj exporter dialogue ensure Write Polylines is checked.  Import the exported obj back into Daz.  Use Transfer Utility to transfer from Source (Genesis 9*) rigging to the Target (Imported SBH obj), setting shape to Current for both. If the Genesis 9 figure is not at default shape (e.g., if you have dialled in a clone shape on the Genesis 9 figure or any other active morph), you will need to set Reverse Source Shape from Target (or whatever it is called) in the Transfer Utility advanced options. 

*Or Genesis 9 haircap instead of Genesis 9 figure.

Option 2: Genesis 8 Skinsuit on Genesis 9

Create a skinsuit for Genesis 9 made out of Genesis 8's skin such that Genesis 9 will wear Genesis 8. You can equip the Editable SBH Object to the Genesis 8 wearable skinsuit since geomery of G8 is conserved.

Again, you will use Transfer Utility to transfer Genesis 9 rigging to Genesis 8.  Again, they will need to be the same shape before you run Transfer Utility.

I have not tested if Option 2 actually works...

I did end up making it from scratch again (better than before so no harm no foul) but I'll keep these in mind for other things, thanks! 

4.24 has corrupted all animation files for me, can animate things just fine, but when I go to render it's like the file corrupts mid-render.

Both Image Seqences and Movies will pop an error saying the file cannot be saved, and ask me if I want to cancel or pick a new file location. Moving the location does nothing, and if I cancel it and try to open the file again, the file can't be opened and Daz tells me there's an error in the file.

Here's what I was able to find in the log about the errors: 

About the Corrupted File:

2025-05-07 14:07:38.375 [INFO] :: Unlocking viewport redraw...
2025-05-07 14:07:38.375 [INFO] :: Viewport redraw unlocked.
2025-05-07 14:12:59.801 [INFO] :: Prepare asset load (open): /Scenes/abo ghoap kissing animation redo.duf
2025-05-07 14:12:59.801 [INFO] :: Locking viewport redraw...
2025-05-07 14:12:59.801 [INFO] :: Viewport redraw locked.
2025-05-07 14:12:59.837 [VERBOSE] :: Native format content directories: 10
2025-05-07 14:12:59.837 [VERBOSE] :: Poser format content directories: 3
2025-05-07 14:12:59.837 [VERBOSE] :: Other import format content directories: 0
2025-05-07 14:12:59.837 [INFO] :: Begin asset load (open): /Scenes/abo ghoap kissing animation redo.duf
2025-05-07 14:12:59.837 [WARNING] :: Error loading asset: FILE.duf

    Operation failed

About the Failure to Save:

2025-05-06 19:52:27.055 [INFO] :: Failed to save image: D:\Roxanne\Documents\DAZ 3D\Studio\Render Library\ghoap\kissing ani\smoochies muah muah006.png
2025-05-06 19:52:27.055 [INFO] ::     Operation failed
2025-05-06 19:54:43.371 [INFO] :: Failed to save image: D:\Roxanne\Documents\DAZ 3D\Studio\Render Library\ghoap\kissing ani\smoochies muah muah006.png
2025-05-06 19:54:43.371 [INFO] ::     Operation failed
2025-05-06 19:54:44.061 [INFO] :: Failed to save image: D:\Roxanne\Documents\DAZ 3D\Studio\Render Library\ghoap\kissing ani\smoochies muah muah006.png
2025-05-06 19:54:44.061 [INFO] ::     Operation failed
2025-05-06 19:54:45.980 [INFO] :: Failed to save image: D:\Roxanne\Documents\DAZ 3D\Studio\Render Library\ghoap\kissing ani\smoochies muah muah006.png
2025-05-06 19:54:45.980 [INFO] ::     Operation failed
2025-05-06 19:54:46.402 [INFO] :: Failed to save image: D:\Roxanne\Documents\DAZ 3D\Studio\Render Library\ghoap\kissing ani\smoochies muah muah006.png
2025-05-06 19:54:46.402 [INFO] ::     Operation failed
2025-05-06 19:54:46.748 [INFO] :: Failed to save image: D:\Roxanne\Documents\DAZ 3D\Studio\Render Library\ghoap\kissing ani\smoochies muah muah006.png
2025-05-06 19:54:46.748 [INFO] ::     Operation failed
2025-05-06 19:54:47.545 [INFO] :: Rendering frame 7...

Other Random Errors:

2025-05-07 14:06:40.124 [VERBOSE] :: Total class factories: 2165
2025-05-07 14:06:40.126 [INFO] :: Creating Script Engine...
2025-05-07 14:06:40.146 [WARNING] :: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
2025-05-07 14:06:40.146 [INFO] :: 3D mouse support library could not be loaded.
2025-05-07 14:06:40.865 [INFO] :: Creating Main Window...
2025-05-07 14:06:40.867 [INFO] :: Creating Viewport Manager...
2025-05-07 14:06:40.900 [INFO] :: Successfully created OpenGL viewport for Viewport1.
2025-05-07 14:06:40.979 [INFO] :: Successfully created OpenGL viewport for Viewport2.
2025-05-07 14:06:41.086 [INFO] :: Successfully created OpenGL viewport for Viewport3.
2025-05-07 14:06:41.145 [INFO] :: Successfully created OpenGL viewport for Viewport4.
2025-05-07 14:06:41.248 [INFO] :: Creating Action Manager...
2025-05-07 14:06:41.272 [INFO] :: Creating Pane Manager...
2025-05-07 14:06:41.423 [INFO] :: Successfully created OpenGL viewport for AuxViewportView.
2025-05-07 14:06:52.032 [INFO] :: Loading Actions: C:/Users/Roxanne/AppData/Roaming/DAZ 3D/Studio4/actions.dsx
2025-05-07 14:06:52.058 [INFO] :: Loading Custom Actions: C:/Users/Roxanne/AppData/Roaming/DAZ 3D/Studio4/customactions.dsx
2025-05-07 14:06:52.064 [INFO] :: Loading Menus: C:/Users/Roxanne/AppData/Roaming/DAZ 3D/Studio4/menus.dsx
2025-05-07 14:06:52.081 [INFO] :: Loading ToolBars: C:/Users/Roxanne/AppData/Roaming/DAZ 3D/Studio4/toolbars.dsx
2025-05-07 14:06:52.582 [VERBOSE] :: Update Check: Interval = 7 days, Since = 2 days, Last = Mon May 5 2025
2025-05-07 14:06:52.582 [VERBOSE] :: Update Check: Days (2) < Min (7)
2025-05-07 14:06:52.589 [INFO] :: Executing startup script...
2025-05-07 14:06:52.638 [INFO] :: Started in: C:/Daz 3D/Applications/64-bit/DAZ 3D/DAZStudio4
2025-05-07 14:06:52.638 [INFO] :: DAZ Studio started
2025-05-07 14:06:52.639 [INFO] :: Creating Pixel Buffer...
2025-05-07 14:06:52.662 [VERBOSE] :: Pixel Buffer: Width = 1024, Height = 1024
2025-05-07 14:06:52.664 [INFO] :: Compiling OpenGL Shaders...
2025-05-07 14:06:52.677 [VERBOSE] :: Compiling Fragment Shader: Succeeded
2025-05-07 14:06:52.680 [VERBOSE] :: Linking Shader Program: Succeeded
2025-05-07 14:06:52.682 [INFO] :: Loading Layout: C:/Users/Roxanne/AppData/Roaming/DAZ 3D/Studio4/layout.dsx
2025-05-07 14:06:54.200 [WARNING] :: QColor::setRgb: RGB parameters out of range
2025-05-07 14:06:54.214 Iray [INFO] - IMAGE:IO ::   1.0   IMAGE  io   info : Loading image "C:\Daz 3D\Applications\64-bit\DAZ 3D\DAZStudio4\shaders\iray\resources\DTHDR-RuinsB-500.hdr", no selector, pixel type "Rgb_fp", 512x256x1 pixels, 1 miplevel.

 

I have 124 Gb free on the drive where I save things, so I don't think it's my drive. Has anyone else been having these issues? I wasn't having any problems before the update, and single images are still rendering 100% fine and those files are not corrupting. I can save and reload them as normal.

Any help is appreciated! Full log is attached. Don't judge my file names too hard.

 

If I'm installing metadata (ones I created myself) with the script, the Compatibility Bases will not be applied on the items, while its not the case when I'm doing the same with the Re-import metadata tool.

To explain the process:

1. Metadata created on my Mac.
2. .dsa / .dsx files transfered on another computer.
3. Script used to install said metadata.

Once I have done that, I can see the product in Smart Content, looking exactly the same as it would on another computer, I can ask Smart Content to show me the addon for one item (let's say a dress) of that product and Smart Content will show me them (material presets in my example).

But if I'm loading that dress and I ask Smart Content to filter by context, with the dress selected in the Scene tab, Smart Content will not show me the material presets. Checking the scene identification of the dress, it has 'None' as Compatibility Bases.

Using the 'Set Default Compatibility Bases' tool, I can watch the list of the known Compatibility Bases and the product I just installed appears here, with the corret Sub-root Compatibility bases.

I tried to import the metadata multiple times with the script: I though that maybe there could be a problem in the order the metadata were processed, so with the Comptibility Bases already created, maybe it would add them to the items,  but it didn't change the problem.

Does someone know the root of the problem ? Is it a problem with the script or a problem on my side of the screen ?

Edit: I forgot but in case it's important, I'm using Daz Studio 4.23 PB on my Mac to create the metadata and I saw the problem on Daz Studio 4.23 PB on Windows but did most of my test on an older machine laying around, using Daz Studio 4.21.

If you dont want to make it again, you have two options:

Option 1: Export and rig using transfer utility

Dial up clone morph on G8/G9 as required so both donor and acceptor figure are same shape. Export the G8 SBH with Tesselation Sides value =1. On obj exporter dialogue ensure Write Polylines is checked.  Import the exported obj back into Daz.  Use Transfer Utility to transfer from Source (Genesis 9*) rigging to the Target (Imported SBH obj), setting shape to Current for both. If the Genesis 9 figure is not at default shape (e.g., if you have dialled in a clone shape on the Genesis 9 figure or any other active morph), you will need to set Reverse Source Shape from Target (or whatever it is called) in the Transfer Utility advanced options. 

*Or Genesis 9 haircap instead of Genesis 9 figure.

Option 2: Genesis 8 Skinsuit on Genesis 9

Create a skinsuit for Genesis 9 made out of Genesis 8's skin such that Genesis 9 will wear Genesis 8. You can equip the Editable SBH Object to the Genesis 8 wearable skinsuit since geomery of G8 is conserved.

Again, you will use Transfer Utility to transfer Genesis 9 rigging to Genesis 8.  Again, they will need to be the same shape before you run Transfer Utility.

I have not tested if Option 2 actually works...

fiskblack111 said:

Bug reports:
In version 6.25.2025.12207:
1) Newest DAZ Studio 2025 is not loading plugins. I installed Octane render engine, but it's not showing up anywhere

Plug-ins will all need to be reworked if they are to work in 2025, assuming the author is available to do so. See https://www.daz3d.com/forums/discussion/727631/daz-studio-2025-6-25-2025-x-evergreen#latest This will also affect some scripts.

2) Viewport is VERY laggy and slow comparing to DAZ Studio 4.23

What GPU? Though I did encounter an issue like this exploring a big (in dimensions) scene last night.

3) DAZ Studio shows error message when trying to load Poser props (.pp2). After clicking "OK" the import process windows still remains, making it impossible to close, and continue use Studio. The only way to get rid of it - kill the process in task manager, loosing the scene

What error?

4) "Texture shaded" mode of the viewports is not working at all. When switching to this mode - everything becomes invisible

What GPU is handling the display? Intel GPUs-on-a-CPU seem to have issues.

Bug reports:
In version 6.25.2025.12207:
1) Newest DAZ Studio 2025 is not loading plugins. I installed Octane render engine, but it's not showing up anywhere
2) Viewport is VERY laggy and slow comparing to DAZ Studio 4.23
3) DAZ Studio shows error message when trying to load Poser props (.pp2). After clicking "OK" the import process windows still remains, making it impossible to close, and continue use Studio. The only way to get rid of it - kill the process in task manager, loosing the scene
4) "Texture shaded" mode of the viewports is not working at all. When switching to this mode - everything becomes invisible

Why do you want to export/import the buttons?

They are probably attached with Rigid Follower Nodes, so can be moved as needed.

So I have learnt to sculpt and modify single piece clothing, but the one I want to modify now has 10 separate buttons attached as objects which will cause a vertice mismatch if I export the shirt with the buttons and then importing as a morph to the shirt.

I could export each individual button along with the base shirt and then import the morph for each individual item but that will be very time consuming, is there an easier way to do this?
 

 

My guess is that the UserData only saves what you have entered in the database. It does not appear to add anything else, or different versions, like a metadata history. I do not know if it saves data for the currently configured library(ies) or all of them (if some are not in the current Content Set). Did you notice anything missing from the smaller files?

I want to be able to import this hair: https://www.daz3d.com/classic-long-hair-with-dforce-for-genesis-8-females and simulate it in Blender, but it causes lags to Blender and I cannot turn this hair to particle for simulation.
Please, if anyone can help me... I am willing to pay you as well if you can solve this problem for me. 

sucan2015 said:

lilweep said:

sucan2015 said:

lilweep said:

if subdvision wasnt high enough, you can increase subdivision...

if you cant load hd morphs, then you dont need to, you dont need a poseable figure for a static render. you can just use your subdivided figure as a static mesh.

Do you mean I should increase subdivisions in ZBrush and then export to DAZ?

 

Zbrush is an example of a sculpting software where you would do this yes

 If so, would I lose all the materials and textures in the process? 

Well, they wouldnt be "lost" you just need to transfer them.  Obviously this process below assumes your method for exporting and importing a sculpt doesnt remove the Surfaces.

Steps:

1. Import your subdivided and sculpted obj file from Zbrush (or whatever software you suclpted it in)

 

2. In the surfaces tab for the imported sculpt, add the same shader that was used on your original figure (e.g., Iray Uber, or PBR Skin, etc)

3. Hide the original figure

.4. Copy the surfaces from the original figure to the imported figure. (Right click and copy in surfaces tab of original figure, paste in surfaces tab for imported figure)

 

Alternatively for making HD morphs there are options on youtube.

 

I might have made a mistake, but I’m not sure. When I increase subdivisions in ZBrush, finish sculpting, and use GoZ to return to DAZ, I choose "Create New Object." However, the newly imported figure only has one surface, so I can’t copy surfaces from the original figure.
If possible, please let me know what I’m doing wrong. Thanks!

GoZ does not preserve groups (I am not sure if this inherent to GoZ or just the way it is implemented). Use OBJ instead, and import materials as groups in the options in ZBrush, but you will need to rename the groups afterwards (unless they have changed it recently ZBrush does not preserve names even if it preserves the actual grouping).

It's probably just either a metadata update or a compatibility update. IDK exactly.

lilweep said:

sucan2015 said:

lilweep said:

if subdvision wasnt high enough, you can increase subdivision...

if you cant load hd morphs, then you dont need to, you dont need a poseable figure for a static render. you can just use your subdivided figure as a static mesh.

Do you mean I should increase subdivisions in ZBrush and then export to DAZ?

 

Zbrush is an example of a sculpting software where you would do this yes

 If so, would I lose all the materials and textures in the process? 

Well, they wouldnt be "lost" you just need to transfer them.  Obviously this process below assumes your method for exporting and importing a sculpt doesnt remove the Surfaces.

Steps:

1. Import your subdivided and sculpted obj file from Zbrush (or whatever software you suclpted it in)

 

2. In the surfaces tab for the imported sculpt, add the same shader that was used on your original figure (e.g., Iray Uber, or PBR Skin, etc)

3. Hide the original figure

.4. Copy the surfaces from the original figure to the imported figure. (Right click and copy in surfaces tab of original figure, paste in surfaces tab for imported figure)

 

Alternatively for making HD morphs there are options on youtube.

 

I might have made a mistake, but I’m not sure. When I increase subdivisions in ZBrush, finish sculpting, and use GoZ to return to DAZ, I choose "Create New Object." However, the newly imported figure only has one surface, so I can’t copy surfaces from the original figure.
If possible, please let me know what I’m doing wrong. Thanks!

About the .dsa/.dsx files related to Metadata, by default, Daz will place them by default inside 'My Library/Runtime/Support' but you're free to move it once created: Daz is checking every /Runtime/Support folders its knows about to check where the files storing the metadata you're currently editing are located.

What I'm doing in that respect is generally:

1. Place every files related to the product I want to create Metadata for inside a Library called Metadonnees (Metadata in French), one that I'm only using to create Metadata for a product.

2. Load every elements of that product (so for clothes, I'm loading every part of it, either through an outfit preset if it's available, or all of them).

3. In the Scene tab, I'm selecting every elements related to the product.

4. Right Click on the Scene tab > Edit > Set Default Compatibility Base

5. Click on the … in the top right corner of the windows to open the list of all Compatibility Bases known by your installation of Daz Studio.

6. Click on the hamburger icon in the top right corner and click on Create New Root Compatibility Base

7. Name it as you want (to avoid conflict, if your chosen name is a bit too generic, add something to the name: an example would be character by Mousso usually are MSO [character name]) and copy-paste it for good measure, then click Accept

8. Paste the name you just typed in the search field which should automatically select it in the list below or select it if you only typed part of the name, then click Accept to close that window, then Accept again to finally tell Daz to set that Compatibility Base for all the items selected: it'll create automatically new sub-root Compatibility base for most selected item based on something that is escaping me right now.

Note: you can also create it manually, by creatin a New Compatibility Base then a New Sub-root Compatibility Base, it's just easier to let Daz in charge of that part of the work, especially when there is a lot of sub-root bases to create.

The next step will happens in the Metadata editor so in the case of your figure

9. In the list of Assets, select the .duf  file that will load it and in the Compatibilities Base tab, click 'Add a new compatibility base to file' and paste the name of the root compatibility base in the search field.

10. Click on it and open it to select the sub-root compatibility base you want to attach to that product, click Accept.

Once you have saved the change, you now have a Compatibility base attached to your figure, one that you'll now be able to set it in the Compatibilities row for all the presets specific to your figure (like poses, materials, wearables presets, etc).

Note that if you created a prop, let's say a weapon, for your figure, if you have a .duf file to load the prop alone, it'll have its own compatibility base and it'll not have Compatibilities set to your figure: you'll have to create a wearable preset (to load the prop where it should be loaded on the figure, so for a weapon, in one of the hand of the figure) which will not have any Compatibility Base but will have your figure sets as Compatibilities.

You best bet if you don't know how to set some metadata, once you have the basics in mind is to open a product with metadata made by Daz and usually, you'll see how they are labelling everything (note: mistakes are not unheard even with metadata created by Daz but at one point, you'll know how to detect them too).

The Compatibility Base is indeed the key to successful metadata, and therefore Smart Content. Assuming you have all the parts in place, a Product defined, Content type, default categories, etc.

I have done this many times with 3rd party products to make DIM-compatible packages using Content Package Assist (CPA for short).

To get a compatibility base working, you need to make a link between the logical definitions and an actual instance of that object. Load all unique assets into a blank scene and select them all. They do not necessarily need to be parented or fit to something, as long as you have one of everything. Right-click on the Scene tab, or on the context menu at the top of the pane, and select Edit -> Set Default Compatibility Base... to set a common root under which all assets will be gathered. 

Click the ellipsis at the far right of the dialog and wait for the list of available bases to show up. This is where you can select or add the appropriate base you need to make the association. You will likely have to enter a new Root Compatibility Base, from the drop-down menu at the far right. The root should be set to the Product Name for convenience, and the other selected assets will automatically be included when you Accept. (The process can take a while if you have many Products). Check the "Selected nodes only" if there are other assets that are not meant to be included, otherwise every object in the scene will be included.

If you do not select all the Assets you want to include, you can always go back and add the stragglers later using the same process, or one at a time using the Edit -> Scene Identification... option and add more Sub-Compatibility bases to the Root Compatibility base.

Once that is done, off to the alphanumeric Product section. Choose your Product from the list, then edit metadata. You are at the Vendor data level, which allows you to set many aspects of the metadata not available in the simpler UserData level. You can select a Store (DAZ 3D and LOCAL USER are the only choices, unless you add another with an external script), a Token (Product number), Artists (your Artist handle, or not), and a Description.

The metadata support file path and name will be completed automatically if Auto-fill is checked. It takes the info from the previous fields construct the name. The metadata will be saved to the folder where the product files are located, in a Runtime/Support folder, created if needed (or maybe the first Library in the Content Set). I personally use a blank test library, first in the list, with nothing other than the Product being processed. Easier to see if anything is missing. Paths are relative, so when you package and install somewhere else, it will be totally transparent.

The Files section will have references to all Support Assets in the product, like file icons, data files, texture bitmaps, i.e., everything else that gets installed. If you have properly set up the Root Compatibility base, you should see your assets in the Scene IDs section. They should be all checked, but you can exclude any that should not be there.

On to the Assets tab. Here is where you make the link between the Compatibility Base and the object in the scene. Select each entry in the top half that has geometry (e.g., Figures, Props, etc.), all at once or one at a time, and select the Compatibility Base tab in the lower half. Right-click each listed Asset in the lower half and select "Add Compatibility Base to Selected File(s)" (your only choice at this point).  This will open the full list of Compatibility Bases, which should look familiar now. Locate you new Root Compatibility base, and expand to show the list of Sub-Bases. Pick the one you want to assign to the file and Accept. Rinse, repeat for each unique element. Each asset can have only one Base.

Materials, Poses, and the like, don't get Bases, but they can be assigned Compatibilities using the same process from the Compatibilities tab. There you can do more than one at a time if, say, several material presets or poses can apply to the same object or objects. You can also set Content type and Default Categories if you haven't already.

If Auto Export is checked, the metadata files will be written to the appropriate folder when you Accept the changes. I personally like to export manually to make sure it went to the right place. Data is committed to the database when you Accept. Now would also be a good time to add your Product thumbnail to the support folder (same name as the metadata files).

Now, to bring all this work into the family, you can package the new metadata files with your Product (with CPA). Uninstall from the test folder and re-install where you want. The new metadata will be installed in the Library with the Product assets. You should now have a fully functional Smart Content Product.

I am sure that there is a utility that can do all this automatically, but I like to see what's going on instead of relying on the unfamiliar.

I believe that covers everything, don't hesitate if you have any questions.

(Edited for small typos)

When I start the DS 2025 Alpha I get this warning. I have no idea what it causes it or what it means:

2025-05-05 00:20:09.387 [INFO] :: Creating Multimedia Manager...
2025-05-05 00:20:09.387 [INFO] :: Creating Content Manager...
2025-05-05 00:20:09.396 [INFO] :: Scanning Import folders...
2025-05-05 00:20:09.396 [INFO] :: Scanning Content folders...
2025-05-05 00:20:09.426 [INFO] :: Creating Render Manager...
2025-05-05 00:20:09.428 [INFO] :: Creating Texture Converter Manager...
2025-05-05 00:20:09.429 [INFO] :: Creating Texture Baker Manager...
2025-05-05 00:20:09.431 [INFO] :: Creating Device Manager...
2025-05-05 00:20:09.431 [INFO] :: Creating CallBack Manager...
2025-05-05 00:20:09.457 [WARNING] :: Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
2025-05-05 00:20:09.567 [INFO] :: Initializing OpenGL extensions...
2025-05-05 00:20:09.572 [VERBOSE] :: Using GLEW 2.1.0
2025-05-05 00:20:09.573 [VERBOSE] :: Supported OpenGL extensions:

And also a bit later:

2025-05-05 00:20:12.983 [INFO] :: Creating Script Engine...
2025-05-05 00:20:13.026 [INFO] :: Creating Main Window...
2025-05-05 00:20:13.026 [INFO] :: Creating Viewport Manager...
2025-05-05 00:20:13.068 [WARNING] :: Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
2025-05-05 00:20:13.174 [WARNING] :: endResetModel called on DzGeometryGroupListModel(0x1bbc1324310) without calling beginResetModel first
2025-05-05 00:20:13.191 [INFO] :: Creating Action Manager...
2025-05-05 00:20:13.203 [INFO] :: Creating Pane Manager...
2025-05-05 00:20:14.301 [INFO] :: Loading Actions: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio6 Public Build/actions.dsx
2025-05-05 00:20:14.418 [INFO] :: Loading Custom Actions: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio6 Public Build/customactions.dsx
2025-05-05 00:20:14.735 [INFO] :: Loading Menus: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio6 Public Build/menus.dsx
2025-05-05 00:20:14.772 [INFO] :: Loading ToolBars: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio6 Public Build/toolbars.dsx
2025-05-05 00:20:15.123 [VERBOSE] :: Update Check: Interval = 7 days, Since = 6 days, Last = Tue Apr 29 2025
2025-05-05 00:20:15.123 [VERBOSE] :: Update Check: Days (6) < Min (7)
2025-05-05 00:20:15.126 [INFO] :: Executing startup script...
2025-05-05 00:20:15.168 [INFO] :: Started in: C:/Program Files/DAZ 3D/DAZStudio6 Public Build
2025-05-05 00:20:15.168 [INFO] :: DAZ Studio started
2025-05-05 00:20:15.251 [WARNING] :: Initializing RHI with OpenGL backend
2025-05-05 00:20:15.265 [INFO] :: Loading Layout: C:/Users/Barb/AppData/Roaming/DAZ 3D/Studio6 Public Build/layout.dsx

 

 

Hi all, 

For a while now I've been working on making my own products. 

I've got pretty much everything figured out, except for the Smart Content. 

All the files are done up and ready to go like a 3rd party product, where one would be able to install the files manually. I purchased the Content Package Assist product (https://www.daz3d.com/content-package-assist), and it works. Everything is able to be installed through DIM. 

But the one thing that doesn't work is that the Smart Content doesn't transfer over. There is a Smart Content Product that exists, but all the files have lost their metadata. The only part of the process of exporting Metadata that I haven't figured out is setting a compatibility base, which for pretty much every tutorial I go through, doesn't cover how to do this for entirely custom figures. (Most just say, "Choose Genesis 8 as your base compatibility and then hit okay.") 

So I'm basically making creatures with poses, textures, props, etc. How do I go about setting the Compatibility bases for something entirely new like this? (I'm told that this needs to happen.) 

With that said, I'm not convinced that this is actually the problem. (I could be wrong.) If not that, then where else might the problem lie? 

Also, when I export the metadata, it puts the file in my main Daz content library, but I have the product assets in a separate base library folder. I will then copy them over to the Runtime/Support folder where they would get installed with the rest of the product. Could that be part of the issue? 

I realize that there's probably more information needed here, but like I said, I'm trying to narrow the problem because most tutorials glaze right over this point that I need help with. 

Thanks! 

FSMCDesigns said:

sandro.diiorio said:

Hi everyone. I would like to make poses to import on Second Life.
I'm trying Daz3D. I can't find compatible models for SL, the ones I found are not Bento, so I can't model them in detail. How can I solve?

Thank you for your time.

yeah, you won't find anything at DAZ that can be used in SL. In the past, anything that is imported into SL automatically became the property of Linden labs and DAZ takes it's copyright on it's property seriously, as they should.

besides, DS uses it's own form of rigging which probably isn't compatable to the bento avatar skeleton in SL.

This is false. There's a tutorial and a kit that you can download from the SL website that lets you make poses in Daz. You have to manually do it, no taking shortcuts, but you can pose a little SL model in Daz, export the pose, and then import it into SL easily in a matter of minutes.

I don't have it (in my wishlist). But it is polygon hair, so can be adjusted in any modeller.

If you don't know a modeller, you might be able to do it with an animated timeline simulation. Start with the character in horizontal position, so the hair falls back, and then use the helper objects, e.g. 2 cylinder primitives, to push the hair towards the center, and then raise the character to upright (default) position. It can be a bit fiddly to get the timing of all the movements right.

If you use the base character for this exercise you can export it, and import as a morph you can use whenever you like.

Just to clarify. That 2D control board your talking about is actually just a rig. It can be done but I don't think anyone actually does it because you can import expressions and what not from daz already. However there's nothing actually stopping someone from building a facial control rig like that. You should be able to find tutorials about it on YouTube pretty easily to learn the concepts.