Jan_Scrapper said:

Oh, my goodness...I used an online program to convert to an obj and the surface names were totally different!

I thought, somehow you are seeing original surface names...I imported the FBX file into DS, which I did NOT know it would do!!!

Thank you so much!!!

I am well on my way to applying all of the textures.

Learn something new everytime I open Daz Studio!!  What a powerful piece of software!!!

 

rigged animated FBX files mostly import too in the past years versions of DAZ Studio

they updated it a while back 

That's a new version of the FAST Blender pipeline that was released a few months ago. Product page says " Supported OS: Windows 11. macOS support coming in Febuary" (the older version did work on Mac IIRC, so it will probably be supported at some point). And no, it doesn't seem to support DS2026 (which is not surprising considering the SDK has still not been published)

From what I can see in the description, it adds features to Blender, not DS. It simply enables you to import your DS content into Blender easily (that part is based on Diffeomorphic IIRC)

I purchased some of your products and was finally able to test them yesterday. The Bone Minions work perfectly. I am having some issues with the Batch Converter. It simply does not convert batches. I can only convert a single pose at a time, which already saves a lot of work, but converting an entire pose folder would of course be much better. It also does not create icons, which is not a big problem since I can use the original images if I rename them accordingly.

I am not at my PC right now, so I do not know my DAZ version, I know it is not the newest, 4.5 I guess. Is there anything I need to enable first in order to convert a complete directory? I should mention that I convert the poses to V4 and then use a script for Poser to transfer these poses into Poser so I can apply them there to V4.

I only need a bit of help with converting a complete directory. Even if all poses in the directory are selected, it always converts only the first one or the one my mouse is hovering over.

edit: it is DAZ 4.23.0.1

hm... now I started again, I read about the Metadata, I disabled it and now it is working. Maybe this was the reason?

Utiltarian said:

jmucchiello said:

How about a text search that works on NAME? Even simply "contains" would be enough. No need for regex or something fancy

A text search/filter is not possible, the site data doesn't provide a full list of product names, only product IDs. At best, I could add a search for items that you just loaded to the page, but that's not much more useful than Ctrl + F in the browser. Your best bet would be to petition Daz to improve the site search.

At least they have added things recently. But most of my problems these days are the items that aren't correctly metadata'd.

Btw, haven't forgotten about the in-cart filters, just haven't had a chance to get around to it (and the other things I had planned). Hopefully soon!

Cool.

BTW, the script doesn't work on daz3d.com/catalogsearch/result... This is the URL if you search in the search box in the upper right of the shop. Is it supposed to work there?

Choose the BSDF method. After performing Diffeomorphic import, a large number of halos and volume fog will appear.

Hey there!
So I'm in the middle of completing my CC5 character by using Daz clothing, but am running into an issue with this shirt. I export the G9 figure with the shirt to an fbx file, and then import it into CC5 using the transformer tool. Now you have an option of using the 'default' skin template, and the 'original' skin template. When I use the default skin template I get weird deformation on the shirt under the armpits, but when I use the original I don't have that issue, except for that while the left arm is perfect, the right one isn't. This is because for some reason when importing to CC5, the right arm is also mapped to the left arm, and the right arm has no weight painting. Does anyone know what's causing this issue? Any help would be greatly appreciated.

Matt_Castle said:

Semicharm said:

One way to handle that is each file has a header with all of the metadata about dependences. That can be read without having to process the entire file. 

This is already how it is done. The formulas for any morph are stored near the start of its DSF file, immediately after the basic parameters of said morph. The morph deltas are further through the file, and indeed do not get processed and loaded until the morph is actually activated.

However, looking in the morph file has reminded me of something I'd forgotten. The basic parameters of a morph include things like what the morph's minimum and maximum limits are. Unless the file is opened and its header sections processed, then DS does not know whether a morph's slider should be displayed to the user with a range of 0% to 100%, -100% to 100%, -50% to 100%, 0 to 200%, or whatever.

This makes the problem of speeding up the processing of morphs a considerably more complicated process than I initially considered, and I'm now not actually sure I can see a better way that actually achieves the aims Daz need to meet.

Either the range info would have to be moved to the meta data section, which would start to bloat things a bit, or it would have to be displayed without specific info until it's completely loaded. That's where using a background task would help. Things the user tries to access can be moved to the front of the queue. 

That of course can be sped up if loading and decoding files was done in paralellel. For example, which file can be processed by a separate thread.

I believe Daz Studio 6 is already moving towards being able to paralellise these things more, but it's not an option we can expect to see added to DS4, which has reached the end of its development life and would have been extremely impractical to rebuild anyway.

I figured as much. Much of the framework for DS4 was set when CPUs only had a few cores and most people still relied on spinning hard drives. Older ones didn't handle multitasking well. Command queuing helps, but the drive was still a massive bottleneck. Parallel processing files would require investing time that would benefit few users back then. 

I'm sure such things were a "next gen" feature. I doubt they ever planned for that next major release to be pushed back this long. 

Semicharm said:

One way to handle that is each file has a header with all of the metadata about dependences. That can be read without having to process the entire file. 

This is already how it is done. The formulas for any morph are stored near the start of its DSF file, immediately after the basic parameters of said morph. The morph deltas are further through the file, and indeed do not get processed and loaded until the morph is actually activated.

However, looking in the morph file has reminded me of something I'd forgotten. The basic parameters of a morph include things like what the morph's minimum and maximum limits are. Unless the file is opened and its header sections processed, then DS does not know whether a morph's slider should be displayed to the user with a range of 0% to 100%, -100% to 100%, -50% to 100%, 0 to 200%, or whatever.

This makes the problem of speeding up the processing of morphs a considerably more complicated process than I initially considered, and I'm now not actually sure I can see a better way that actually achieves the aims Daz need to meet.

That of course can be sped up if loading and decoding files was done in paralellel. For example, which file can be processed by a separate thread.

I believe Daz Studio 6 is already moving towards being able to paralellise these things more, but it's not an option we can expect to see added to DS4, which has reached the end of its development life and would have been extremely impractical to rebuild anyway.

Matt_Castle said:

TheMysteryIsThePoint said:

Why force the user to wait for dials that the user has expressed no interest in, instead of initializing them into some kind of inactive state and only loading them if/when they are actually used?

Because, for very important practical reasons, control links have to be able to be defined in either direction.

That is to say that if you have a Controller A, with child morphs B, C & D, then the code can be in A to say "when A is dialled in, dial in B, C & D". Or the code can be in each of B, C & D to say "Go and look at A. If it's dialled in, dial me in too, thanks". Or various combinations.

Being able to link in either direction is very important, both practically and legally.

Let's say someone creates some new expressions, but *also* wants to have correctives for those expressions to make them look their absolute best on Victoria 9. So, they need to link the correctives to Victoria 9's morph so those correctives only activate on her shape. But they cannot update Victoria 9's morph because a) if everyone who needed to link to Victoria 9's morph had to alter it, then only one person could ever link to it, b) it would stupidly bloat everything if you needed to send around updated morphs for everything you wanted to link to, and c) they do not have the copyright to alter and redistribute Victoria 9's morph. So the link to Victoria 9's morph needs to be saved in the expression corrective file, not Victoria 9's.

As such, an on-demand top-down indexing of the morph library of "only look in the files once you know you need them" is impossible, because a lot of morph links are defined bottom-up and thus you don't know for sure whether you do or don't need a file until you've looked in it.

Now, possibly there are better ways to handle this infrastructure. Maybe the links could exist as files themselves, and their file names are encoded such that DS can tell for sure "Hey, that link file has a name that matches this morph file's name, so I know that it tells me about a link I will need to use if I ever dial this morph in, but I don't need to look in it right now", but it would not be possible to migrate an existing figure base to a new system like that.

For now, Daz Studio is forced to work the way it does, opening and checking every morph file it can find in the library folders for that base figure to find all possible links before proceeding.

One way to handle that is each file has a header with all of the metadata about dependences. That can be read without having to process the entire file. The rest can be posponed untill the file is required or as a background task. Wating until a dial is used can trigger 50 or more dependences being loaded, which can cause the app to freeze while that's being processed.

That of course can be sped up if loading and decoding files was done in paralellel. For example, which file can be processed by a separate thread. The best way to do that depends on where the bottlenecks in the pipeline are. 

lkopop908 said:

For a while Ive wondered. Why hasnt Daz been made into a full scale plugin for Blender, "merge" the two?

I dont mean to export/import but to pretty much be the Daz library/poses/login/ease of use in Blender?

By "merging" Daz into Blender they could "catch" quite a few Blender users increasing their user base / $ coming in.

Yes I know PA's would have to learn to script for Blender, but again the Blender community is massive in comparison leading to more $ for them as well.

Looking at it from my view its costing them more $ to keep a pure "Daz3d" going, more people=more money.

 

Just my thoughts, was curios if a Daz dev/the communtiy had thoughts on it. 

Thank you !!!!
Exactly my thoughts.
After installing successfully at least for one, Deiffeomorphic on my machiene, turns out it was all for nothing with a new Blender release.
I want to render in Blender, but I just cannot do it. there is no easy bridge obviously.
I watched YT tutorials, telling me for 20 minutes how "easy" it is.  Sorry a 20 minutes tutorial viedeo is far from "easy".
Hey DAZ developers:
If we are caught in DAZ Studio, give us at least a better more photreal renderer, without complex material conversions by hand and replace dforce with something useful.
I am ready to pay some perpetual, ONLY! perpetual liscence money for that, of course.
BTW: same for HD tools.
Do not even think of paywall rentals.

Richard Haseltine said:

V8 Infinite said:

I tried the Alpha version yesterday just before it went into Beta, and the rendering speed is much faster, with much larger iteration packets (tested with an RTX 40 Series).

 

The only bug I encountered was with .obj imports; the rotation axis was incorrect.

I assume you are testing with an OBJ that was right before, otherwise it might just be that  the OBJ came from a different application.

Those things are controlled by options in the import options dialogue, that opens after selecting a file - they shouldn't have  changed spontaneously, but make sure that they make sense (choosing a different preset from the drop-down in the dialogue will also potentially change any of the settings, of course). 

It's fixed, thank you.

How deep? A really deep hole, or a right through the body hole, would probably best be handled with a Geometry Graft - essentially take the figure into a modeller, at base resolution and with no morphs or posing applied, then delete everything but the polygons around the area(s) to be effected. Don't touvh the edges or  vertices around the area, but you can do what you like within to do the base shape of the hole (don't go mad on detail at this stage) - the main issue will be that you will probably need to do fresh UVs for the new area. Once done you import that into DS, use the Transfer Utility to rig it, refine that as needed (with luck it will be OK as is), fit it to the base figure, then select the base figure and use the Geometry Editor to select the area of the figure that is to be replaced with the graft (everything you kept to being the modelling) then right-click>Geometry Assignment>Set AutoHide Faces for Grafts. When you switch to a regular posing tool the skin over the hole should vanish as long as the graft is fitted, you then have the little issue of texturing it. Not a trivial task, and possibly not a New User task depending on your basic skillset, but it is doable.

Masterstroke said:

WendyLuvsCatz said:

lilweep said:

isnt all that stuff free on quixel 

maybe its not free anymore,  but for me it's free since i claimed.

 https://quixel.com/megascans/collections?category=environment&category=urban

I was actually considering sharing that too since that is where I have seen and used it, in Twinmotion, Megascan assets are actually included to download in it too .

(free for me signed into my Epic account but possibly not for those who join now, I own every Unreal freebie they have given away the last 10 years I reckon)

but was too apprehensive it might not have been what Masterstroke was looking for

because again, I am not an architect 

It is now on FAB. Neoclassical modules, well at least something. One question though:
How do I make use of it in DAZ Studio? 

The steps would just be same process for importing any external mesh into daz.

1. Buy them all, assuming theyre not free for you.  (For me they are all still free and in my library but I dont know if thats true for everyone now)

2. Download them in whatever format.  If i look at my library, the formats are available as fbx, glb or gltf, but not obj (daz prefers obj).  You could try directly bringing fbx into daz, but my preference would be to convert to obj first before importing to daz to ensure everything works properly.

3. To convert to obj, I would use Blender. Simply Import the files and then export as obj.
Note that the file formats (fbx, gltf, glb) should load into Blender with textures/shaders set up so you could also use "Blender to DAZ" instead of obj.  Assuming this process works, it means you could skip the material set up step in Daz.

4. If you exported as obj, drag all exported obj files into Daz Studio viewport.

6. Drag  all texures into relevant channel of the Surfaces tab for each modular piece.  There are probably only 3 textures with these.

 - Base color - > base color

- Roughness - > Glossy Roughness (ensure Glossy Roughness value is set to 1.0, ensure Glossy Layer Weight is set to 1.0 or thereabouts)

- Normal -> Normal

- Ambient Occlusion (AO) -> Ignore this

7. Manually assemble all the modular pieces into buildings.  (or do this part in blender if you prefer blender controls)

New bi-weekly batch of “Limited-Time Free” from Fab (until Mar 24 at 9:59 AM ET).

• Abandoned Lighthouse Island – Modular Environment Pack. Unreal format.
• Ruined Modern Buildings Pack. Exterior structures. Unreal format.
• Probably hard to translate to Genesis type figures: Combat Magic Animations. Unreal format.

With Fab freebies, you can choose a Personal or Professional license. I always switch to the Professional license (since it’s free and gives you more).

Note that these are usually in Unreal or sometimes Unity, Godot, Blender, or generic 3D formats, so will require some work to convert for use in Daz.

I’m not aware of any tool for straight conversion from Unreal to Daz. so it takes a couple steps. First, convert from Unreal Engine to Blender format, then export/import between Blender and Daz. This article covers some ways of doing the conversion from Unreal to Blender: “Exporting from Unreal Engine to Godot, Unity or Blender”. Then from Blender to Daz, you can use one of the various tools, such as Diffeomorphic.

Please take discussion to the discussion thread. Let’s keep this thread “Announcements Only”, as it was intended.

V8 Infinite said:

I tried the Alpha version yesterday just before it went into Beta, and the rendering speed is much faster, with much larger iteration packets (tested with an RTX 40 Series).

 

The only bug I encountered was with .obj imports; the rotation axis was incorrect.

I assume you are testing with an OBJ that was right before, otherwise it might just be that  the OBJ came from a different application.

Those things are controlled by options in the import options dialogue, that opens after selecting a file - they shouldn't have  changed spontaneously, but make sure that they make sense (choosing a different preset from the drop-down in the dialogue will also potentially change any of the settings, of course). 

Not a really easy case... but I would like to show one of my ways by using helpers.

1) Create two primitives of Sphere and parent them to Left / Right hands so as to prevent the cloth from being penerated by fingers... (screenshot 1) 
2) Simulate with an animated range. (screenshot 2).  Select the Boho, export it to OBJ file. Clear the simulation result !
3) Import OBJ with Morph Loader Pro to the Boho. Dial the morph and hide two Spheres ! (screenshot 3)
4) Now Simulate with Current Frame ! Done ~ (screenshot 4)

I attached a Wearable Preset of two Spheres down below. You can load the helpers to the figure and give it a try if you'd like to ~~

Just a fyi I am a total newbie at this but basically I found some amazing assets in the renderosity site like Easy pants by Hameleon. It uses geoshells and I like the way it makes everything properly sit on the skin really nicely.

Now the problem is its a geoshell, and I want it to be a clothing item where I can use tools like fit control with morphs or create my own morphs if I ever need it. From googling, It told me to export the geoshell out as obj and then import it back in, and then use the transfer utility feature. I then try to fit to the genesis 8 female but the pants would no longer be aligned (it just moved away from the char ) and it doesn't seem to correctly react accordingly with different poses etc like normal clothing items. 

Is there a guide or any sort of resource anyone can provide me regarding this? Idk if I am missing some steps/settings but I would greatly appreciate it if anyone can help guide me on this. Thanks

The Brig said:

So how about from anyone else for whom it is a problem? Those folks being pretty much the target of the question, anyway.

The problem with all of this is that there are multiple issues.  The first is that your problem might be due to stuff out of Daz3d's control such as your own computer's performance and disk issues (I have had the rare mess up due to running out of RAM where a restall fixed it), the second is that you have tools to adjust the metadata to recatagorize products as you go, third, there are updates to fix metadata.  I think I would have you figure why so many things are in lost and found rather than using a hypothetical tool that would break updates for you.

Hi Samuel,

As far as I know, the Daz to 3ds Max bridge hasn’t received any major updates for the newer versions like 3ds Max 2024 or 2025 yet. The last public updates were mainly focused on compatibility with earlier Max versions and adding support for Genesis 8 / 8.1 characters, but development on the bridge seems to have slowed down quite a bit.

Some users are still able to use it with newer versions of 3ds Max by installing the bridge and then manually copying the plugin files into the newer Max plugin directories, but results can vary depending on the build.

If you’re mainly trying to bring Genesis characters into newer versions of Max, a common workaround is to export from Daz Studio using FBX and then import into 3ds Max. It’s not as seamless as the bridge, but it generally works reliably.

Hopefully Daz or the community picks up development again because continued support for newer 3ds Max versions and Genesis generations would definitely be helpful.

Hi,

I have this rigged bracelet which is fitted to G8F's right wrist.  I want to export the bracelet as a .obj prop.  It exports OK, but when I import the .obj file back into the scene, it appears at the scene origin.

I was hoping to leave the bracelet in its original scene position - oriented where G8F's right wrist would be.  Is this somehow possible?